Audit trail & history
Where to find order history, workflow audit logs, report history, and payment history for operational and compliance review.
Auditability is a legal and operational requirement in OmniValVMS. Operators need to know who did what, when, why, and what changed — especially for P0 flows such as assignment, QC, payment, and agency submission.
Do not build operational processes that depend only on email, screenshots, or tribal knowledge. The order history, workflow audit log, report history, and payment history are the platform records used to reconstruct what happened.
Order history
Order history is the first place to look when reconstructing an order timeline. It records status changes, comments, assignment changes, workflow actions, and other order-level events visible to the caller's scope.
| Action | Endpoint |
|---|---|
| List client-visible order history | |
| List vendor-visible order history | |
| Get a single history entry | |
| List history types |
Workflow audit logs
Workflow automation can add comments, attach documents, create exceptions, place orders, request revisions, and assign vendors. Use workflow audit logs to understand automation decisions behind the order timeline.
Related workflow actions include:
| Automated action | Endpoint |
|---|---|
| Add workflow comment | |
| Record workflow exception | |
| Attach workflow document | |
| Auto-assign vendor | |
| Auto-request revision |
Report and submission history
For QC, revision, and final delivery questions, inspect report history alongside order history.
| Action | Endpoint |
|---|---|
| List report submission history | |
| Request a revision | |
| Accept a report | |
| Send report to borrower |
Payment history
Payment history is separate from general order history because financial actions need a precise trail for charges, refunds, vendor payments, and reconciliation.
| Action | Endpoint |
|---|---|
| Order payment history | |
| Vendor payment history | |
| Billing statement payment history |
What a useful audit record should answer
For every critical action, the audit trail should make these questions easy to answer:
- Who performed the action?
- What order, client, vendor, report, or payment was affected?
- What was the previous state and new state?
- Why was the action taken, if a reason is required?
- When did it happen, and from what workflow or integration?
- Was the action successful, rejected, retried, or reversed?
For manual overrides, cancellations, refunds, revision requests, and status changes, capture a clear reason code or operator note whenever the workflow asks for one. A future reviewer should not have to infer why the action happened.
Investigation workflow
Start with order history
Confirm the visible order timeline and current status.
Check specialized history
For QC, use report history. For money movement, use payment history. For automated actions, use workflow audit logs.
Compare against the state machine
Verify the action followed the expected order lifecycle and did not skip a required gate such as acceptance, inspection, QC, delivery, or payment.
Escalate with IDs and timestamps
Include order ID, client ID, user, endpoint, timestamp, and the relevant history entries so support can reproduce the timeline.