Rule 88 - Identification number for each transaction
CGST Rules, 2017
ACTIVECONSOLIDATED_BASE_WITH_CURRENT_CONTROLindex,follow
Source control: The text/status on this page is tied to the official source gateway and the Phase 1 legal-review register. Open official source.
Finin2min Summary - Rule in 2 Minutes
Electronic liability discharge follows statutory order; credit/cash posting must match the liability register.
Exact operative text
88. Identification number for each transaction.-(1) A unique identification number shall be generated at the
common portal for each debit or credit to the electronic cash or credit ledger, as the case may be. (2) The
unique identification number relating to discharge of any liability shall be indicated in the corresponding entry
in the electronic liability register. (3) A unique identification number shall be generated at the common portal
for each credit in the electronic liability register for reasons other than those covered under sub-rule (2).
Paragraph-wise decode
Electronic liability discharge follows statutory order; credit/cash posting must match the liability register.
Section-Rule-Form-Notification bridge
No direct Rule certified in Phase 1. Check notifications, circulars, forms and corresponding State law.
The mapping is a legal concordance, not a round-robin related-link list. It is limited to instruments certified in this phase.
Practical example
Apply the rule to the relevant form, period, portal event and evidence trail before reaching a compliance conclusion.
Professional alert
Verify the latest official active Rule page, amending Gazette and portal version before filing or advising.
Implementation checklist
- Fix the transaction, taxable period and jurisdiction.
- Read every subsection, proviso, explanation and omission marker.
- Open the mapped Rule, form, notification and circular.
- Test State/UT variation and portal version.
- Preserve evidence, approvals, working papers and acknowledgements.
- Record the conclusion, assumptions, source date and reviewer.
Evidence and retention checklist
- Contract, purchase order, invoice or underlying transaction document.
- Registration, return, ledger, challan and portal acknowledgement.
- Official Act/Rule/notification version used and effective date.
- Internal tax position paper, computation and management approval.
- Correspondence, notices, replies, orders and appeal papers where applicable.
Practical Q&A
- What does rule 88 regulate?
- It regulates identification number for each transaction. Read the exact text, conditions, exceptions and transaction date together.
- Which subordinate law should be checked?
- No direct CGST Rule has been certified in this phase. Notifications, circulars, forms and the corresponding SGST/UTGST layer may also apply.
- What evidence should be retained?
- Preserve the contract or transaction record, invoice or form, portal acknowledgement, payment/ledger evidence, correspondence, legal working and the official source version used.
- Can portal behaviour override the statute?
- No. Portal functionality is operational evidence; legal entitlement and liability remain controlled by the Act, Rules, notifications and binding decisions.