Trace a Hubdoc Document From Intake to Publishing

Start with the simplest question: did Hubdoc create a document at all? Hubdoc support says each organization has a unique intake email address found in Organization Settings and also shown from Upload Document. The same support article says the default intake address should be changed when the organization is first set up, and that the full email address includes extra unique characters.

If an emailed document does not create a Hubdoc document, check the exact address copied into the email or rule. Hubdoc support specifically calls out missing the @app.hubdoc.com domain, an unchanged default intake address, spam blocking, middleware forwarding services, and Outlook contact corruption that can remove attachments. Do not infer that Hubdoc extraction failed until the message created a document.

For web uploads, confirm whether the upload method matched the file. Hubdoc documents Standard Document Upload, Multi-page PDF Split, drag-and-drop, and a separate Bank Statement Upload option for organizations in the United States or Canada. A multi-page PDF may need a split workflow if each page is a separate document, while ordinary attachments sent by email create separate Hubdoc documents by attachment.

Copy the current intake email from the Hubdoc organization instead of using an old saved contact. Check whether the email was returned with a rejection or delivery error. Confirm the attachment reached the email, especially when Outlook, forwarding middleware, or supplier systems are involved.

A source email can look useful to a human while giving Hubdoc little to process. Hubdoc says that when you email one or more attachments, it creates a separate document for each attachment. By default, it does not create a document from the body of the email, although an organization setting can create documents from both the attachments and the body. If the receipt details live only in the email body, verify that setting before assuming the document was lost.

Hubdoc also says it cannot create a document from an attachment that must be accessed through a hyperlink in the email. Portal emails are a common reason teams think Hubdoc missed a receipt: the vendor sent a link, not the actual document. Download the receipt or invoice first, then upload or email the actual file.

Supplier direct-send can work when the supplier sends a usable attachment to the correct intake address, but it deserves controls. A supplier can change billing templates, send portal links, include logos that Hubdoc identifies as not documents, or send statements that need review. Keep a human-visible source trail for recurring vendors instead of relying on a hidden rule nobody checks.

If the email body contains the only useful data, check the Organization setting for body-to-document creation. If the vendor sent a portal link, download the file and submit the file itself. If a rule forwards supplier emails, test the exact sender and subject pattern that triggered the rule.

Hubdoc support lists current upload and email file types as PDF, JPEG, PNG, IMG, HEIC, HEIF, HTML, and Plain text, with a 35MB maximum for a single document. It also says Hubdoc does not unzip folders or extract data from spreadsheet files. If the source file falls outside those rules, route a supported copy instead of troubleshooting extraction.

A supported file can still fail extraction. Hubdoc says common reasons include a blurry, crumpled, or faded image; missing mandatory information such as date, amount, or supplier name; or multiple receipts for different transactions in the same image. If multiple receipts appear in one image, Hubdoc says they must be for the same transaction.

The Failed tab is not one single error type. Hubdoc status documentation says Failed includes documents that failed data extraction and documents that failed to publish to a destination. Open the document and inspect the context before choosing the fix. A file-quality problem needs a clearer document. A publishing failure needs destination setup work.

Use a clear PDF or image that shows date, supplier, and total amount. Avoid spreadsheets, zipped folders, and files that require a hyperlink download. Treat a Failed status as a diagnostic starting point, not proof that email delivery failed.

Hubdoc status tabs explain where the document sits in the workflow. Processing shows manually uploaded documents that are having data extracted. Review shows documents that completed extraction or have extraction turned off. Failed includes extraction and publishing failures. Archived includes successfully published documents, auto-archived supplier documents, documents uploaded while the account was in a non-paying state, and manually archived documents.

Extraction timing is not the same as arrival timing. Hubdoc says data extraction usually happens within seconds, can take up to a few hours depending on document type and queue size, and the data extraction overview says some documents can take up to 24 hours. If the document is newly submitted, check the Processing tab and the document details before assuming it is stuck.

Settings can also explain unexpected status. Hubdoc allows organizations to disable data extraction. When extraction is off, new documents show in Archived with a green check mark; if extraction is disabled and later turned back on, documents imported during the disabled period do not go through extraction and need manual data entry before publishing or search results. Account billing or trial state can also affect workflow, so verify the organization state when statuses do not match expectations.

Processing: wait, then inspect document type, size, and queue-sensitive behavior. Review: confirm extracted fields and complete missing or incorrect data. Archived or Failed: check whether extraction was disabled, publishing failed, or the document was already sent to a destination.

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

Confirmed recurring patterns can route new documents automatically. Portal notices, missing attachments, and unusual messages remain visible when they need attention.

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

Escalate only after you know the failing layer. Email administrators should investigate forwarding verification, spam filtering, stripped attachments, middleware allowlists, and mailbox contact issues. Hubdoc support should investigate documents that reached Hubdoc but failed extraction, failed to load, showed unexpected status, or failed publishing despite correct setup. Your bookkeeping owner should decide paid vs unpaid routing, supplier rules, duplicate handling, and reconciliation.

A useful escalation includes the original sender, Hubdoc intake address used, date and time sent, upload method, attachment name, file type, file size, document ID if available, current Hubdoc status tab, destination attempted, and any returned email or Hubdoc error. That turns a vague processing complaint into a traceable workflow failure.