The fear with AI bookkeeping is simple: it misclassifies an entry, a return goes out wrong, and your client gets a notice. OnGravy is built so that can’t happen quietly. A human approves every statutory number, every entry is fingerprinted and audit-trailed, and any mistake reverses in the open — never in secret. This page is exactly how, with nothing claimed that the product doesn’t already do.
“One-click filing” is the scariest promise on any accounting site — so we gated it. OnGravy’s filing engine will refuse to submit a GST or TDS return that hasn’t been approved. The AI never reaches the portal on its own.
You see the full return — every table, the net tax payable — computed from your own books. Nothing is a black box.
The return sits at status “approved” only after a human marks it so. The filing engine checks this first and rejects anything that isn’t approved.
Filing needs a live OTP from the government portal, tied to your GSTIN — a second human gate the AI cannot pass alone.
“File — this cannot be undone.” One last explicit click before anything is submitted.
✓Reads bills and invoices, drafts the double-entry behind them
✓Suggests HSN/SAC codes and GST rates from the item and description
✓Reconciles GSTR-2B against your purchase register overnight
✓Flags anomalies — unusual amounts, new parties, likely duplicates
✓Prepares returns so the numbers are ready to review
✕File a statutory return on its own — approval + OTP are required
✕Post silently over your correction — every draft is editable
✕Hide its working — every entry shows where it came from
✕Lock you out — full export and drill-down to every voucher, always
✕Overrule a human — a person’s decision is always final
Each journal entry gets a deterministic hash of its contents. Change one rupee after the fact and the fingerprint no longer matches — silent edits are detectable.
Every approval, edit request, and decision is written to an append-only log — actor, timestamp, comment. Records are added, never overwritten.
Editing an already-posted entry doesn’t just happen — it raises an edit request that an owner/admin/CA approves. The before/after is preserved.
Close a period and it locks. Postings into a locked period are refused; a correction has to be made in the open, in the current period.
A ready-to-hand statutory audit-trail report of every edit — exactly what an auditor asks for under the Companies (Accounts) Rules.
Your books are yours. Export to Excel or Tally XML, drill into any party ledger or voucher. No lock-in, no black box.
The honest answer to “what if the AI gets it wrong?” isn’t “it won’t.” It’s “you’ll catch it before it counts, and if something does slip, the fix is clean and on the record.”
The anomaly net (Reviews) routes an entry to a human when the amount is ≥ 3× the baseline for that party, it’s the first transaction with a new party, or it looks like a duplicate. It waits for a decision before it counts.
Reject an entry and OnGravy posts a counter-entry that nets the original to zero. The books stay balanced, both rows survive in the audit trail, and the rejection reason is recorded.
If a filed return needs a correction, the standard amendment path applies (e.g. GSTR-1A). The original filing and the correction both stay in the trail — nothing is erased.
Everything above is shipped and verifiable inside your own account — not a roadmap promise. We don’t quote an accuracy figure we haven’t measured on real books, and where a safeguard depends on your setup (like connecting your GST portal), we say so. The point of an audit-grade ledger is that you never have to take our word for it — you can check every number yourself.
Create an account, run one entity, and check the audit trail yourself. The approval gates and reversals are on from day one.