GSTR-1 records invoices issued, not whether they were collected. That limitation shaped how we used invoice data in early pilots with NBFC partners. The data still offered evidence of buyer relationships and business activity that bank statement cash flow alone could not show.
Early pilots tested that view against portfolio data, with more nuanced results than expected. Some invoice signals were genuinely predictive; others proved noisy for this borrower segment. This account covers the findings and where the data did not support the original hypothesis.
Invoice Data Available for SME Credit Assessment
GST-registered businesses above specified turnover thresholds must file GSTR-1, an outward supply return listing invoices issued. For GST-registered borrowers, this creates a government-verified invoice record accessible through GSTN via a licensed GST Suvidha Provider.
GSTR-1 records invoice number, date, counterparty GSTIN, taxable value, and tax amount. It records invoices issued, not invoices collected, so it does not show payment status. It cannot identify which invoices were paid, partly paid, or outstanding. That limits its use in receivable aging analysis.
For receivable aging, bank statements are the stronger source because collections appear as inward credits. GSTR-1 shows revenue, while bank statements show collections. Together they support rough aging analysis when the borrower's GSTIN is the sole originating entity, the counterparty is GST-registered, and payment moves through the main bank account.
Invoice Signals That Proved Predictive
In early pilots with NBFC partners, covering several hundred applications across lending segments in Maharashtra and Gujarat, predictive invoice signals clustered in three areas.
Counterparty count and stability mattered. Borrowers invoicing five or more distinct counterparty GSTINs had meaningfully different default profiles from those reliant on one or two buyers. Concentration also mattered: when more than sixty percent of invoiced revenue came from one GSTIN, default risk was higher, likely because disruption in that relationship affected cash flow.
Invoice frequency relative to stated business type was useful. In sectors such as FMCG distribution and raw material supply, a sharp monthly decline was meaningful. A distributor issuing twenty-plus invoices monthly, then falling to three or four before applying, showed activity inconsistent with its stated business.
GSTR-1 to GSTR-3B reconciliation also warranted review. When GSTR-3B turnover was materially below aggregate GSTR-1 invoice value, the difference could reflect credit notes, returns, or a reporting mismatch. Persistent large gaps were relevant compliance signals in credit assessment.
Invoice Signals That Did Not Hold Up
Receivable aging alone performed poorly in this borrower segment. Because GSTR-1 shows invoices raised, not collected, aging was computable only for borrowers with clean bank-to-GSTR matching, and that subset was not representative. Elsewhere, missing data or uncertain estimates made the feature unreliable.
Invoice value trends also underperformed as an income proxy. Declining values were expected to signal a slowdown, but commodity prices and seasonal demand can change invoice amounts without indicating weaker business health. A produce distributor may show lower values in the lean season without higher default risk. Applying sector-specific calibration requires more pilot data than we currently have.
Invoice timing regularity was too variable across business types to form a clean signal. Retail distributors, service businesses, and project-based firms invoice on different cycles, including milestone schedules that appear irregular. Reliable timing features would need segment-specific baselines and more data per segment than the pilots supplied.
How Invoice Data Works with Bank Statement Signals
Our current approach uses invoice data mainly as context for bank statement cash-flow signals, not as standalone features. It helps distinguish business income from other inward credits, improving income estimates drawn from bank statements.
Bank statement inward credits may include business income, personal transfers, and financial transactions. Without outside context, identifying revenue requires heuristics. When GSTR-1 can be matched to bank statement timing, business income credits can be classified more precisely, improving cash-flow features instead of creating a separate invoice feature layer.
This shaped the current model: invoice data improves cash-flow computation rather than forming a separate feature set. In early pilots with 3 NBFC partners across a 90-day cohort, invoice-assisted income classification improved feature quality where both data types were available and reconcilable. Gains were negligible where GSTR-1 to bank reconciliation was poor.
Where Invoice Data Adds Value
For NBFCs offering invoice financing or supply chain lending, invoice data is core, not optional. In working capital loans for distribution businesses, counterparty diversification and invoice frequency directly inform repayment risk.
For general micro-business working capital loans, where overall cash flow rather than specific receivables is the collateral, invoice data supplements bank statement analysis. Use it when available and reconcilable, but do not block or materially downgrade assessment when it is absent. Bank statement cash-flow analysis remains the stronger primary signal.
Invoice data followed a familiar alternative-data path: early enthusiasm gave way to a clearer view of which features carry signal and under what conditions. That calibration process is necessary, making early pilot findings more useful than the assumptions that preceded them.
Assess borrowers in minutes
Saarathi's API connects to your loan origination system in one day and returns a scored credit file in three minutes.