The key was rejected, or verification returns an authentication error
Likely cause. The API key is missing, mistyped, revoked, or belongs to a different Yashvan account.
What to do. Open IN Compliance Setup and paste the key into the API Key field again — the connection is checked as soon as you enter it. Keys are stored per company, so a key set up in one company is not available in another. If the key was regenerated in the Yashvan portal, the old one stops working immediately and must be replaced here.
Verification fails with an insufficient credits message
Likely cause. The credit balance on the Yashvan account has run out.
What to do. Top up credits at verify.yashvan.com. Completed lookups are charged; errors are not. The current balance is shown on IN Compliance Setup.
Everything is configured but API access is refused
Likely cause. The annual Integration entitlement is missing or has lapsed. A credit balance alone does not authorise API access from an ERP.
What to do. Check the entitlement status in the Yashvan portal and renew it. The entitlement and the credit balance are separate — one can be valid while the other is not.
A scheduled verification shows an error
Likely cause. The API key is invalid, credits or the entitlement have run out, the data source could not process that identifier, or the vendor is blocked.
What to do. Open Job Queue Entries to read the error for that vendor. Fix the cause and schedule the vendor again from the Vendor List. Other vendors in the same run are not affected.
Credits are being consumed faster than expected
Likely cause. More vendors were scheduled than intended, or vendors were verified again soon after a previous run.
What to do. The confirmation before a scheduled run shows how many vendors will be verified. The Verification Log records every call with the check performed and the credits debited.
A PAN or GSTIN returns no result
Likely cause. The identifier is not present in the official records, is incorrectly recorded on the vendor card, or the vendor is genuinely not registered.
What to do. Check the identifier on the vendor card first. A vendor with no Udyam registration is a valid answer, not an error — it means the MSME payment rules do not apply to them. Results depend on records maintained by third parties; we do not warrant that they are complete or current.
The MSME due date is not what was expected
Likely cause. The MSME due date comes from the posting date, the agreement type on the document and the day limits in IN Compliance Setup, not from payment terms.
What to do. Check the agreement type on the document and the limits in setup.
The Udyam certificate is not attached to the vendor
Likely cause. The certificate is returned by the MSME verifications. If no MSME verification has been run, or the vendor has no Udyam registration, there is nothing to attach.
What to do. Run a MSME verification from the vendor card. The certificate is stored as a standard Document Attachment on the vendor record, inside your own tenant.