OneStream Transaction Matching for Finance Teams
If you are evaluating OneStream transaction matching, you are likely looking for a structured way to compare financial records, spot discrepancies, and keep reconciliation work audit-friendly. For many finance teams, the challenge is not just matching transactions once. It is building a repeatable workflow for bank reconciliation, payment reconciliation, settlement reconciliation, vendor reconciliation, and other recurring close processes.
Cointab is designed for that broader reconciliation need. It helps finance teams compare Side A records with Side B records, identify matched and unmatched transactions, review exceptions, and download audit-ready reconciliation reports.
What transaction matching means in finance
Transaction matching is the process of comparing two sets of records and determining which entries correspond to each other. In a finance workflow, that usually means matching your internal records against external reports received from banks, payment gateways, marketplaces, logistics partners, vendors, or other systems.
A typical reconciliation setup includes:
- Side A: your internal records, such as sales reports, books, ERP exports, or ledger data
- Side B: external records, such as bank statements, settlement files, payment gateway reports, or vendor statements
- Matching logic based on identifiers, amounts, dates, references, and business rules
- Exception handling for partial matches, open items, and skipped rows
- Reporting for review, audit, and follow-up
This approach is useful when the same reconciliation needs to be repeated every day, week, month, or period close.
How Cointab supports transaction matching
Cointab provides a structured reconciliation engine for finance teams that need more than a one-time spreadsheet comparison. Users can upload files, map fields, run reconciliation, and review the results in a clear workflow.
Core capabilities
| Capability | How it helps finance teams |
|---|---|
| Side A / Side B setup | Organizes internal and external records in a clear reconciliation model |
| Popular reconciliations | Supports pre-built workflows for standard partner reports |
| Custom reconciliations | Lets teams define their own business-specific reconciliation logic |
| Supporting data uploads | Helps enrich, merge, or prepare primary reports before reconciliation |
| Derived columns | Allows calculated fields to be created with AI-generated Excel-style formulas |
| Structured matching engine | Supports one-to-one, one-to-many, many-to-one, and net-to-net matching logic |
| AI-assisted open-item analysis | Helps review difficult unmatched items and possible reasons for differences |
| Manual match | Allows finance users to resolve exceptions that require human judgment |
| Audit-ready reports | Exports matched, partially matched, unmatched, and skipped records |
When a flexible reconciliation platform matters
Finance teams often need to reconcile more than one report type. A single process may include sales data, payment gateway files, bank statements, settlement reports, credit notes, refunds, fees, or delivery partner records. In these cases, rigid matching rules can slow the close process and create repeat manual work.
A flexible reconciliation platform is useful when you need to:
- Reconcile multiple data sources in the same workflow
- Reuse the same setup across future periods
- Handle partial matches, contra entries, and grouped transactions
- Review open items without losing audit trail visibility
- Automate recurring runs instead of rebuilding the process every month
- Keep matched, unmatched, and skipped transactions visible to the team
Cointab is built to support those needs with a reusable workflow that can be configured once and run again for future periods.
Popular reconciliations and custom workflows
Cointab supports two broad reconciliation patterns.
Popular reconciliations
Popular reconciliations are pre-built templates for common workflows where the report structure is generally standard. Examples include sales vs payment, marketplace vs settlement, bank vs books, and COD delivery partner reconciliation.
This approach is useful when finance teams work with recurring external reports and want a faster setup with consistent matching logic.
Custom reconciliations
Custom reconciliations are for business-specific workflows. Teams can define their own Side A and Side B reports, map key fields, upload multiple files, create derived columns, and apply matching rules based on their process.
This is useful for workflows such as:
- Internal sales report vs multiple payment gateway files
- ERP sales vs marketplace settlement
- Books vs bank statement
- Vendor ledger vs vendor statement
- Order report vs delivery partner report
Field mapping, supporting data, and derived columns
Reconciliation quality depends on clean inputs. Cointab lets users map important fields such as date, amount, and identifier columns. It also supports CSV, XLS, and XLSX uploads.
Users can also upload supporting data to prepare the main reconciliation files. This can help with lookups, merges, enrichment, or calculations before matching begins.
Examples include:
- Product master files
- Fee rate files
- Order metadata
- SKU mappings
- Customer or vendor masters
- Tax mapping files
- Delivery partner reference data
If a required value needs to be calculated, users can create derived columns. AI can help generate Excel-style formulas from plain-language instructions, which reduces manual formula building and keeps the workflow easier to maintain.
Matching logic and exception handling
Cointab's reconciliation engine is built to compare records using structured matching logic. It supports:
- One-to-one matching
- One-to-many matching
- Many-to-one matching
- Many-to-many matching
- Partial matching
- Contra matching
- Net-to-net comparison
Once structured rules are applied, open transactions can be analyzed further with AI support. This is helpful when references are inconsistent, descriptions are unstructured, or the matching logic needs business context.
Finance teams can then focus on the records that actually need review instead of checking every row manually.
The reconciliation report separates records into clear buckets:
- Fully matched
- Partially matched
- Unmatched
- Skipped
That visibility is important for month-end close, partner follow-up, and internal audit preparation.
Reporting, manual review, and reuse
After a reconciliation run is complete, users can review the report dashboard, filter transaction-level tables, inspect matched and unmatched items, and download the Excel report for internal review.
If the system or AI cannot confidently resolve a transaction, users can manually match records where the totals tally. This keeps the workflow practical for real finance operations, where some exceptions always need human judgment.
Cointab also supports missed file handling. If a required file arrives late, teams can upload it under the same reconciliation and refresh the report instead of rebuilding the setup.
That reuse is valuable for recurring finance processes because the same configuration can be used again for the next period with less setup effort.
Automation for recurring reconciliation
Once a reconciliation is configured, teams can automate input and output flows through email, SFTP, or API integrations. That means Cointab can fit into daily finance operations instead of acting only as a manual file upload tool.
Automation can support:
- Scheduled reconciliation runs
- Automated file receipt and validation
- Report generation after all required files are received
- Output delivery back to ERP, accounting, BI, or internal systems
- Dashboard visibility into when each run happened and what data was used
For finance teams handling regular transaction matching, this reduces repetitive work and helps keep reconciliation current.
Why finance teams evaluate alternatives
Teams often look for an alternative to rigid transaction matching tools when they need:
- A clearer Side A / Side B workflow
- Reusable reconciliation setup
- Better handling of unmatched and partially matched records
- AI support for formulas and open-item analysis
- Team-based workspaces with access control
- Audit-friendly reporting and history
Cointab is built around those requirements, with a focus on transparency, repeatability, and structured reconciliation rather than black-box matching.
Frequently asked questions
What is OneStream transaction matching used for?
OneStream transaction matching is generally used to compare financial records and identify differences across systems. Finance teams evaluate it when they need a structured reconciliation workflow for transaction matching and exception review.
Can Cointab handle custom reconciliation workflows?
Yes. Cointab supports custom reconciliations where teams define Side A and Side B reports, map fields, upload supporting data, create derived columns, and reuse the setup for future runs.
What happens to unmatched transactions?
Unmatched transactions stay visible in the reconciliation report so finance teams can review them, investigate missing files or data issues, and decide whether a manual match or follow-up action is needed.
Can reconciliation runs be automated?
Yes. Cointab supports recurring reconciliation workflows with data input and output automation through email, SFTP, and API-based integrations.
Does Cointab support audit-ready reporting?
Yes. Users can export reconciliation reports that include fully matched, partially matched, unmatched, and skipped records for review and audit support.
