Compliance · for your CA

Compliance
that's just done.

The reason you have a part-time CA is that GST is a part-time job. It shouldn't be. The rules are knowable. The math is doable. We did both, from the first line of code, in software your CA will recognise.

India, from the first line of code.

Every Indian business runs two systems. One for what they actually do. One for what the government needs them to say they did. The gap between the two is what your CA bills you to close.

Most ERPs were not built for India. Compliance is bolted on, often as a separate module, sometimes as a separate company. Returns get prepared from exports. The exports lie a little. Somebody fixes the lies. Somebody else explains the fixes. It's a wonder anything gets filed on time.

Invariant is built for India in the only sense that matters: the kernel knows the rules. GST math, place-of-supply logic, e-invoice thresholds, e-way bill conditions, TDS sections, TCS conditions, MSME 45-day timing — these are invariants on the spine. They cannot be bypassed. They do not need to be re-checked at month-end. They were checked when the event landed.

What's ready, all the time.

Returns are not reports we generate. They are projections of the log that are always live. If you filed today, this is what you'd file.

GSTR-1.
Outward supplies, generated from invoices on the spine. Live JSON for the GST portal. Reconciled with e-invoice IRNs automatically — if the IRN doesn't match, the kernel flagged it before the invoice was issued.
GSTR-3B.
Summary, ITC, tax payable. Reconciled with GSTR-2B by the agent. Mismatches don't get hidden — they get raised. The agent proposes adjustments; your team approves.
GSTR-9 / 9C.
Annual return is a query, because every monthly return was a query of the same log. Reconciliation with audited financials is almost trivial, because the audited financials are the same data.
e-Invoice.
IRN generated for every invoice above the threshold the moment it's issued. QR codes on the printed invoice. Cancellations handled. The handler ack rolls back as an event; the IRN sits on the spine.
e-Way Bill.
EBN generated whenever a movement crosses the value or distance threshold. Validity tracked. Extensions, updates, cancellations all on the log. Vehicle and transporter details captured at dispatch, not back-filled.
TDS / TCS.
Deducted at source by section, with thresholds tracked per deductee. Quarterly returns (24Q, 26Q, 27Q, 27EQ) live. Form 16 and 16A generated. Lower-deduction certificates honoured. Reconciled with 26AS-equivalent data automatically.
ITC-04.
Job work in and out. Lot aging. The 12-month and 3-year clocks. Deemed supply triggers as scheduled events, not as audit-time surprises. Quarterly, half-yearly, or annual filing depending on your turnover — same data, different fold.
MSME 45-day rule.
Section 43B(h), tracked per vendor, per invoice, on the spine. The agent flags exposure before the deadline. The disallowance calculation, if it ever has to happen, is automatic — not a March 31st panic.

The portal is just a handler.

We talk to the GST portal, the e-invoice IRP, the e-way bill portal, TRACES. Every submission is an outbound effect. Every acknowledgement comes back as an event on the log. If the portal is down, we queue. When it returns, we send. You don't manage any of this.

When rates change, when forms change, when thresholds change — and they do, often — we update the rules. Your data doesn't move. Your books don't get recomputed in suspicious ways. The new rule applies to events from its effective date. The old rule still explains everything before it.

Your CA is a user, not an integration.

Most “GST tools” expect your CA to log into a separate dashboard, download a JSON, upload it to the GST portal, and explain whatever is wrong. That isn't a workflow. That's a relay race.

On Invariant, your CA logs into your company. They see what they need: returns ready to review, exceptions to clear, ITC mismatches to chase, late-fee exposure, draft GSTR-9. They sign off, with a proper audit trail, and the agent files. One workflow. One record. One person.

If you have a CA firm doing the books for you, give them access. They'll see less work and more leverage. The good ones will love you for it. The other ones will get nervous. You can decide what that means.

For your CA, specifically.

Returns that match.
GSTR-1 ties to GSTR-3B ties to your books ties to your e-invoice register. Not because someone reconciled them. Because they were never separate.
Reconciliations that finish.
2B vs 3B, ITC eligibility, TDS vs 26AS, e-invoice vs sales register. The agent runs them. Mismatches get raised with the underlying transactions. You finish the reconciliation in the afternoon, not over the weekend.
Notices, with context.
When a notice arrives, every transaction it references is one click away, with full history. Replies are drafted by an agent who has actually read the underlying events. You sign and send.
Statutory work, not data work.
Your CA stops being your data engineer. They go back to being your CA. Advisory, planning, structuring. The work that was worth their qualification.
A quiet pitch to CA firms reading this. Onboard your client to Invariant, and your firm becomes the leverage point — same client, ten times the throughput, ten times the surface to actually advise on. Talk to us about partner pricing.

File without dread.

Bring last quarter's GSTR data. We'll show you what filing looks like on Invariant by the end of the call. Bring your CA. We've yet to meet one who didn't immediately get it.