Payment and invoice boundaries
Records establishes eligible volume; providers confirm funds; Trusted Billing orchestrates invoices under contract.
Responsibility and state diagram
Authoritative sources
Technical usage is not automatically a debt. Accepted manifests and rate versions define billable amounts. Payment providers confirm/reconcile recipient, amount and references. Issuers confirm invoice issuance; Records retains verified links and states.
Failure effects
Query authoritative status after payment timeouts before recreating requests. Failed invoices require correction/eligible retries, not reverting paid funds. Adjustments/disputes retain versions, approvers and history rather than erase prior transactions.
Continue the workflow
Two journeys, one records lifecycle
Connect paper and born-digital records through persistent identifiers, policies and evidence.
Read detailsIntegration quickstart
Exercise ingest → job tracking → registration → verification with synthetic data.
Read detailsIntegrity, provenance and evidence
Each evidence type answers a different question; hashes, timestamps and approvals are not interchangeable.
Read detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment