Infor SyteLine3 min readNetray Engineering TeamUpdated March 4, 2025

Auditable Data Changes in SyteLine: Preview, Confirm, Record, Undo

Every SyteLine site changes data outside the happy path: a due date pushed, a price corrected, a status fixed after a process hiccup. The question auditors, and good controllers, ask is simple: who changed what, when, from what value to what value, and can you show me? For direct SQL fixes the honest answer is often no. As AI-assisted tools start touching ERP data, the audit question becomes existential: governance is the difference between a capability and a liability.

What a Real Audit Trail Contains

The standard is not a log line saying a table was updated. It is a record, per change, of the affected rows, each field's before and after values, the identity of the person who approved the change, and the timestamp, kept permanently and queryable. That record turns what happened to this order from an investigation into a lookup, and it is the foundation for the property auditors care about most: reversibility. If you recorded the before-state, you can restore it.

Row-level before and after values for every changed field.
Attribution: the named user who confirmed the change.
Permanence: audit records are append-only history, not overwritable state.
Reversibility: recorded before-states make undo a first-class operation.

Governance for AI-Assisted Changes

AI assistance raises the stakes because it lowers the effort of making changes, which is the point, and the risk. The governed pattern SyteRay implements: the change is computed and shown as a preview, affected records with current and proposed values, against the live database; nothing executes without explicit confirmation scoped to that exact change set; the confirmed change lands in a permanent audit table; and undo restores the recorded before-state through the same previewed, confirmed, audited flow. Write capability as a whole ships disabled by default and is enabled deliberately per deployment. Stored procedures with write effects, including effects inherited through nested calls, route through the same gate.

Why Conservative Governance Wins Adoption

The counterintuitive lesson: strict governance accelerates adoption rather than slowing it. Controllers and IT managers extend scope to systems whose every action is previewable, attributed, and reversible, because the worst case of a mistake is a recorded, undoable event. One ungoverned surprise, by contrast, can end an AI program's credibility at a site permanently. The audit trail is not compliance overhead; it is the mechanism by which the system earns more responsibility.

Frequently Asked Questions

Does SyteLine track who changed data?

Application-level changes flow through SyteLine's own mechanisms, but direct SQL fixes and external tools often bypass meaningful auditing. A governed editing layer adds row-level before/after capture, attribution, and undo for changes made through it, regardless of the field being changed.

Can AI-made ERP changes be undone?

In a properly governed system, yes. If every change records its before-state in a permanent audit trail, undo is a restore of recorded values, executed through the same preview-and-confirm flow as the original change. This is how SyteRay implements it.

Should AI write access to ERP be on by default?

No. Write capability should ship disabled and be enabled deliberately per deployment, with previews, explicit confirmation, audit, and undo as structural requirements. Read-only operation should be the default posture.

Key Takeaways

1What a Real Audit Trail Contains: The standard is not a log line saying a table was updated. It is a record, per change, of the affected rows, each field's before and after values, the identity of the person who approved the change, and the timestamp, kept permanently and queryable.
2Governance for AI-Assisted Changes: AI assistance raises the stakes because it lowers the effort of making changes, which is the point, and the risk. The governed pattern SyteRay implements: the change is computed and shown as a preview, affected records with current and proposed values, against the live database; nothing executes without explicit confirmation scoped to that exact change set; the confirmed change lands in a permanent audit table; and undo restores the recorded before-state through the same previewed, confirmed, audited flow.
3Why Conservative Governance Wins Adoption: The counterintuitive lesson: strict governance accelerates adoption rather than slowing it. Controllers and IT managers extend scope to systems whose every action is previewable, attributed, and reversible, because the worst case of a mistake is a recorded, undoable event.