What does an AI agent's audit trail in finance record?

Key Takeaways

• The Transformance audit log records six fields per action: timestamp, what the system did, what the user did, who approved, the input and the confidence.
• 64% of companies expect auditors to review the control environment around their AI use in financial reporting in more detail (KPMG, 2024).
• The ERP proves what posted and when; the agent’s log explains why and who approved. An auditor needs both to agree.
• In every ERP covered here, a reversal undoes the clearing first or with it, and posts in an open period.
• Transformance can initiate a reversal and post it back to the ERP once a person approves, so the original and its correction both stay visible.

In This Article

• Key Takeaways
• What does an AI agent’s audit trail in finance record?
• Why is the ERP’s own log not enough for an auditor?
• What does one complete audit-log entry look like?
• Who approves what, and how does the log show it?
• How do you reverse a journal entry an AI agent posted?
• How does each ERP reverse a cleared payment?
• What stops a reversal from posting?
• What should you check in an AI audit-trail review?

What does an AI agent’s audit trail in finance record?

For every action, the Transformance audit log records six fields: the timestamp, what the system did, what the user did, who approved, the input and the confidence.

What the audit trail records, and where the rest lives

Illustrative entries; field labels as recorded by Transformance, ERP fields as your ERP names them.

An AI audit trail is the record of every agent action that lets a third party see what was proposed, on which evidence, and who allowed it to reach the ledger. “What the user did” records whether a person accepted, changed or rejected what the system did.

‍

‍

Auditors are already asking. Across 1,800 companies in 10 countries, 64% of financial reporting executives and board members expected auditors to conduct a more detailed review of the control environment around their use of AI in financial reporting, and 72% were piloting or using AI selectively (KPMG, 2024). What Transformance reads and writes in each ERP is mapped in what AR automation reads from and writes to the ERP.

Why is the ERP’s own log not enough for an auditor?

The ERP proves which document posted, when and under which user, but not the evidence, the confidence or the person who approved it outside the ERP.

Every ERP records its side on the posting document: number, date, period, entity, posting user and, for a reversal, the reason. The gap is the user field. An integration typically posts under its own ERP user, so the ERP shows that technical user, not the AR lead who approved. The approver, the remittance email and the confidence live in the agent’s log. Two records, one story: the auditor tests whether they agree.

So agree before go-live which reference ties a log entry to its ERP document (customer, amount, posting date, a reference field your ERP stores), and ask the vendor to show the tie on a real entry.

For US audits, the auditor’s own procedures are changing too. The PCAOB amended AS 1105 and AS 2301 to clarify requirements for audit procedures that use technology-assisted analysis, effective for audits of fiscal years beginning after 15 December 2025 (Deloitte DART, 2024; US).

What does one complete audit-log entry look like?

One complete entry for a matched payment shows the proposal, the evidence and confidence behind it, what the reviewer changed, who approved it and when it posted.

Illustrative example (company and figures are fictional). On 14 October, Customer B pays EUR 48,250.00 with “PAYMENT OCT” as the only text. A remittance email lists three invoices: 2026-3305 for EUR 20,000.00, 2026-3318 for EUR 18,250.00 and 2026-3342 for EUR 10,000.00, together EUR 48,250.00.

• Timestamp: proposal at 09:12, approval at 09:31.
• What the system did: proposed clearing the three invoices against the payment.
• The input: the bank statement line and the remittance email.
• The confidence: recorded with the proposal.
• What the user did: the AR analyst accepted the proposal unchanged.
• Who approved: the AR lead, because the amount is above the threshold set for Customer B.

The ERP side is a separate record: a clearing document with its own number, posted on 14 October in period 10 under the integration’s ERP user. Together, the two trace the payment from bank line to cleared items.

ClearMatch auto-matches 95% of payments, and nothing posts without human sign-off; Vero, the Transformance agent, investigates the rest and proposes with evidence (how AI cash application works).

Who approves what, and how does the log show it?

Approvals follow thresholds you set by amount, entity and customer; admins configure the rules, finance users approve, and the log records who approved each action.

Transformance works within a multi-level approval model (read, recommend, execute, post) with a human in the loop for ERP postings. Thresholds follow your business: for example a stricter rule above a set amount, for one legal entity or for a key account.

Segregation of duties shows up in the log as two users: the admin who changed a rule and the finance user who approved its output. The person who configures a rule should not approve what that rule proposes. The full threshold table is in who approves what when an AI agent works in your ERP.

How do you reverse a journal entry an AI agent posted?

Correct it with a reversal, never a deletion: Transformance can initiate the reversal and post it back to the ERP once a person approves, and the ERP reopens the items.

‍

‍

How a wrong AI agent posting is reversed, in 6 steps

1. A person flags the wrong posting, for example after a customer email or a reconciliation check. The log entry shows what was posted, on which input and who approved it.
2. Transformance initiates the reversal for that posting and its clearing.
3. A person approves the reversal under your thresholds, as for any ERP posting. The log records who approved.
4. The reversal posts back to the ERP: the clearing is undone first, then the document is reversed in an open period.
5. The ERP reopens the affected items, and the payment goes back to matching, where Vero investigates it from Customer 360 and proposes the correct match.
6. Check that both records agree: the reversal document and reason in the ERP, what the system and the user did in the log.

NetSuite’s help explains why: voiding a customer payment “is preferred to deleting the transaction because voiding the transaction keeps the audit trail” (Oracle NetSuite, help center). A reversal is a new journal entry that mirrors the original, so the ledger shows both the error and the fix. The log stores the six fields for what the system and the user did, the approval included.

The example, continued. On 16 October, Customer B writes that its EUR 10,000.00 was meant for invoice 2026-3351, also EUR 10,000.00. The AR lead approves the reversal with that email as evidence; the clearing is reset and reversed in period 10, still open, and all three invoices reopen. Vero proposes EUR 20,000.00 to 2026-3305, EUR 18,250.00 to 2026-3318 and EUR 10,000.00 to 2026-3351, a person approves, and 2026-3342 stays open.

How does each ERP reverse a cleared payment?

Every ERP undoes the clearing as part of a reversal: SAP resets cleared items, Dynamics 365 undoes the settlement, Business Central unapplies entries and NetSuite voids the payment.

How each ERP reverses a cleared customer payment

Menu names vary by release; confirm the procedure with your ERP team. Transaction codes describe how SAP works, not what an integration calls.

In the vendors’ own words:

• SAP: “You cannot reverse documents that contain cleared items. You need to reset the document before reversing it.” Every reversal needs a reversal reason (SAP Learning, S/4HANA course; more in how AI agents work with SAP).
• Business Central: “An entry can only be reversed one time” (Microsoft Learn, 2026); after unapplying, “the entries that the application closed are reopened” (Microsoft Learn, 2025).
• Oracle Fusion: a receipt reversal “creates reversal journal entries in the general ledger and reopens all of the debit and credit items that were closed by the receipt” (Oracle, 26D, 2026; NetSuite and Oracle in how AI agents work with Oracle and NetSuite).
• Odoo: “Unreconciling a payment unlinks it from the invoice or bill but does not delete the payment” (Odoo, 18.0 docs); a credit note “generates a reverse entry” for the original (Odoo, 18.0 docs).

How the payment was posted and cleared in the first place is in how external systems post payments and clear open items.

What stops a reversal from posting?

Closed periods, a completed year-end close, clearings that were not reset first and follow-on documents block reversals, so set the reversal date and order before you approve.

• Closed period. A payment cleared on 30 September, an error found on 3 October after September closed. Dynamics 365 rejects a reversing date in a period that isn’t open, but lets you move it to an open period where the transaction supports a reversing date; settled items need Settlement > Undo settlement first (Microsoft Learn, 2024). In SAP, the reversal reason can allow a reversal date different from the original posting date (SAP Learning). See period close.
• Year-end close. In Dynamics 365, once the year-end close has run for a fiscal year, its transactions can’t be reversed, even if a period is still open (Microsoft Learn, 2024).
• Order of steps. Undo the clearing before the reversal. In Business Central, unapply the latest application first when an entry was applied several times (Microsoft Learn, 2025).
• Follow-on documents. If the clearing left a residual item that has since been paid and cleared, reset that later clearing first, because SAP will not reverse a document that contains cleared items. Oracle chargebacks and NetSuite credit card payments have their own routes (table above).
• Currency differences. Business Central’s correcting entries include currency gains and losses (Microsoft Learn, 2025), and Odoo posts the exchange difference automatically (Odoo, 18.0 docs). Review those lines in the same approval.
• Entities. Reverse in the entity that posted (SAP company code, Dynamics 365 legal entity, NetSuite subsidiary). Transformance consolidates several SAP instances, company codes, subsidiaries and legal entities in one environment (AR across legal entities).

What should you check in an AI audit-trail review?

Pull one approved and one rejected entry, check all six fields, tie each to its ERP document, then reverse a test posting and confirm both records show it.

The test works on any vendor, us included:

1. One approved posting: all six fields present, with a named approver.
2. One rejected or changed proposal: what the user did, and when.
3. The ERP document for the approved posting: number, period and posting user, tied to the log entry by the reference you agreed.
4. One test reversal on a pilot entity, checked in both records.

Then ask in writing how a log entry is tied to the ERP document, how rule and model changes are tracked and approved, who can read and export the log, and how retention matches your policy. With Transformance, people sign in through SSO/SAML with role-based access control (RBAC), data is hosted in your region, and no customer data is used to train models. The procurement view is in the enterprise AI vendor checklist for finance.

Run the review during the proof of value, 4-5 weeks on one entity, before posting rights widen to more entities (how AI agents access ERP data safely).

Who Transformance is for

• ERPs: SAP S/4HANA and SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations and Business Central, and Odoo in production with customers; Oracle and Infor supported. Every posting and reversal goes back to the same ERP.
• Size: mid-market to large enterprise, 250 to 2,000+ employees, including groups with several entities and shared service centres.
• Payment volume: from under 1,000 to over 100,000 payments a month.
• Industries: manufacturing, consumer goods and food and beverage, logistics, e-commerce, agriculture, energy and professional services.
• Scope: cash application alone, or the full order-to-cash (cash application, deductions, AR collections, cash forecasting).

Conclusion: log the why, reverse the what

An agent’s audit trail explains why each entry was proposed and who approved it, the ERP proves what posted, and an approved reversal corrects it without erasing anything.

Before go-live, ask for one real log entry and one test reversal, and check that the two records tell the same story.

Key terms

• Audit trail: the record that lets a third party trace an entry from its source to the ledger and back.
• Journal entry: the posting record in the ledger; a reversal is a new journal entry that mirrors it.
• Sub-ledger: the customer ledger where open items are cleared and, after a reversal, reopened.
• Period close: closing a posting period; reversals then need a date in an open period.
• AI governance: the rules, roles and records that keep AI decisions controlled and reviewable.
• Explainable AI: AI whose outputs come with the inputs and reasoning a person can check.

Related guides

• Which ERP systems does Transformance integrate with?
• Who approves what when an AI agent works in your ERP?
• How do external systems post payments and clear open items?
• What data does AR automation read from and write to the ERP?
• How does Transformance integrate with SAP S/4HANA?
• How do AI agents access your ERP and customer data safely?
• Enterprise AI vendor checklist for finance

Frequently Asked Questions

Which ERPs can Transformance post and reverse entries in?

Transformance posts and reverses entries in SAP S/4HANA, SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations and Business Central, and Odoo, all in production with customers; Oracle and Infor are supported.

Does the audit trail work across several entities or company codes?

Yes: multiple SAP instances and company codes, NetSuite subsidiaries and Dynamics 365 legal entities consolidate in one Transformance environment, and approval thresholds can differ by entity.

How long does it take to set up the connection and approvals?

The ERP connection typically takes 2-3 days, and your IT team may be involved; the full rollout, including approval thresholds, takes 4-8 weeks. A proof of value runs 4-5 weeks on one entity (implementation time).

What does Transformance cost?

The cost depends on scope and the number of entities, so the quickest way to a figure is a short scoping call: Book a Call.

Can an AI agent delete a posting from the ERP?

A wrong posting is corrected with a reversal, which keeps the original visible: Transformance can initiate the reversal and post it back to the ERP once a person approves.

What should an auditor ask an AI vendor about its audit log?

Ask for one real approved entry and one rejected or changed proposal, check all six fields on each, and ask how each entry ties to its ERP document.

Does Transformance train models on our finance data?

No: no customer data is used to train models, and Transformance hosts your data in your region, with VPC deployment in your own cloud available (data in your region).