Automate Receipt Emails to Hubdoc

A dependable Hubdoc workflow begins with the organization, not with a Gmail rule. Hubdoc documents a unique intake email address for each organization. The address appears in Organization Settings and in the Upload Document dialog, and Hubdoc adds unique characters when an administrator changes it. Once changed, the previous address no longer works.

Treat that address as controlled organization configuration. A named Hubdoc administrator should own changes, keep the full current address in the approved routing destination, and tell the inbox-routing owner when it changes. Employees, vendors, and mailbox rules may send to the address, but they should not become the source of truth for it.

This matters when one finance team works across several entities. Each Hubdoc organization has its own intake boundary, and Hubdoc-to-Xero connections are organization-specific. The routing decision must identify the business entity before it identifies a supplier pattern. A correct receipt sent to the wrong organization is still an intake failure.

Configuration owner: maintains the organization address and Hubdoc user access. Routing owner: uses the complete address copied from the intended organization. Sender or employee: supplies the source document but does not choose the accounting entity by assumption.

Email intake is not one document per message. Hubdoc says that each emailed attachment creates a separate document and uses the attachment name as the display name. A message with an invoice PDF, a terms PDF, and a second copy can therefore create three Hubdoc documents. Route the message only when all attached files belong; otherwise obtain and submit the correct source file through an approved Hubdoc path.

The email body follows a different rule. By default, Hubdoc does not create a document from the body. An organization setting can create documents from both attachments and the body; when enabled, Hubdoc converts the body to a separate PDF and uses the subject as its display name. This can preserve body-only receipts, but it can also produce an extra document when the body merely repeats an attached invoice.

A hyperlink is not an attachment. Hubdoc states that it cannot create a document from a file that must be accessed through a link in the email. A portal notification therefore needs a retrieval owner, not an automatic route. The actual downloaded file must enter Hubdoc through email, upload, mobile capture, or another supported intake method.

Attachment present: route only when the attachments are the documents the organization intends to create. Body-only evidence: route only if the organization has deliberately enabled body-to-PDF creation. Attachment plus useful body: expect separate documents when the body setting is enabled; decide whether both belong. Portal link only: hold the message and assign retrieval of the source file. Mixed or unrelated attachments: keep in review instead of sending the whole message blindly.

An exception policy determines what happens when a message is not a clean receipt with a known organization and a usable source document. Without one, automation either forwards too much or silently leaves work in a queue. The policy should name the owner, required evidence, permitted action, and completion signal for each exception class.

Use four outcomes. Route means the evidence is present and the organization is known. Retrieve means a portal or account owner must obtain the source file. Clarify means the entity, document type, or accounting purpose is uncertain. Reject or redirect means the message is not source evidence for Hubdoc, is a duplicate, or belongs in another workflow.

Credits, refunds, statements, order acknowledgements, renewal notices, and payment alerts should not inherit an invoice rule merely because they share a sender. They may still be valid accounting evidence, but their treatment requires a deliberate decision. Keep mixed-event senders in review until each subject pattern has a stable, documented outcome.

Portal-only: assign retrieval; complete when the actual file is routed or the owner records that none is available. Missing or irrelevant attachment: request the source document; do not forward a placeholder message. Unknown organization: hold until the legal entity or client is confirmed. Possible duplicate: preserve the source trail and let the designated reviewer compare before another route. Mixed sender or subject: keep manual review; do not widen a rule to capture unrelated events.

Expensent finds current and historical receipt and invoice emails and sends selected documents to the current Hubdoc organization address.

Confirmed sender-and-subject patterns can route new recurring documents automatically. Portal notices and unusual messages remain visible when they need attention.

Hubdoc continues with extraction, supplier rules, review, and publishing after delivery.