What does rule 74 regulate?

It regulates final acceptance of output-tax reduction. Read the exact text, conditions, exceptions and transaction date together.

Which subordinate law should be checked?

No direct CGST Rule has been listed in this repository. 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.

CGST Rule 74 — Final acceptance of output-tax reduction

CGST Rules, 2017

OMITTED HISTORICALRepository module RULE CONTROL

Source control: The text/status on this page is tied to the official source gateway and the Repository module legal-review register. Open official source.

Official sources

Use the official source for the controlling wording, footnotes, effective date and amendment history.

Source review date: 2026-07-28. Historical-period questions require the version applicable to the transaction date.

Finin2min Summary - Rule in 2 Minutes

Paragraph / test Professional meaning Current status The rule has no operative application for current periods. Historical use Retain the former rule only to analyse legacy periods, notices and system architecture. Current framework Use current sections 16, 34, 38, 41, 52 and applicable Rules/portal controls. Exceptions and

official statutory reference

[Omitted with effect from 1 October 2022 by Notification No. 19/2022-Central Tax dated 28 September 2022.]

Paragraph-wise decode

Section-Rule-Form-Notification bridge

No direct Rule certified in Repository module. 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 listed in this repository.

Practical example

A professional first identifies whether the facts trigger rule 74, fixes the relevant period, checks the mapped subordinate instruments and preserves evidence before filing or advising.

Professional alert

• Do not cite the former MIS/GSTR-3 matching process as current law. • Historical disputes must be tested against the law applicable to their tax period.

Finin2min | P0-R05 Rules 62-84 Finin2min.com | Finance & Law Explained in 2 Minutes | Educational and professional reference

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 74 regulate?: It regulates final acceptance of output-tax reduction. Read the exact text, conditions, exceptions and transaction date together.
Which subordinate law should be checked?: No direct CGST Rule has been listed in this repository. 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.

Repository module professional rule control

Legal state: Omitted historical · Checked: 27 July 2026. Current legal/release state is controlled by the Repository module master; read the official statutory reference and amendment history together.

Why Rule 74 matters

Final acceptance of output-tax reduction should be read with its enabling CGST Act provision, prescribed forms, amendment notification, transaction date and the live portal workflow. The operative-text block already released on this page remains the legal core; Repository module adds application controls without altering that block.

Rule → Form → evidence bridge

No prescribed form is the primary legal trigger; use the Rule text and portal workflow applicable to the transaction.

Confirm the Rule version that was operative on the relevant date.
Check every proviso, explanation, inserted/omitted sub-rule and commencement notification.
Use the current prescribed form/portal utility rather than a saved legacy template.
Preserve the Rule source, filing/approval evidence, computation and decision-maker trail.

Finin2min decision path

Trigger: What transaction, registration event, return, credit, valuation, refund, appeal or enforcement event activates this Rule?
Date: Which Rule version and amendment notification applied on that date?
Conditions: Have every mandatory condition and exception been tested?
Form/portal: Is the prescribed form or electronic workflow the correct current version?
Evidence: Can the conclusion be reconstructed from books, invoices, portal records and official sources?

Practical cases

Transaction test

Fix the tax period, legal trigger and effective version of the Rule.

Portal execution

Reconcile portal fields to the legal rule and retain the generated acknowledgement/order.

Dispute readiness

Preserve source version, computation and evidence so the position can be defended later.

Accounting, ERP and portal controls

Do not let an ERP default or portal auto-population override the legal Rule.
Map the Rule trigger to the correct tax period and retain before/after reconciliation where values change.
Archive ARN, acknowledgements, generated PDFs, payment/ledger records, notices and orders where applicable.

Notice and litigation risk

Separate a portal mismatch from a statutory breach; they are not automatically the same issue.
Identify whether a circular/instruction is clarificatory or whether an amendment changed the Rule itself.
Apply judicial hierarchy: Supreme Court → jurisdictional High Court → other High Courts → GSTAT; AAR/AAAR is not universal precedent.

Common mistakes

Using today's Rule for an older transaction without an effective-date test.
Reading a form instruction as if it overrides the Act or Rule.
Ignoring State/UT procedural overlays where the Rule requires a local notification or officer action.
Treating a source-gated local reproduction as cleared statutory text.

Finin2min Q&A

What does CGST Rule 74 deal with?: Final acceptance of output-tax reduction. Start with the operative Rule version and then test the connected Act provision, forms and amendments.
Which GST form is connected to Rule 74?: No single prescribed form is the primary trigger. The Rule and live portal workflow control.
Can I rely only on the GST portal?: No. Portal functionality is execution infrastructure; legal eligibility and consequences come from the Act, Rules and valid instruments.
What should I keep on file?: The official Rule version used, amendment/effective-date evidence, underlying transaction records, computation, portal submission and resulting acknowledgement/order.

← Previous Next →