Automate Divvy Receipt Emails to BILL Spend & Expense

Start by naming the downstream record. A card receipt supports an existing BILL Divvy Card transaction. A reimbursement supports an employee claim for out-of-pocket spend. An AP document supports a supplier bill, approval, and payment process. The same merchant can send documents for more than one lane, so sender identity alone is not enough.

Current BILL pages place card receipt matching and reimbursements within Spend & Expense, but they remain distinct workflows. BILL AP separately captures, approves, and pays supplier bills. Route each document to the account-confirmed path for its intended record; do not send all financial mail to a generic Divvy destination.

Card receipt: preserve the cardholder context and target the approved card-receipt path. Reimbursement: keep it in the company reimbursement submission and approval path. AP document: send it to the approved AP intake process, not card receipt matching.

Do not hard-code a legacy Divvy receipt address from memory, search results, or another company playbook. Use the destination displayed in the current BILL account or supplied by the company administrator or current BILL support instructions for the exact card, reimbursement, or AP workflow. The related branding and destination comparison explains why older Divvy names and current BILL paths cannot be treated as interchangeable.

Destination is only half of the test. BILL documents a Gmail receipt integration that searches a participating cardholder inbox after a card transaction clears, and admins choose which employees are included. That connected-mailbox boundary does not prove that an assistant, alias, shared mailbox, or forwarding service will be attributed to the same user. Preserve the original user context where the approved path requires it, and verify any alternate sending path in the live account.

Record the approved destination separately for card receipts, reimbursements, and AP. Record which user or connected mailbox BILL expects for the card receipt path. Treat aliases, delegated accounts, and shared inboxes as unverified until a controlled test succeeds.

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

Confirmed sender-and-subject patterns can route new recurring receipts automatically. Preserve the cardholder or user attribution required by the account's current receipt workflow.

Keep card receipts, reimbursements, and AP invoices on their separate BILL paths after delivery.

Some messages cannot be authorized from sender and subject alone. A portal notice may announce a receipt without containing the document. A body-only receipt may render differently after routing. A marketplace message may combine an order, split shipment, refund, or several attachments. An invoice-like document may belong to AP rather than the card transaction that prompted the search.

Keep these messages in Action Center review until a person obtains the usable document, identifies the cardholder and product lane, and chooses the approved destination. Do not infer universal support for body content, attachments, alternate senders, or file handling from one successful example; those details can vary by intake path and account configuration.

Portal notice: obtain the source receipt before routing. Body-only receipt: keep in review until the exact path has been tested. Ambiguous document: identify card receipt, reimbursement, or AP before sending. Unclear user: resolve cardholder or mailbox attribution before automation.