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.
Forward extracted bill PDFs to your Bill.com inbox and its Intelligent Virtual Assistant opens a bill with the vendor, invoice number, amount, and due date already filled in. Each forwarded bill stays linked to its vendor and purchase order in your workspace.
Well writes reconciled bill, vendor, attachment to Bill.com after they clear your review queue, with the source-record link preserved. Use Bill.com as the destination for entries enriched across your other connected tools.
| In Well | To Bill.com | Relation | |
|---|---|---|---|
Payable | Bill | Writes as | |
Supplier | Vendor | Resolves to | |
Source PDF | Attachment | Attaches as |
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.
The forwarded PDF is the bill record itself in Bill.com's inbox.
Bill.com's IVA OCR resolves the vendor name from the document. You complete the vendor setup (banking, tax) separately.
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.
Connect Bill.com over OAuth 2.0: you approve on Bill.com's authorize screen, so the password never reaches Well; Well holds only a scoped token it can refresh.
Bill.com is a delivery target, not a source, so Well pulls nothing in. Once a record clears review, Well's pipeline can create a bill in Bill.com inbox.
Before delivery Well reconciles and enriches each document, resolving the bill, attachment, and vendor so what reaches Bill.com arrives matched and carries its full audit trail.
Well forwards each reconciled document to your Bill.com email-in address; Bill.com drafts the record from it and you review and post. Well holds no write credential to Bill.com.
Ask in plain language. Well answers from your connected Bill.com connection, resolved against the rest of your stack.
Ask anything about your Bill.com connection
Ask about your Bill.com connection…
Find your Bill.com inbox email address in Bill.com (the address its Intelligent Virtual Assistant reads documents from) and add it as the Bill.com delivery target in Well's Connections panel. There is no OAuth handshake to approve; the link is the inbox address itself.
Once the address is set, every document Well captures and extracts is forwarded as a PDF to the Bill.com inbox. Bill.com's OCR reads the attachment and opens a bill with vendor, invoice number, amount, and due date populated.
From there your team approves and pays the bill inside Bill.com as usual, while Well keeps the same bill linked to its vendor and purchase order for querying in your workspace. Bill.com stays the system of record for the payment.
Because delivery is email-in, there is no client secret to rotate. Removing the inbox address in Well stops delivery; bills already created in Bill.com are unaffected.
Bill.com receives documents through its inbox email address, so Well's only credential is the delivery target you configure, not an OAuth token into Bill.com's API. Well forwards extracted PDFs to that inbox and Bill.com's Intelligent Virtual Assistant opens the bill; Well cannot read Bill.com's ledger or alter a posted bill. The boundary is deliberate: Well delivers, Bill.com books.
Read Bill.com records
Endpoints the Bill.com API token grants, scoped by your consent.
Resolve bill, vendor, and payment across your stack
Match identifiers in Bill.com against the same entities your other connected tools expose, so each record carries cross-tool context.
Deliver documents to your Bill.com inbox
Well forwards approved documents to your Bill.com email-in address; Bill.com drafts the record and you post it. No write credential to Bill.com is requested.
Store Bill.com passwords or session cookies
Authentication runs through OAuth 2.0 tokens we never see.
Well takes a document you have already captured and extracted, then forwards the PDF to your Bill.com inbox email address. Bill.com's Intelligent Virtual Assistant reads the PDF and opens a bill with the vendor, invoice number, amount, and due date filled in, ready to enter your approval workflow. There is no spreadsheet hop and no retyping; the file Well sends becomes the bill record itself.
No. Delivery runs entirely through Bill.com's email-in inbox, which is the surface Bill.com exposes for document capture. Well sends the PDF there and Bill.com's OCR does the rest. A direct OAuth write that creates the bill object without the inbox step is not part of the connector today, so the honest path is email-in to the IVA, not an API push.
The approver opens a Bill.com bill that already carries the vendor, invoice number, amount, and due date the IVA pulled from the PDF Well sent, with the source document attached to the record. Because Well extracted the fields before forwarding, what lands is a complete bill rather than a blank shell waiting on manual entry. The reviewer approves or routes it instead of keying it in.
Inside your workspace, yes. Well keeps the extracted bill linked to the matching vendor record and any open purchase order it can resolve, so the payable sits next to its supplier and order context before it is ever sent to Bill.com. On the Bill.com side, the IVA-created bill carries the fields Well extracted; Bill.com remains the system of record for the approval and payment that follow.
Well forwards each extracted PDF to the Bill.com inbox in the background as documents clear extraction, so a bill appears in Bill.com's inbox shortly after Well captures it. Bill.com's OCR then turns the attachment into a draft bill on its own side. Well is the capture-and-delivery layer here, not a poller of Bill.com state.
Open the Bill.com connection in Well and remove it, and Well stops forwarding documents to your Bill.com inbox immediately. Nothing needs to be unwound on the Bill.com side because Well only ever sent PDFs to the inbox; it never held a write token into Bill.com's ledger. Bills that already arrived in Bill.com stay there under your control.
Ready-to-ship workflows that pair Bill.com with another tool through Well.
Square
Reconcile Square supplier-side activity inside Well, forward…
Ramp
Reconcile approved Ramp bills inside Well, forward each docu…
Razorpay
Bridge Razorpay supplier-side activity into Bill.com as sche…
Stripe
Route Stripe supplier-side activity into Bill.com as schedul…
Gmail
Capture supplier invoices from Gmail attachments and draft B…
More in Payments
Popular cross-category
Gmail
Connect Gmail to Well to collect and process invoices from your inbox.
QuickBooks
Connect QuickBooks to Well to sync accounting data and ledger records.
Xero
Connect Xero to Well to sync accounting data and ledger records.
Google Drive
Connect Google Drive to Well to import and export documents and invoices from your cloud storage.
Connect once. Every bill, vendor, payment reconciled in Well flows out to Bill.com with its source-graph link preserved. Disconnect any time.