Two sources are prepared and mapped independently.
Reconciliation for financial operations
Reconcile thousands of movements. Review only the exceptions.
DueHub Match prepares two independent inputs, combines operational rules with a solver, and leaves your team in final control of groups, exceptions, and exports.
- Separate A/B inputs
- Human review and decision record
- Visible complete or incomplete results
The engine evaluates combinations within the configured rules.
Exceptions and decisions remain visible to the team.
Visual demonstration
From raw movements to a clear review queue.
The flow keeps both sources visible and separates reconciled groups from rows that need intervention.
A Input A
Invoice 1842$ 12,480.00
Invoice 1843$ 8,230.00
Invoice 1844$ 2,150.00
Matching engineRules + solver
Result
Reconciled group1:1
Reconciled group1:N
Exception to review1
Reconciled Exception Rules-based engine
Less effort on repetitive work
Reconciliation should not hide the important decisions.
When movements arrive from different sources, manual work often results in duplicate spreadsheets, scattered rules, and little visibility into what remains pending.
DueHub Match structures the process: explicit rules, engine-based group selection, review of persisted results, and an exportable output to continue operations.
Operational process
Four steps to work with control.
- 01
Upload
Upload inputs A and B in CSV or XLSX as independent sources.
- 02
Map
Select the sheet, headers, and amount, date, and customer columns.
- 03
Run
Set rules, tolerances, and cardinalities before starting the process.
- 04
Review and export
Verify groups, address exceptions, and download available results.
MVP capabilities
Clear rules for more focused review.
1:1, 1:N, N:1 and N:N
Configure all four available cardinalities for each run. For N:N, the maximum row count applies to each side of the group.
Tolerances and rules
Apply amount and date tolerances, document criteria, and monthly grouping.
Reusable templates
Save compatible mappings and rules to prepare the next process with fewer steps.
History and review
Return to each run, review groups, and retain the record of decisions made.
Operational exports
Download available results in CSV or XLSX when the review is complete.
Two independent inputs
Work with A and B separately from upload, preview, and mapping through to the result.
Designed with explicit boundaries
Active organization, controlled access, and tenant-separated data.
Sessions and permissions. The application derives the active organization from the session and revalidates access in authenticated operations.
Isolated resources. Uploads, runs, templates, and results are queried within the active organization scope.
Operational traceability. History, review decisions, and run states remain linked to the process.
Current plans
Visible capacity, with no checkout or public pricing.
Limits are shown as they are currently defined for each organization. Plan changes are not part of this MVP.
Free
To validate the reconciliation flow with the team.
- 10 runs / month
- 1,000 rows per input
- 3 active members
Starter
For teams with recurring operations and more volume.
- 50 runs / month
- 5,000 rows per input
- 10 active members
Growth
For operations requiring greater processing capacity.
- 500 runs / month
- 10,000 rows per input
- 50 active members
Frequently asked questions
What matters before you begin.
What group types can I configure?
The public interface allows 1:1, 1:N, N:1, and N:N. For N:N, each side of the group needs at least two rows.
Does the engine always return a complete reconciliation?
No. A run can finish as incomplete, for example if the solver reaches a limit or does not obtain an optimal solution. That state is shown for team review.
Can I review results before exporting them?
Yes. Available groups can be approved or rejected, and unreconciled rows are shown for follow-up.
Which formats can I use?
Inputs accept CSV and XLSX. Available results can be exported as CSV or XLSX.
Start with a clear process