Filing week is a symptom, not a season
Every month, in thousands of finance departments, the same fire drill runs. Sales registers exported and re-keyed into a filing tool. Purchase data hunted across mailboxes and spreadsheets. Mismatches between the books and the return discovered at the deadline, when the only options are to hold the filing or eat the difference. Then the quarter-end version, with TDS. Then the year-end version, with everything.
The pain is real, but it is a symptom. The disease is architectural: the numbers you file live in a different system from the transactions that produced them, and a human bridges the gap by re-typing. Every re-keyed row is a chance for the invoice and the return to disagree, and every disagreement is discovered at the worst possible moment — filing week.
The cure is equally architectural: compute the returns from the posted documents themselves. This is the design principle behind compliance in xMatix, and this guide walks through what it means in practice — with checklists a finance controller can act on regardless of what system runs the books today.
The principle: filings fall out of operations
Picture your compliance surface as two columns. On the left, the operational documents your business posts every day: sale invoices, dispatches, purchase bills, expense lines, pay runs. On the right, the statutory artifacts each one owes: e-invoices, e-way bills, GSTR-1 and GSTR-3B, the 2B match and the ITC ledger, TDS and TCS with the 26AS reconciliation, salary TDS returns and Form 16.
In a re-keying shop, humans carry data from left to right, monthly, under deadline. In xMatix, the arrows are computed. GSTR-1 and GSTR-3B filing grids are built from posted sale documents; the ITC picture is built from posted purchases and expenses; TDS returns are built from posted bills and pay runs. Every line is stamped with its branch, business unit, and GSTIN off one chart of accounts, so a multi-GSTIN business slices its returns by registration without running parallel books. A Tax Center console ties the whole surface together — and any return line drills back to the source document, which is the answer to the auditor's favorite question.
No re-keying. The document you posted is the return you file.
GSTR-1 and 3B: get the source documents right
If returns are computed, return quality becomes document quality. The work moves from filing week to posting time — which is exactly where you want it, because posting time is when errors are cheap to fix.
- Validate at capture. GSTIN, PAN, and HSN are validated on every document in xMatix, and place of supply is determined by the system. A wrong GSTIN caught at invoicing costs a correction; the same error caught in a filing grid costs a follow-up cycle with the customer.
- Post everything, promptly. Unposted documents are invisible to a computed return. The discipline is daily posting, not monthly catch-up.
- Corrections as documents. Credit and debit notes are posted documents too, so they flow into the same grids — no side-spreadsheet of "adjustments to remember."
Controller's checklist — monthly, before the outward filing:
- All sale invoices, credit notes, and debit notes for the period posted — zero drafts pending.
- Documents with failed GSTIN/HSN validation cleared or corrected.
- GSTR-1 grid reviewed by GSTIN; 3B liability tied back to the ledger.
- Sample-drill three return lines to their source documents — if the drill works, the audit trail works.
ITC hygiene: 2B matching and the credits hiding in expense claims
Input tax credit is where compliance stops being a cost and starts being cash. Two disciplines matter.
Match against 2B, continuously
xMatix carries GSTR-2B matching and an ITC ledger, so the question "what have we claimed that our suppliers haven't reported?" has a running answer instead of a quarterly surprise. The operating rhythm: match monthly, chase the unmatched suppliers while the trail is warm, and let the ITC ledger — not a spreadsheet — be the record of what was claimed, reversed, and carried.
Stop leaking ITC through expenses
The most commonly abandoned credits are not on purchase bills; they are on employee expense claims — the hotel bill, the fuel invoice, the tooling bought on a company card. In xMatix, GST is captured line by line on expense claims: the CGST/SGST/IGST/cess split, ITC eligibility and category, blocked-credit reason where credit is barred, supplier GSTIN, place of supply, and HSN/SAC. Eligible lines debit input GST and feed the same GST analytics as purchases; blocked lines carry an explicit reason instead of a shrug. The credit either arrives in the ledger or is declined on the record — never lost in a claims pile.
Controller's checklist — ITC, monthly:
- 2B match run; unmatched suppliers listed and chased with a named owner.
- ITC ledger reconciled to the GL input-tax accounts.
- Expense-claim GST capture spot-checked: eligibility marked, blocked credits carrying reasons.
- Ineligible claims sampled — is "blocked" being used correctly, or as a default?
e-Invoicing and e-way bills: from the transaction, not after it
e-Invoicing and e-way bill generation in xMatix run from the transaction itself — the sale invoice and the delivery documents — not from a re-entered copy. That matters for two reasons. First, speed: goods do not wait at the gate for the back office. Second, consistency: an e-invoice generated from the posted invoice cannot disagree with the books, because there is only one set of numbers. The same holds on the road — as covered in our van-sales piece, even an invoice raised from a moving van is a posted document that carries its own statutory artifacts.
Controller's checklist — continuous:
- e-Invoice generation is part of the invoicing flow, not a batch job someone runs.
- Dispatches requiring e-way bills produce them from the delivery documents.
- Exceptions (failed generations) surface the same day, with an owner.
TDS and TCS: the quarter should hold no surprises
TDS discipline is set at bill entry, not at return time. In xMatix, vendor bills carry TDS section tagging when they are posted, so deduction happens where the liability is born and the quarterly picture accrues all quarter long. Form 26AS reconciliation then closes the loop from the other side — what deductors reported against you versus what your books say — so differences are investigated as routine, not archaeology.
Controller's checklist — quarterly:
- Vendor bills carrying the right TDS sections — sample by vendor category.
- Deposits tied to the ledger's statutory payables before the return.
- 26AS reconciled against books; every gap has a named explanation.
People compliance, same ledger
Salary TDS is usually the loneliest compliance stream, computed in a payroll silo and re-keyed twice. In xMatix, payroll posts to the same general ledger as everything else, and the statutory stream falls out of the runs: the salary income-tax engine computes both regimes on every run from one fact set, the quarterly salary TDS return is computed straight from posted pay runs with an e-return export file in the standard layout, and Form 16 certificates issue from a numbered register that stamps back onto the ledger. The return cannot disagree with payroll, because it is made of payroll.
Controller's checklist — payroll compliance:
- Pay runs posted before the return is computed — the return only sees posted runs.
- Statutory challans reconciled to the payable controls in the GL.
- Form 16 register complete against the employee roll; certificate numbers sequential.
What filing week looks like after the fix
None of this eliminates filing; it eliminates reconstruction. When returns are computed from posted documents, filing week compresses into a review: open the Tax Center, check that the period's documents are posted and validated, review the computed grids, clear the exception lists, file. The fire drill was never really about GST. It was about distance — between the transaction and the return, between the operation and the obligation. Close the distance to zero, and compliance becomes what it should have been all along: a property of well-posted books.