Reconciliation Processes Built for Finance Teams

Cointab helps finance teams streamline reconciliation processes across internal records and external records. Instead of rebuilding spreadsheets for every period, teams can upload files, map key fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped transactions in a structured report.

The platform is designed for recurring finance work where accuracy, control, and auditability matter. It supports popular reconciliation templates as well as custom workflows, so teams can compare bank statements, payment gateway reports, marketplace settlements, vendor statements, ERP exports, and other operational data without relying on repeated manual checks.

What reconciliation processes look like in Cointab

Cointab uses a Side A and Side B model.

• Side A contains your records, such as sales reports, books data, ERP exports, internal order reports, or receivable and payable ledgers.
• Side B contains external records from banks, payment gateways, marketplaces, logistics partners, vendors, customers, or tax and settlement systems.

A reconciliation process begins when the user uploads or receives both sides of the data. The user then maps required fields such as date, amount, and reference identifiers. After that, Cointab applies structured matching logic to identify what matches, what only partially matches, what remains open, and what should be skipped.

Popular reconciliation processes

Cointab supports common finance workflows that many teams repeat every month, week, or day.

Bank reconciliation

Match bank statements with books or ledger data to identify receipts, payments, missing entries, and timing differences.

Payment reconciliation

Compare internal sales or order data with payment gateway reports to identify paid, unpaid, underpaid, overpaid, refunded, or unmatched transactions.

Settlement reconciliation

Reconcile marketplace or payment settlements against internal records to review deductions, fees, returns, refunds, and payout differences.

ERP reconciliation

Compare ERP exports with other financial or operational reports so accounting teams can validate invoices, postings, and transaction records.

Vendor reconciliation

Match vendor statements with vendor ledger entries, invoices, and payments to review open balances and exceptions.

Customer reconciliation

Compare receivables, statements, or payment records to identify outstanding, delayed, or disputed items.

COD and delivery partner reconciliation

Match cash-on-delivery order data with delivery partner remittance reports to identify missing remittances or amount differences.

Refund and chargeback reconciliation

Review refunds, reversals, and chargebacks against original sales or payment records so finance teams can understand what was reversed and why.

Custom reconciliation workflows

Not every business uses the same report structure. Cointab also supports custom reconciliation workflows for cases where the business needs to compare its own internal records against external files from multiple sources.

Examples include:

• Internal sales report vs multiple payment gateway reports
• ERP sales vs marketplace settlement
• Books vs bank statement
• Vendor ledger vs vendor statement
• Order report vs delivery partner reports

In a custom workflow, users can define Side A and Side B, upload multiple files on both sides, and configure the matching logic around identifiers, amounts, and grouping rules. This makes the reconciliation setup reusable for future periods.

How the reconciliation workflow runs

A typical reconciliation process in Cointab follows a clear sequence:

1. The user signs in to a team workspace.
2. The user starts a new reconciliation.
3. The user selects a popular reconciliation or creates a custom one.
4. The user uploads files on Side A and Side B, or configures automated data input.
5. The user maps required fields such as date, amount, and reference columns.
6. The user can upload supporting data for lookups, merging, enrichment, or calculations.
7. The user can create derived columns using AI-generated Excel-style formulas.
8. The user runs reconciliation manually or schedules it to run automatically.
9. Cointab performs structured matching across the uploaded data.
10. Remaining open items can be reviewed with AI assistance when rules are not enough.
11. The user reviews the reconciliation report and filters records by status.
12. The user can download the Excel report for internal review, audit, or follow-up.

What the report shows

Cointab separates the output into clear transaction states so finance teams can focus on exceptions instead of reviewing every row manually.

Fully matched

These are transactions where the identifiers and amounts match according to the configured reconciliation logic.

Partially matched

These are transactions where the records are related, but the amounts do not match exactly. Partial matches are useful for spotting deductions, fees, short payments, rounding differences, or other exceptions.

Unmatched

These are records present on one side but not found on the other side. They often point to missing files, timing gaps, partner issues, or internal posting differences.

Skipped

These are rows excluded from reconciliation because of missing required data, invalid values, duplicates, or other file issues. Skipped records remain visible so the user understands what was ignored and why.

Supporting data, derived columns, and AI assistance

Many reconciliation processes need more than a direct file-to-file comparison. Cointab supports optional supporting data to help prepare the main files before reconciliation.

Examples of supporting data include:

• Product master
• Fee rate file
• Return report
• Order metadata
• Mapping files
• Tax or GST reference data
• Delivery partner reference files

Teams can also create derived columns on both sides. These are calculated fields built from existing data, such as clean order IDs, net amounts, normalized references, or amount-after-fee values.

AI can help generate Excel-style formulas from natural-language instructions, which reduces manual formula writing while keeping the logic reviewable.

After structured matching is complete, AI can also help analyze difficult open items and suggest possible reasons or actions. If the evidence is weak, the transaction remains unmatched rather than being forced into a match.

Why finance teams reuse reconciliation processes

Reusable reconciliation processes help teams reduce repeat work and keep month-end close more consistent.

Instead of rebuilding the same setup every period, finance teams can:

• Select an existing reconciliation
• Choose the period
• Upload the required files
• Run reconciliation
• Review the report

This reuse matters when the same workflow is needed for monthly bank reconciliation, daily payment reconciliation, recurring marketplace settlement checks, or vendor and customer follow-ups.

Automation for recurring finance operations

Once a reconciliation process is configured, Cointab can support recurring data flow through email, SFTP, or API-based automation. That means the system can receive or pull files, validate the format, run the reconciliation, and prepare the output on a schedule.

This is useful for finance teams that want reconciliation to become part of daily operations instead of a one-time spreadsheet exercise.

Cointab can also deliver reconciliation output back to other systems through email, SFTP, or API, making it easier to keep downstream accounting, reporting, or operations workflows updated.

Team workspaces and audit readiness

Cointab supports team-based workspaces so finance teams can work from one shared environment instead of passing Excel files around. Multiple users can collaborate with roles, permissions, and shared reconciliation history.

That shared structure helps teams maintain a clearer audit trail, keep report history available for future reference, and reduce confusion over who ran which reconciliation and when.

When reconciliation files arrive late

In real finance operations, files do not always arrive at the same time. If a file was missed, users can upload it under the same reconciliation and refresh the report. That makes it easier to handle late reports from banks, marketplaces, payment gateways, or delivery partners without rebuilding the process from scratch.

Common outcomes of a strong reconciliation process

A well-structured reconciliation process helps finance teams:

• Reduce manual Excel work
• Review discrepancies faster
• Keep reports consistent across periods
• Improve visibility into open items
• Support month-end and audit preparation
• Reuse the same workflow for recurring reconciliation runs

The result is a more controlled reconciliation process with clearer matching logic, easier exception handling, and reports that are ready for internal review and follow-up.