How ReconLoom works
Import Excel or CSV exports, confirm the fields and rules that matter, run deterministic reconciliation, review matches and exceptions, and export a result you can explain.
A reviewable workflow
Select a step to see what happens. The explanations are part of this page and remain available without JavaScript.
Choose CSV, XLS or XLSX exports from each source. ReconLoom inspects the files locally; it does not connect directly to source systems.
Review and confirm the fields and rules that define your comparison. Suggestions do not confirm mappings for you.
ReconLoom applies the configured rules deterministically. It does not use AI to decide which records match.
Inspect the result categories, available source values, differences, provenance and unresolved cases supported by the workflow.
Record supported review decisions, complete the applicable finalization step, then export a local CSV or XLSX report. Financial and Generic Record have different finalization rules.
Inside the result
Inspect result categories, available source values, differences, source provenance and unresolved exceptions together.
Two workflows, one product
For transaction-style comparisons such as bank and ledger, payments and settlements, or advertising spend and finance exports.
Confirm reference fields, amount, currency, date, sign conventions and supported tolerances. Optional group matching is available where eligible.
For structured records such as old and new ERP exports, inventory and warehouse files, or other tabular datasets.
Define typed identity fields and select comparison fields to inspect exact matches, changes, one-sided records and exceptions.
Result guide
Open a result to see how to interpret it. Categories depend on the workflow and confirmed rules.
Records satisfy the configured matching rules.
In Generic Record, records share the configured identity but differ in one or more selected comparison fields.
A record appears on one side without a corresponding record found on the other.
Multiple or incompatible candidates prevent a single supported result.
A row cannot be reconciled with the configured field or type requirements.
Ambiguous records and supported exceptions remain open for your decision. Financial and Generic Record workflows have different review outcomes.
Built for a result you can check
Reconciliation source files and rows are processed on your device. Large workloads may use local browser storage.
Matching follows the fields and rules you confirm. AI does not decide matches.
Inspect available values, differences, result categories and source provenance.
Ambiguous records remain open for review instead of being silently forced into a match.
Work with the exports you have
Compare bank transactions with accounting ledger records.
Investigate differences between processor and settlement exports.
Compare exported advertising costs with finance or billing records.
Validate before-and-after structured exports.
Compare structured inventory records and investigate discrepancies.
Current access
Available now for your own files.
Available now with sample data.
Available where configured.
Checkout coming soon; not currently purchasable.
Product questions
ReconLoom supports structured CSV, XLS and XLSX exports.
Reconciliation source files and rows are processed locally on your device. Large workloads may use local browser storage. Trial, entitlement and privacy-safe analytics metadata may use network services.
No. Matching follows the fields and rules you confirm.
No. You choose and export the structured files you want to compare; ReconLoom does not directly connect to banks or ERPs.
Financial is for transaction-style comparisons with amount, currency, date and reference rules. Generic Record is for structured records with typed identity fields and selected comparison fields.
Ready to get started?
Start with your own files for free, or open Demo to see the workflow using sample data.
A practical business question
Confirm the record identity and compared fields before matching. Inspect which source values were available, why records were classified, and what still needs human review. An export reflects the configured comparison, not a guarantee that the underlying records are correct.
Try with synthetic sample exports or review the related workflow before using business-sensitive data.