Before you start
casparser version
1.1.0
Python version
3.14.2
CAS issuer
CAMS
CAS type (CAMS/KFintech only)
Detailed
What happened?
For CAMS/KFin detailed CAS PDFs containing multiple investors, each folio section identifies its holder using a name and PAN. Casparser extracts the PAN but does not retain the corresponding holder name.
investor_info.name represents the statement’s global addressee. It is not necessarily the holder of every folio. The Folio model has no holder-name field.
Impact:
- Applications cannot accurately associate investor names with PANs.
- Assigning investor_info.name to every folio incorrectly gives all PANs the same name.
- Nominee names under schemes[].nominees cannot be used because they are not folio holders.
- Downstream systems must either leave investor names blank or parse the PDF again duplicating the effort.
The parser should extract the holder name from each folio header and expose it as folios[].name or folios[].holder_name
Command or code used
NA - this is not a runtime issue, but an extraction issue
Full traceback / error output
Redacted sample (optional)
No response
Sharing a sample privately
Before you start
casparser version
1.1.0
Python version
3.14.2
CAS issuer
CAMS
CAS type (CAMS/KFintech only)
Detailed
What happened?
For CAMS/KFin detailed CAS PDFs containing multiple investors, each folio section identifies its holder using a name and PAN. Casparser extracts the PAN but does not retain the corresponding holder name.
investor_info.name represents the statement’s global addressee. It is not necessarily the holder of every folio. The Folio model has no holder-name field.
Impact:
The parser should extract the holder name from each folio header and expose it as folios[].name or folios[].holder_name
Command or code used
Full traceback / error output
Redacted sample (optional)
No response
Sharing a sample privately