Data requirements
A smaller, documented input makes the service safer and easier to audit.
The normal starting point is a normalized open-approval register. Nothing operational should be sent through the public website.
Accepted profile
Fields the working schema is designed around.
- invoice token
- entity token
- approval stage
- owner role
- age band
- SLA band
- exception code
- evidence state
The field list is a planning profile, not a request to email data. The exact schema and secure exchange are agreed in writing after fit review.
Explicit exclusions
Data and authority we do not need.
No payment initiation, bank linking, vendor-master writes, invoice PDFs, tax IDs, credentials, fraud guarantee, or accounting advice.
Credentials, unrestricted system access, and unrequested free text are never part of the published plan.
Data lifecycle
Five visible handling stages.
- 01
Agree
Write down the permitted fields, purpose, owner, transfer, retention, and deletion rule.
- 02
Prepare
The buyer exports and normalizes only the agreed minimum input.
- 03
Validate
Schema failures and unknown values are rejected without inference.
- 04
Deliver
Portable outputs carry definitions, exceptions, and confirmation states.
- 05
Delete
Working data follows the written retention rule; the buyer keeps the final pack.
Field glossary
Shared definitions prevent expensive rework.
- Approval stage
- The buyer-defined closed state in the approval path.
- SLA band
- A buyer-authored time range for expected stage movement.
- Open approval
- An item reported as awaiting a buyer-owned decision.
- Exception code
- A neutral reason code supplied or derived from an agreed rule.
- Evidence state
- Whether the required approval metadata is present as reported.
- Reject log
- Rows that could not be processed without guessing.
A useful first conversation
Check the data boundary before discussing a plan.
Describe it in general terms. We will tell you which plan fits, what we would need, and where we would draw the line.