Beyond Tally: Running an AI-Assisted Audit When Your Client Runs SAP, Zoho, or a Custom ERP
Nearly every AI-audit demo you'll sit through opens with a Tally connection. That makes sense — Tally is the dominant ERP among the small-and-mid-size clients most CA firms audit — but it also means the question comes up in almost every serious evaluation conversation: "To what extent does this work for a non-Tally client?" If your firm's client base includes even a handful of SAP, Zoho Books, NetSuite, Busy, or genuinely custom-built ERP users, that question isn't academic. It's the difference between a tool you can actually deploy across your whole practice and one you can only use for a third of your engagements.
Why "Tally-first" AI tools quietly become "Tally-only" in practice
A live database connector is the fastest, cleanest way to pull a trial balance and general ledger — which is exactly why most AI audit tools build that path first and market it hardest. The problem is what happens next: a client on SAP S/4HANA, or a mid-market ERP with no public connector, or a genuinely bespoke system a founder built a decade ago, simply doesn't have that door to walk through. If a vendor's answer to "what about SAP?" is "it's on our roadmap," you're being told, politely, that the tool doesn't work for that client yet.
The actual answer: standard reports, not a live connection
The workable path for non-Tally ERPs doesn't require a live database connector at all — it uses the standard exports every ERP already produces. For SAP specifically, that means the reports your team is already pulling for manual work: FBL3N (line item display), F.01 (financial statement version), FS00 (G/L account master). For NetSuite, saved searches. For Busy, the Day Book, Trial Balance, and Account Master. For genuinely custom systems, the fallback that covers almost anything: a Day Book, Trial Balance, and Ledger Master in Excel.
The important design point here is what happens after the upload. On CORAA, the Engagement Setup module treats the Tally connector and the Excel upload path as two doors into the exact same room — once the data lands, the interface, the ledger classification, and every downstream working paper are identical regardless of which ERP it came from. A partner reviewing a working paper can't tell, and doesn't need to, whether the underlying client runs Tally or SAP.
What "Excel upload" actually means in practice
This isn't a euphemism for "manually re-enter your ledger." The auditor exports the standard reports their ERP already produces — nothing bespoke, nothing the client's IT team needs to build — and uploads them. From there, ledger classification runs exactly as it would on a live Tally feed: every ledger gets an AI-suggested classification the auditor confirms or overrides, never auto-applied. Zoho Books gets a more direct path still — a native OAuth connection, not a file upload, alongside Tally's live connector.
The one honest gap as of today: Microsoft Dynamics 365 and QuickBooks Online aren't yet supported through either path — both are scheduled for upcoming releases. For any other system that can produce a Day Book, Trial Balance, and Ledger Master in Excel, the generic upload path works today, not "on the roadmap."
Why this matters more than it looks
The firms who raise this question aren't being difficult — they're usually the ones with the most complex client rosters, the ones auditing manufacturing companies on SAP or fast-growing startups that migrated off Tally the moment they outgrew it. For those firms, an AI audit tool that only works on Tally isn't a productivity tool, it's a tool for one-third of the practice and business as usual for the rest. The test worth applying to any vendor: ask them to actually run a real ledger from your most complex non-Tally client through their system in the demo, not a Tally sample dataset that makes every tool look identical.
Frequently Asked Questions
Does an AI audit tool need a live connection to work with SAP or other ERPs?
No — the practical path is standard report exports (trial balance, ledger, journal detail) that any ERP already produces, uploaded rather than pulled live. The downstream working papers are identical either way.
Is Excel upload a second-class experience compared to the Tally connector?
It shouldn't be. On CORAA, the interface and every downstream working paper are identical regardless of which ingestion path was used — a reviewer can't tell which ERP the data came from.
Which ERPs does CORAA currently support?
Tally Prime via a live connector, Zoho Books via OAuth, and SAP, NetSuite, Busy, and Marg via standard-report Excel upload. MS Dynamics 365 and QuickBooks Online are scheduled for upcoming releases.
What if my client's system isn't on that list at all?
Any system that can produce a Day Book, Trial Balance, and Ledger Master as an Excel export can ingest through the generic upload path — it doesn't need to be a named, pre-built integration.
Related: Engagement Setup module · Start a free trial