What QuickBooks data does Well pull into Ramp?

Well polls the QuickBooks API on a fixed cadence and pulls bills, customers, and tax codes polled hourly from QuickBooks Online. Well resolves and scores each counterparty, then writes draft bills via email-in at the @ap.ramp.com address, with invoice number, vendor, payment details, and line items pre-filled by Ramp's OCR into Ramp with the original QuickBooks record ID kept on the entry.

How often does QuickBooks data sync to Ramp?

Well polls the QuickBooks API hourly, which fits QuickBooks's rate-limit envelope and keeps the downstream match window inside the same business day. The hourly pull respects QuickBooks's rate limits and feeds Ramp once per window with the batch's confidence outcomes already resolved.

Does Well handle multi-currency records between QuickBooks and Ramp?

QuickBooks carries the original transaction currency on every record, but Ramp ledgers in a single base; Well preserves the source currency, attaches the FX rate at the timestamp of the event, and the converted figure and the source amount both travel on the document Well forwards to Ramp, so both sides of the trade are visible when you post.

How does Well prevent duplicates when posting QuickBooks records to Ramp?

Well maintains a sync marker against QuickBooks so each window only pulls records strictly newer than the last successful sync; the QuickBooks record ID is then tracked into Ramp for second-line dedup. If the same record appears twice through a manual re-import or a sync marker rewind, Well recognises the ID and updates the existing Ramp entry rather than duplicating it.

What happens if a QuickBooks record fails to post to Ramp?

When a record fails to post to Ramp (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original QuickBooks record. Nothing silently drops.

How does Well authenticate with QuickBooks and Ramp?

QuickBooks runs a manual OAuth 2.0 flow that you approve inside QuickBooks; Well receives a refresh token scoped to the resources it needs to read. For the delivery side, Well forwards the reconciled document to your Ramp email-in address once it clears the matching threshold; Ramp creates the draft record from it and you confirm and post it. Well holds no write credential to Ramp. Tokens are encrypted at rest and in transit under TLS 1.3. QuickBooks and Ramp together cover multiple regions; Well's storage region is configured per workspace.

QuickBooks to Ramp

AvailableNative · QuickBooksNative · Ramp

Connect QuickBooks to Ramp with Well

Move QuickBooks bills and customers through Well and into Ramp as draft bills, with the audit trail kept on every record.

Connect both toolsView all integrations

QuickBooks

Source

The QuickBooks connection delivers documents into QuickBooks Online through its @qbodocs.

Ramp

Target

The Ramp integration connects your corporate card and expense management platform to Well.

Why this pair

Connect QuickBooks to Ramp through Well so records flow without manual rework.

What Well does between QuickBooks and Ramp

One-way: QuickBooks into Well into Ramp
Sync mode: Polling every 60 minutes
Up to 24 syncs/day

Trigger from QuickBooks

4 events · pick one

Well engine·recipe·When a QuickBooks bill is read

Source

from upload · hourly poll

Slack Technologies

via QuickBooks

Bill

When a QuickBooks bill is read

INV-2026-04-100 · 22 Apr 2026€1,284.00

Extract

6 fields read from QuickBooks

6 fields read

VendorSlack Technologies
Invoice numberINV-2026-04-100
Issue date22 Apr 2026
Total€1,284.00
Tax€256.80

Enrich

against your historical record graph

5 fields added

Legal entitySlack Technologies
Tax idEU372014983
Domainslack.com
Ledger account6064 · SaaS

Confidence97%

<55% refused55–85% review≥85% auto-posts

Post

reconcile as draft bills

Create a draft bill in Ramp Bill Pay

auto-posted

posted

TypeBill
VendorSlack Technologies
Amount€1,284.00
Ledger6064 · SaaS
Source docattached
Confidence97%

audit linkto Ramp

Action in Ramp

1 compatible with this trigger

Create a draft bill in Ramp Bill Pay

12 signals and actions across QuickBooks and Ramp

When a QuickBooks bill is read
Pulls QuickBooks bills with vendor, due date, line items, totals, and tax code on the hourly poll.
Trigger·Invoice
When a QuickBooks purchase order is read
Pulls QuickBooks purchase orders with vendor, line items, and totals to match against the arriving bill.
Trigger·Invoice
When a QuickBooks sales invoice is read
Captures QuickBooks sales invoices with customer, amount, currency, and reference for reconciliation.
Trigger·Invoice
When a QuickBooks payment is read
Reads the payment recorded against a QuickBooks invoice or bill with method and amount.
Trigger·Payment method
When a QuickBooks customer is read
Reads QuickBooks customer and vendor records with name, billing address, and tax registration to match against your companies.
Trigger·Company
When a QuickBooks credit memo is read
Captures QuickBooks credit memos with customer, totals, and tax so refunds reconcile against the original invoice.
Trigger·Invoice
When a QuickBooks account is read
Pulls bank-type accounts from the QuickBooks chart of accounts with currency and account number.
Trigger·Account
When a QuickBooks attachment is read
Picks up the source document attached to a QuickBooks bill or invoice.
Trigger·Document
Attach the source document to the Ramp bill
The forwarded PDF is stored on the Ramp draft bill as the source document.
Action·Document

Reference

Field mapping for QuickBooks → Ramp

9 fields across 2 record types, open to see the full table.

Invoice fields

4 fields flow from QuickBooks into Ramp.

QuickBooks field	Label		Ramp field	Label
Bill.TotalAmt.total	Total	→	matched_record.amount	Matched amount
Bill.CurrencyRef.currency	Currency	→	matched_record.currency	Currency
Bill.DocNumber.invoice_number	Doc number	→	matched_record.reference	Reference
Bill.Id.id	QuickBooks id	→	matched_record.id	Source id

Transaction fields

5 fields flow from QuickBooks into Ramp.

QuickBooks field	Label		Ramp field	Label
Purchase.TotalAmt.amount	Amount	→	transaction.amount	Transaction amount
Purchase.CurrencyRef.currency	Currency	→	transaction.currency_code	Currency
Purchase.TxnDate.created	Transaction date	→	transaction.user_transaction_time	Transaction time
Purchase.PrivateNote.description	Memo	→	transaction.merchant_name	Merchant
Purchase.Id.id	Purchase id	→	transaction.id	Ramp transaction id

Connect QuickBooks and Ramp in three steps.

1
Connect QuickBooks
Click Connect with QuickBooks; you approve the connection inside QuickBooks Online and authorise read access to bills, customers, and tax codes polled hourly from QuickBooks Online. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your QuickBooks Online.
- AuthConnect
2
Map your accounts
Well discovers QuickBooks's bills, customers, and tax codes polled hourly from QuickBooks Online and the the Ramp Bill Pay drafts queue awaiting approval. Match candidates are scored on counterparty, amount, date, and reference; above 85% confidence the link posts automatically, below it the candidate set queues for sign-off.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Ramp
Click Connect with Ramp; the Ramp MCP server registers a Well client automatically. Ramp's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
- First sync~30 min

How QuickBooks and Ramp stay secure with Well

Well calls QuickBooks with an OAuth 2.0 token scoped to read-only access. QuickBooks's consent screen lists the scopes before you approve; access tokens are exchanged and refreshed automatically before they expire. Well's storage region is configured per workspace regardless of where QuickBooks and Ramp host theirs.

OAuth 2.0Storage region per workspaceGDPR-aligned

Scopes Well requests

Read QuickBooks records
Scoped to bills, customers, and tax codes polled hourly from QuickBooks Online. No access to anything else in your QuickBooks account.
granted
Deliver documents to your Ramp inbox
Well forwards the extracted document to your Ramp email-in address; Ramp reads draft bills via email-in at the @ap.ramp.com address, with invoice number, vendor, payment details, and related records from it and you review and post. No write credential to Ramp is requested.
granted
Modify or delete QuickBooks records
Not granted. QuickBooks is read-only on Well's side; the source of truth never moves.
refused
Read other workspaces' data
Encryption keys are per-workspace; another tenant's records are inaccessible by design.
refused

Disconnect any time from Well settings or QuickBooks’s admin panel.

Frequently asked questions about QuickBooks and Ramp on Well

01What QuickBooks data does Well pull into Ramp?: Well polls the QuickBooks API on a fixed cadence and pulls bills, customers, and tax codes polled hourly from QuickBooks Online. Well resolves and scores each counterparty, then writes draft bills via email-in at the @ap.ramp.com address, with invoice number, vendor, payment details, and line items pre-filled by Ramp's OCR into Ramp with the original QuickBooks record ID kept on the entry.
02How often does QuickBooks data sync to Ramp?: Well polls the QuickBooks API hourly, which fits QuickBooks's rate-limit envelope and keeps the downstream match window inside the same business day. The hourly pull respects QuickBooks's rate limits and feeds Ramp once per window with the batch's confidence outcomes already resolved.
03Does Well handle multi-currency records between QuickBooks and Ramp?: QuickBooks carries the original transaction currency on every record, but Ramp ledgers in a single base; Well preserves the source currency, attaches the FX rate at the timestamp of the event, and the converted figure and the source amount both travel on the document Well forwards to Ramp, so both sides of the trade are visible when you post.
04How does Well prevent duplicates when posting QuickBooks records to Ramp?: Well maintains a sync marker against QuickBooks so each window only pulls records strictly newer than the last successful sync; the QuickBooks record ID is then tracked into Ramp for second-line dedup. If the same record appears twice through a manual re-import or a sync marker rewind, Well recognises the ID and updates the existing Ramp entry rather than duplicating it.
05What happens if a QuickBooks record fails to post to Ramp?: When a record fails to post to Ramp (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original QuickBooks record. Nothing silently drops.
06How does Well authenticate with QuickBooks and Ramp?: QuickBooks runs a manual OAuth 2.0 flow that you approve inside QuickBooks; Well receives a refresh token scoped to the resources it needs to read. For the delivery side, Well forwards the reconciled document to your Ramp email-in address once it clears the matching threshold; Ramp creates the draft record from it and you confirm and post it. Well holds no write credential to Ramp. Tokens are encrypted at rest and in transit under TLS 1.3. QuickBooks and Ramp together cover multiple regions; Well's storage region is configured per workspace.