90-second operating demo

One receivable. Five participants. No uncontrolled data spill.

LedgerLine turns receivables finance into a shared operating file: lenders see credit economics, settlement agents see repayment state, auditors see evidence, and counterparties see only what their role permits.

Launch the guided workflow

—modeled receivables

5participant roles

3outcome paths

✓Daml verified

OPERATING BRIEFCANTON / DAML

Same receivable. Different participant views.

The product idea is simple: replace fragmented receivables operations with a permissioned deal record. Each participant works from the same lifecycle, but disclosure follows the role — buyer identity, face value, tier, reserves, and lender economics are not sprayed across every workflow view.

DamlCanton/Daml model for private shared state.

EvidenceActor, state, timestamp, and packet hash on every transition.

ControlsSwitch roles and watch fields reveal, scope, or redact.

OutcomeSettlement, dispute, cure, and blocked-action paths.

Select receivableStart with a verified invoice packet and counterparty obligation.

Switch participant roleSwitch from lender to auditor and watch economics disappear while evidence remains.

Inspect lifecycle evidenceReview state transitions and final settlement/exception state.

The operating console for a private credit deal file.

This is the product surface: a controlled record of receivable status, participant permissions, economics, evidence, and exception handling.

Deal workspace

Scenario

Receivable record

Invoice	Participant-visible counterparty	Exposure	Risk	Outcome

Why this mattersPrivate credit workflows require shared state but not shared visibility.

What Canton addsDaml authorization and private contract state are the reference pattern.

What this provesLifecycle state, evidence, and access boundaries can be shown from one record.

Disclosure matrix.

The product point is visible here: each participant receives a different authorized slice of the same receivable record while the evidence trail remains auditable.

Role-scoped access for selected record

Implementation proof is available after the visual demo.

The workflow interface gives business stakeholders the operating view first; the proof package supports technical diligence when details are requested.

17Lifecycle, scenario, dashboard, and surface tests pass.

DARDaml build creates ledgerline-reference-0.1.0.dar.

4 / 14Daml Script result: 4 active contracts, 14 transactions.

Apache-2.0Open reference package; production deployment is out of scope.

Demonstration records illustrate role-scoped disclosure, lifecycle state transitions, and tamper-evident evidence trails. The public workspace is not connected to production money movement, real invoices, or live counterparty systems.