Invoices cleared with exact or tolerance-based matching.
Demo Reconciliation
This page shows the workflow users actually care about: upload both files, map columns, inspect mismatches, and export a review-ready report without creating an account.
A public sample run built to show the exact reconciliations SaralKar performs on books-side and portal-side GST data.
Rows moved to review because of missing, duplicate, or value-delta issues.
Representative reconciliation runtime on a 284-row sample file.
What SaralKar does in this run
The system aligns invoice numbers, GSTINs, taxable values, and tax components. Exact matches move straight through. Rows with small deltas land in a minor-difference bucket. Missing invoices and portal-only rows become actionable exceptions.
- Purchase register normalization before matching
- Books-only and portal-only separation
- Duplicate-aware review queue
- Export-ready summary for filing and review
What the reviewer sees
Reviewers do not need to inspect every row. They see the match summary, the exception queue, the reason code, and the recommended action. That is the conversion story as well as the product story.
- Matched rows with confidence
- Minor differences with reason codes
- Missing invoices flagged by vendor
- Downloadable reconciliation output
Frequently asked questions
Do I need to upload a live file to understand the workflow?
No. This sample shows the structure, the matching logic, and the output format before you start a real reconciliation.
What data is shown in the sample?
Representative purchase register rows, GSTR-2B rows, mismatch examples, and a report summary with realistic amounts and statuses.