The discount field that broke a GST return (an illustrative case)

Picture a mid-sized components maker in Tiruppur running ERPNext. Sales asks for a new field on the sales invoice: a scheme discount for dealers who hit a quarterly target. An AI agent is asked to add it. In minutes, the field exists, the print format shows it, and the sales team is happy.

What went wrong

The new field reduced the amount the dealer paid, but it was added after tax was calculated. Invoices now showed one taxable value in the books and another on the e-invoice that the Invoice Registration Portal had already accepted. Nobody noticed for a month, because every individual invoice looked fine.

The mismatch surfaced when the accountant prepared GSTR-1. Outward supplies in the return no longer agreed with the ledger. Correcting it meant credit notes, amended e-invoices and an uncomfortable conversation with the company's chartered accountant, roughly three weeks of rework for a change that took minutes.

Why a review would probably have missed it

A person reviewing the change would have seen a sensible new field with a sensible label. The problem was not in the field; it was in how the field interacted with tax calculation, the e-invoice payload and the return. You find that kind of fault by running the change against real data, not by reading it.

The checks that would have caught it

elan1 Work is designed so that an ERP change is tested on a copy of your own data before it goes live. Each change runs through 8 checks, from ledger balance to audit trail. In this case, three of them matter:

• Ledger integrity: last month's invoices are replayed with the new field, and the trial balance must still tie.
• Tax consistency: taxable values on the replayed invoices must match what the e-invoice payload would report.
• Audit trail: the change itself must be recorded in a way that satisfies the MCA audit-trail rule.

The replay would have shown taxable values diverging on every invoice that used the scheme discount. The change would have been held, with the reason in front of the finance head, before any dealer saw a new invoice.

The audit trail is not optional

Since 1 April 2023, companies in India must use accounting software that records an audit trail of every change and cannot be switched off, under Rule 3(1) of the Companies (Accounts) Rules, 2014. Auditors report on it under Rule 11(g) of the Companies (Audit and Auditors) Rules, 2014. The rule was written with people in mind. It applies just as much when the edit comes from an agent.

A person still commits the change

Even when every check passes, the change goes live only when a person you name approves it, and it can be reversed for 30 days, with the reversal checked too. The agent drafts it. A person you name commits it.