India Audit Lens
Review and control GST API credits
Monitor the firm's GST API credit pack, remaining/used credits, validity, and authorised transaction history before vendor verification, GSTR fetches, IRN validation, or other provider-backed actions. The current…
By India Audit Lens product team · Updated 2026-08-03
Before you begin
Open the correct firm workspace and confirm the setting you intend to change. Check that your role allows the action. Gather the approved firm, user, template, rate, branding, or integration details needed for the task. Review any effect on active users, clients, engagements, returns, or reports before saving.
Review balance and validity
Navigate to Settings → Integrations → GST API Credits. Click Refresh before a time-sensitive API operation. Review Credits remaining, total purchased, Total used, and Validity. Read any Low credit balance warning. If authorised for history, review Recent transactions: When, Type, delta, balance, note, and actor. Reconcile unexpected consumption with the relevant GST operation/audit activity.
The transaction-history API may be limited to Partner-or-above access. A blank history for a lower role is not proof that no credits were consumed.
No active pack or low balance
Record the state without exposing firm values in a support screenshot. Check whether the planned GST action actually requires provider credits and whether portal/manual alternatives are supported for that workflow. Notify the authorised firm purchaser/support route before the deadline. Do not assume Buy Credit Pack or Buy Another Pack can be used when those actions are disabled. Use the authorised provisioning or support route shown for the firm. After an authorised pack is provisioned outside this screen, click Refresh and verify balance, validity, and transaction record.
Investigate unexpected usage
Identify transaction time, type, delta, actor, and note. Compare with GSTIN verification/fetch/IRN actions and activity records for that window. Check for repeated clicks/retries or scheduled/background provider calls. Escalate unexplained usage without publishing GSTIN, client name, or full record identifiers. If credentials/provider use may be compromised, stop affected actions and follow the integration incident procedure.
Expected result
The firm knows its current usable balance and expiry, can trace authorised consumption, and does not promise a self-service purchase flow that the current UI has not implemented.