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 the document is a vendor bill, AP invoice, supplier payment request, or procurement record, keep it in the BILL AP path your company uses. Expensent can help before either destination by finding receipt and invoice emails, showing what needs review, and routing selected messages to the destination you configure.

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.

The risky part of old Divvy guidance is not the word Divvy. It is the assumption that a saved receipt address, sender setting, or matching rule still applies to all current BILL Spend & Expense accounts. Receipt submission details can vary by account configuration, admin settings, product path, connected integrations, and whether the receipt is tied to a card transaction, a reimbursement, or a bill.

If your internal instructions still mention receipts@divvy.co, do not delete them just because the brand changed. First verify whether your current BILL Spend & Expense account still shows that address for the workflow you use. If it does, test it with one known card receipt and confirm the result in BILL. If BILL shows another destination or product-specific path, use the current destination instead.

The same caution applies to secondary receipt emails, shared inboxes, forwarding aliases, multiple attachments, body-only receipts, confirmation emails, and file limits. Current public BILL product pages verify receipt capture and matching at the product level, but they do not publish one universal receipt address or file-format rule for every account and channel. Confirm those details in your current BILL workflow.

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.

The biggest change is not that Divvy disappeared from user vocabulary. The change is that BILL now owns the product family, names, settings surface, and help materials. Current pages use BILL Spend & Expense for the spend-management product and BILL Divvy Card for the card. Older pages and company playbooks may still say Divvy, Divvy card, or old receipt-address language.

The second change is that receipt capture is broader than manual forwarding. BILL product updates in 2026 describe receipt matching through integrations, a Transaction Agent for Spend & Expense, admin-level Gmail receipt matching controls, Lyft receipt integration, travel receipt handling, and receipt-policy updates. Those updates point to a product that is evolving beyond a single email address.

That evolution is useful, but it is also why older guidance needs verification. A legacy instruction might still work for one account, while another account uses an integration, connected Gmail workflow, mobile capture, text-to-receipt path, or admin-controlled policy. The safe operating answer is not to argue about the old name. It is to check the current BILL account, test the path, and document the result.

Expensent helps before BILL receipt matching. It connects to the inbox where receipt and invoice emails arrive, identifies likely financial-document emails, and shows them by next action. A user can forward a reviewed message, keep ambiguous items in review, handle portal-download messages separately, or create a rule from a known sender and subject pattern.

That is different from replacing BILL Spend & Expense. BILL remains the system for the BILL Divvy Card, card transactions, budgets, policies, approvals, reimbursements, receipt matching, accounting sync, mobile capture, connected integrations, and administrator controls. Expensent does not decide whether a receipt matches a transaction after it reaches BILL.

The best Expensent fit is inbox routing: historical catch-up, receipts spread across multiple staff inboxes, recurring vendor receipts, shared mailbox review, body-only receipts that need judgment, and portal notices that should not be blindly forwarded. After you verify the current BILL/Divvy destination and sender behavior, Expensent can route selected or rule-approved messages to that destination and keep exceptions visible.

If your team has a Divvy-era receipt checklist, update it by proof, not by find-and-replace. Keep the useful operational memory, but label which parts are confirmed in the current BILL account and which parts are historical context. The goal is to avoid breaking a working workflow while removing stale assumptions that can misroute receipts.

First, list the existing claims: product name, receipt address, sender requirements, alternate emails, file types, mobile upload, matching expectations, confirmation emails, and escalation path. Second, verify each claim against the current BILL account or current official source. Third, run a small test batch that includes a clean PDF receipt, a body-only receipt, a portal notice, a shared-mailbox send, and a known cardholder send if those cases matter to your process.

Finally, decide which automation is safe. Broad mailbox rules are brittle because a merchant can send receipts, refunds, reminders, security alerts, and promotional messages from related addresses. Expensent rules are better suited to reviewed sender-and-subject patterns. Even then, keep exception categories visible so finance can catch documents that need a portal download, manual review, or AP routing.