Business lending teams and DSAs are among the heaviest buyers of GST-based prospecting data, and among the most likely to misuse it. The error is treating registration as a credit signal. A GSTIN issued last week tells you a business exists and has a PAN. It tells you nothing about revenue, repayment capacity or whether the business has traded at all — and for a lending product specifically, a day-one registration is close to the worst possible target, because there is nothing to underwrite.
This guide covers what GST data legitimately contributes to a lending motion, where the actual targets sit, and the compliance boundaries that matter more here than in almost any other segment.
What registration data can and cannot support
| Use | Supported? |
|---|---|
| Confirming a business entity exists | Yes |
| Verifying legal name and registered address | Yes |
| Confirming current registration status | Yes |
| Establishing entity type and structure | Yes |
| Identifying business vintage | Partly — registration date, not trading start |
| Estimating turnover | No |
| Assessing repayment capacity | No |
| Predicting default risk | No |
| Determining loan eligibility | No |
The line is clean: GST data is identity and existence infrastructure. It belongs in verification and in targeting. It does not belong anywhere in a credit decision, and using it as a proxy for financial health produces both bad lending and a conduct problem.
Return filing status is not a financial statement
Consistent GST return filing is a compliance-behaviour signal — a business filing on time is meeting an obligation. It is not turnover, not profit and not capacity to repay. Using filing regularity as a soft input to targeting is reasonable. Using it as an underwriting input is not, and it will not survive scrutiny.
Where the real targets are
If your product is working capital or a business loan, the newest cohorts are the wrong list.
| Registration age | Suitability | Why |
|---|---|---|
| 0–90 days | Poor | No trading history exists to assess |
| 3–12 months | Emerging | First working-capital gaps appear; some history exists |
| 1–3 years | Strongest | Real history, real constraints, still underserved by banks |
| 3+ years | Competitive | Established banking relationships to displace |
The 1–3 year band is where the MSME credit gap actually sits and where a DSA's economics work. Cohort structure and sequencing are in the outreach playbook.
There is a legitimate case for touching the 0–90 day cohort with a current account or banking relationship offer rather than credit — that is a genuinely day-one need, and it builds the relationship that makes the lending conversation possible twelve months later. But sell what they need now, not what you want to sell. That motion is a discipline of its own, covered in where current account leads come from and the cross-sell sequence that follows.
Combining registers for qualification
For companies and LLPs, joining GST to MCA changes what you can see. Extract the PAN from GSTIN positions 3–12 and join to MCA master data:
- Incorporation date — true corporate vintage, often earlier than GST registration.
- Authorised and paid-up capital — a rough scale indicator, not revenue.
- Directors and DINs — who signs, and their other directorships.
- Charges — registered security interests, which tell you who has already lent and against what. For a lending team this is the single most valuable MCA field.
- Filing status — corporate compliance behaviour.
The charge registry is the reason lending teams should not run on GST data alone. It shows existing secured exposure, which no GST field can. Full comparison in GST data vs MCA company data.
The constraint: proprietorships and partnerships have no MCA presence at all, and they are a large share of MSME borrowers. For that population, GST registration plus filing status is most of what public data offers, and everything else has to come from the applicant.
A targeting sequence
- Registration age 1–3 years. Filter first on the band where your product fits.
- Constitution. Proprietorship, partnership and private limited are different products, different documentation and different ticket sizes. Split them before writing any message.
- Nature of activity. Manufacturing, trading and services have different working-capital cycles. A trader's cash conversion gap is a different conversation from a manufacturer's capex.
- Status active, filing consistent. Basic hygiene, not a credit assessment.
- Join to MCA where applicable. Check charges before spending time.
- Verify status at the moment of contact — see the API guide.
The compliance boundary
Lending outreach in India sits under both data protection and telecom marketing rules, and financial services attract more complaints and more scrutiny than most categories.
- Registered senders and consent. Promotional calls and SMS require the registered-sender framework and respect for subscriber preferences. B2B is not a blanket exemption — a proprietor's mobile is a personal number. See the TRAI and DND guide.
- Purpose limitation. Data acquired for prospecting is not automatically available for other purposes. See the DPDP checklist.
- No implied endorsement. Holding GST-derived data does not associate you with any government body, and any suggestion of "government approved" or pre-approved status is false.
- No pre-approval claims. "Pre-approved loan" messaging to a prospect you have not assessed is a conduct problem independent of any data question.
- Documented provenance. In a regulated business, being able to state where every contact came from is not optional. Audit vendors with the data quality checklist.
Have your compliance function review the sourcing contract before the first campaign, not after the first complaint.
On sourcing: MCA-derived platforms — Probe42, Tofler, InstaFinancials — are the ones carrying the charge registry that matters most here. GST-based feeds such as FinScreener, built by the team publishing this site (see our disclosure), reach the unincorporated borrowers those platforms cannot see. Serious lending teams run both.
Measuring properly
| Metric | Why |
|---|---|
| Contact rate | Data quality |
| Qualification rate | Whether your filter matches your credit box |
| Application rate | Message and offer fit |
| Approval rate | Whether the targeting matches what you can actually fund |
| Cost per funded loan | The only number that matters |
| Complaint / opt-out rate | Regulatory early warning |
Approval rate by data segment is the diagnostic most DSA teams skip. High application volume with low approval means your targeting is pulling businesses your credit policy will reject — which burns rep time, annoys applicants and produces nothing. Fix the filter, not the pitch.
Common questions
Can I estimate turnover from GST data? Not from public registration data. Turnover is not published. Some products infer bands from other signals; treat any such estimate as a hypothesis and never as an underwriting input.
Is a composition-scheme taxpayer a good lending prospect? Composition is limited to smaller turnover by design, so ticket sizes are small. Suitability depends on your product economics — but the scheme itself tells you something useful about scale, which is more than most fields do.
How do I verify a borrower's GSTIN? Free on the official portal for single checks, or via API for volume. Procedure in finding company details from a GST number.
Can I use GST filing history in credit scoring? Filing behaviour is a compliance signal, not a financial one. Any use in a credit model is a decision for your risk and compliance functions, and should be validated rather than assumed. Nothing in this article is advice on that question.
Which data source is best for lending? GST for existence and the unincorporated population, MCA for corporate substance and existing charges, applicant-provided documents for anything financial. No public register substitutes for the third.