Turn agreements into obligations, charges, and receivables
Verifable contains a contract-driven subledger engine: agreements decompose into obligations, obligations attach to charge rules, and charge rules produce receivables that carry the data an invoice needs. The engine itself is implemented; the user-facing surfaces around it — the screens for configuring agreements and reviewing receivables — are still being built.
The subledger engine runs on the platform today, reachable through the API contract. A public human workflow for it is not exposed here.
The capability boundary
The engine prepares invoice data from an agreement. Reviewing, rendering and sending the invoice remain separate steps in your invoicing process.
- Agreement
- Obligation
- Charge rule
- Receivable
- Invoice-ready data
- Rendered invoice
What you remain responsible for
Verifable produces invoice-ready data from a receivable. Checking the invoice, correcting it where necessary, and sending it through your chosen invoicing channel stay yours to do. Verifable is not a full accounting package, does not perform bank reconciliation, and does not collect payment on your behalf.
Payment allocation stays outside the platform today: banking data is neither collected nor held here. A public payment-allocation API is not offered.
Charge types
A charge rule can attach to any of the following, and combine more than one:
- Parties
- Organisations
- Properties and assets
- Services
- Agreements
- Contract periods
- Recurring charges
- Event-based charges
- Performance-driven charges
- Obligations
Performance-driven charges
A performance-driven charge ties what is billed to evidence about how an asset or service actually performed, traced back to a specific product or asset identifier:
- Charge type
- Required evidence
- Product or asset identifier
- GS1 Digital Link or appropriate resolver
- Relevant performance service
- Trusted evidence
- Calculation
- Receivable
Every charge type carries the same set of defining facets:
- Applicable subject
- What the charge can apply to — an agreement, an asset, a party, a service.
- Required evidence
- What must exist before the charge can be calculated.
- Accepted formats
- The evidence formats the charge rule will read.
- Trusted issuers or devices
- Who or what is allowed to supply the evidence.
- Units
- The measurement unit the charge is calculated in.
- Period
- The time window the charge covers.
- Aggregation
- How multiple evidence points combine over the period.
- Calculation
- The formula applied to the aggregated evidence.
- Rounding
- How the calculated amount is rounded.
- Missing-data policy
- What happens when required evidence does not arrive.
- Dispute policy
- How a disputed charge is handled.
- Effective version
- Which version of the charge-type definition applied at calculation time.
Trust in the evidence
Assess the source and reliability of the evidence used to calculate a performance-driven charge. Issuer and device identity, credential checks and hardware-backed evidence can help establish where a measurement came from. The required checks depend on the charge rule and the integration. A signature does not by itself prove that a sensor reading is accurate or that a charge is justified. See wallets and tools for how that evidence is held and inspected.
Further reading
Real-estate maintenance, Digital Product Passports, wallets, and reporting and ESRS evidence for how a receivable's performance charge traces back to reported facts.