The record requirement covers both sides of the ledger
Rule 56(3) requires every registered person to keep a separate account of advances received, advances paid and adjustments. A customer-advance list alone therefore leaves part of the record population unaddressed. This guide, checked on 27 October 2026, builds the ledger reconciliation rather than repeating the separate rules determining when an advance creates output tax or ITC. A bank receipt labelled “advance” is not a legal conclusion about the underlying supply. ICAI GST bare law, April 2026: Rule 56(3).
Create separate received and paid populations
Use a unique advance reference, counterparty, contract, date, currency, original amount and unadjusted balance. Keep received advances separate from supplier advances; netting them simply because the same party appears on both sides can hide liabilities and assets. Document any legally supported set-off separately. For multiple GST registrations, identify the relevant registered person and transaction rather than treating a group cash pool as one GST account. ICAI GST bare law, April 2026: Rule 56(3).
Link allocation to the actual invoice or refund
Record the invoice or refund reference, amount adjusted, date and remaining balance. An invoice entered in accounts does not prove that an advance has been allocated to it. Conversely, allocating the same receipt to two invoices can leave both customer and tax records unreliable. Preserve the allocation history and corrections. Distinguish gross cash, taxable value and any tax component; this article’s examples use stated monetary ledger amounts without prescribing a tax rate.
Separate genuine deposits and disputed balances
Use the contract and the actual appropriation to decide whether a deposit belongs in an advance population; do not relabel every refundable security balance as consideration. Maintain pending-identification receipts and disputed supplier advances with a clear status, not a fictitious invoice. Ageing identifies items requiring review but does not itself authorise writing off the balance, taxing it or claiming credit. ICAI GST bare law, April 2026: Rule 56(3).
Reconcile the ledger to bank, books and the separate tax working
Opening unadjusted balance plus new advances less invoice allocations and refunds should explain closing balance, with other movements separately supported. Reconcile allocations to the sales or purchase ledger and to the applicable return working. Avoid taxing or claiming credit twice merely because both the original advance record and the final invoice are visible. The actual time-of-supply, receipt/refund voucher and input-credit rules must be independently applied to the facts.
Close exceptions rather than just forcing agreement
Investigate negative balances, duplicate allocations, unmatched refunds and advances transferred to unrelated contracts. Retain the original source, reason and approval for corrections. The CBIC rule text and April 2026 bare-law compilation support the recordkeeping requirement; neither supplies a universal tax consequence for every residual advance. A zero ledger balance can still be wrong if an unrelated invoice was used to clear it. ICAI GST bare law, April 2026: Rule 56(3).
Applicable primary references
ICAI GST bare law, April 2026: Rule 56(3) CBIC CGST Rules: advances account requirement
Six worked illustrations
All facts and amounts below are fictional. Assumptions describe the model, not additional statutory rules.
Illustrative example 1: Received-advance roll-forward
Opening advances ₹2,00,000 plus receipts ₹5,00,000 less invoice allocations ₹4,00,000 and refunds ₹50,000 close at ₹2,50,000. Keep the allocations and refunds separately identifiable.
Illustrative example 2: Supplier-advance roll-forward
Opening ₹1,00,000 plus payments ₹3,00,000 less purchase-invoice allocations ₹2,40,000 gives ₹1,60,000 outstanding. This is not automatically eligible ITC.
Illustrative example 3: One advance, several invoices
An advance ₹3,00,000 is allocated ₹1,20,000 and ₹1,00,000 to two invoices. The unallocated amount is ₹80,000, not nil merely because two invoices exist.
Illustrative example 4: Duplicate allocation
An advance ₹1,50,000 is allocated ₹1,00,000 and ₹80,000. The ₹30,000 excess allocation is an exception requiring correction; it is not evidence of a further cash receipt.
Illustrative example 5: Same-party gross balances
A counterparty has customer advances ₹2,00,000 and supplier advances ₹1,20,000. The gross records remain ₹2,00,000 received and ₹1,20,000 paid unless a supported adjustment is made; an ₹80,000 net report hides both populations.
Illustrative example 6: Refund gap
The bank shows a refund ₹60,000 but the advance ledger records only ₹45,000. Investigate the ₹15,000 difference. Do not presume a GST credit note or output-tax reduction solely from that arithmetic gap.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Define the registered person | GSTIN and relevant transaction population. |
| 2 | Separate advances received and paid | Gross customer and supplier ledgers. |
| 3 | Assign unique references | Contract, counterparty and original receipt/payment. |
| 4 | Confirm the underlying character | Advance, deposit or unidentified cash. |
| 5 | Reconcile cash movements | Bank entries and original evidence. |
| 6 | Map invoice allocations | Invoice reference, amount and allocation date. |
| 7 | Trace refunds | Bank refund and original advance linkage. |
| 8 | Test duplicate or negative allocations | Exceptions and supported corrections. |
| 9 | Reconcile tax separately | Applicable liability, vouchers and credit conditions. |
| 10 | Approve the closing balance | Roll-forward, ageing and unresolved items. |
Sixteen practitioner FAQs
1. Does Rule 56(3) cover advances paid?
Yes, as well as advances received and adjustments.
2. Can a customer-only register suffice?
It omits the paid-advance population required by the rule.
3. Should both sides be netted automatically?
No. Preserve gross records and support any actual set-off.
4. Is every receipt an advance for a supply?
Classify using the agreement and facts.
5. Are security deposits always consideration?
Do not presume so; examine appropriation and the applicable rules.
6. Does an invoice automatically clear an advance?
Record the actual allocation instead of assuming it.
7. Can one advance cover multiple invoices?
Yes, but the aggregate allocation must reconcile to available funds and supported movements.
8. What does a negative balance indicate?
It is an exception to investigate, not automatic evidence of new money.
9. Does an old balance automatically become income?
Age alone does not establish that conclusion.
10. Does supplier advance payment establish ITC?
No. Apply the separate credit conditions.
11. Does this guide prescribe an advance tax rate?
No. It isolates recordkeeping and reconciliation.
12. Should refund entries identify the original receipt?
Yes, to prevent clearing the wrong obligation.
13. Can a bank refund alone prove a tax reduction?
No. The applicable tax and document conditions remain separate.
14. How should unexplained receipts be held?
Use a transparent pending-identification status rather than a fictitious invoice.
15. Can group companies share one undifferentiated register?
Identify the actual registered person and transaction; a cash pool does not settle GST ownership.
16. What makes a closing zero unreliable?
An unsupported allocation to an unrelated invoice can force a false zero.
Conclusion
Reconcile advances received and paid separately, trace invoice allocations and refunds, and keep the Rule 56(3) record distinct from the tax-liability decision.