Merchant and POS Reconciliation

Merchant and POS reconciliation helps finance teams compare sales captured at the point of sale with external records such as bank statements, payment gateway reports, settlement files, refund reports, and chargeback data. When these records do not align, teams need a structured way to identify differences, review exceptions, and keep financial records accurate.

Cointab provides a reusable reconciliation workflow for this process. Finance teams can upload files, map required fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped transactions in an audit-friendly report.

What merchant and POS reconciliation covers

Merchant and POS reconciliation is the process of matching internal sales or merchant records with external settlement and payment records. It is commonly used to confirm:

• Which sales transactions were paid successfully
• Which payments settled later than expected
• Which refunds, reversals, or chargebacks affected the final amount
• Which deductions, fees, or short settlements need review
• Which transactions are missing from one side of the reconciliation

For finance teams, the goal is not only to match transactions. It is also to understand why a record remains open, whether a file is missing, and what action is needed next.

Common challenges in merchant and POS reconciliation

Merchant and POS reconciliation often becomes time-consuming because the same transaction can appear differently across systems.

Common issues include:

• Different payment methods settle on different timelines
• Sale amounts in the merchant system do not always match received settlement amounts
• Refunds, chargebacks, and deductions create partial differences
• Reference numbers may appear in different formats across files
• Multi-store, multi-terminal, or multi-channel files are difficult to review manually
• Excel-based checks become harder to audit as transaction volume grows
• Exception handling varies when multiple team members work on the same process

These issues are especially common when finance teams manage multiple merchant accounts, payment channels, or settlement reports in the same period.

How Cointab handles merchant and POS reconciliation

Cointab uses a Side A and Side B reconciliation model.

• Side A is your internal record, such as POS sales, merchant ledger, order data, or books data.
• Side B is the external record, such as a bank statement, payment gateway report, merchant settlement report, refund file, or chargeback file.

1. Upload and map the source files

Users can upload CSV, XLS, or XLSX files for the required reports. For each primary report, they map the header row, date column, amount column, and one or more identifier columns.

Typical identifier fields include:

• Transaction ID
• Order ID
• Settlement ID
• Payment reference
• Bank UTR
• Invoice number
• Merchant reference
• Terminal or store reference

If a file does not match the configured format, Cointab can reject it with a clear error so the team knows exactly what needs to be corrected.

2. Add supporting data where needed

Some merchant reconciliation workflows need additional data before matching begins. Supporting data is optional and is used to enrich or prepare the primary reports.

Examples include:

• Product master files
• Order metadata
• Fee rate files
• Refund files
• Tax mapping files
• Store mapping files
• Delivery or service reference files

Supporting data can help teams complete lookups, merge reports, or calculate net amounts before running reconciliation.

3. Create derived columns with AI assistance

Cointab supports derived columns on both sides of the reconciliation. These are calculated fields built from existing data.

Finance users can describe the required logic in plain language, and AI can help generate an Excel-style formula.

Derived columns can be used for:

• Clean transaction references
• Net amount calculations
• Amount after fees
• Refund amount as negative
• Normalized identifiers
• Matching fields for grouped transactions

This is useful when the source files contain inconsistent formatting or when finance teams need to standardize values before matching.

4. Run structured matching

Cointab's reconciliation engine applies structured matching logic to compare records across sides.

It supports:

• One-to-one matching
• One-to-many matching
• Many-to-one matching
• Many-to-many matching
• Net-to-net comparison
• Contra matching
• Partial matching

The engine can compare identifiers using equality, contains, and subset-based logic. It can also work when one side has grouped records and the other side has individual transactions.

After structured matching is complete, AI can help analyze remaining open items where deterministic rules are not enough.

5. Review matched and open items

Once reconciliation is complete, users can review the report dashboard and filter transactions by status.

The report shows:

• Fully matched transactions
• Partially matched transactions
• Unmatched transactions
• Skipped transactions
• Manual matches

This gives finance teams a clear view of what was reconciled, what still needs review, and what was excluded from the run.

Typical merchant and POS reconciliation scenarios

Why finance teams use Cointab for this workflow

Merchant and POS reconciliation is often repeated every day, week, or month. A reusable workflow reduces repeated setup and makes the process easier to control.

Key benefits include:

• Reusable setup — configure the reconciliation once and run it again for future periods
• Better accuracy — use structured matching logic instead of manual spreadsheet checks
• Clear exception handling — focus on open items instead of reviewing every line manually
• Audit-ready output — download Excel reports with matched, partially matched, unmatched, and skipped records
• Team collaboration — work in a shared workspace with roles, permissions, and audit logs
• Flexible automation — receive files or send output through email, SFTP, or API integrations

Recurring reconciliation and automation

For merchant operations that run on a regular schedule, Cointab can support automated data input and scheduled reconciliation runs.

This means teams can set up the workflow once and then:

1. Receive files through email, SFTP, or API
2. Validate the incoming data
3. Load the files into the correct reconciliation
4. Run reconciliation automatically or on schedule
5. Review the resulting report in the dashboard
6. Push output back to internal systems if needed

This is especially useful for daily merchant settlements, recurring POS reconciliations, and month-end review cycles.

Handling exceptions and missed files

Merchant reconciliations often depend on late-arriving reports or corrected files. Cointab supports a practical finance workflow for these cases.

If a file is missed, users can upload it under the same reconciliation and refresh the report. Manual match is also available for transactions that need human review and confirmation.

This helps teams keep the reconciliation workflow moving without rebuilding the setup from scratch.

Merchant and POS reconciliation for finance teams

The value of this use case is not just transaction matching. It is operational control.

Finance teams need to know:

• Which records matched
• Which records were partially matched because of amount differences
• Which transactions are still open
• Which items were skipped and why
• What needs manual review
• Whether the same setup can be reused for the next period

Cointab is designed to make that workflow transparent, reviewable, and repeatable.

Frequently asked questions

What is merchant and POS reconciliation?

It is the process of matching internal sales or merchant records with external settlement, bank, gateway, refund, or chargeback records to verify that amounts and transaction references align.

Can Cointab handle refunds and chargebacks?

Yes. Refunds, chargebacks, reversals, and deductions can be included in the reconciliation workflow so finance teams can review differences in the final settlement.

Can the same reconciliation be reused for future periods?

Yes. Once a merchant or POS reconciliation is configured, it can be reused for later periods without rebuilding the workflow each time.

What happens when a transaction does not match?

Cointab separates the record into unmatched or partially matched status, and AI-assisted analysis can help identify possible reasons or next steps. Users can also manually match transactions when needed.