Every movement,documented.
Treviya runs on documented commerce. Every cycle generates a set of records, authorisation, procurement, inspection, shipment, settlement, written once and retained for audit. This page explains what is kept, why and how you access it.
Selective record-keeping undermines everything else. If the platform keeps only the cycles that cleared, only the shipments that arrived clean, only the settlements that landed above base case, then the record is a marketing document, not a record.
Treviya's documentation philosophy is the opposite: write once, retain fully, export on request. The appended-only ledger holds the source. Every member, supplier and partner touches the same timeline. The cycle archive publishes outcomes above, within and below base case, every time.
Member allocation, chosen path (resale or delivery), timestamp, signed receipt hash.
Purchase order, agreed specification, payment schedule, milestone terms, acceptance criteria.
Sample plan, grade check, chemistry or moisture readings where applicable, inspector signature.
Bill of lading, packing list, certificate of origin, phyto/health certificates per lane.
Arrival inspection, quarantine decisions, release authorisation.
For delivery-path allocations, carrier POD, timestamp, recipient signature where applicable.
For resale-path allocations, per-channel dispatch, sell-through, realised price, commission.
Append-only event log, every cost, fee, exception, adjustment. The source of the settlement statement.
Itemised line-by-line close. Net to members. Outcome band (above / within / below base case).
Per-cycle log of deviations with timestamps, evidence hashes and resolution notes.
Write-once at the source
Events are written to the ledger the moment they occur, an authorisation, a supplier milestone acknowledgement, an inspection release, a channel partner dispatch. Each event carries the cycle ID, a monotonic sequence number, a timestamp and a signed evidence hash.
Materialised views, not edited truth
The settlement statement is a materialised view over the ledger, a readable summary generated from the events. If an exception is identified after close, the platform issues a revised statement that references the original ledger entries. The history is never rewritten.
Daily reconciliation
Every night, ledger sums are reconciled against stored balances per cycle and per member. Any divergence is flagged to the platform team within two hours. Confirmed divergences are corrected through additional ledger entries, never by editing history.
Export
Members can export their records at any time in CSV, JSON or signed PDF. The signed PDF includes a document hash that can be verified against the platform's published signing key. This matters for members who need to produce records to their own auditors, regulators or counterparties.
Read-only access to every cycle they participated in. Full export. Dispute flow where a record looks incorrect.
Read-only access to their cycles, contracts, milestones and settlements. Private supplier dashboard.
Read-only access to their dispatches, sell-through and commission settlements. Partner portal.
Full ledger access under role-based controls. Every staff action is itself logged to an internal audit trail.
On-request ledger export, under NDA, for qualified institutional members and regulators.
Anonymised cycle-level outcome bands and aggregate platform figures published on the archive.
Written once.Retained fully.
The same records are visible to members, suppliers and auditors, on the same timeline, with the same export formats.