Simplify Transaction Matching with Cointab’s Mapping Feature

Cointab’s mapping feature helps finance teams set up transaction matching in a structured, reusable way. Instead of comparing files manually in Excel, users define how Side A and Side B records should relate, map the required columns, and run reconciliation through a clear workflow.

The result is a more controlled process for matching sales, payments, settlements, bank entries, vendor statements, or other internal and external records. Finance teams can review fully matched, partially matched, unmatched, and skipped transactions in the same reconciliation report.

What the mapping feature does

The mapping feature defines how data from two sides should be compared during reconciliation.

• Side A is your internal or expected record set, such as sales, books, ERP exports, or ledgers.
• Side B is the external record set, such as payment gateway reports, bank statements, marketplace settlements, or vendor statements.

Mapping tells the system which columns to use for matching, such as:

• transaction date
• amount
• order ID
• invoice number
• settlement ID
• bank UTR
• payment reference
• AWB number
• customer or vendor code

Once configured, the same mapping can be reused for future reconciliation runs, reducing repeated setup work.

How mapping supports transaction matching

Cointab uses mapping as part of a broader reconciliation workflow. Users do not need to define every comparison from scratch each time. Instead, they configure the relationship between fields and let the engine apply structured matching logic.

Common matching patterns include:

This is useful when identifiers appear in different forms, when values need to be grouped, or when the reconciliation requires partial matching before the final review.

Setting up a reconciliation mapping

Cointab keeps the setup process practical for finance teams. A typical workflow looks like this:

1. Select a popular reconciliation or create a custom one.
2. Upload the required files for Side A and Side B.
3. Map the key fields, such as date, amount, and identifier columns.
4. Add supporting data if enrichment or lookup is needed.
5. Create derived columns if a cleaned or calculated field is required.
6. Save the configuration and run reconciliation.

For recurring processes, the same mapping setup can be used again in the next period. That makes it easier to handle monthly close, settlement reconciliation, payment reconciliation, or bank reconciliation without rebuilding logic every time.

Why finance teams use mapping instead of manual spreadsheet checks

Manual matching in spreadsheets can work for small files, but it becomes harder to manage as volumes grow or formats change. Mapping gives finance teams a clearer and more repeatable structure.

Better consistency

The same column definitions and matching logic are applied every time, which helps reduce variation between users and periods.

Faster setup for recurring reconciliations

Once a mapping is saved, the workflow can be reused for future runs. Users do not need to reconfigure the same relationship repeatedly.

Clearer exception handling

After the match run, the report separates records into matched, partially matched, unmatched, and skipped groups. This helps teams focus on exceptions instead of reviewing every row manually.

More audit-friendly output

Cointab produces downloadable Excel reconciliation reports, which help with internal review, audit preparation, and partner follow-up.

Mapping works with supporting data and derived columns

Not every reconciliation can be solved with the primary reports alone. Cointab supports optional supporting data and derived columns to make the matching process more complete.

Supporting data

Supporting data is not reconciled directly. It is used to enrich or prepare the primary reports before matching.

Examples include:

• product master files
• fee rate files
• order metadata
• return reports
• mapping files
• tax reference files
• customer or vendor master files

Derived columns

Users can also create calculated fields on either side of the reconciliation. These are useful when a raw column must be cleaned, combined, or transformed before matching.

Examples include:

• Clean Order ID
• Net Amount
• Normalized Transaction ID
• Refund Amount as Negative
• Amount After Fee
• Clean AWB Number

Derived columns can be created using AI-assisted formulas, which is helpful when the finance team knows the business rule but does not want to write the formula manually.

How the report reflects mapped transactions

After reconciliation runs, the report dashboard shows how the mapping performed across the uploaded files.

Users can review:

• total summary
• fully matched transactions
• partially matched transactions
• unmatched transactions
• skipped rows
• transaction-level tables
• filters for deeper analysis
• downloadable Excel output

This gives finance teams a clear view of what matched, what needs review, and what may require manual follow-up.

When manual matching is still useful

Even with structured mapping, some exceptions need human review. Cointab includes a manual match option for transactions that the system and AI cannot confidently match.

Manual matching is useful when:

• a partner file is incomplete
• a reference number is missing
• the same transaction is split across multiple rows
• a one-off exception needs to be resolved
• the business context is known by the finance team

Manual matches remain visible in the report, which helps preserve transparency and auditability.

Common reconciliation workflows that benefit from mapping

Cointab’s mapping feature supports a wide range of finance workflows, including:

• sales vs payment gateway reconciliation
• marketplace sales vs settlement reconciliation
• bank statement vs books reconciliation
• vendor statement vs vendor ledger reconciliation
• order report vs delivery partner reconciliation
• customer receivable vs customer statement reconciliation

These workflows often involve different file formats, repeated periods, and exceptions that do not fit a simple one-to-one comparison. Mapping helps create a repeatable reconciliation setup for those cases.

Mapping as part of a reusable finance workflow

The main value of the mapping feature is not just the initial setup. It is the ability to reuse that setup for future periods, teams, and recurring reconciliation cycles.

Finance teams can:

• configure the reconciliation once
• reuse the mapping for future files
• run reconciliation manually or on schedule
• review open items in the dashboard
• refresh the report if a missed file is uploaded later
• keep the workflow available for future reference

That makes the feature useful for both periodic close work and recurring operational reconciliation.

Frequently asked questions

What is Cointab’s mapping feature used for?

It is used to define how Side A and Side B records should be matched during reconciliation. Finance teams use it to compare transaction data across internal and external reports in a repeatable way.

Can the mapping feature handle complex matching?

Yes. Cointab supports one-to-one, one-to-many, many-to-one, many-to-many, net-to-net, and contra matching scenarios where a simple row-by-row comparison is not enough.

Can the same mapping be reused later?

Yes. Once a reconciliation is configured, the mapping setup can be reused for future periods so teams do not need to rebuild the workflow every time.

Does mapping work with supporting files?

Yes. Supporting data can be uploaded to enrich or prepare the primary reconciliation files before matching begins.

What happens to unmatched transactions?

Unmatched records remain visible in the report so users can review them, investigate missing files or mismatched values, and handle exceptions manually if needed.