What Ramp data does Well pull into QuickBooks?

Ramp streams card transactions, approved bills, reimbursements, vendor records, and policy events to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to QuickBooks as bills or receipts via email-in at the @qbodocs.com address, with vendor, date, and amount populated by QuickBooks, with the Ramp event ID preserved on the entry for audit.

How does Well match Ramp records to entries in QuickBooks?

Ramp transactions are scored against open QuickBooks entries on counterparty, amount, date proximity, and reference; above 85% the bank line reconciles automatically and posts to the right account, between 55% and 85% the candidate QuickBooks entries are surfaced for sign-off, below 55% the line stays open and is added to a review queue.

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

Ramp sends each event with a stable resource ID that Well tracks against the QuickBooks ledger. Webhook replays (which Ramp can issue for delivery retries) are recognised by ID and either skipped or used to update the existing QuickBooks entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.

Can I customise which Ramp fields are sent to QuickBooks?

The default mapping covers every Ramp field your QuickBooks chart of accounts accepts (counterparty, amount, currency, reference, tax). From the integration settings page you can override mappings field-by-field, attach computed values from your connected data (GL code, project tag, tax bucket), or ignore fields QuickBooks does not need. Custom mappings are versioned and apply only to records reconciled after the change, so anything you have already reviewed and posted in QuickBooks is left exactly as it stands.

What happens if I disconnect Ramp or QuickBooks?

Disconnecting Ramp stops the flow at the source. Well asks the Ramp MCP server to revoke the access token; Ramp returns confirmation and stops streaming events the moment it is acknowledged. Anything you already reviewed and posted in QuickBooks is QuickBooks's own record and is untouched; Well never held a write credential to it. Records held for review in Well remain in the queue so you can finish them by hand. Reconnecting later resumes from the last successful sync, not from scratch.

How does Well authenticate with Ramp and QuickBooks?

Ramp's MCP server handles authorisation directly; Well receives an access token through Dynamic Client Registration and never sees raw user credentials. For the delivery side, Well forwards the reconciled document to your QuickBooks email-in address once it clears the matching threshold; QuickBooks creates the draft record from it and you confirm and post it. Well holds no write credential to QuickBooks. Tokens are encrypted at rest and in transit under TLS 1.3. Ramp and QuickBooks together cover multiple regions; Well's storage region is configured per workspace.

Ramp to QuickBooks

AvailableNative · RampNative · QuickBooks

Connect Ramp to QuickBooks with Well

Reconcile Ramp card transactions and bills against your open invoices inside Well, then forward the matched documents to QuickBooks's email-in inbox for one-click review.

Connect both toolsView all integrations

Ramp

Source

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

QuickBooks

Target

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

Why this pair

Ramp closes its books fastest when its card spend lands in the general ledger already classified.

Ramp pushes card-transaction events to Well over its MCP server with the policy classification and receipt attached; QuickBooks Online accepts emailed PDFs at @qbodocs. com and turns them into bills or receipts. Connecting Ramp to QuickBooks through Well matches each Ramp charge inside Well against the right vendor and surfaces the Ramp policy category, then forwards the matched document to QuickBooks' email-in. QuickBooks creates the bill or receipt with vendor, date, and amount populated; your team confirms the expense account and bank reconciliation in the For Review tab.

What Well does between Ramp and QuickBooks

One-way: Ramp into Well into QuickBooks
Sync mode: Real-time MCP push
Events arrive in seconds

Trigger from Ramp

4 events · pick one

Well engine·recipe·When a Ramp card is swiped

Source

from card · live webhook

Algolia SAS

via Ramp

Card

When a Ramp card is swiped

INV-1024 · 22 Apr 2026€1,284.00

Extract

5 fields read from Ramp

5 fields read

CounterpartyAlgolia SAS
Booking date22 Apr 2026
Amount€1,284.00
CurrencyEUR
ReferenceINV-1024

Enrich

against your historical record graph

4 fields added

CounterpartyAlgolia SAS
Tax idFR75814107155
Ledger account6156 · Search infra
Match1 candidate invoice

Confidence97%

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

Post

post as bills and receipts

Route the record to the For Review tab

auto-posted

posted

TypeReview
VendorAlgolia SAS
Amount€1,284.00
Ledger6156 · Search infra
Source docattached
Confidence97%

audit linkto QuickBooks

Action in QuickBooks

1 compatible with this trigger

Route the record to the For Review tab

Reconcile Ramp transactions to QuickBooks ledger lines.

01Featured

Resolve the merchant behind a charge

Well reads spend from Ramp and matches each merchant to a company record, then forwards the matched document to QuickBooks's email-in address with the vendor resolved.

Collapse look-alike merchants

Merchant strings that resolve to one company are treated as the same vendor inside Well before the forward, so QuickBooks does not accumulate near-duplicates.

Carry the spend context onward

Each forwarded document keeps the Ramp charge and its resolved company attached, so QuickBooks sees the vendor and the spend behind it together.

Keep the source charge attached

The Ramp transaction Well matched stays linked to the document sent to QuickBooks, so each entry traces back to the charge it came from.

10 signals and actions across Ramp and QuickBooks

When a Ramp card is swiped
Captures every card transaction with merchant, amount, currency, and category. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Transaction
When a Ramp transaction is coded by a Ramp rule
Picks up Ramp transactions that arrive with an automated coding rule already applied. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Transaction
When a Ramp transaction trips a spend policy
Pulls the policy_violations field on the transaction so non-compliant lines surface for review. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Transaction
When a Ramp card account is read
Pulls each Ramp card account the workspace holds with its limit and the cards bound to it. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Account
When a Ramp vendor record appears in your account
Well discovers new Ramp vendors via the read-only ETL load and mirrors them as company records. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Company
When a Ramp reimbursement is filed
Pulls employee reimbursement requests with their amount and category as a transaction. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Transaction
Resolve the vendor from the bill
QuickBooks OCR resolves the vendor name from the document. You confirm or merge against an existing vendor on first sight.
Action·Company
Attach the source document to the QuickBooks record
The forwarded PDF is stored on the QuickBooks bill or receipt as the source.
Action·Document
Create a bill or receipt in QuickBooks
Well forwards the PDF to your @qbodocs.com address; QuickBooks creates a bill or receipt with vendor, date, and amount populated. QuickBooks picks the record type per document.
Action·Invoice

Reference

Field mapping for Ramp → QuickBooks

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

Transaction fields

3 fields flow from Ramp into QuickBooks.

Ramp field	Label		QuickBooks field	Label
transaction.amount	Amount	→	Amount	Amount
transaction.currency_code	Currency	→	CurrencyRef	Currency
transaction.id	Transaction id	→	PrivateNote	Source id

Invoice fields

4 fields flow from Ramp into QuickBooks.

Ramp field	Label		QuickBooks field	Label
bill.invoice_number	Invoice number	→	DocNumber	Doc number
bill.invoice_date	Issue date	→	TxnDate	Bill date
bill.due_date	Due date	→	DueDate	Due date
bill.currency_code	Currency	→	CurrencyRef	Currency

Connect Ramp and QuickBooks in three steps.

1
Connect Ramp
Click Connect with Ramp; the Ramp MCP server registers a Well client automatically. Ramp's MCP server registers a read-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
2
Map your accounts
Well discovers Ramp's card transactions, approved bills, reimbursements, vendor records, and policy events and the the QuickBooks For Review inbox. Counterparty proximity, amount, date, and reference drive the match score; lines above 85% post automatically and the rest queue for a one-click sign-off.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect QuickBooks
Click Connect with QuickBooks; you approve the connection inside QuickBooks Online and authorise read-only discovery of your existing records so Well can match against them when forwarding documents. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your QuickBooks Online.
- AuthOAuth 2.0
- First syncup to an hour

How Ramp and QuickBooks stay secure with Well

Well connects to Ramp through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived Ramp secret; the server refreshes its own tokens on each session. Well's storage region is configured per workspace regardless of where Ramp and QuickBooks host theirs.

MCP server authStorage region per workspaceGDPR-aligned

Scopes Well requestsramp-mcp-remote.ramp.com/mcp

Read Ramp records
Scoped to card transactions, approved bills, reimbursements, vendor records, and related records. No access to anything else in your Ramp account.
granted
Deliver documents to your QuickBooks inbox
Well forwards the extracted document to your QuickBooks email-in address; QuickBooks reads bills or receipts via email-in at the @qbodocs.com address, with vendor, date, and amount populated by QuickBooks from it and you review and post. No write credential to QuickBooks is requested.
granted
Modify or delete Ramp records
Not granted. Ramp 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 Ramp’s admin panel.

Frequently asked questions about Ramp and QuickBooks on Well

01What Ramp data does Well pull into QuickBooks?: Ramp streams card transactions, approved bills, reimbursements, vendor records, and policy events to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to QuickBooks as bills or receipts via email-in at the @qbodocs.com address, with vendor, date, and amount populated by QuickBooks, with the Ramp event ID preserved on the entry for audit.
02How does Well match Ramp records to entries in QuickBooks?: Ramp transactions are scored against open QuickBooks entries on counterparty, amount, date proximity, and reference; above 85% the bank line reconciles automatically and posts to the right account, between 55% and 85% the candidate QuickBooks entries are surfaced for sign-off, below 55% the line stays open and is added to a review queue.
03How does Well prevent duplicates when posting Ramp records to QuickBooks?: Ramp sends each event with a stable resource ID that Well tracks against the QuickBooks ledger. Webhook replays (which Ramp can issue for delivery retries) are recognised by ID and either skipped or used to update the existing QuickBooks entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.
04Can I customise which Ramp fields are sent to QuickBooks?: The default mapping covers every Ramp field your QuickBooks chart of accounts accepts (counterparty, amount, currency, reference, tax). From the integration settings page you can override mappings field-by-field, attach computed values from your connected data (GL code, project tag, tax bucket), or ignore fields QuickBooks does not need. Custom mappings are versioned and apply only to records reconciled after the change, so anything you have already reviewed and posted in QuickBooks is left exactly as it stands.
05What happens if I disconnect Ramp or QuickBooks?: Disconnecting Ramp stops the flow at the source. Well asks the Ramp MCP server to revoke the access token; Ramp returns confirmation and stops streaming events the moment it is acknowledged. Anything you already reviewed and posted in QuickBooks is QuickBooks's own record and is untouched; Well never held a write credential to it. Records held for review in Well remain in the queue so you can finish them by hand. Reconnecting later resumes from the last successful sync, not from scratch.
06How does Well authenticate with Ramp and QuickBooks?: Ramp's MCP server handles authorisation directly; Well receives an access token through Dynamic Client Registration and never sees raw user credentials. For the delivery side, Well forwards the reconciled document to your QuickBooks email-in address once it clears the matching threshold; QuickBooks creates the draft record from it and you confirm and post it. Well holds no write credential to QuickBooks. Tokens are encrypted at rest and in transit under TLS 1.3. Ramp and QuickBooks together cover multiple regions; Well's storage region is configured per workspace.