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.

Request a demoBuild on the Context API
What Rivet connectsOne canonical model over many providers.
AccountingOne per organization · OAuth
QuickBooks OnlineAvailable
Intuit · customers, vendors, invoices, bills, payments
XeroAvailable
Contacts, invoices, bills, payments
SageComing
Sage Business Cloud Accounting
NSOracle NetSuiteComing
SuiteTalk · customers, vendors, invoices, vendor bills, payments · On Scale
MessagingBuilt in, plus where documents arrive in chat
RivetRivet MessagesBuilt inInternal channels, DMs, and cross-company conversations attached to the transaction · email routes inExplore Workspace →
SlackAvailable
Documents and notes from bound channels · status back in the thread
Microsoft TeamsComing
Documents and notes from bound channels · status back in the thread
WhatsAppComing
Counterparty messages from the field
Banking and exchangeBuilt in, plus the accounts you hold elsewhere
RivetRivet MoneyBuilt inAccounts, payments, and treasury inside Rivet · ACH, USDCExplore Rivet Money →
PlaidAvailable
Read the accounts you keep at other banks
CoinbaseAvailable
Business, personal or sandbox account · read-only by default
VendorsOrder through Gio or by hand
Amazon BusinessComing
Orders through Gio or by hand · paid with your buying group's own method
UCPShopify / UCP merchantComing
Any store speaking the Universal Commerce Protocol
cXMLPunchout supplierContact us
Grainger, Uline, McMaster… — cXML punchout, set up per supplier
EDIEnabled by support
EDIEDI (X12 / EDIFACT)Contact support
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 →

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.

Your systemQuickBooks
Your books · Vendor: Kestrel
Vendor ID · GL codePrivate to you
The shared relationship
Meridian ↔ KestrelBoth sides linked
Shared documents, workflow, and payment state, synchronized to each side’s own records.
Their systemWhatever they run
Their books · Customer: Meridian
Customer ID · GL codePrivate to them

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 →
Rivet Connect · Foundation

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

Request a demoPartner with Rivet
Rivet Connect — Your Systems Stay. Rivet Reads and Writes Through Them.