Why a Divvy Receipt Did Not Match in BILL

Start with naming and scope because Divvy, BILL Spend & Expense, BILL Divvy Card, BILL Expenses, and BILL AP are easy to mix up. The search query may say Divvy, but BILL now markets the spend-management product as BILL Spend & Expense and the card as the BILL Divvy Card. That card receipt workflow is not the same as BILL AP bill intake or a reimbursement-only process.

A receipt will not match if it is in the wrong product lane. A meal receipt for an existing BILL Divvy Card transaction belongs in the card expense workflow. A vendor invoice, AP bill, or payment request belongs in the AP workflow your company uses. An out-of-pocket expense or reimbursement can have a separate review path. Before fixing matching, confirm the document type and the destination your administrator expects.

BILL public product pages say Spend & Expense combines company cards, expense tracking, budgets, controls, receipt capture, and matching. That means BILL owns the transaction record and the matching decision after the receipt arrives. Expensent belongs upstream: it helps teams find, review, and route inbox receipts toward the configured BILL/Divvy destination.

If the receipt never appears or lands under the wrong person, inspect sender identity before changing the file. BILL product updates describe Gmail receipt matching controls for Spend & Expense, including admin selection of which employees are included and a matching search scoped to transaction amount, merchant name, and date. That is different from a generic mailbox blast where any sender can submit any receipt for any cardholder.

Look at the actual From address on the email. Mail clients can hide aliases, delegated senders, shared mailboxes, and forwarding services behind a friendly display name. If the receipt was forwarded by an assistant, travel coordinator, procurement alias, or shared inbox, BILL may see a sender that is not tied to the cardholder or not enabled for the company workflow.

Older Divvy instructions have referenced secondary receipt emails, but the current setting name and availability can vary by account and admin configuration. Treat any secondary or alternate sender as a thing to verify in the live BILL Spend & Expense profile or current Help Center, not as a permanent fact. For diagnosis, ask the cardholder to send one clean original receipt from the address BILL associates with their account.

Many finance teams remember the legacy Divvy receipt address, receipts@divvy.co. Because BILL has continued to evolve Spend & Expense under BILL branding, do not assume that address is universal or unchanged. Use the receipt destination shown inside your BILL Spend & Expense account or current BILL Help Center instructions for your specific workflow.

This matters when a user says, "I sent it to Divvy." They may have sent it to an old address, a team alias, an AP intake inbox, a reimbursement address, or a destination copied from another company. Any of those can produce the same symptom: the receipt is missing from the expected card transaction.

When the destination is uncertain, test one known-clean receipt instead of bulk-forwarding old emails. Pick a visible card transaction, use the account-confirmed destination, send from the confirmed user address, and document the timestamp. If the receipt still does not appear, you have removed the two most common variables: sender and destination.

Receipt matching depends on the expected transaction existing in BILL Spend & Expense. BILL public product updates refer to receipt matching against card transactions, including Gmail receipt matching for cleared card transactions. If the transaction is not visible, not ready for review, or still changing after authorization, the receipt may not have a stable target.

Timing problems show up in predictable places: restaurants where the final amount includes a tip, hotels where folios close after checkout, online orders that split shipments, marketplaces that charge under a different descriptor, and travel purchases where an itinerary arrives before final payment details. A receipt sent too early can look valid in the inbox but still fail to match.

Do not make repeated retries the first fix. Confirm the transaction amount, merchant descriptor, date, cardholder, and status in BILL. If the transaction is missing, wait until it appears or ask the cardholder/admin to confirm whether the charge belongs to another card, another entity, a virtual card, or a reimbursement path.

BILL has described Spend & Expense receipt matching in terms of transaction amount, merchant name, and date for its Gmail integration controls, and its product pages market automatic matching to the right transaction. Use those fields as the first reviewer checklist even when the submission came through a different channel.

Start with amount. The receipt may show the pre-tip subtotal while the card charge includes tip, tax, delivery fees, currency conversion, authorization holds, or later adjustments. Next compare merchant. The receipt may show the storefront while the card descriptor shows a parent company, processor, booking platform, or franchise entity. Then compare date. The receipt date, service date, shipment date, hotel checkout date, and posted transaction date can differ.

If the receipt is correct but the fields do not line up cleanly, treat it as a review case rather than a routing failure. Attach or review it in BILL according to your company process, add context where required, and avoid using Expensent or any inbox rule as a way around policy requirements.

BILL does not publish one universal public rule for receipt formats, file sizes, confirmation timing, or body-only email behavior across every Spend & Expense path. Those details can change by product path, upload channel, or account setting.

Use a conservative receipt test. Prefer the original vendor receipt email or a readable PDF/image from the vendor. Avoid sending password-protected PDFs, calendar invites, shipping notices with no itemized proof, forwarded chains with many quoted messages, embedded signature images, or multi-attachment bundles until you have confirmed how BILL handles them in your account.

Body-only receipts deserve special attention. Some merchants put the entire receipt in the email body, while others link to a portal or hide key proof in images that forwarding can strip or compress. If a clean attachment works but a body-only email does not, the failure is not the card transaction. It is the intake format, and the safer fallback is manual upload or a reviewed routing rule that keeps those cases visible.

Manual review is the right answer when the receipt is real but automatic matching did not prove the relationship. Open the expected transaction in BILL Spend & Expense, attach or review the receipt through the workflow your company supports, and add any required memo, category, project, or policy context.

If the receipt attached to the wrong transaction, do not leave duplicate support in place. Remove or correct the bad attachment according to BILL and company policy, then attach the receipt to the right transaction. If the receipt is missing but the email delivery record exists, keep the evidence with the transaction notes or support request so reviewers can see what happened.

Escalate with specifics. A useful support note says who sent the receipt, where it was sent, when it was sent, which card transaction should have matched, and what the receipt file/body contained. A vague "Divvy did not match my receipt" note often sends support back to the same checklist.

Use Expensent when the problem starts in the inbox: receipts buried across multiple users, historical catch-up after a messy close, vendor emails that arrive in shared mailboxes, portal notices that need judgment, or recurring receipt patterns that should be reviewed before routing. Expensent gives finance a controlled inbox-to-Divvy step before BILL Spend & Expense attempts matching.

The boundary is important. Expensent does not replace BILL Spend & Expense, the BILL Divvy Card, budgets, policy rules, approvals, reimbursements, receipt matching, accounting sync, or admin configuration. It helps users identify likely invoice and receipt emails, decide what should be sent, route selected documents to the configured BILL/Divvy destination, and keep exceptions out of blind forwarding rules.

A practical rollout starts with proof. Confirm the current BILL destination, test a few clean card receipt examples, verify where they land, and then create Expensent rules from real reviewed sender-and-subject patterns. Keep ambiguous document types, body-only receipts, portal links, and shared-mailbox sends in review until the downstream BILL behavior is known.