What Dropbox data does Well pull into QuickBooks?

Well watches Dropbox for attachments matching the configured invoice and receipt filters, extracts supplier-invoice and document files read from a watched folder via Apideck file-storage, and forwards the structured output to QuickBooks as bills or receipts via email-in at the @qbodocs.com address, with vendor, date, and amount populated by QuickBooks, with the original email message ID stored on every record for audit.

What happens to historical Dropbox data when I first connect to QuickBooks?

Dropbox exposes the last full year through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing QuickBooks ledger, and re-running the backfill is safe because Well tracks the Dropbox record IDs and updates existing QuickBooks entries instead of duplicating them.

Can I customise which Dropbox fields are sent to QuickBooks?

The default mapping turns every parsed Dropbox attachment into a QuickBooks-shaped record (vendor, amount, due date, tax). From the integration settings page you can adjust the parsing prompt, force a vendor mapping, attach the original PDF on a specific QuickBooks field, or compute a tag from your connected data. Custom mappings are versioned so a change does not retroactively touch already-posted QuickBooks entries.

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

When a record fails to post to QuickBooks (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 Dropbox record. Nothing silently drops.

What happens if I disconnect Dropbox or QuickBooks?

Disconnecting Dropbox stops the flow at the source. Well calls the Dropbox OAuth revoke endpoint; the refresh token is invalidated and any in-flight access token is rejected on the next call. 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 Dropbox and QuickBooks?

Dropbox runs a manual OAuth 2.0 flow that you approve inside Dropbox; Well receives a refresh token scoped to the resources it needs to read. 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. Dropbox and QuickBooks together cover multiple regions; Well's storage region is configured per workspace.

Dropbox to QuickBooks

AvailableNative · DropboxNative · QuickBooks

Connect Dropbox to QuickBooks with Well

Dropbox attachments are parsed inside Well for vendor, amount, VAT, and due date, then the documents arrive at QuickBooks as drafts with the original message ID attached.

Connect both toolsView all integrations

Dropbox

Source

The Dropbox connection lets Well write processed documents into your Dropbox folder.

QuickBooks

Target

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

Why this pair

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

What Well does between Dropbox and QuickBooks

One-way: Dropbox into Well into QuickBooks
Sync mode: Polling every 15 minutes
Up to 4 syncs/hour

Trigger from Dropbox

2 events · pick one

Well engine·recipe·When an invoice file lands in the watched Dropbox folder

Source

from upload · 15-min poll

OpenAI Ireland

via Dropbox

Invoice

When an invoice file lands in the watched Dropbox folder

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

Extract

6 fields read from Dropbox

6 fields read

VendorOpenAI Ireland
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 entityOpenAI Ireland
Tax idIE3893540LH
Domainopenai.com
Ledger account6156 · AI services

Confidence97%

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

Post

post as bills and receipts

Create a bill or receipt in QuickBooks

auto-posted

posted

TypeBill
VendorOpenAI Ireland
Amount€1,284.00
Ledger6156 · AI services
Source docattached
Confidence97%

audit linkto QuickBooks

Action in QuickBooks

2 compatible with this trigger

Create a bill or receipt in QuickBooksResolve the vendor from the bill

What Well does with Dropbox invoices on the way to QuickBooks.

01Featured

Capture supplier invoices from email

Well watches Dropbox for attachments matching invoice patterns, extracts amount, VAT, supplier, and due date in Well, then forwards the PDF to QuickBooks's email-in inbox. The original message ID stays on the document so the audit trail traces from QuickBooks back to the email that delivered the invoice.

Route personal-card vs supplier receipts

Receipts arriving in Dropbox from employee personal cards are kept on the expense-reimbursement path inside Well, while supplier invoices route to the supplier-bill path. The category is decided from the sender domain plus the invoice format, so the right document type lands at QuickBooks rather than a mixed pile.

Resolve a new vendor from the invoice header

When an invoice arrives from a vendor Well does not recognise, the header (legal name, tax ID, bank IBAN) is parsed and a vendor record is proposed inside Well. The matched document is then forwarded to QuickBooks with the proposed match so QuickBooks's OCR can resolve it on arrival.

Catch missing attachments before delivery

If an Dropbox invoice references a credit memo or a delivery note that did not arrive, Well flags the missing attachment inside its own queue and holds delivery until you forward the supporting document. Documents reaching QuickBooks always carry their supporting paperwork.

7 signals and actions across Dropbox and QuickBooks

When a supplier is detected on a parsed Dropbox file
Extracts the supplier named on a parsed file and matches it against your existing companies. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Company
When an invoice file lands in the watched Dropbox folder
Reads the new PDF from the watched Dropbox folder and parses it into a structured invoice with supplier, amount, date, and tax. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Invoice
When a document file lands in the watched Dropbox folder
Picks up a new receipt or supporting document from the watched folder and stores it as a Well document for matching. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Document
Route the record to the For Review tab
The created bill or receipt lands in the QuickBooks For Review tab so your team confirms the expense account and bank match before posting. Well never writes the ledger entry itself.
Action·Transaction
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
Attach the source document to the QuickBooks record
The forwarded PDF is stored on the QuickBooks bill or receipt as the source.
Action·Document
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

Reference

Field mapping for Dropbox → QuickBooks

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

Invoice fields

7 fields flow from Dropbox into QuickBooks.

Dropbox field	Label		QuickBooks field	Label
parsed.total_amount	Total amount	→	TotalAmt	Total
parsed.currency	Currency	→	CurrencyRef	Currency
parsed.invoice_date.issue_date	Invoice date	→	TxnDate	Bill date
parsed.due_date	Due date	→	DueDate	Due date
parsed.invoice_number	Invoice number	→	DocNumber	Doc number
parsed.tax_total.tax	Tax total	→	TxnTaxDetail	Tax
file.id	File id	→	PrivateNote	Source id

Company fields

3 fields flow from Dropbox into QuickBooks.

Dropbox field	Label		QuickBooks field	Label
parsed.supplier_name	Supplier name	→	DisplayName	Display name
parsed.supplier_tax_id	Supplier tax id	→	TaxIdentifier	Tax id
parsed.vendor_domain	Domain	→	WebAddr.URI	Website

Connect Dropbox and QuickBooks in three steps.

1
Connect Dropbox
Click Connect with Dropbox; you authorise the folder Well watches through Apideck's file-storage connection and authorise read access to supplier-invoice and document files read from a watched folder via Apideck file-storage. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your Dropbox.
- AuthConnect
2
Map your accounts
Well discovers the Dropbox attachments matching your invoice pattern (supplier-invoice and document files read from a watched folder via Apideck file-storage) and the the QuickBooks For Review inbox. Tune the parsing prompt once on the first ten records; Well saves the mapping and applies it to every subsequent attachment above 85% confidence.
- 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.
- AuthConnect
- First syncup to an hour

How Dropbox and QuickBooks stay secure with Well

Well calls Dropbox with an OAuth 2.0 token scoped to read-only access. Dropbox'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 Dropbox and QuickBooks host theirs.

OAuth 2.0Storage region per workspaceGDPR-aligned

Scopes Well requests

Read Dropbox records
Scoped to supplier-invoice and document files read from a watched folder via Apideck file-storage. No access to anything else in your Dropbox 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 Dropbox records
Not granted. Dropbox 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 Dropbox’s admin panel.

Frequently asked questions about Dropbox and QuickBooks on Well

01What Dropbox data does Well pull into QuickBooks?: Well watches Dropbox for attachments matching the configured invoice and receipt filters, extracts supplier-invoice and document files read from a watched folder via Apideck file-storage, and forwards the structured output to QuickBooks as bills or receipts via email-in at the @qbodocs.com address, with vendor, date, and amount populated by QuickBooks, with the original email message ID stored on every record for audit.
02What happens to historical Dropbox data when I first connect to QuickBooks?: Dropbox exposes the last full year through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing QuickBooks ledger, and re-running the backfill is safe because Well tracks the Dropbox record IDs and updates existing QuickBooks entries instead of duplicating them.
03Can I customise which Dropbox fields are sent to QuickBooks?: The default mapping turns every parsed Dropbox attachment into a QuickBooks-shaped record (vendor, amount, due date, tax). From the integration settings page you can adjust the parsing prompt, force a vendor mapping, attach the original PDF on a specific QuickBooks field, or compute a tag from your connected data. Custom mappings are versioned so a change does not retroactively touch already-posted QuickBooks entries.
04What happens if a Dropbox record fails to post to QuickBooks?: When a record fails to post to QuickBooks (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 Dropbox record. Nothing silently drops.
05What happens if I disconnect Dropbox or QuickBooks?: Disconnecting Dropbox stops the flow at the source. Well calls the Dropbox OAuth revoke endpoint; the refresh token is invalidated and any in-flight access token is rejected on the next call. 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 Dropbox and QuickBooks?: Dropbox runs a manual OAuth 2.0 flow that you approve inside Dropbox; Well receives a refresh token scoped to the resources it needs to read. 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. Dropbox and QuickBooks together cover multiple regions; Well's storage region is configured per workspace.