Rivet Connect

Connect both sides without combining your systems.

Each company links Rivet to its own accounting or operating platform. Rivet coordinates the relationship while keeping internal system records private.

The privacy boundary

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

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

QuickBooks
Your books · Vendor: Kestrel
Private to you
The shared relationship
Meridian ↔ KestrelBoth sides linked
Shared documents, workflow, and payment state — synchronized to each side's own records.
Their system
Their books · Customer: Meridian
Private to them
Accounting

Start with QuickBooks. Expand from there.

QuickBooks

Connect QuickBooks to your side of each relationship — customers, vendors, invoices, and bills stay in sync with the shared work.

Xero

Ledger sync for Xero organizations, built on the same per-side privacy model.

Sage

Sage connectivity following the same canonical document model.

NetSuite

Mid-market ERP sync against the same canonical document model, per side.

Running something else? Tell us what you use — more connectors are in development.

Where Rivet connects

One canonical model over many providers.

Rivet owns the shared document, workflow, and payment models and treats external systems as interchangeable rails — keep your systems and providers; Rivet brings the experience together.

Accounting and ERP
QuickBooks, Xero, Sage, and NetSuite; more to follow.
Payments and banking
Payment, account, and settlement rails through partners, connected to the workflow.
Email
Invites, replies, and inbound documents route back into the relationship context.
Industry systems
Auction, floorplan, and operational platforms as the automotive network grows.

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

Rivet Connect — Connect Both Sides Without Combining Your Systems