How a $1.2B Specialty Chemicals Maker Closed Its Books in 3 Days Instead of 11 — Across SAP, Oracle and NetSuite

High-volume, well-defined entries — accruals, prepaid amortisation, fixed-asset depreciation, FX revaluation, intercompany eliminations, bank reconciliations, and any journal where the supporting evidence and posting rules are clear. Material, judgement-heavy or unusual entries always route to a human controller.

The entry routes to a human controller inside their ERP’s approval workflow, with the proposed journal, the agent’s reasoning trace, every cited supporting document, and a confidence breakdown attached. The controller either approves, edits or rejects — and every override is captured for the next retraining cycle.

Yes. Every agent action — every ERP call, every reasoning step, every controller override — writes an immutable audit entry. The close-cycle audit pack assembles itself as the close runs. SOC 2 Type II controls in place across the full pipeline. The manufacturer in this case ran their first year on the platform with zero SOX 404 ITGC findings.

Twelve weeks to a single-plant production pilot. Twenty-two weeks for the full 14-plant rollout the manufacturer ran. Year-one outcomes — 11→3 day close, $850K savings, zero SOX findings — landed by month 12.

Yes. Native integration with SAP S/4HANA and ECC (OData, IDoc, BAPI), Oracle E-Business Suite and Cloud ERP (REST, concurrent programs), NetSuite (SuiteScript, SuiteTalk), Workday Financial Management (REST/RaaS), and Sage Intacct (API). We’ve also integrated bespoke ERPs where the customer’s data model required it — the agent crew is ERP-portable by design.

Every controller override is captured, labelled and fed into a weekly retraining job. Per-ERP, per-GL-account reconciliation accuracy and post-failure rates are tracked on dashboards, so confidence thresholds can be tuned where the agents are over- or under-posting. Most engagements see auto-post rate climb another 5–10 percentage points in the first six months after launch.