Treviya
Platform · Ledger

Every event,written once.

Treviya writes every financial event, authorisations, procurement commitments, freight, duties, commissions, platform fees, exceptions, to an append-only ledger. Entries never change.

Architecture specs
ArchitectureAppend-only event log
MutabilityImmutable post-write
Reconciliation cadenceDaily · automated
Divergence SLA< 2 hours to flag
Audit trail retention7 years minimum
Statement assemblyMaterialised from ledger
Export formatCSV · JSON · signed PDF
Access controlRole-based · member-scoped
How it reads

The ledger is organised per cycle. Every event carries the cycle ID, an event type, a monotonically increasing sequence number, a timestamp and the signed evidence hash. Events cannot be edited. Corrections take the form of additional entries that reference the original.

At cycle close, the statement is materialised from the ledger, the cycle's events are reduced into the itemised breakdown that members see. Because the source is append-only, every number on the statement is traceable to a specific event with a specific timestamp.

Reconciliation

Every night the reconciliation job compares ledger sums against stored balances per cycle and per member. Any divergence is flagged to the platform team within two hours. Divergences are investigated and, if confirmed, corrected through additional ledger entries, never by editing history.

Export

Members can export their ledger entries in CSV, JSON or signed PDF format. The signed PDF includes a document hash that can be verified against the platform's published signing key.

Read next
Begin

Every number,traceable to source.

That is the promise underneath every cycle statement. Read a live brief and you will see the itemisation that flows from the ledger.