Rivet Connect · Foundation

Your systems stay. Rivet reads and writes through them.

Each company links Rivet to the accounting, messaging, banking, and vendor systems it already runs. Every layer reads and writes through the connector, and the Connected Ledger stays in sync with each company’s books. Internal records stay private.
Under every layerCoordinationProofFinance

Tags come from the product’s own connector catalog: Available where it ships today, Coming where it doesn’t yet.

The privacy boundary

Each side links its own books. Neither sees the other’s.

A relationship in Rivet is linked to the matching vendor record in your system, and to a different customer record in theirs. Internal identifiers never cross the connection.

Carmony
QuickBooks Online
Vendor recordVEND-0042

Private to Carmony. Never crosses the connection.

The shared relationship
Carmony ↔ Ridgeline Parts Supply
DocumentsApprovalsStatusPayments

Shared on the Connected Ledger, in each side’s own terms.

Ridgeline Parts Supply
Xero
Customer recordCUST-1180

Private to Ridgeline Parts Supply. Never crosses the connection.

Keep your systems. Share the transaction.

See the architecture
How a sync works

Your system of record stays yours. Rivet is the system of action between them.

Each side links once. From then on, the shared work in Rivet and the private record in your books describe the same transaction, each in its own terms.

01

Link your system

Authorize the connector for your organization. Your credentials and your books stay on your side.

02

Match the relationship

Each Rivet connection maps to your own customer or vendor record. The counterparty maps it to theirs.

03

Work the transaction in Rivet

Documents, approvals, conversation, and payment happen on the shared record, on the Connected Ledger.

04

State syncs back

Invoice and bill status, payments, and settlement land in each company’s own books, and only theirs.

Building on Rivet yourself? The Context API is the same door, for code and for agents.

See the Context API
The catalog

Connectors for the systems your business already runs.

Accounting, messaging, banking, vendors and EDI, with Rivet’s own Messages and Money built in. Each connector says what it reads and writes, and what stays private.

Accounting · One per organization
Available

QuickBooks Online

Intuit · customers, vendors, invoices, bills, payments

Available

Xero

Contacts, invoices, bills, payments

Available

Sage

Sage Business Cloud Accounting

Available

Oracle NetSuite

Customers, vendors, invoices, vendor bills, payments · On Scale

Messaging · Built in, plus where documents arrive in chat
Built inRivet MessagesInternal channels, DMs, and cross-company conversations attached to the transaction · email routes inExplore Workspace
Available

Slack

Documents and notes from bound channels · status back in the thread

Coming

Microsoft Teams

Documents and notes from bound channels · status back in the thread

Coming

WhatsApp

Counterparty messages from the field

Banking and exchange · Built in, plus the accounts you hold elsewhere
Built inRivet MoneyAccounts, payments, and treasury inside Rivet · ACH, USDCExplore Rivet Money
Available

Plaid

Read the accounts you keep at other banks

Available

Coinbase

Business, personal or sandbox account · read-only by default

Vendors · Order through Gio or by hand
Coming

Amazon Business

Orders through Gio or by hand · paid with your buying group's own method

UCPComing

Shopify / UCP merchant

Any store speaking the Universal Commerce Protocol

cXMLContact us

Punchout supplier

Grainger, Uline, McMaster… — cXML punchout, set up per supplier

EDI · Enabled by support
EDIContact support

EDI (X12 / EDIFACT)

Inbound translation of 810 / 850 / 856 into documents

Tags come from the product’s own connector catalog: Available where it ships today, Coming where it doesn’t yet. Running something else? Tell us →

Rivet Connect · Foundation

Keep the systems you trust. Connect the work between them.

Rivet Connect — Your Systems Stay. Rivet Reads and Writes Through Them.