BILL Inbox vs Vendor Direct-Send: Which Invoice Intake Path Fits?

The right BILL invoice intake path depends on where invoices arrive. Vendor direct-send works when a trusted vendor sends a clean invoice to the current BILL AP destination. Expensent covers invoices that still reach employee or shared mailboxes, including historical documents and recurring vendor emails.

BILL is the AP system after the invoice arrives. Its public accounts payable page describes vendors emailing digital invoices to a dedicated AP address, paper invoices being uploaded by drag and drop or mobile capture, AI reading and extracting data for review, approval routing, payment methods, and accounting sync. That is the downstream workflow. The intake decision is about how the invoice gets there without losing vendor context or flooding BILL with noise.

A good decision framework separates three questions: who receives the original invoice, who reviews unclear messages, and where the approved document should land. If a vendor can send directly and the result is clean, use vendor direct-send. If the invoice lands with an employee or shared inbox, forward it internally or through Expensent. If the email is only a portal alert, keep it in a download-and-review queue until the actual invoice file is available.

Vendor direct-send means the vendor sends the invoice directly to the BILL AP destination your company provides. This can remove an employee from the forwarding loop, reduce lag, and give finance a consistent intake path for recurring bills. It is strongest when the vendor portal allows a billing contact email, the invoice is attached as a readable document, and the vendor rarely sends unrelated mail from the same billing channel.

The risk is that vendor direct-send can hide context. If the vendor changes the email template, sends a renewal quote instead of an invoice, attaches a statement instead of a bill, or requires a portal login, the message may still arrive at the AP front door. Finance then has to determine whether the item is payable, informational, duplicate, or incomplete.

Use direct-send deliberately. Keep a register of vendors that were given the BILL destination, confirm the first few arrivals inside BILL, and document who owns exceptions. If a vendor sends invoices for multiple entities, projects, or approvers, direct-send may still work, but only after the team confirms how that context will be captured in BILL.

Good fit: stable recurring vendors with clean invoice attachments. Good fit: vendor portals that support a billing email or AP contact. Poor fit: portal-only notices, mixed transaction emails, statements, refunds, quotes, and vendors that require employee context.

Internal forwarding keeps a person or shared mailbox in the loop before the document enters BILL. That is useful when the invoice was sent to a project owner, office manager, founder, or bookkeeper who knows why the bill exists. The forward can preserve the original message, include the attachment, and add notes that explain the vendor, department, entity, or expected approver.

The weakness is repeat work. Manual forwarding depends on people noticing the invoice, remembering the BILL destination, including the attachment, and not forwarding the same document repeatedly. A broad mail rule can reduce clicks, but it can also route confirmations, statements, refunds, and account notices into the AP inbox. The more vendors and inboxes involved, the harder it becomes to see what has already been sent.

Internal forwarding is often the right default for one-off vendors and ambiguous invoices. It becomes a bottleneck when the same recurring messages pile up every month or when year-end cleanup requires reviewing older email. That is where a reviewed queue is more useful than a raw forwarding rule.

Good fit: first-time vendors, ad-hoc invoices, and messages that need internal notes. Good fit: invoices that arrive in employee or shared inboxes before finance sees them. Poor fit: high-volume recurring invoices that follow a proven sender and subject pattern.

Vendor direct-send works for reliable recurring vendors. Expensent covers invoices that still arrive in employee or shared inboxes, including historical documents.

Send selected documents to the BILL destination shown in the account, then create sender-and-subject rules for confirmed recurring patterns.

Portal notices and unusual messages remain visible, while BILL handles the AP workflow after each invoice arrives.

Portal-only vendors are one reason a direct-send policy can look better on paper than it works in practice. The email may say an invoice is available, but the actual payable document is behind a login. Sending that alert to BILL does not necessarily give BILL the invoice file it needs for review and approval.

Exceptions also include statements, credit notes, refund notices, payment confirmations, renewal quotes, shipping documents, W-9 requests, and HTML-only receipts. Some of these may belong in BILL later. Others should be archived, attached to a vendor record, or ignored. The intake workflow should keep them visible until the team knows what they are.

A clean process gives exceptions their own path. Do not train vendors, employees, or mail rules to send all financial-looking email to BILL. Instead, decide what qualifies as a payable invoice, what needs a download, what needs employee context, and what should stay out of AP.

Portal alert: download the PDF or use the vendor-supported document path before routing. Statement: review whether it supports reconciliation or duplicates existing bills. Quote or renewal notice: keep it out of payment workflow until it becomes an invoice.

The same company may need all three paths: vendor direct-send for reliable recurring vendors, internal forwarding when an employee must add context, and Expensent for inbox catch-up and recurring email automation.

For a recurring SaaS invoice with a stable PDF attachment, vendor direct-send or an Expensent rule can both work. If a subcontractor sends invoices to a project manager with job notes, keep that context in the handoff. If a software vendor sends portal alerts, download the invoice before routing it.

Start with an inventory. List the vendors that send invoices by email, the inboxes that receive them, the vendors that require portal downloads, and the destination shown in BILL for the company or entity. Avoid changing vendor billing contacts until the team knows which path each vendor should use.

Next, test a few examples. Send a clean invoice to the BILL destination shown in the account, review how BILL captures fields, and confirm the approval and payment workflow that follows. Separately, route a few employee-received invoices through Expensent or internal forwarding and confirm whether the notes, attachments, and sender context are useful to finance.

Then automate only proven patterns. Give direct-send instructions to vendors that can reliably follow them. Create Expensent rules for confirmed sender-and-subject patterns. Keep portal notices, mixed sender types, and unfamiliar vendors in review. Revisit the policy when BILL product updates, plan changes, entity changes, or approval workflows change.