Manual spreadsheet routine
- Formulas tied to column positions
- Copied helper columns and repeated filters
- Manually scan rows for exceptions
- Rebuild formulas when export layouts shift
- Hard to explain why a pair matched
LOCAL-FIRST RECONCILIATION
Compare spreadsheet exports. Find what doesn't match.
When exports from two systems disagree, find missing or changed records, review exceptions, and export a result you can check. You confirm the fields and rules.
From two exports to a decision you can explain
- Match what belongs together. Choose the record identifiers and comparison rules.
- Spot exceptions quickly. Inspect missing, changed, conflicting and invalid records.
- Keep a reviewable result. Check source values and export the results locally.
CSV, XLS and XLSX files · No direct system integration required · Source rows processed on your device
A simple workflow
Source A + Source BMapMatchReviewExport
See: Matched records · Changed records · Missing records · Conflicts · Invalid rows · Review before export
Inside the workflow
See matches, changes and missing records before you export.
Review result categories, available source values, differences and provenance together before export.
A clearer alternative to formula chains
Excel is useful for analysis. Reconciliation can get fragile as exports change.
With ReconLoom
- Map the fields you intend to compare
- Set explicit identity and comparison rules
- Classify results and surface exceptions for review
- Keep source provenance visible while investigating
- Export a reviewed result locally
Compare the exports you already have
One workspace for common reconciliation problems.
Use exports from the systems your team already relies on; direct bank, ERP, processor or warehouse connections are not required.
Bank ↔ Ledger
Find missing transactions and amount or date differences.
Payments ↔ Settlements
Compare processor payments with settlement records.
Ad spend ↔ Finance
Compare advertising exports with card, accounting or client billing files.
Old ERP ↔ New ERP
Validate before-and-after exports for missing or changed records.
ERP Inventory ↔ Warehouse
Compare exported quantities, statuses and locations.
Built for a result you can check
Four ways to understand the result.
Local-first
Your source data is processed on your device. Large workloads may use local browser storage.
Deterministic
Matching follows the configured rules. AI does not decide matches.
Explainable
Inspect result types, available source values, differences and source locations.
Human-reviewed
Ambiguous records stay unresolved for review before supported finalization and export.
Product integrity
See what the software decided — and what it left for you.
Same rules, consistent decisions
ReconLoom applies configured matching rules deterministically instead of inferring what a match should mean.
Ambiguous cases stay unresolved
Potential conflicts are not silently forced into a match. Review supported decisions before completing the workflow.
Review before export
Financial results must be finalized before export. Generic Record finalization records a reason and acknowledges unresolved exceptions when present.
How it works
From your source exports to a reviewed result.
- Import.Choose supported CSV, XLS or XLSX files for each source.
- Map.Review and confirm which fields and rules to compare.
- Match.Run explicit rules; ambiguous candidates are not guessed.
- Review.Inspect matches, changes, missing records, conflicts and invalid rows.
- Export.Finalize the applicable result and create a local CSV or XLSX report.
Plan limits
Limits depend on your access and device.
Free
Up to 10,000 rows total (5,000 per side)
2 files per side
Try Demo
Up to 100,000 rows total (50,000 per side)
2 files per side
Pro Trial
Up to 100,000 rows total (50,000 per side)
32 files per side
Paid Pro
Planned capacity: up to 10,000,000 rows total (5,000,000 per side)
32 files per side
CSV files support up to 500,000 rows per file; XLS/XLSX files support up to 50,000 rows per file. Large workloads may use local browser storage and depend on available device resources. Paid Pro is planned; checkout is not currently available, and final pricing has not been published.
Questions, answered
Know what to expect before you start.
Can I use my real data?
Reconciliation source files and rows are processed locally on your device. Large workloads and saved run details may use local browser storage. Trial verification, entitlement checks and limited analytics use network services when those features are used; see the Privacy Notice before use.
Are my source rows sent to ReconLoom?
Source rows and spreadsheet cells are not sent to ReconLoom services. Large workloads may use local browser storage. Trial verification, entitlement checks and limited analytics use network services when those features are used.
Does AI decide which records match?
No. Matching follows the fields and rules you configure. Ambiguous candidates remain available for review.
Does ReconLoom connect directly to my bank or ERP?
No. Choose the structured CSV, XLS or XLSX exports you want to compare.
How many rows can I compare?
Limits depend on your access, file format and device. See the plan limits above.
Ready to compare your files?
Compare your files for free.
Start with your own exports for free, or try Demo with sample data. Pro Trial is available where configured.
A practical business question
What will you investigate first?
A finance team can compare a bank export with ledger entries; a warehouse team can compare SKU quantities from two systems; and a migration team can check before-and-after customer records. ReconLoom works on exported files, not live system connections. These are examples, not testimonials or measured savings.
Try with synthetic sample exports or review the related workflow before using business-sensitive data.