# How to Reconcile Issued and Cancelled Documents for GST Reporting

Reconcile issued and cancelled documents by maintaining a complete register of each relevant document type and numbering series, identifying genuine cancellations and comparing the resulting counts with the outward-supply records. A sales-value reconciliation alone cannot establish that document reporting is complete.

GSTN’s GSTR-1 workflow includes Table 13 for documents issued. Its May 2025 controls made this table mandatory in the specified circumstances where outward data is reported. Prepare it from evidence rather than entering approximate counts merely to pass the filing validation.

## Define the series and period

Consider an illustrative Bhopal office-supplies business using one invoice series for wholesale and another for its retail counter. It also maintains separate credit-note and debit-note series. Each series needs a clear identity and record of numbers used during the period.

Record GSTIN, document type, series, first and last number as relevant, total documents, cancellations and net issued count. Preserve dates and source-system references. Different branches under the same GSTIN may use distinct series that must all reach the return preparation team.

Do not combine unlike prefixes simply because their numeric portions overlap. `WS/001` and `RT/001` can be different valid documents. A matching routine that strips both prefixes may falsely call them duplicates or undercount the population.

## Work through the count arithmetic

Suppose the wholesale series runs from `WS/001` to `WS/080`, with 80 documented numbers in the relevant population and five valid cancellations. The illustrative net issued count is 75. A separate retail series has 120 documents and two cancellations, giving 118 net issued.

| Illustrative series | Total documents | Cancelled | Net issued |
|---|---|---|---|
| Wholesale invoices | 80 | 5 | 75 |
| Retail invoices | 120 | 2 | 118 |
| Credit notes | 6 | 1 | 5 |

The credit notes are a separate document category, not five more sales invoices. Counts and taxable values answer different questions, so do not expect the Table 13 total to equal the number of positive-value rows in a sales ledger automatically.

The arithmetic also assumes the source population is understood. A numeric interval does not prove that every number within it was issued. Investigate gaps and system allocation practices before treating every missing number as a cancelled invoice.

## Distinguish cancellation from later adjustment

A cancelled invoice is different from a completed supply followed by returned goods or a price correction. The latter may require a credit note, amendment or other appropriate treatment while preserving the original invoice history.

For the Bhopal business, an invoice issued in August and adjusted by a September credit note should not be retroactively relabelled as a September cancellation merely to reduce the current sales count. Track the documents according to their actual status, dates and applicable reporting process.

Likewise, an unused draft or abandoned order should not be called an issued tax invoice without examining the system and source records. Keep the reason for each status so a reviewer can understand what happened.

## Verify cancellations with evidence

Retain the cancelled document or system record, approval, reason and any related customer communication. Check whether a replacement invoice was issued and link it. A cancellation followed by replacement should not cause both to remain active in the reporting export.

Where e-invoicing applies, the IRN status and the accounting document status need reconciliation. Do not assume that cancelling an internal record automatically completes every external cancellation requirement or that a return edit changes the e-invoice status.

Review bank receipts and delivery records for invoices marked cancelled. If goods were delivered and money collected, the status may require investigation. A convenient cancellation flag should not make real activity disappear from the return population.

## Reconcile counts in both directions

Trace issued documents to sales or other appropriate records, and trace recorded sales back to valid documents. One-direction testing can miss invoices never entered in the accounts or ledger entries without a proper source document.

Explain gaps by series, number and reason. A monthly log can show whether a number was reserved, not generated, cancelled, replaced or missing evidence. Assign unresolved items to the responsible billing team rather than carrying a generic difference indefinitely.

Do not close a count mismatch by changing the first or last serial number without evidence. That can conceal the missing documents and create problems when the next period begins from a different sequence.

## Check the final return population

Reconcile the document summary with the final outward data after all notes, corrections and cancellations are processed. An old count prepared before a batch of cancellations may no longer describe the filed records.

For QRMP, understand the relationship between period documents, IFF-furnished details and quarterly reporting. A document reported through IFF does not become a second issued invoice at quarter end. Keep reporting status separate from document existence.

Review the applicable Table 13 categories and live controls for GSTR-1 or GSTR-1A. A successful validation is not proof that the counts are complete; it only shows that the entered data passed the system’s checks.

Document the source of the count. A billing-system report, manual invoice book and spreadsheet can use different meanings for “generated” or “issued.” Agree which status supports each reported category and reconcile the alternatives. This is particularly important when a draft receives a reserved number before approval. Clear status definitions prevent staff from labelling every reserved number as either an active invoice or a cancellation without evidence.

## Preserve the control for the next month

Archive the series register, cancellation log, reconciliation, final summary and filing acknowledgement together. Carry open gaps forward with named owners and closure evidence. Review repeated cancellations or unexplained numbering breaks as process issues.

A strong document reconciliation explains every relevant series without erasing history. Establish the population, substantiate cancellations and connect net issued documents with the records of actual activity. The resulting summary becomes a useful completeness control rather than a last-minute count entered on filing day.

## Sources and references

- [GSTN: Creation and submission of GSTR-1](https://tutorial.gst.gov.in/userguide/returns/Creation_of_Outward_Supplies_Return_in_GSTR-1.htm)
- [GSTN: HSN Table 12 and document Table 13 advisory, May 2025 period onward](https://tutorial.gst.gov.in/downloads/news/updated_advisory_hsn_table12_25042025.pdf)
- [GSTN: GSTR-1 and GSTR-1A FAQs](https://tutorial.gst.gov.in/userguide/returns/GSTR_1.htm)