A cost line references unaccepted usage; reconcile under the contract and raise an item-specific dispute.
Trusted Records · Platform
Usage, invoices and payment
Let owners reconcile charges with accepted quantities and agreed billing rules.
Inputs and starting conditions
Usage summaries, acceptance references, billable rule/version, invoices/payments and approved adjustments.
Workflow and control gates
- 01Inspect usage
- 02Match acceptance
- 03Inspect billable lineage
- 04Check invoice
- 05Pay / dispute
Accepted and billable are distinct; accepted work may be excluded contractually. VI uses dot thousands/comma decimals; EN uses comma thousands/dot decimals.
Exceptions and recovery
Unmatched charges, duplicate retry billing or delayed payment status require reconciliation, preserving invoices and adjustment history.
Roles, outputs and states
| Responsibilities | Evidence and states |
|---|---|
| Customers inspect; billing explains; authorized approvers approve adjustments/refunds; finance updates payment status. | Usage → acceptance → billable → invoice lineage, payment references and dispute receipts. States: issued / outstanding / paid / disputed according to records. |
Scenario and acceptance criteria
Complete only when
Costs retain unit, period, usage source and adjustment decisions.
Interfaces for this workflow
Integration handoff
End-to-end integration workflows
Connect technical states to business decisions instead of merely listing endpoints.
Read detailsOpenAPI and Swagger Reference
The proposed contract is rendered from one local specification; no network Try-It or real credentials.
Read detailsErrors and next actions
A consistent error envelope guides recovery without disclosing sensitive data.
Read detailsContinue the workflow
Service models and billing principles
Reconcile accepted quantities with contractual rules before billing instead of charging all processing attempts.
Read detailsTwo 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 detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment