Data requirements

A smaller, documented input makes the service safer and easier to audit.

The normal starting point is buyer-normalized B2B invoice-state and event metadata. Nothing operational should be sent through the public website.

Accepted profile

Fields the working schema is designed around.

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

No payment custody, debt-collection claim, autonomous credit hold, legal threat, unrestricted inbox access, or accounting write.

Credentials, unrestricted system access, and unrequested free text are never part of the published plan.

Data lifecycle

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

Follow-up state: The buyer-reported stage in its approved cadence.
Promise state: A closed-enum record of a buyer-reported commitment state.
Dispute state: A buyer-reported flag that requires human handling.
Protected account: An account the buyer excludes from routine treatment.
Coverage: The share of eligible records with an as-reported next step.
Balance band: A coarse buyer-normalized range rather than an exact financial amount.

A useful first conversation

Describe it in general terms. We will tell you which plan fits, what we would need, and where we would draw the line.