Set your MSME limits and interest rate
The statutory time limits and the interest rate used by the delay report are yours to configure. The app applies arithmetic to your parameters and takes no view on what is correct for your contracts.
Back to India Compliance VerificationSetup guide
Getting started
From a clean Business Central environment to your first verified vendor. The app is free to install; verifications are paid for with credits on a Yashvan account you hold separately.
Before you begin
- Microsoft Dynamics 365 Business Central online, version 28 or later
- The Microsoft India localisation apps India Tax Base and India GST
- Outbound HTTPS access from Business Central to api.yashvan.com
- Permission to install extensions and to open IN Compliance Setup in the target environment
Setup
- 1
Install the app from Microsoft AppSource
Search for India Compliance Verification in AppSource, or install it from Extension Marketplace inside Business Central. The app is free to install. Assign the permission set to the users who will run verifications.
- 2
Create your Yashvan account
Go to verify.yashvan.com and register. The app cannot verify anything without an account — it holds no credentials of its own.
- 3
Add the Integration entitlement and top up credits
The annual Integration entitlement authorises API access from an ERP. Credits pay for individual verifications and are consumed only on a successful result. Both are managed in the Yashvan portal, not in Business Central.
- 4
Generate an API key
Create a key in the portal and copy it. Treat it as a secret — activity under your key is your responsibility.
- 5
Enter the key in IN Compliance Setup
In Business Central, search for IN Compliance Setup and paste the key into the API Key field. The connection is checked straight away, and the page shows your credit balance and when the Integration entitlement expires. Use Refresh Balance to check again at any time. The key is stored in Isolated Storage as a secret, scoped per company — it is never written to a table field and never displayed back.
- 6
Verify your first vendor
Open any vendor with a PAN or GSTIN on the card and run a verify action. Results are written to named fields with the verification date against each, and the Udyam certificate is attached to the vendor record.
Once you are running
Scope the scheduled job carefully
A job queue entry re-verifies vendors matching a filter you define. That filter controls both scope and cost — a wide filter across a large vendor master consumes credits in proportion. Start narrow.
Check the API log
Every call is recorded with its trace id, the check performed, credits debited and balance remaining. It is the first place to look if a result or a balance is unexpected.
Something not working?
The help page covers the common failures — an expired or rejected key, an exhausted credit balance, an inactive entitlement, and a scheduled job that stopped part-way.