The Vendor Everyone Kept Reconciling Around: Why Invozen Scores Compliance Per Vendor, Not Per Invoice

Three Clean Closes That Weren’t

A supplier’s invoice goes missing from GSTR-2B in March. It gets chased down, resolved, filed. In June, a different invoice from the same supplier comes up short by a few thousand rupees. Also resolved. In September, another one’s missing entirely again. Also resolved.

Each month closes clean. Reconciliation for that period says so. Nobody ever opens the March result next to the June result next to the September result, because reconciliation is built to answer “did this period match,” not “does this vendor keep doing this.” By the time someone notices the pattern - usually because the amounts finally get big enough to notice - it’s not a five-minute fix anymore. It’s a vendor whose filing habits have been quietly costing you credit for two quarters.

Why Getting Every Period Clean Still Wasn’t Enough

Invoice-level reconciliation, done well, tells you exactly what’s wrong with a given invoice in a given month. That’s real signal, and it should keep existing - a missing invoice or a value mismatch still needs to get chased down and closed the month it appears.

What it can’t tell you is whether the invoice sitting in front of you is a one-off, or the fourth one this year from the same supplier. A single missing invoice from a vendor who’s otherwise spotless is worth a two-line email. A vendor who’s shown up short three periods out of the last six is a different conversation entirely - maybe their accountant is sloppy about filing on time, maybe they’re on the edge of losing GST registration, maybe it’s worth moving spend elsewhere before Q4. None of that is visible from inside a single period’s reconciliation, because nothing carries the history forward.

Going and rebuilding that history by hand means pulling every past reconciliation for a vendor and re-reading it end to end - exactly the kind of work that only happens after the problem has already gotten expensive enough to justify the digging.

What We Set Out to Build

We wanted vendor risk to be something the system already knew, not something you had to go reconstruct from old reconciliations when a supplier finally became a problem.

The vendor had to be the unit, not the invoice. Every purchase invoice from a supplier, across a rolling 3, 6, or 12-month window, needed to roll up into one view of that vendor - not eight separate reconciliation results you’d have to mentally stitch together.

A repeat problem had to look different from a one-off. One mismatched period is noise. Two or more, or a large enough rupee amount sitting at risk, is a pattern - and those two situations needed different colors, not the same generic “has issues” flag.

The exact kind of gap still had to travel with the vendor score, not get lost in it. Whether a period’s problem was an invoice missing from GSTR-2B, a value that didn’t match, a date that didn’t line up, or the vendor simply not showing up in GSTR-2B at all for that period - a reviewer opening a vendor’s record needed to see which of those it actually was, period by period.

It had to be something you could hand to someone else. A partner deciding whether to keep buying from a vendor, or a client asking why credit got blocked, shouldn’t require a walkthrough of the software - an export they can open in Excel and read on its own needed to exist.

How Invozen Actually Handles This

Every purchase invoice already reconciled against GSTR-2B feeds a per-vendor view, grouped by supplier GSTIN across whichever window you pick - the last 3, 6, or 12 return periods.
Each period in that window keeps its own result - clean, or an issue, broken down into invoices missing from GSTR-2B, value or date mismatches against what was matched, and periods where the vendor has purchases in your books but no GSTR-2B footprint at all.
The vendor gets one risk color for the whole window. Green means every period was clean. Amber means an isolated issue. Red means the same kind of gap has shown up in more than one period, or the rupee value sitting at risk has crossed a threshold worth escalating regardless of how many periods it spans.
You can filter straight to red or amber vendors instead of scanning every supplier you’ve ever bought from, and drill into any one of them to see exactly which periods and which invoices are driving the score.
The whole thing exports to Excel - a vendor summary, a period-by-period breakdown, and a full issue log - so a risk conversation with a partner or a client doesn’t require them to log into anything.

What This Means for You

A vendor who’s been fine for two years and slips once doesn’t get treated the same as one who’s slipped every other month since March. The system already knows the difference, because it’s carrying the history forward instead of starting over at zero every period.

It also changes what “reconciliation is done” means. Closing out this month’s mismatches was never the whole job - knowing which vendors keep generating them is the part that actually protects next quarter’s credit, and that’s the part that used to only surface once someone got curious enough to go digging.

If a Vendor’s Track Record Has Ever Surprised You at Filing Time

If a supplier’s pattern of missing or mismatched invoices only becomes visible once you’ve gone back and reread six months of old reconciliations by hand, that’s exactly the gap this was built to close. Book a 30-minute demo and we’ll show you a vendor’s compliance history across periods, scored the moment the data’s there.