1
PAN verification
- Validity of the PAN
- Holder name as registered
- Holder category — individual, company, firm, trust and so on
Back to Add-Ons
India Compliance VerificationFree to installRequires a Yashvan account
India Compliance Verification for Dynamics 365 Business Central
Verify a vendor's PAN, GST and Udyam registration without leaving Business Central, and know whether the MSME payment clock is running before you post the invoice.
Available on Microsoft AppSource for Business Central 28 or later with Microsoft's India localisation. Published by SS Dynamics Solutions Pvt. Ltd.
Why this matters
Two rules make MSME status a finance problem
Under the MSMED Act, 2006, a buyer must pay a registered micro or small enterprise on the date agreed in writing, and in any case within 45 days of acceptance. Where there is no written agreement, the limit is 15 days. A contract specifying 30 days makes 30 the operative limit, not 45. Payment beyond the applicable limit attracts interest under the Act.
Under India's income-tax rule for payments to micro and small enterprises (introduced in 2023 as section 43B(h)), an amount still outstanding to a micro or small supplier beyond that limit is not deductible in the year it was incurred. The deduction moves to the year of actual payment — which lands as a tax cost in the year you can least plan for it.
The hard part
Knowing the answer at the moment you post
Neither rule is hard to follow. The hard part is knowing, at the moment a purchase invoice is entered, whether this particular vendor is a registered micro or small enterprise — and whether the PAN and GSTIN on the vendor card are even correct.
That answer usually lives outside the ERP: a spreadsheet someone maintains, a declaration collected at onboarding two years ago, or a portal someone checks when there is time. This app puts the answer on the vendor record, sourced from official government records, with the date it was verified.
This section is factual background on the statutory position and is not legal or tax advice.
What gets verified
Four verifications, run from the vendor record or on a schedule
Every result is written back onto the vendor and stamped with the date it was verified.
2
MSME by PAN
- The Udyam registration number behind a PAN
- Where the source returns the number alone, a follow-up call completes the profile
- Udyam registration certificate as a PDF
3
MSME by Udyam
- Enterprise type — micro, small or medium
- Major activity and organisation type
- Classification year and date, and date of registration
- Udyam registration certificate as a PDF
4
GST taxpayer status
- Registration status
- Legal name and trade name
- Registration date
- Principal place of business
Plus the Udyam certificate
Both MSME verifications return the registration certificate as a PDF, attached to the vendor record. Certificate retrieval is built into the MSME call, not a separate one.
Vendors are classified automatically as Micro, Small or Medium from the Udyam response, so the classification is available for filtering, reporting and the payment-term logic below.
The GST check does double duty
Alongside the registration status it returns the legal name, trade name and principal place of business — so you can populate a new vendor's address from the GSTIN, or reconcile what is already on the card against what is registered. Vendor master hygiene, without the retyping.
Results are sourced from official government records through the Yashvan verification API. Live data, not a cached list.
Payment terms
MSME payment terms and the delay report
Once a vendor is classified, the MSME flag and the payment due date flow from the vendor to the purchase header, then on to the general journal line and the vendor ledger entry — so the obligation stays visible from order through to payment, not just at the moment of data entry.
The due date follows your contract, capped by statute
The agreed term is the vendor's standard Business Central payment terms — an existing field, not a parallel one to maintain. The app applies the MSMED Act limit where that term exceeds it, or where none is recorded. The statutory limits are configurable in setup, so a change in the law is a setup change rather than an upgrade.
When the due date is breached, the app raises a warning
It does not block posting. The decision stays with your team; the app makes sure nobody makes it unknowingly.
The delay report
Lists overdue payables to MSME vendors with interest computed on each. The interest rate is one you define — the app applies arithmetic to your parameters and takes no view on the statutory rate that should apply to your contracts.
The report is for reporting and review. No interest entries are posted to the ledger. What you do with the figures, and how you account for them, remains your decision and your auditor's.
How it works
Inside Business Central
On the Vendor card
Verify actions for PAN, MSME and GST, plus one-click download of the Udyam certificate. Results are written to named fields on the vendor with the verification date against each, so anyone opening the record can see both the answer and how old it is.
On a schedule
A job queue entry re-verifies vendors matching a filter you define. The filter is how you control both scope and cost — a wide filter across a large vendor master consumes credits in proportion, so scope it deliberately.
Certificates stay with you
The Udyam certificate is stored as a standard Document Attachment on the vendor record, inside your own tenant, under your own retention policy.
Every call is logged
The in-product API log records each call with its trace id, the product checked, credits debited and balance remaining — so a disputed result or an unexpected balance can be traced to the call that caused it.
One setup page
Paste your API key on the IN Compliance Setup page. The connection is checked straight away, and the page shows your credit balance and entitlement expiry.
Security
Security and data handling
Only the identifier being checked is sent
When you run a verification, the extension sends the PAN, Udyam registration number or GSTIN being checked, with related request details and your API key. No vendor names, addresses, contacts, transactions or documents leave your tenant.
Where they go
The identifiers are sent over TLS to the verification service you subscribe to, which is governed by its own terms and privacy policy. Results and the request log stay in your Business Central tenant.
Your API key is held in Isolated Storage
Business Central holds the key as a secret, scoped per company. It is never written to a table field and never displayed back.
One outbound destination
The extension communicates only with api.yashvan.com. It holds no credentials for any upstream data source, so there is nothing in your tenant that could be used to reach one.
Telemetry is designed to carry no vendor data
The extension sends technical telemetry — feature usage, performance and errors — to SS Dynamics, to support and improve the extension. It is designed not to include vendor identifiers or verification results. The API log stays inside your Business Central tenant.
Everything stays in your tenant
Verification results, the Udyam certificate and the API log are written into your own Business Central tenant, on the Microsoft Azure infrastructure that already hosts it. SS Dynamics has no access to them.
What you need
The Business Central app is free to install from Microsoft AppSource. A Yashvan account is required to use it. Verifications are paid for with credits, and an annual Integration entitlement unlocks API access for ERP use. Credits are consumed only on a successful result.
Prerequisites
- Microsoft Dynamics 365 Business Central online, version 28 or later
- The Microsoft India localisation apps India Tax Base and India GST
- Outbound HTTPS access to api.yashvan.com
- Available for India; interface in English
Getting started
- 1Install the app from Microsoft AppSource
- 2Create an account at verify.yashvan.com, add the Integration entitlement and top up credits
- 3Generate an API key in the portal
- 4Open IN Compliance Setup in Business Central and paste the key
- 5Open any vendor and verify
Know the MSME answer before you post
Put verified PAN, GST and Udyam status on the vendor record, with the date it was checked — and let Business Central carry the MSME due date through to the ledger.