Connected Ledger · Foundation

Every transaction has a story. Rivet keeps it connected.

The record under every layer. Rivet connects the documents, conversations, approvals, workflow states, payments, and system records behind a business transaction, so both sides, and their AI, work from the same history.
Beneath every layerCoordinationProofFinance
Connected Ledger · INV-4417APR 02PO-8842 created, synced from Carmony’s QuickBooks
CACarmonyBuyer · QuickBooks
APR 02· Carmony
PO created
PO-8842 · v1
Synced from QuickBooks
APR 09· Ridgeline
Quantity revised
180 → 240 · now v3
Customer confirmed
APR 10· Ridgeline
Invoice issued
INV-4417 · $48,200.00
Synced from Xero
APR 10· Carmony
Freight line flagged
Not on the PO
Rivet observed
APR 11· Carmony
Approved and signed
Jordan Kim · v3
Entered by a user
APR 11· Carmony
Payment initiated
Remittance attached
Rivet observed
APR 12· Ridgeline
Settled
$48,200.00 received
Payment provider reported
APR 12· Carmony
Posted · QuickBooks
Bill INV-4417 · paid
Carmony’s books
APR 12· Ridgeline
Posted · Xero
Invoice INV-4417 · paid
Ridgeline’s books
RPRidgeline Parts SupplySupplier · Xero
CoordinationProofFinancePosted
The line between the lanes is the shared record. Every state on it keeps its source.

From the first document to final settlement, keep the evidence with the transaction.

Beyond the books

Your books show what was paid. Rivet shows how it got there.

An accounting system records the result inside one company: what posted, for how much, on which day. The reasons behind it, a revised order, an approval, a flagged freight line, a conversation with the supplier, live in email, chat and the other company’s systems. Rivet keeps them with the transaction.

INV-4417$48,200.00Carmony pays Ridgeline Parts SupplyPaid Apr 12, 2026
What you’d want to know
Carmony’s books
The Rivet record
What was paid
$48,200.00 on Apr 12
$48,200.00, settled Apr 12
Payment provider reported
Why it’s 240 units, not 180
Shows 240. Not why.
Ridgeline revised the quantity on Apr 9, and Carmony confirmed v3 of PO-8842
Customer confirmed
Which version was approved, and by whom
Not recorded
v3, approved and signed by Jordan Kim on Apr 11
Entered by a user
What happened to the freight line
Not recorded
Flagged on Apr 10 as not on the PO, and resolved before approval
Rivet observed
Where it was discussed
Not recorded
Four replies in the conversation, attached to PO-8842
Entered by a user

The record is not just the result. It is the evidence behind the result.

One transaction, all of it

Seven kinds of context, one record.

Rivet treats business objects as living parts of a relationship, not files detached from the work around them. Workspace, Gio, and Money all read and write this record.

Documents

The source document, current version, revisions, and related artifacts, together.

Conversations

Questions and decisions stay with the order, invoice, approval, or exception they affect.

Workflow

What happened, what is waiting, who owns the next action, and which state changed.

Approvals

Who approved which version or action, and when.

Money

Payment requests, payment status, settlement, and reconciliation, connected to the commercial event.

Systems

Relevant state synchronized to each company’s own platform, with boundaries preserved.

Identity and audit

The actor, organization, source, timestamp, and history behind critical changes.

One record, read by all three

Workspace, Gio and Rivet Money all read and write it, so your team, your AI and your money work from the same history.

Trace the outcome

Move from “what happened?” to “why did it happen?”

When the history stays connected, teams move backward from an outcome to the evidence that produced it.

Questions it answers
Which version of the purchase order was approved?
Who authorized the change, and what did the customer acknowledge?
Why did the invoice amount change?
What is blocking payment right now?
Which document supports this payout?
When did the accounting system last synchronize?
INV-4417 · traced backnewest first
Settlement complete
Apr 12 · payment provider reported
INV-4417 paid
$48,200.00 · remittance attached
Invoice approved after quantity correction
Jordan Kim · Carmony AP
PO revision 03 acknowledged
Quantity 180 → 240 · customer confirmed
Change requested in the conversation
4 replies · attached to PO-8842
Original PO created
Apr 2 · synced from QuickBooks

Follow the outcome back to the decision, and the decision back to the evidence.

Verified states, visible source

Know where a state came from.

Not every piece of information carries the same authority. Every important state keeps its source, so when a document changes, a payment settles, or an AI answer appears, people can see the evidence rather than treating every field as equally authoritative.

Entered by a user

Typed into Rivet by a named person.

Synced from QuickBooks

Imported from a connected system.

Customer confirmed

Acknowledged by the counterparty.

Rivet observed

A workflow event Rivet recorded directly.

Payment provider reported

Financial state reported by the provider.

AI summary — derived

Generated from the record, marked as derived.

AI-generated conclusions stay distinguishable from verified states and link back to the records that support them.

Meet Gio
Enterprise value

A better record changes more than audit.

Account management

“Why did this invoice change?”

Answer from the transaction instead of asking billing, operations, and finance to reconstruct it.

Finance

“What does this payment settle?”

Move backward from the payment through invoices, approvals, and source documents.

Operations

“Why hasn’t this order shipped?”

See the change, the exception, the dependency, and who owns the next action.

Audit and compliance

“Show me how this happened.”

Reconstruct history without hunting through inboxes, drives, private chat, and accounting notes.

Executive

“Why do these transactions take longer?”

See the relationship-level history behind delays, disputes, and cash movement. Operational context, not just financial output.

Risk and controls

“Who had the authority?”

Preserve the chain of authority behind approvals and consequential actions, inside organizational boundaries.

Common questions
Is the Connected Ledger an accounting ledger?

No. Accounting systems remain essential internal systems of record. The Connected Ledger is the connected operational history around a transaction: the documents, conversations, workflow states, approvals, and payment events that explain how it progressed.

Does Rivet expose one company’s internal systems to another?

No. Each side connects its own systems, and only the appropriate shared transaction state appears in the relationship workspace.

Is this blockchain?

No. The Connected Ledger is a private, hash-linked history that Rivet runs, and your data never goes on a blockchain. Rivet publishes only a fingerprint of each batch of records to a public chain, so anyone can confirm the history hasn’t changed since. Zero-knowledge proofs then let a company prove a specific fact, such as an approved amount clearing a lender’s threshold, without sharing the record. Stablecoin settlement is a separate feature.

Does Rivet replace our ERP or accounting platform?

It is complementary. Your existing systems stay your internal systems of record while Rivet coordinates the shared work and history between counterparties.

How does the connected record help AI?

It gives Gio permissioned context to reason over: source documents, versions, approvals, conversations, workflow states, and payment history, rather than an isolated file.

Connected Ledger · Foundation

Stop reconstructing the transaction after the fact.

The value is not more data. It is preserving the relationships between identity, intent, action, evidence, and settlement.

Connected Ledger — Every Transaction Has a Story