Here is something most compliance teams discover too late. The GST portal does not maintain an Electronic Credit Ledger for ISD registrants. Unlike a regular taxpayer whose ITC is tracked in a portal-level ledger, an ISD has no system-generated balance sheet of what it received, what it distributed, and what remains.
The ISD is purely a distribution mechanism. Credit flows through GSTR-6A from supplier filings. Credit flows through GSTR-6 to recipient units. What happens between those two points – the classification decision, the ratio applied, the tax head conversion, the ISD invoice generated, the reconciliation status of each distribution – exists nowhere on the GST portal in a consolidated view.
This is the gap the Central ISD Ledger fills. It is a platform-level construct that maintains a single, unified view of every credit movement through the ISD – from the moment a supplier invoice is received to the moment a recipient unit confirms the claim in their GSTR-3B. Combined with a structured audit trail, it turns the ISD’s compliance position from an assertion into a documented, traceable record.
This blog explains what the Central ISD Ledger captures, how it is structured, how the audit trail it generates supports departmental scrutiny and Section 65 GST audits, and what the absence of such a ledger costs a group entity when a notice arrives.
The Portal Gap – Why the Central ISD Ledger Is Needed
Understanding why the ledger matters starts with understanding what the GST portal provides to an ISD and what it does not.
What the GST Portal Gives the ISD
| Portal Feature | Available to ISD? | What It Shows |
| Electronic Credit Ledger | No | Not maintained for ISD registrants – ISD has no credit balance of its own |
| Electronic Cash Ledger | No | Not applicable – ISD does not discharge any tax liability |
| GSTR-6A (read-only) | Yes | Supplier invoices auto-populated from their GSTR-1 filings |
| GSTR-6 filing dashboard | Yes | Return filing status for the current and past periods |
| ARN (Acknowledgement number) | Yes | Proof of GSTR-6 filing per period |
| GSTR-6 filed return data | Yes | Historical GSTR-6 tables for each filed period |
| Recipient GSTR-2A reflection | Indirectly | Distributed credit visible in each unit’s GSTR-2A |
The GST portal gives the ISD a filing interface, not a ledger. There is no single place on the portal where an ISD can see: total credit received this financial year, total credit distributed by unit, credit pending distribution, reconciliation status of each distribution, or the audit trail of every allocation decision.
What That Means in Practice
Without a central ledger, an ISD managing 12 months of filings across 15 recipient units faces a fragmented picture. The data exists – in 12 separate GSTR-6 filings, in supplier invoices, in ISD invoices, in recipient GSTR-3B filings – but it is scattered across the portal, the ERP, and the team’s working files. Pulling a consolidated view for any purpose – a department audit, an internal review, a year-end reconciliation – means manually assembling data from multiple sources.
The Central ISD Ledger assembles this data automatically and maintains it as a live, running record throughout the year.
What the Central ISD Ledger Captures
The Central ISD Ledger is built on three pillars: receipts, distributions, and reconciliation notes. Together, they create the single view of the ISD’s complete credit lifecycle.
Pillar 1 – Receipts
The receipts section of the ledger records every credit that entered the ISD’s orbit – whether it was distributed in the same month or is pending action.
| Field Captured | Source | Purpose |
| Supplier GSTIN | GSTR-6A / purchase register | Identifies the vendor; used for GSTIN active status tracking |
| Invoice number | GSTR-6A / supplier invoice | Unique identifier; used for duplicate detection and amendment tracking |
| Invoice date | GSTR-6A | Date range validation; Section 16(4) window tracking |
| Taxable value | GSTR-6A | Base for tax computation |
| IGST amount | GSTR-6A | Credit head at ISD |
| CGST amount | GSTR-6A | Credit head at ISD |
| SGST/UTGST amount | GSTR-6A | Credit head at ISD |
| CESS amount | GSTR-6A | Tracked separately; distributed as CESS to units |
| GSTR-6A reflection date | Portal sync | Confirms supplier has filed GSTR-1; credit is available |
| Invoice classification | Allocation engine / team input | Exclusive / Common / Ineligible – determines distribution path |
| Classification basis | Allocation engine | Which rule or manual decision drove the classification |
| Classification date and user | Platform log | Audit trail for classification decisions |
| GSTR-6A vs register match status | Reconciliation engine | Matched / Mismatch / Missing in register / Missing in GSTR-6A |
| Mismatch reason | Reconciliation engine | Amount variance / tax head variance / date variance |
| Period of receipt | Calendar month | Month and year the invoice was received and reflected in GSTR-6A |
Pillar 2 – Distributions
The distributions section records every ISD invoice issued – the core output of the ISD’s compliance function.
| Field Captured | Source | Purpose |
| ISD invoice number | Platform (auto-sequential) | Unique distribution reference; links to original supplier invoice |
| ISD invoice date | Platform | Must match the GSTR-6 filing period |
| Recipient GSTIN | Recipient master | The unit receiving the credit |
| Recipient name | Recipient master | Human-readable label for reports and notices |
| Recipient state | Derived from GSTIN | Drives tax head conversion logic |
| Allocation method | Allocation engine | Turnover-ratio / Custom ratio (headcount/equal) / Direct attribution |
| Ratio applied | Allocation engine | Exact percentage used for this recipient for this invoice |
| Eligible ITC distributed – IGST | Allocation engine | Credit amount by tax head |
| Eligible ITC distributed – CGST | Allocation engine | Credit amount by tax head |
| Eligible ITC distributed – SGST | Allocation engine | Credit amount by tax head |
| Ineligible ITC distributed | Allocation engine | Separately tracked; flagged with Section 17(5) or other ineligibility reason |
| Tax head conversion applied | Allocation engine | Yes/No; original head and converted head recorded |
| GSTR-6 period | Filing period | Which GSTR-6 return this distribution appeared in |
| GSTR-6 Table reference | Platform | Table 5 (eligible) or Table 8 (credit note) – where in GSTR-6 this line appears |
| GSTR-2A reflection status | Reconciliation engine | Reflected / Pending / Not reflected |
| GSTR-2A reflection date | Reconciliation engine | Date credit appeared in unit’s GSTR-2A |
| Recipient claim status | Reconciliation engine | Claimed in GSTR-3B / Not yet claimed / Claimed in excess / Reversed |
| Recipient claim date | Reconciliation engine | Date unit’s GSTR-3B was filed with this ITC |
| Claim amount in GSTR-3B | Reconciliation engine | Actual amount claimed by unit – may differ from distributed amount |
| ISD credit note reference | Platform | If a credit note was issued against this distribution, links to the credit note record |
Pillar 3 – Reconciliation Notes
The reconciliation notes section captures the resolution story behind every discrepancy. This is what transforms the ledger from a data store into an audit-defensible record.
| Note Type | When Captured | What It Records |
| Exception raised | When reconciliation engine flags a gap | Exception type, invoice reference, amount affected, unit GSTIN, date flagged |
| Exception status | Ongoing until resolved | Open / In progress / Resolved / Escalated |
| Resolution action | When exception is closed | What was done: amendment filed, credit note issued, unit reversed, no action needed |
| Resolution date and user | At resolution | Who resolved and when – creates individual accountability |
| Supplier follow-up log | When invoice missing from GSTR-6A | Date contacted, response received, date supplier filed, outcome |
| GSTR-6 amendment note | When prior period correction filed | Original value, corrected value, amendment period, reason for correction |
| ISD credit note note | When credit note issued | Reason (supplier credit note / ratio error / wrong GSTIN), original distribution reference |
| Recipient query log | When unit raises a question | Query text, date raised, platform response, resolution date |
| Ineligible credit alert | When ineligible credit is distributed | Ineligibility reason, units notified, reversal confirmed or pending |
| Section 16(4) deadline alert | When pending credit approaches window | Invoice date, window expiry date, action taken or deferred |
| Year-end carry-forward note | At financial year close | Credit distributed vs credit claimed comparison; any carry-forward to next year |
| Notice linkage | When a department notice references the ledger | SCN or audit query reference number, date received, items queried, response prepared |
The three pillars together answer every question a GST officer, statutory auditor, or internal reviewer can ask about ISD credit: What came in? What went out? To whom? On what basis? What was the outcome? What discrepancies were found and how were they resolved? No reconstruction required – the ledger holds it all.
The Single View – What the Ledger Looks Like in Practice
The Central ISD Ledger presents its data in multiple views, each designed for a different user and purpose.
The Running Balance View
This is the month-by-month summary of the ISD’s credit position. It shows, for each period:
| Column | Description |
| Opening credit | Credit brought forward from prior period amendments or pending redistributions |
| Credit received in period | Total ITC from supplier invoices reflected in GSTR-6A for the month, by tax head |
| Credit distributed – eligible | Total eligible ITC distributed to all recipient units in GSTR-6 Table 5 |
| Credit distributed – ineligible | Total ineligible ITC distributed in GSTR-6 Table 5 with ineligible flag |
| Credit notes issued | ISD credit notes distributed in Table 8 (negative adjustments) |
| Net distributed | Eligible distributed minus credit notes |
| Balance | Credit received minus net distributed – should be zero if all credit is distributed in the same month |
| Exception amount | Credit in exception status (mismatch, not reflected, over-claimed) |
ISD cannot carry forward eligible credit to future months – Rule 39 requires distribution in the same month as receipt. The balance column in the running view should always be zero for eligible credit. A non-zero balance is an immediate compliance flag.
The Unit-Wise Distribution View
This view shows each recipient unit’s credit position across all periods – what was distributed, what was reflected in GSTR-2A, and what was claimed in GSTR-3B.
| Column | Description |
| Recipient GSTIN | Identifies the unit |
| Period | Month and year |
| Credit distributed (IGST/CGST/SGST) | By tax head – from GSTR-6 Table 5 |
| GSTR-2A status | Reflected / Not yet reflected |
| GSTR-3B claimed | Amount claimed by unit – pulled from their filed GSTR-3B |
| Variance | Distributed minus claimed – positive means unclaimed, negative means over-claimed |
| Exception type | Bucket classification if variance exists |
| Resolution status | Open / In progress / Resolved |
The Invoice-Level Drill-Down View
Every supplier invoice in the ledger can be drilled into for the complete chain: from the supplier’s GSTR-1 filing to each unit’s GSTR-3B claim. This is the view that matters most in an audit.
- Supplier invoice details – GSTIN, invoice number, date, value, tax head, GSTR-6A reflection date.
- Classification decision – Exclusive/Common/Ineligible, rule applied, date, team member.
- Allocation computation – Ratio type, financial year data used, exact percentage per unit, computed credit amount per unit.
- Tax head conversion – Original head at ISD, converted head per unit, conversion rule applied.
- ISD invoice generated – ISD invoice number, date, recipient GSTIN, credit amount, tax head.
- GSTR-6 table entry – Which GSTR-6 return, which table, which row.
- GSTR-2A reflection – Date appeared in recipient’s GSTR-2A, amount, tax head.
- GSTR-3B claim – Filing date, amount claimed, Table 4(A)(5) entry confirmed.
- Exception history – Any exceptions raised, resolution taken, dates and users.
This chain – from supplier invoice to recipient claim – is the complete lifecycle of a single credit entry. The drill-down view presents it in one screen, exportable for any purpose.
The Period Summary View
For each GSTR-6 filing period, the ledger shows a consolidated summary:
- Total invoices in GSTR-6A for the period.
- Matched vs mismatched vs missing invoices.
- Total eligible ITC received and distributed.
- Total ineligible ITC received and distributed.
- Number of recipient units credited.
- GSTR-6 filing date and ARN.
- Number of open exceptions.
- Number of resolved exceptions.
- Total ITC claimed by units in GSTR-3B for the period.
- Total unclaimed ITC (available in GSTR-2A but not yet in GSTR-3B).
The Audit Trail – Structure and Depth
The audit trail is not the same as the ledger. The ledger shows the current state of each credit entry. The audit trail shows every action taken on every entry, in chronological order, with the user and timestamp. Together, they create a complete, tamper-evident record.
What the Audit Trail Records
Every action in the ISD compliance workflow creates an audit trail entry. The trail captures:
| Event | Audit Trail Entry |
| Supplier invoice synced from GSTR-6A | Invoice reference, sync date/time, GSTR-6A period, amount per tax head |
| Invoice matched/mismatched against purchase register | Match status, variance amount if mismatch, user who ran reconciliation, date/time |
| Invoice classified | Classification assigned, rule applied or manual override, user, date/time, approval if required |
| Custom ratio applied | Ratio type, basis (turnover/headcount/custom), values used, deviation from statutory method, approver |
| Allocation computed | Input data (turnover percentages), computed credit per unit, tax head conversion applied |
| ISD invoice generated | Invoice number, recipient GSTIN, credit amount, tax head, date/time |
| GSTR-6 draft reviewed | Reviewer name, review date/time, tables confirmed, notes added |
| Pre-filing validations run | Validation set executed, pass/warning/error count, errors listed with table reference |
| Errors corrected | What was changed, original value, corrected value, user, date/time |
| GSTR-6 filed | Filing date/time, ARN received, total credit distributed per tax head |
| GSTR-2A reflection confirmed | Per recipient unit: date reflected, amount, tax head |
| GSTR-3B claim confirmed | Per recipient unit: GSTR-3B filing date, amount claimed, Table 4(A)(5) |
| Exception flagged | Exception bucket, invoice reference, amount, recipient GSTIN, date flagged |
| Exception assigned | Assigned to team member, due date, priority level |
| Exception resolved | Resolution action, date/time, user, notes, follow-up actions if any |
| Supplier contacted | Contact date, subject (missing GSTR-1 / wrong invoice value), response received, outcome |
| ISD credit note issued | Credit note number, reason, recipient GSTIN, amount, period, linked to original ISD invoice |
| GSTR-6 amendment filed | Amendment period, original value, corrected value, reason, ARN of amended return |
| Recipient query received | Query date, unit GSTIN, query text, assigned to, resolution date |
| Notice received | Department notice reference, date received, items queried, response deadline |
| Notice response prepared | Response date, documents cited from ledger, submitted by |
Audit Trail Properties
A compliance-grade audit trail has specific properties that make it defensible in a department scrutiny or court proceeding:
- Immutable: Once an entry is written to the audit trail, it cannot be edited or deleted. Corrections are made as new entries that reference the original – not by overwriting the original.
- Timestamped: Every entry carries a server-side timestamp – not the user’s local machine time. This prevents backdating.
- User-attributed: Every action is linked to the user who performed it, with their name, login ID, and role. If multiple people worked on the same GSTR-6 preparation, the trail shows exactly who did what.
- Linked: Entries are linked across the lifecycle. The audit trail entry for a GSTR-6 filing links back to the classification decisions, ratio computations, and pre-filing validation results that produced it. The trail entry for an exception links to the GSTR-6 entry that created it and the resolution action that closed it.
- Exportable: The audit trail can be exported in structured formats – PDF for human review, Excel for data analysis, or JSON for system integration. Exports are timestamped and logged as export events themselves.
- Searchable: The trail can be filtered by period, invoice reference, recipient GSTIN, user, event type, or exception status. This allows targeted extraction for any specific query without manually scanning the full history.
How the Audit Trail Supports Departmental Scrutiny
GST scrutiny of ISD compliance typically takes one of three forms: a scrutiny notice under Section 61, a departmental audit under Section 65, or an investigation under Section 67. Each has different documentation requirements – but the Central ISD Ledger and its audit trail address all three.
Section 61 Scrutiny Notice
A Section 61 scrutiny notice is issued when the tax officer identifies a discrepancy in a filed return. For an ISD, the most common triggers are:
- Mismatch between credit distributed in GSTR-6 and credit reflected in recipient GSTR-2A.
- A recipient unit claiming more ITC than the ISD distributed.
- Credit distributed in GSTR-6 not appearing in the corresponding GSTR-6A data from the supplier.
- Ineligible credit distributed in Table 5 subsequently claimed by the recipient unit as eligible.
For each of these triggers, the Central ISD Ledger provides the complete response package:
| Scrutiny Trigger | Ledger Evidence Available | Audit Trail Support |
| GSTR-6 vs GSTR-2A mismatch | Invoice-level drill-down showing GSTR-6 entry vs GSTR-2A reflection date | GSTR-6 filing timestamp confirms credit was filed before GSTR-2A was generated; timing explains the gap |
| Recipient over-claim | Unit-wise distribution view showing amount distributed vs amount claimed | Reconciliation notes show whether the over-claim was flagged, when, and what action was taken |
| Credit in GSTR-6 not in GSTR-6A | Receipt ledger showing purchase register entry vs GSTR-6A status | Supplier follow-up log shows attempts to get supplier to file; classification decision predates GSTR-6 filing |
| Ineligible credit claimed as eligible | Distribution ledger showing ineligible flag on the specific ISD invoice | Audit trail shows alert was sent to recipient unit, when, and whether reversal was confirmed |
Section 65 Departmental Audit
A Section 65 audit is a structured examination of a taxpayer’s records by a GST officer. For an ISD, the auditor will typically examine:
- Whether the ISD is correctly registered and separate from the regular taxpayer registration.
- Whether all common service invoices have been routed through the ISD GSTIN.
- Whether credit has been distributed in the same month as receipt, without carry-forward.
- Whether the distribution ratio is consistent with the statutory turnover-based method or has been varied without documentation.
- Whether eligible and ineligible credit have been separately distributed and correctly flagged.
- Whether all recipient units have claimed their ISD credit and not over-claimed.
- Whether GSTR-6 has been filed on time for all periods under audit.
The Central ISD Ledger provides a structured response to every one of these examination points:
| Audit Examination Point | Ledger Response | Audit Trail Evidence |
| ISD registration correctness | Registration details in ledger header; ISD GSTIN vs regular GSTIN clearly distinguished | GSTR-6 ARNs confirm ISD-type filing for each period |
| All common invoices routed through ISD | Receipt ledger – all common service invoices with GSTR-6A match status | Classification decisions show every invoice explicitly classified as common/exclusive/ineligible |
| Same-month distribution | Running balance view – balance column shows zero for each month | GSTR-6 filing timestamp vs invoice receipt date confirms same-month distribution |
| Distribution ratio consistency | Allocation engine log – ratio used per invoice, financial year data source | Audit trail shows same ratio applied consistently; any variation has custom ratio approval entry |
| Eligible vs ineligible separation | Distribution ledger – Table 5 eligible vs ineligible flag per invoice per unit | Classification audit trail shows who flagged ineligible and on what basis |
| Recipient claim verification | Unit-wise distribution view – claim status per unit per period | Reconciliation notes show exceptions flagged, alerts sent, reversals confirmed |
| GSTR-6 filing timeliness | Period summary view – filing date vs 13th deadline for each month | GSTR-6 ARNs with filing timestamps for all periods |
A Section 65 audit that would previously require 3 to 5 days of document assembly by the CA team is reduced to a 1-day review when the Central ISD Ledger is available. The auditor can ask for any transaction, period, or unit – and the response is pulled from the ledger in minutes rather than days.
Section 67 Investigation
A Section 67 investigation is initiated when there is reason to believe that a taxpayer has suppressed transactions, filed incorrect returns, or claimed credit fraudulently. For an ISD, this is most commonly triggered by:
- Large discrepancies between GSTR-6 distributed credit and recipient GSTR-3B claims across multiple periods.
- Credit distributed to GSTINs that are found to be fake or non-existent.
- Supplier invoices in GSTR-6 that do not correspond to any actual service.
The audit trail’s immutability is most valuable in this context. If an investigation questions whether a distribution decision was genuine and made contemporaneously – or was retrospectively created to justify a credit claim – the server-side timestamps on the audit trail entries provide definitive evidence. Classification decisions made on the 3rd of the month, ratio computations on the 5th, GSTR-6 filed on the 12th, GSTR-2A reflected on the 15th – each step has a timestamp that cannot be altered.
One of the most important properties of the audit trail is its immutability. If a GST investigation alleges that records were created after the fact to justify a credit position, the audit trail’s server-side timestamps and linked event chain directly rebut that allegation. Spreadsheet logs, email threads, and manually maintained records cannot provide this assurance.
GST Audit Requirements – What the Law Requires You to Maintain
Understanding what the law actually requires an ISD to maintain for audit purposes is the foundation for designing the Central ISD Ledger structure correctly.
Section 35 – Maintenance of Accounts and Records
Section 35 of the CGST Act requires every registered person to keep and maintain accounts and records at their principal place of business. For an ISD, this translates to:
- Records of all inward supply invoices received.
- Records of all ISD invoices issued for distribution.
- Records of credit distributed to each recipient unit, by period and by tax head.
- GSTR-6 returns filed for each period, with the ARN.
- Documents supporting the allocation basis – turnover data, ratio computation, and any custom ratio justification.
Section 36 – Retention Period
All records must be retained for 72 months (6 years) from the due date of the annual return for the relevant financial year. Since ISDs do not file an annual return (GSTR-9 is not required for ISDs), the retention period is calculated from the last date of filing GSTR-6 for the last period of the financial year.
For FY 2024-25: GSTR-6 for March 2025 was due on April 13, 2025. Records from FY 2024-25 must be retained until April 13, 2031. The Central ISD Ledger and its audit trail must be searchable and exportable throughout this 6-year window.
Rule 56 – Manner of Maintaining Accounts
Rule 56 of the CGST Rules requires accounts to be maintained in the form of a register or electronic record. For an ISD, the key requirements are:
- A register of tax invoices received, with the supplier’s GSTIN, invoice number, date, taxable value, and tax amounts.
- A register of ISD invoices issued, with the recipient’s GSTIN, invoice number, date, and credit distributed.
- A register showing the basis of distribution – the ratio used and the supporting turnover data.
The Central ISD Ledger satisfies all three register requirements in a single, integrated system. The electronic record format is fully compliant with the GST Act’s requirements for digital records.
What Auditors Look For in ISD Records
Based on the structure of Section 65 audits and scrutiny notices for ISD entities, the documentation that auditors most frequently request falls into five categories:
| Audit Document Request | Where It Lives in the Central ISD Ledger |
| List of all supplier invoices received in a period | Receipt ledger – period filter |
| ISD invoices issued for a period with recipient GSTINs | Distribution ledger – period filter, all units |
| Basis for credit distribution ratio | Allocation audit trail – ratio type, turnover data source, financial year, computation |
| Evidence that eligible and ineligible credit were separated | Distribution ledger – eligible/ineligible flag per invoice; GSTR-6 Table 5 vs Table 8 mapping |
| Proof of same-month distribution | Running balance view – balance zero for each period; filing timestamp vs receipt date |
| Evidence of GSTR-6 timely filing | Period summary – filing dates and ARNs for all periods |
| Recipient unit claim verification | Unit-wise distribution view – claim status and GSTR-3B confirmation |
| Amendment history | Amendment audit trail – original filing, what changed, when, why, ARN of amended return |
| Documentation for custom ratio deviation | Allocation audit trail – custom ratio entry with approver and documented business reason |
| Reconciliation notes for any exceptions | Reconciliation notes log – exception type, resolution, date, responsible person |
Audit Trail vs Forensic Trail – Understanding the Difference
These two terms are often used interchangeably, but they serve different purposes in ISD compliance.
| Dimension | Audit Trail | Forensic Trail |
| Primary purpose | Operational accountability – who did what and when during normal compliance workflow | Dispute resolution and investigation – reconstructing the full chain of events for any transaction |
| Scope | Actions taken on the ISD platform | Complete lifecycle of every credit entry from supplier invoice to recipient claim |
| Depth | Event log with timestamp and user | Event log plus linked data at each event – values, sources, decisions, outcomes |
| Use case | Internal review, process improvement, compliance confirmation | Department scrutiny, Section 65 audit, SCN response, litigation support |
| Accessibility | Compliance team internal view | Exportable, structured, suitable for submission to authorities |
| Immutability | New entries only – cannot edit existing entries | Same – with additional hash or checksum protection in some platforms |
| Retention | 72 months minimum (Section 36) | Same – but forensic trail is often retained longer for litigation risk |
The Central ISD Ledger maintains both layers. The audit trail handles operational accountability. The forensic trail handles investigation and dispute resolution. For most compliance purposes, the audit trail is sufficient. When a department notice arrives or a dispute escalates, the forensic trail is what matters.
Ledger and Audit Trail in Action – Use Cases
GST Department Scrutiny Notice on ISD Distribution
A GST officer issues a scrutiny notice to the ISD entity for FY 2024-25. The notice queries three specific items: (a) credit distributed to Unit C in October 2024 appears higher than the turnover ratio would support, (b) a supplier invoice dated August 2024 was distributed in November 2024, and (c) one unit claims it did not receive a particular ISD credit that GSTR-6 shows as distributed.
Response from the Central ISD Ledger:
- Item (a) – Higher distribution to Unit C: The allocation audit trail for October 2024 shows that Unit C was onboarded in July 2024 with no preceding year turnover. The platform switched to current year turnover as per Rule 39, which was 45% at the time of filing. The ratio is documented with the financial year data source and the approval log. The statutory basis is clear.
- Item (b) – August invoice distributed in November: The receipt ledger shows the August 2024 invoice. GSTR-6A reflection date: November 3, 2024 (supplier filed GSTR-1 late). The supplier follow-up log shows three contacts between August and October before the supplier filed. The distribution followed GSTR-6A reflection, as required.
- Item (c) – Unit claims no credit received: The distribution ledger shows ISD invoice number ISD/2024-25/0187 for the unit’s GSTIN, distributed in GSTR-6 Table 5 for October. GSTR-2A reflection confirmed on November 15. However, the reconciliation notes show a Bucket 2 exception (GSTR-2A reflected but not claimed). An alert was sent to the unit’s CA on November 18. The unit’s GSTR-3B for December shows the credit was claimed in that month. Complete resolution record available.
What would have taken the CA team 3 days to reconstruct from spreadsheets and email threads is responded to in 4 hours. The response is structured, referenced, and documented – not reconstructed.
Internal Annual Audit by Statutory Auditor
The statutory auditor requests a reconciliation of all ISD credit distributed in FY 2024-25 against ITC claimed by recipient units, with documentation of any discrepancies and their resolution.
Response from the Central ISD Ledger:
- Export the annual reconciliation report from the period summary view: total credit received (by tax head), total distributed (by unit), total claimed in GSTR-3B, total exceptions, total resolved, total outstanding.
- For each outstanding exception: exception type, amount, unit GSTIN, resolution status, and projected impact on ITC for the group.
- For any ISD credit notes issued: original distribution reference, credit note reason, unit-wise recovery, net credit after credit notes.
- For any GSTR-6 amendments: original vs corrected values, amendment date, reason.
The auditor reviews the export, selects three random invoices for deep verification, and uses the invoice-level drill-down to trace each from supplier invoice to recipient claim. The audit is completed in a day, not a week.
Group Tax Head Monthly Review
The group tax head wants a monthly dashboard view of ISD compliance health across all three ISD registrations in the group.
Central ISD Ledger dashboard shows:
- ISD 1 (Mumbai): 45 invoices, Rs 8.2 lakh distributed, GSTR-6 filed on 12th, 3 open exceptions (all Bucket 2 – unclaimed), total unclaimed credit Rs 87,000.
- ISD 2 (Bangalore): 28 invoices, Rs 4.5 lakh distributed, GSTR-6 filed on 11th, 1 exception (Bucket 4 – supplier credit note pending ISD credit note issuance), Rs 23,000 pending recovery.
- ISD 3 (Delhi): 12 invoices, Rs 2.1 lakh distributed, GSTR-6 filed on 13th, 0 exceptions.
In 5 minutes, the group tax head has a complete picture of the group’s ISD compliance health, open financial risks, and pending actions – across all registrations, in one view.
The Central ISD Ledger on Cygnet’s Platform
Cygnet’s GST compliance platform maintains the Central ISD Ledger as a live, continuously updated record connected to the allocation engine, GSTR-6 filing module, reconciliation engine, and ERP. The ledger is not a periodic report – it is a real-time view that updates as each compliance event occurs.
Platform Capabilities
| Ledger and Audit Trail Need | How Cygnet Handles It |
| Receipt ledger | Auto-populated from GSTR-6A sync; purchase register match status updated daily |
| Distribution ledger | Populated by allocation engine; every ISD invoice linked to original supplier invoice and GSTR-6 table entry |
| Reconciliation notes | Exception log auto-generated; resolution notes captured in structured format |
| Running balance view | Monthly credit flow summary with same-period distribution compliance flag |
| Unit-wise distribution view | Per-unit credit position with GSTR-2A and GSTR-3B claim status |
| Invoice-level drill-down | Complete lifecycle chain from supplier GSTR-1 to recipient GSTR-3B |
| Period summary | Filing date, ARN, exception count, claim confirmation status per GSTR-6 period |
| Audit trail | Immutable, timestamped, user-attributed event log for every compliance action |
| Forensic trail export | Structured PDF or Excel export for any invoice, unit, or period range |
| Section 36 retention | 72-month searchable archive; no data purge without explicit compliance review |
| Notice response support | Direct export of ledger evidence for SCN response; documents labelled per notice item |
| Multi-ISD dashboard | Group-level view across all ISD registrations under the same PAN |
| Annual reconciliation report | Full year credit distributed vs claimed summary ready for statutory audit |
| Role-based access control | Tax team, CAs, auditors, and recipients each see the view appropriate to their role |
What This Means for Different Stakeholders
- Group tax head: One screen shows the health of all ISD registrations – credit flow, exceptions, filing status, and financial risk outstanding.
- ISD compliance team: Daily work list driven by the ledger – which invoices need classification, which exceptions need resolution, which supplier needs follow-up.
- CA managing the ISD: GSTR-6 preparation and filing directly from the ledger; pre-filing validation confirms all ledger entries are clean before submission.
- Recipient unit CA: Unit-level view of credit distributed, reflected, and claimed; query interface links directly to the ledger for instant response.
- Statutory auditor: Annual reconciliation export in structured format; drill-down access for sample verification; no document assembly required.
- Department audit officer: Structured export for any audit query; complete chain from supplier invoice to recipient claim; audit trail with immutable timestamps.
For a group entity with 3 ISD registrations, 15 recipient units, and 80 monthly invoices, Cygnet’s Central ISD Ledger provides what the GST portal does not: a single, unified, continuously updated record of the group’s complete ISD credit lifecycle – from the first GSTR-6A sync of the year to the last recipient unit’s GSTR-3B claim confirmation.
What Happens Without a Central ISD Ledger
Most ISD entities that rely on manual processes or basic spreadsheets discover the cost of the absence only when a scrutiny notice or audit arrives.
| Without Central ISD Ledger | With Central ISD Ledger |
| 12 separate GSTR-6 filings in 12 separate portal sessions – no consolidated view | Single ledger view across all 12 months, all units, all tax heads |
| Ratio computation in Excel with version control issues; no record of who made which change | Allocation audit trail shows every ratio decision with user and timestamp |
| Ineligible credit tracked informally; risk of units wrongly claiming | Ineligible flag on every distribution; unit alerts auto-generated |
| Supplier follow-up via email with no structured log | Follow-up log in reconciliation notes; outcome tracked to resolution |
| Exception detection depends on team spotting mismatches manually | Reconciliation engine runs automatically; exceptions classified and assigned |
| SCN response takes 3-5 days to reconstruct from spreadsheets and emails | SCN response generated in hours from ledger exports |
| Annual reconciliation for statutory audit is a 2-week exercise | Annual report generated in one click from ledger period summaries |
| Section 65 audit requires manual assembly of all ISD records | Audit evidence packaged from ledger drill-down and audit trail in one day |
| ITC leakage from unclaimed credit often discovered only at year-end | Unclaimed credit flagged monthly; Section 16(4) deadline tracked per invoice |
| No consolidated view of ISD health for group management | Multi-ISD dashboard visible to group tax head in real time |
Best Practices for Maintaining the Central ISD Ledger
- Treat the ledger as a live document, not a monthly report. Classification decisions, reconciliation notes, and exception resolutions should be entered as they happen – not at month-end. A ledger that is only updated at filing time is a filing-time record, not an audit trail.
- Ensure every classification decision is documented at the time it is made. If an invoice is classified as ineligible, the reason must be logged immediately. A classification log that says ‘blocked under Section 17(5) – club membership’ is defensible. One that says ‘marked ineligible’ is not.
- Document every deviation from the statutory turnover ratio. Custom ratios are legitimate but require contemporaneous documentation. The approver, the basis, and the business reason must be in the ledger at the time the ratio is applied – not added after a notice arrives.
- Review the running balance view every month on the 14th. A non-zero balance after GSTR-6 is filed means eligible credit was not distributed in the month of receipt. This is a compliance failure that needs immediate investigation.
- Confirm recipient claims monthly, not annually. The unit-wise distribution view should show all credit claimed within 30 to 45 days of distribution. Unclaimed credit that ages past 90 days without a documented reason is a leakage risk.
- Export and store a period snapshot after every GSTR-6 filing. The live ledger is continuously updated. A period snapshot captures the exact state of the ledger as of the filing date – useful if a question arises about what was known at the time of filing.
- Link every notice to the specific ledger entries it references. When a department notice is received, tag the notice reference to the relevant ledger entries immediately. This builds the notice response package concurrently with the compliance workflow.
Frequently Asked Questions
Is there an Electronic Credit Ledger for ISD registrants on the GST portal?
No. The GST portal explicitly does not maintain an Electronic Credit Ledger for ISD registrants. This is confirmed in the GST portal FAQs. The ISD’s function is purely distribution – it does not hold credit of its own, so no electronic credit balance is maintained by the portal. The Central ISD Ledger is a platform-level construct that fills this gap by providing a consolidated view of receipts, distributions, and reconciliation status.
What is the difference between GSTR-6A and the receipts section of the Central ISD Ledger?
GSTR-6A is a read-only, auto-generated statement on the GST portal showing invoices that suppliers have filed in their GSTR-1. It is the portal’s view of credit available to the ISD. The receipts section of the Central ISD Ledger includes GSTR-6A data but adds the ISD’s purchase register match status, classification decision, mismatch reason if any, and supplier follow-up log. It is the complete view of what arrived and what was done with it – GSTR-6A is only the source data.
Can the Central ISD Ledger be submitted directly to a department officer during an audit?
Yes – the ledger can be exported in structured formats and submitted as documentary evidence. The export includes the invoice-level drill-down, the allocation audit trail, the reconciliation notes, and the GSTR-6 filing records for each period. The export is timestamped and reflects the actual data in the system, making it suitable for submission under Section 71 of the CGST Act (access to business premises and records for officers).
How long must the Central ISD Ledger data be retained?
Section 36 of the CGST Act requires records to be maintained for 72 months (6 years) from the due date of the annual return for the relevant financial year. Since ISDs do not file GSTR-9, the reference date is typically the last GSTR-6 filing date for the financial year. All ledger data – receipts, distributions, reconciliation notes, and audit trail – must be searchable and exportable throughout this 6-year retention window.
Does the Central ISD Ledger cover multiple ISD registrations under the same group?
Yes. For a group with multiple ISD registrations across states, the platform maintains a separate ledger for each ISD GSTIN. A consolidated multi-ISD dashboard is available for the group tax head, showing the combined credit flow and exception status across all registrations. Each ISD ledger is independently maintained and can be audited separately.
What happens to the audit trail when a GSTR-6 amendment is filed?
The original GSTR-6 filing and its audit trail are preserved unchanged. The amendment creates a new audit trail entry that references the original, shows what changed and why, and records the ARN of the amended return. The distribution ledger is updated to show the revised credit amounts per unit, with the original amounts preserved in the amendment history. The complete before-and-after record is available for any period where an amendment was filed.
Conclusion
The GST portal gives an ISD a filing interface. It does not give an ISD a ledger. The difference is significant.
A filing interface records what was submitted. A ledger records why, on what basis, with what supporting data, in what sequence, by whom, and what happened after. In the context of ISD compliance – where credit allocations affect the ITC of 10 to 20 recipient units, where the statutory basis must be consistently applied and documented, and where the mandatory ISD framework from April 2025 has brought the mechanism under intensified regulatory focus – a ledger is not optional.
The Central ISD Ledger captures the three pillars of ISD compliance in a single view: what credit was received (receipts), what was done with it (distributions), and how every discrepancy was identified and resolved (reconciliation notes). The audit trail records every action in that workflow with immutability, user attribution, and server-side timestamps.
Together, they answer the question that every department officer, statutory auditor, and group tax head eventually asks: Can you show me, completely and contemporaneously, the lifecycle of every rupee of ISD credit from the moment a supplier filed their GSTR-1 to the moment each recipient unit confirmed the claim in their GSTR-3B?
With the Central ISD Ledger, the answer is yes – pulled from a screen, not reconstructed from a filing cabinet.