Demat Statement Reconciliation for Holdings, Trades, and Fees

Demat statement reconciliation helps finance and investment operations teams match internal records with external statements across trades, holdings, corporate actions, dividends, and charges. It is useful when transaction data is spread across broker statements, depository files, portfolio reports, and internal books.

Cointab turns that work into a structured reconciliation workflow. Teams can upload files, map fields once, run reconciliation, review exceptions, and download audit-ready reports. The same setup can be reused for future periods, which reduces repetitive spreadsheet work and keeps the process consistent.

What demat statement reconciliation covers

A demat reconciliation process typically compares two sides of data:

• Side A: your internal records, such as trade logs, portfolio working papers, holdings reports, or books data
• Side B: external records, such as demat statements, broker statements, depository files, dividend records, or fee statements

The goal is to identify which records are fully matched, partially matched, unmatched, skipped, or manually resolved. That gives finance teams a clearer view of where balances, transactions, or statement entries need review.

Common items included in a demat reconciliation workflow are:

• buy and sell transactions
• opening and closing holdings
• corporate actions such as bonus issues, splits, and rights issues
• dividend receipts
• demat or brokerage fees
• settlement differences
• reference or identifier mismatches

Why manual reconciliation becomes difficult

Demat-related data often arrives in multiple formats and at different times. Teams may still compare files in Excel, use formulas, or maintain separate working sheets for each period. That can create avoidable work and inconsistent results.

Typical challenges include:

1. Multiple source files
   Trade data, holdings data, dividend entries, and fee statements may all need to be reviewed together.

2. Different identifiers across systems
   The same transaction may appear with different reference numbers, descriptions, or posting dates.

3. Corporate actions and adjustments
   Bonus shares, splits, and other events can change the expected quantity or value of holdings.

4. Partial differences
   A trade may match by reference but differ slightly in amount because of fees, rounding, or settlement timing.

5. Late or missing files
   A demat or broker statement may arrive after the first review, requiring the report to be refreshed.

6. Repeat work every period
   The same reconciliation structure is often rebuilt month after month.

How Cointab structures demat reconciliation

Cointab uses a finance-friendly reconciliation flow that keeps the setup clear and auditable.

1) Upload files on Side A and Side B

Users upload CSV, XLS, or XLSX files and define the required columns, such as:

• date
• amount
• quantity
• identifier or reference fields

For a demat workflow, identifier fields may include order IDs, trade references, settlement numbers, transaction IDs, ISINs, folio numbers, or any business-specific reference used in the records.

2) Map the fields once

Teams map the columns needed for reconciliation and reuse that setup later. If the source file structure stays the same, future runs are faster and more consistent.

3) Add supporting data where needed

Supporting data can help enrich the primary files before reconciliation. Examples include:

• portfolio master data
• instrument mapping files
• fee rate files
• dividend reference data
• corporate action support files
• internal working sheets used for lookups or merges

Supporting data is not reconciled directly. It is used to prepare the main records for matching.

4) Create derived columns if required

If a field needs to be normalized or calculated, users can create derived columns on either side. AI can help generate Excel-style formulas from plain-language instructions.

Examples:

• clean transaction reference
• adjusted holding quantity
• net amount after charges
• normalized instrument code
• dividend amount after tax or fee adjustments

5) Run reconciliation

After the files are loaded, Cointab performs structured matching across the two sides. The engine can compare records in multiple ways, including one-to-one, one-to-many, many-to-one, and grouped comparisons.

When simple matching rules are not enough, AI can help analyze difficult open items. It can suggest likely reasons for differences, while keeping the result conservative and reviewable.

What the reconciliation report shows

Once the run is complete, finance teams can review the report dashboard and work through exceptions efficiently.

The output includes:

• total summary
• fully matched records
• partially matched records
• unmatched records
• skipped records
• transaction-level tables
• filters for deeper review
• detailed matched views
• downloadable Excel reports

This helps teams focus on exceptions rather than scanning every row manually.

Fully matched records

These are entries where the identifier and amount, or other configured logic, align as expected.

Partially matched records

These are records that are related but do not fully match. For example, a transaction reference may align while the amount differs because of a fee, rounding difference, or posting adjustment.

Unmatched records

These are records found on one side but not the other. In a demat workflow, that could mean a holding, trade, dividend, or fee entry that needs follow-up.

Skipped records

Skipped rows are excluded from the reconciliation because of missing data, invalid values, duplicates, or file issues. They remain visible so the team understands what was not included and why.

Common demat reconciliation scenarios

Cointab can support demat-related reconciliation as a flexible custom workflow. Typical examples include:

• internal trade report vs broker statement
• portfolio holdings report vs demat statement
• dividend working vs bank receipt records
• fee or charge report vs broker fee statement
• corporate action tracker vs updated holdings
• internal investment ledger vs external statement data

The same platform can also be reused for other finance reconciliation work, such as bank reconciliation, vendor reconciliation, payment reconciliation, and settlement reconciliation.

Why finance teams use a structured reconciliation workflow

A reusable reconciliation setup gives finance teams more control over the process.

Benefits include:

• less manual spreadsheet handling
• consistent matching logic across periods
• clearer exception review
• easier handoff between team members
• audit-ready output for internal review
• faster refresh when a missed file arrives later
• a shared workspace for finance and operations teams

Because the setup can be reused, teams do not need to rebuild the same logic every month or quarter. They can simply select the reconciliation, choose the period, upload the files, and run the process again.

Automation for recurring demat reconciliation

For repeat workflows, Cointab can support automated data input and scheduled reconciliation runs through email, SFTP, or API-based flows. That makes it easier to keep reports current without depending on manual uploads every time.

After reconciliation is completed, output can also be pushed back to downstream systems such as accounting, ERP, BI, or internal reporting workflows through email, SFTP, or API.

Practical result for finance teams

Demat statement reconciliation is not just about comparing two files. It is about creating a repeatable process for matching investment-related records, reviewing differences, and keeping reporting ready for finance, audit, and operational follow-up.

With a structured workflow, teams can see what matched, what did not match, what was skipped, and what still needs attention.

FAQs

What can be reconciled in a demat statement workflow?

A demat workflow can reconcile trades, holdings, dividends, charges, settlement entries, and corporate action-related records between internal and external statements.

Can Cointab handle custom demat file formats?

Yes. Users can define the required columns, map the fields, and reuse the setup for future runs as long as the file structure follows the configured format.

Can supporting files be used in the reconciliation process?

Yes. Supporting data can be uploaded to enrich or prepare the primary records before reconciliation. It is useful for lookups, merges, calculations, and reference mapping.

What happens if a statement file arrives late?

The missed file can be uploaded under the same reconciliation and the report can be refreshed, which helps teams handle delayed external statements without rebuilding the workflow.

Can partially matched items be reviewed separately?

Yes. Partially matched, unmatched, and skipped records are separated in the report so finance teams can review exceptions and resolve them in a structured way.