Keep the document register connected to the tax accounts
CGST Rule 56(4) requires registered persons other than section 10 composition taxpayers to maintain accounts of tax payable, including the specified reverse-charge tax, tax collected and paid, input tax and input tax credit claimed together with a register of tax invoices, credit notes, debit notes and delivery challans issued or received during the tax period. The professional task is more than archiving PDFs: each relevant document must be identifiable, retrievable and reconcilable to its accounting and tax treatment. A register count alone does not prove the correct tax liability or entitlement to credit.
Read the applicable text: CBIC CGST Rules: rule 56(1), (4) and (8).
Preserve document identity and direction
Use a document key that distinguishes GSTIN, financial year, document type, direction and document number as appropriate to the records. Similar numbers in a supplier’s incoming series and the company’s own outgoing series do not necessarily identify a duplicate. Retain dates, counterparty, linked original documents, values, tax-head amounts, ledger entry and reporting treatment. This is a suggested control design, not a new statutory form or a claim that rule 56(4) prescribes these exact software columns.
Do not net different document populations blindly
An incoming supplier credit note and the company’s outgoing sales credit note affect different sides of the accounts. A delivery challan documents movement under its applicable rules; it is not automatically a sales invoice or taxable revenue. Link the movement to a subsequent invoice, return or other supported disposition where relevant. Keep the document’s existence separate from its tax result, and investigate orphaned records rather than deleting them to achieve matching totals.
Use credit and debit notes with their legal conditions
An issued credit note can be a commercial adjustment without satisfying every condition for reducing GST liability. An inward invoice can be recorded without establishing all ITC conditions. Rule 56(4)’s register requirement does not override the substantive Act or the document-specific rules. Accordingly, label the examples as reconciliation of assumed legally eligible tax amounts; they do not prescribe tax rates, credit-note deadlines or ITC eligibility. Examine those questions separately for the actual period and supply.
Reconcile completeness before amounts
Compare the source-system document population with the register, then the register with ledger and return workings. Explain cancelled or superseded records, differences in direction and legitimate timing differences with evidence. Where one tax period’s movement is invoiced in another, do not force both into a single period merely to make a count agree. An unexplained missing document is an exception needing investigation, not automatic proof of suppression, fraud or a fixed tax demand.
Finish with a traceable exception file
Record each unresolved item, its amount, tax head if known, source evidence, owner and proposed resolution. Rule 56(8) prohibits erasing, effacing or overwriting entries: paper corrections are scored out under attestation and the correct entry is then recorded; electronic records must retain a log of every edited or deleted entry. Keep the original document and correction history when rectifying the register. A documented closing process should allow a reviewer to trace a chosen ledger or reporting amount back to the underlying invoice, note or challan and in the opposite direction. This guide concerns the record-to-account bridge, distinct from invoice field requirements, electronic-backup restoration and the separate determination of output tax or ITC.
Six worked illustrations
All facts and amounts are fictional. Calculations illustrate the stated assumptions, not a predetermined legal outcome.
Illustrative example 1: Source documents versus register
The issue system contains 120 invoices for the period while the register contains 117. The three-document gap needs investigation. It does not establish that three taxable sales were omitted until cancelled, duplicate, timing and other evidence is reviewed.
Illustrative example 2: Eligible output-tax note bridge
Assume valid output-tax amounts on invoices ₹1,80,000, eligible debit-note tax ₹9,000 and eligible credit-note reduction ₹18,000. The supported net working is ₹1,71,000. Record all three populations separately so the net does not hide missing documents. These are assumed tax amounts, not a rate calculation.
Illustrative example 3: Direction changes the population
The company has 15 issued credit notes and 10 received supplier credit notes. The document count is 25, but only 15 belong to its issued-credit-note population. Netting the counts to 5 would lose the direction distinction and cannot establish a tax amount.
Illustrative example 4: Challans are not automatic turnover
Twenty challans cover 1,000 units. Supported later documents account for 750 units through invoices and 200 through returns, leaving 50 units unresolved. Reconcile 1,000 − 750 − 200 = 50; do not record all 1,000 as sales merely because a challan exists.
Illustrative example 5: The same number need not be a duplicate
Supplier A invoice 001 is ₹40,000 and supplier B invoice 001 is ₹60,000. The supported incoming total is ₹1,00,000 across two distinct documents. Deduplicating only on the string 001 could omit one real invoice. Verify the supplier and document identity.
Illustrative example 6: Commercial adjustment differs from tax adjustment
The ledger records a commercial customer credit of ₹50,000. Only ₹30,000 of the base is established, on the assumed facts, as supporting the relevant GST reduction; the remaining ₹20,000 is separately classified. The register should preserve the ₹50,000 document and the explained split, rather than treating the whole amount as an automatic tax-base reduction.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Define the period and GSTIN | Registration and tax-period scope. |
| 2 | Collect issued and received documents | Source populations for invoices, notes and challans. |
| 3 | Assign reliable document identity | Type, direction, counterparty and original reference. |
| 4 | Check source completeness | Register count and documented exceptions. |
| 5 | Link invoices and notes | Original document and adjustment rationale. |
| 6 | Link challans to disposition | Movement, invoice, return or supported non-sale treatment. |
| 7 | Reconcile ledger entries | Document-to-account and account-to-document tests. |
| 8 | Validate tax treatment separately | Actual output-tax/ITC eligibility and period rules. |
| 9 | Resolve timing and commercial differences | Explained differences with retained evidence. |
| 10 | Approve the closing register | Exceptions, responsible owners and accessible source records. |
Sixteen practitioner FAQs
1. Who is excluded from rule 56(4)’s stated population?
The sub-rule excludes persons paying tax under section 10; examine their separate record obligations.
2. Is this a new filing form?
No. It is an internal register and reconciliation workflow around the existing rule.
3. Are received documents included?
The rule includes the named documents issued or received during the tax period.
4. Is a PDF folder enough to prove correct tax?
No. Documents must connect to the accounts and their substantive tax treatment.
5. Should incoming and outgoing credit notes be netted by count?
No. Keep direction and the different accounting populations visible.
6. Is every delivery challan revenue?
No. Establish the movement and its actual legal/accounting disposition.
7. Does a credit-note entry always reduce output tax?
No. The substantive conditions for GST reduction must be checked separately.
8. Does an inward invoice guarantee ITC?
No. Recording an invoice does not replace the eligibility analysis.
9. Can identical invoice numbers occur for different suppliers?
Yes. Use a reliable composite identity instead of the number alone.
10. What if the source has more documents than the register?
Investigate the difference with evidence; do not assume a specific tax outcome from count alone.
11. Should cancelled records simply be deleted?
Preserve the cancellation and correction trail needed to explain the population.
12. How are later invoices linked to earlier challans?
Use the actual movement and disposition references and explain the period difference.
13. Are the suggested software columns statutory fields?
They are a practical control design, not a newly prescribed form.
14. Does the example prescribe a GST rate?
No. It uses assumed document tax amounts to illustrate reconciliation.
15. Can commercial and GST adjustments differ?
Yes. Explain the split without changing or hiding the original commercial document.
16. What should a reviewer be able to trace?
Both directions between the register, underlying documents, ledger and reporting workings, with unresolved exceptions visible.