What Dropbox data does Well pull into Bill.com?

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 Bill.com as bills via email-in inbox, with vendor, invoice number, amount, and due date populated by Bill.com's IVA OCR, with the original email message ID stored on every record for audit.

How often does Dropbox data sync to Bill.com?

Well polls the Dropbox API every fifteen minutes for new records; new activity reaches the downstream target on the next polling cycle. Records collected during a polling window are matched in a batch, then ranked by confidence; the Bill.com write happens at the end of the window, never mid-sync.

Does Well handle multi-currency records between Dropbox and Bill.com?

Dropbox carries the original transaction currency on every record and Bill.com natively ledgers in multiple currencies. Well preserves the original amount, applies your Bill.com chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Bill.com, so the Bill.com entry you post keeps both sides of the trade.

How does Well prevent duplicates when posting Dropbox records to Bill.com?

Every Dropbox message has a stable message ID, and Well stores it the moment the attachment is parsed. If the same email is reprocessed (label change, mailbox migration, or a manual rerun), Well recognises the message ID and skips the duplicate, or updates the linked Bill.com entry if a downstream field changed. Forwarded copies of the same invoice are caught by counterparty-plus-amount matching before they reach Bill.com.

Can I customise which Dropbox fields are sent to Bill.com?

The default mapping turns every parsed Dropbox attachment into a Bill.com-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 Bill.com field, or compute a tag from your connected data. Custom mappings are versioned so a change does not retroactively touch already-posted Bill.com entries.

How does Well authenticate with Dropbox and Bill.com?

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 Bill.com email-in address once it clears the matching threshold; Bill.com creates the draft record from it and you confirm and post it. Well holds no write credential to Bill.com. Tokens are encrypted at rest and in transit under TLS 1.3. Dropbox and Bill.com together cover multiple regions; Well's storage region is configured per workspace.

Dropbox to Bill.com

AvailableNative · DropboxNative · Bill.com

Connect Dropbox to Bill.com with Well

Stop hand-entering bills: Dropbox invoices arrive in Bill.com with vendor, amount, due date, and tax pre-filled, plus a credit-note offset when Well detected one.

Connect both toolsView all integrations

Dropbox

Source

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

Bill.com

Target

The Bill.

Why this pair

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

What Well does between Dropbox and Bill.com

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

Trigger from Dropbox

1 events · pick one

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

Source

from upload · 15-min poll

Figma Inc.

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

VendorFigma Inc.
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 entityFigma Inc.
Tax idEU826145320
Domainfigma.com
Ledger account6064 · SaaS

Confidence97%

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

Post

schedule as bills

Create a bill in Bill.com inbox

auto-posted

posted

TypeBill
VendorFigma Inc.
Amount€1,284.00
Ledger6064 · SaaS
Source docattached
Confidence97%

audit linkto Bill.com

Action in Bill.com

1 compatible with this trigger

Create a bill in Bill.com inbox

What Well does with Dropbox invoices on the way to Bill.com.

01Featured

Turn invoices into bills ready for scheduling

Well parses every invoice attachment in Dropbox into a bill record in Well (vendor, amount, due date, line items), then forwards the PDF to Bill.com's email-in inbox. The original message ID is kept on the document so AP can trace any bill back to the originating email.

Match parsed invoices to existing vendors

Before creating a new vendor proposal, Well probes the parsed invoice header against your prior history inside its own ledger. Above the match threshold the bill attaches to the existing vendor record; below it the proposal queues for sign-off, and the match is reflected on the document forwarded to Bill.com.

Capture amount context for the approval step

Each parsed Dropbox attachment carries amount and cost-centre context inside Well so approval routing in Bill.com sees the right metadata. Small invoices flow straight through; larger ones wait on a named approver in Bill.com based on the parsed amount.

Reconcile credit notes against the originating bill

Credit notes received in Dropbox are parsed inside Well, matched to the originating bill in its own ledger, and the offset is captured before delivery. The document forwarded to Bill.com reflects the net balance so AP does not have to compute the offset manually.

7 signals and actions across Dropbox and Bill.com

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.
Trigger·Company
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.
Trigger·Document
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.
Trigger·Invoice
Resolve a Bill.com vendor from the bill
Bill.com's IVA OCR resolves the vendor name from the document. You complete the vendor setup (banking, tax) separately.
Action·Company
Route the bill through Bill.com's multi-step approval policy
The created bill enters your Bill.com approval policy and is routed to the assigned approver roles in sequence; each approver reviews the coding and signs off before the bill is cleared for AP. Well never approves the bill, picks a funding account, or releases payment.
Action·Invoice
Create a bill in Bill.com inbox
Well forwards the PDF to your Bill.com inbox; Bill.com's IVA reads the vendor, invoice number, amount, and due date into a new bill and drops it straight into your AP approval policy.
Action·Invoice
Attach the source PDF to the Bill.com bill
The forwarded PDF is the bill record itself in Bill.com's inbox.
Action·Document

Reference

Field mapping for Dropbox → Bill.com

6 fields across 1 record type, open to see the full table.

Invoice fields

6 fields flow from Dropbox into Bill.com.

Dropbox field	Label		Bill.com field	Label
parsed.total_amount	Total amount	→	amount	Amount
parsed.currency	Currency	→	currency	Currency
parsed.invoice_date.issue_date	Invoice date	→	invoice_date	Invoice date
parsed.due_date	Due date	→	due_date	Due date
parsed.invoice_number	Invoice number	→	invoice_number	Invoice number
file.id	File id	→	external_id	External id

Connect Dropbox and Bill.com 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 Bill.com inbox awaiting approval. 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 Bill.com
In Bill.com, open Settings > Developer > API keys and create a key paired with your developer ID. Paste the key into Well; Bill.com's discovery endpoints are reached over TLS 1.3 and the secret is never echoed in the UI.
- AuthConnect
- First sync~10 min

How Dropbox and Bill.com 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 Bill.com 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 Bill.com inbox
Well forwards the extracted document to your Bill.com email-in address; Bill.com reads bills via email-in inbox, with vendor, invoice number, amount, and related records from it and you review and post. No write credential to Bill.com 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 Bill.com on Well

01What Dropbox data does Well pull into Bill.com?: 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 Bill.com as bills via email-in inbox, with vendor, invoice number, amount, and due date populated by Bill.com's IVA OCR, with the original email message ID stored on every record for audit.
02How often does Dropbox data sync to Bill.com?: Well polls the Dropbox API every fifteen minutes for new records; new activity reaches the downstream target on the next polling cycle. Records collected during a polling window are matched in a batch, then ranked by confidence; the Bill.com write happens at the end of the window, never mid-sync.
03Does Well handle multi-currency records between Dropbox and Bill.com?: Dropbox carries the original transaction currency on every record and Bill.com natively ledgers in multiple currencies. Well preserves the original amount, applies your Bill.com chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Bill.com, so the Bill.com entry you post keeps both sides of the trade.
04How does Well prevent duplicates when posting Dropbox records to Bill.com?: Every Dropbox message has a stable message ID, and Well stores it the moment the attachment is parsed. If the same email is reprocessed (label change, mailbox migration, or a manual rerun), Well recognises the message ID and skips the duplicate, or updates the linked Bill.com entry if a downstream field changed. Forwarded copies of the same invoice are caught by counterparty-plus-amount matching before they reach Bill.com.
05Can I customise which Dropbox fields are sent to Bill.com?: The default mapping turns every parsed Dropbox attachment into a Bill.com-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 Bill.com field, or compute a tag from your connected data. Custom mappings are versioned so a change does not retroactively touch already-posted Bill.com entries.
06How does Well authenticate with Dropbox and Bill.com?: 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 Bill.com email-in address once it clears the matching threshold; Bill.com creates the draft record from it and you confirm and post it. Well holds no write credential to Bill.com. Tokens are encrypted at rest and in transit under TLS 1.3. Dropbox and Bill.com together cover multiple regions; Well's storage region is configured per workspace.