Transaction Reconciliation for Do it Best with Cointab
Cointab helps finance teams simplify transaction reconciliation when internal records need to be matched with external settlement, ERP, or partner data. For a business like Do it Best, where transaction accuracy affects reporting, operations, and period-end close, a structured reconciliation workflow reduces manual checking and makes exceptions easier to review.
Instead of rebuilding spreadsheets for every period, teams can upload files, map key fields once, run reconciliation, and review matched and unmatched transactions in a clear report. Cointab is designed to handle recurring finance workflows where records must be compared across systems and differences need to be explained quickly.
Why transaction reconciliation matters
High-volume businesses often manage transaction data across multiple systems. Internal records may come from ERP exports, sales reports, or ledger files, while external records may come from settlement reports or partner statements. When those records do not line up, finance teams need a reliable way to find the difference.
Manual reconciliation usually creates avoidable friction:
- Files are compared in Excel with formulas that are difficult to reuse or audit.
- Large datasets become harder to review line by line.
- Different team members may prepare exceptions differently.
- Underpayments, overpayments, missing entries, and canceled transactions can remain open longer than needed.
- Month-end close becomes slower because the same checks must be repeated for each period.
Cointab replaces that manual process with a repeatable workflow for transaction reconciliation and ERP reconciliation.
How Cointab structures the reconciliation
Cointab uses a Side A and Side B model so finance teams can clearly define what they expect to match.
Side A: your records
Side A contains the records the business expects to be correct. For a Do it Best-style workflow, this may include ERP exports, internal sales records, invoice data, or other source-of-truth files.
Side B: external records
Side B contains records received from external systems or partners. This may include settlement reports, vendor statements, bank data, or other third-party records.
Once the files are uploaded, the user maps key fields such as date, amount, and identifier columns. Identifier fields can include invoice number, transaction reference, order ID, settlement ID, or other business-specific values.
The reconciliation engine then compares the two sides using structured matching logic.
Common reconciliation scenarios
A transaction reconciliation workflow often needs to handle more than simple one-to-one matches. Cointab supports common finance scenarios such as:
- one-to-one matching
- one-to-many matching
- many-to-one matching
- many-to-many matching
- partial matching
- net-to-net matching
- contra matching
That matters when records do not line up cleanly across systems.
For example:
- A transaction appears in both the ERP report and the settlement file with the same reference and amount.
- A reference matches, but the amount differs because of fees, deductions, or adjustments.
- A record appears in one file but is missing from the other.
- Multiple transactions need to be grouped before they can be compared.
Cointab separates these outcomes clearly so finance teams know what matched and what still needs review.
What finance teams see after the run
After reconciliation is completed, users can review a report dashboard with transaction-level detail. The report typically includes:
- total summary
- fully matched transactions
- partially matched transactions
- unmatched transactions
- skipped records
- filters for deeper review
- transaction tables for each status
- downloadable Excel output
Fully matched
Fully matched records are transactions where the relevant identifiers and amounts match according to the configured logic.
Partially matched
Partially matched records are transactions where the identifiers relate to each other, but the amounts differ. These differences are important because they may indicate deductions, fees, timing differences, or data issues.
Unmatched
Unmatched records exist on one side but not the other. In a transaction reconciliation workflow, this could mean a record appears in the ERP system but not in the settlement file, or vice versa.
Skipped
Skipped records were not included in the reconciliation because they were excluded by rule, incomplete, invalid, or otherwise not usable. Keeping skipped records visible helps finance teams understand what was ignored and why.
Handling exceptions with more control
Reconciliation is not only about matching records. It is also about explaining exceptions.
Cointab helps finance teams focus on open items after the structured matching pass. AI can assist with difficult cases where identifiers are incomplete, descriptions are inconsistent, or the relationship between records is not obvious. If the evidence is weak, the transaction remains unmatched rather than being forced into a weak match.
Users can also perform manual matches when they know the business context and the totals tally. This is useful for one-off exceptions or cases where the source data is incomplete.
Reusable workflows for recurring periods
One of the biggest advantages of Cointab is reuse. Once a transaction reconciliation is configured, the same setup can be used again for future periods without rebuilding the workflow from scratch.
That makes it easier to reconcile recurring monthly, quarterly, yearly, or custom reporting periods. Finance teams can simply:
- Select the reconciliation.
- Choose the period.
- Upload the required files or receive them automatically.
- Run reconciliation.
- Review the report.
This reduces repetitive setup work and helps standardize the reconciliation process across periods and users.
Supporting data, formulas, and file validation
Not every workflow begins with perfectly prepared files. Cointab supports supporting data uploads for enrichment, lookup, and calculation before reconciliation begins.
Examples include:
- mapping files
- master data
- fee or rate files
- return reports
- customer or vendor reference files
- other supporting datasets used for lookup-style enrichment
Users can also create derived columns using AI-assisted formulas. This is helpful when the finance team knows the logic but does not want to build the formula manually.
File validation is also part of the workflow. If a file does not match the configured structure, the system can reject it with a clear error so the issue is easy to fix before the run proceeds.
Why this works well for finance operations
A transaction reconciliation process should give finance teams clarity, not just a match rate. Cointab is built to show what was matched, what was partially matched, what was unmatched, and what was skipped so the review process stays transparent.
That supports common finance needs such as:
- better control over transaction differences
- faster exception review
- cleaner period-end reporting
- audit-ready Excel exports
- reduced dependency on manual spreadsheets
- reusable setup for recurring work
For teams that manage ERP reconciliation, settlement reconciliation, or transaction matching across multiple files, the result is a more structured and reviewable workflow.
FAQ
Can Cointab handle ERP reconciliation and settlement reconciliation?
Yes. Cointab is designed to compare internal records with external records, so ERP reconciliation, settlement reconciliation, and other transaction matching workflows can be configured as either popular or custom reconciliations.
Does every reconciliation have to be rebuilt for the next period?
No. Once a reconciliation is configured, it can be reused for future periods. Teams can run the same workflow again by selecting the reconciliation, choosing the period, uploading the files, and reviewing the output.
What happens when records do not match exactly?
Cointab separates fully matched, partially matched, unmatched, and skipped records. This makes it easier for finance teams to focus on the exceptions that need review rather than checking every transaction manually.
Can users review and correct open items manually?
Yes. If the system and AI cannot confidently resolve an item, users can review it manually and create a manual match when the records and totals support it.
