Skip to main content

Documentation Index

Fetch the complete documentation index at: https://enfinitos.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Settlement is the layer that turns metered units into invoices, reconciliations, and finance-grade reports. It is designed in from the start so it doesn’t have to be bolted on later under audit pressure.

​
What settlement consumes

Settlement consumes three things:
  1. Metering projections for the period, from the metering layer.
  2. Contract terms — price-per-unit, discounts, minima, caps, tiered structures.
  3. Adjustment events — refunds, credits, manual corrections, each with their own audit record.

​
What settlement produces

For each tenant × counterparty × period, settlement produces:
  • A reconciliation document with the metered units, the contractual rate card, the resulting line items, and the totals.
  • A proof-pack appendix — the reconciliation is embedded in the relevant proof packs so the auditor can re-run it.
  • An invoice draft — surfaced into the operator dashboard for human review before issue.

​
What the auditor checks

The auditor re-runs settlement reconciliation from the metering projection and the on-chain contract terms. The output must be bit-identical — any divergence fails verification. This is the property that makes settlement legally defensible: nobody — not even EnfinitOS — can produce a settlement number that isn’t reproducible from the underlying signed events.

​
Adjustments

Adjustments don’t mutate historical packs. They are issued as new proof events, signed and chained, and they roll forward into the next reconciliation. The audit trail of “we adjusted X for Y reason” is preserved permanently.