Divvy vs BILL Spend & Expense Receipts: What Changed?

The current official naming is not the same as the old search habit. BILL completed its acquisition of Divvy in 2021. BILL now markets the spend-management product as BILL Spend & Expense and the card product as the BILL Divvy Card. Many teams still say Divvy because their users, bookmarks, old workflows, and receipt habits were built before the rebrand.

For receipts, that means older Divvy guidance is useful context, not a reliable operating manual by itself. A page, forum answer, or saved internal note that says to send receipts to an old Divvy address may describe a real historical workflow, but it does not prove the destination, sender requirements, file handling, or matching behavior for your current BILL account.

Use this rule: if the document supports a BILL Divvy Card transaction, troubleshoot it in BILL Spend & Expense. If it is a vendor bill or AP invoice, keep it in the BILL AP path. Expensent can find and route either document type to the destination you configure.

Use current BILL account instructions for receipt destinations and sender rules. Treat Divvy-era receipt addresses as account-specific until verified. Separate card receipts from BILL AP bills before forwarding anything.

The name map is the first thing to fix because the receipt workflow depends on product scope. Divvy was the spend-management company that combined expense software with corporate cards. BILL acquired Divvy and now presents the spend-management area as BILL Spend & Expense. Current BILL pages describe Spend & Expense as company cards, expense tracking, spend controls, budgets, receipt capture, matching, reimbursements, and accounting connections in one product family.

The BILL Divvy Card is the card product inside that family. BILL describes the card as part of BILL Spend & Expense, with physical and virtual card use, credit access subject to approval, budgets, mobile controls, and accounting integrations. That is the card lane most people mean when they ask why a Divvy receipt did not match.

BILL Expenses is not a separate legacy Divvy product in the way many search results imply. It is a current BILL product page and feature area under Spend & Expense. BILL AP and AR are different product areas for payables and receivables. Mixing those names leads to wrong routing: a receipt for a card swipe should not be handled like a vendor bill, and an AP invoice should not be forced into a card receipt matching flow.

Start with the product lane. Open BILL and confirm whether the document belongs to Spend & Expense, the BILL Divvy Card, reimbursements, AP, procurement, or another workflow your company has enabled. A receipt can fail to appear simply because it was sent to the wrong lane. A vendor invoice may belong in BILL AP, while a meal receipt for a card swipe belongs with the card transaction.

Next verify sender identity. Look past the display name and check the actual From address that will reach BILL. Assistants, shared mailboxes, procurement aliases, travel desks, and forwarding services can produce a sender that is not tied to the cardholder. BILL product updates also describe Gmail receipt matching controls where admins can include or exclude employees. That makes sender and user scope a real setup variable, not a generic email feature.

Then test the receipt path with a clean example. Use one visible card transaction, one clear vendor receipt, the account-confirmed destination, and the sender address BILL recognizes. After sending, check the result inside BILL Spend & Expense. Did the receipt arrive? Did it match the expected transaction? Did it need review? Did it attach to the wrong item? Record those answers before expanding routing to old inboxes or recurring vendor patterns.

BILL AP and BILL Spend & Expense can live under the same BILL platform, but the workflows solve different problems. BILL AP pages focus on capturing invoices, routing approvals, processing payments, and syncing with accounting software. BILL Spend & Expense pages focus on cards, expense tracking, budgets, receipt capture, matching, reimbursements, and spend controls.

That distinction matters for teams that inherited both Bill.com and Divvy names. A supplier bill that needs approval and payment is not a card receipt just because it arrived by email. A card receipt is not an AP bill just because it has a PDF attached. If your company uses both product areas, ask which downstream record is supposed to exist before you route the document.

Pricing language can also cause confusion. The current pricing page checked for this guide lists BILL Spend & Expense at $0 per user per month and says AP and AR are paid subscriptions with transaction fees depending on payment type. That does not mean all BILL workflows are free, and it does not remove card, credit, eligibility, or bank-partner terms. For content and operations, keep AP subscription questions separate from Spend & Expense receipt routing.

Expensent finds current and historical receipt emails and sends selected documents to the destination confirmed in the active BILL Spend & Expense account.

Confirmed sender-and-subject patterns can route new recurring receipts automatically. This keeps old Divvy documentation from becoming the routing source of truth.

BILL Spend & Expense handles transaction matching and expense completion after delivery.