High risk
2
Portal-only and GSTIN mismatch cases that need immediate follow-up.
Exception proof
Sample Mismatches
These examples show the exact kinds of issues a reviewer sees: missing invoices, duplicate rows, tax deltas, GSTIN mismatches, and portal-only entries.
A public gallery of the kinds of exceptions SaralKar isolates during reconciliation.
Minor review
2
Small tax or value deltas that can be cleared quickly.
Control issue
2
Duplicate or normalization-related exceptions to remove from the queue.
How the queue is sorted
SaralKar should not bury the critical cases under minor differences. Missing invoices, duplicate risk, and GSTIN mismatch sit near the top. Small amount differences stay visible, but they do not block the reviewer from moving on to the high-impact cases.
- High-risk exceptions first
- Minor differences grouped separately
- Recommended action shown for each row
- Reason codes visible in the report
What the reviewer needs
A reviewer needs enough context to decide quickly. That means the invoice number, the vendor, the reason, the filing impact, and the next action. These are the exact signals this gallery surfaces.
Downloadable sample files
Frequently asked questions
Are these examples realistic?
Yes. They mirror the kinds of data quality and portal timing issues GST teams deal with every month.
Do all mismatch rows need manual work?
No. Some are one-step cleanups, such as normalization or duplicate removal. Others need vendor follow-up.