SAP's expense agent needs a field-by-field provenance check

Label every field as sourced, derived, or inferred

The direct control is a field-level evidence view on the draft. For each card transaction, date, merchant, amount, currency, traveler, trip, expense type, business purpose, project, entity, cost center, tax treatment, receipt match, attendees, and policy status, record whether the value came directly from an authorized system, was deterministically derived, was inferred from context or past behavior, or was entered or corrected by the employee. Preserve the source record, timestamp, transformation, confidence or exception state, policy and master-data version, and last editor. A complete-looking report should not hide which fields are facts and which are proposals, especially when the field controls accounting, reimbursement, tax, client billing, or management reporting.

Do not let past behavior become policy

Past coding can help draft a familiar cost center or expense category, but it can also reproduce a prior error, obsolete project, manager workaround, changed entity, expired tax rule, or personal pattern that is inappropriate for a new trip. Define which historical fields may inform a suggestion, the lookback period, minimum evidence, employee visibility, and conditions that force a blank or exception. Reconcile suggestions against current card feeds, travel records, chart of accounts, projects, employee assignments, entity and currency rules, receipt requirements, approval matrices, and effective-dated policy. Test new employees, transfers, reorganizations, closed projects, split expenses, personal charges, credits, duplicate transactions, foreign exchange, missing receipts, and an amended policy.

Preserve employee correction and reviewer independence

The employee should be able to inspect, change, explain, or remove each proposed field without the interface treating acceptance as proof of accuracy. Capture the original proposal, correction, reason, and evidence while minimizing unnecessary personal data. Then route the report through the existing policy and approval chain with approvers able to see material provenance and exceptions. Keep agent configuration and report preparation separate from approval, payment, accounting changes, and control certification. Test whether the system suppresses or overweights exceptions, whether approvers can identify an inferred business purpose or category, and whether a rejected or corrected pattern affects later drafts. An employee review step is meaningful only if it is informed, usable, and preserved.

Accept the workflow on errors and rework, not draft speed

Before scaling, compare representative reports with the prior process on field accuracy, unsupported inference, receipt and transaction matching, policy exceptions, employee corrections, approver rework, duplicates, reimbursement timing, posting errors, tax and client-billing adjustments, help requests, and total handling time. Segment results by expense type, entity, geography, currency, traveler population, and exception complexity so high-volume easy reports do not conceal risky tails. Reconcile the approved report, reimbursement, payable, tax record, and ledger posting, and verify that corrections propagate. SAP's estimated time benefit is provider evidence, not the buyer's result; a faster first draft is useful only when downstream control effort and financial error do not rise.

Turn this source into a reviewable decision

For AI for CFOs, use this briefing as a dated decision record rather than a substitute for the source. Preserve SAP Business AI: Release Highlights Q2 2026, the exact URL, the August 26, 2026 review date, the supported facts above, the editorial interpretation, the limitations, and any buyer-specific evidence. Link that record to the decisions most directly affected: Spend intelligence and procurement challenge; Internal control and audit evidence; Finance policy and self-service; Management reporting and external disclosure support. State whether the source changes the scope, evidence requirement, control, sequence, or only the language used to describe the decision.

Before action, name the accountable owner, affected population and workflow, exact offering or configuration, source data and rights, human decision point, exception and appeal path, complete cost, expected benefit, failure and stop conditions, retained evidence, and next review date. Keep official facts, provider statements, buyer observations, representative tests, measured outcomes, editorial inferences, and unknowns visibly separate. Reopen the record when the source, offer, model, integration, data, policy, population, responsible person, or measured result changes.

Limitations and unknowns

SAP is the provider source. Its July 20, 2026 Q2 release-highlights article identifies Expense Automation Agent as generally available and describes transaction collection, context- and past-behavior-based field completion, employee review, and an estimated completion-time benefit. It does not independently establish a buyer's product and region availability, license, configuration, data sources, field provenance, historical lookback, policy and master-data alignment, inference accuracy, employee experience, exception handling, approvals, segregation, reimbursement, tax and posting behavior, control effectiveness, cost, time saved, or finance outcome. Current contracts and documentation, field and source inventory, effective-dated policies and master data, representative draft, correction, exception, approval, payment and posting tests, operating evidence, and qualified finance, accounting, tax, audit, people, privacy, security, accessibility, procurement, and legal review control.