Trace a Hubdoc Document From Intake to Publishing

When a Hubdoc document does not process as expected, first separate the problem into stages. A receipt can fail before Hubdoc receives it, arrive but fail extraction, wait in Review, fail destination publishing, or follow bank statement rules that are different from ordinary bills and receipts. Resending too early can create duplicates or hide the original failure.

Use the original source as your evidence record. Note whether the document was uploaded in the web app, emailed to the organization unique intake email address, sent by a supplier, captured through mobile, or routed from another inbox workflow. Record the sender, recipient, sent time, attachment name, file type, file size, subject line, and whether the email body was supposed to become a document.

Hubdoc is strongest once the document reaches the account. The diagnostic work is proving where the handoff broke: document arrival, unsupported or failed document, extraction status, destination publishing setup, bank statement handling, email-source gap, or upstream inbox routing.

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.

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.

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.

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.

If the document exists in Hubdoc but is absent from Xero, QuickBooks Online, BILL, or cloud storage, the intake stage is over. Hubdoc must be connected to the destination, the document data must be configured, and the destination-specific publish workflow must be used. Do not describe this as Hubdoc failing to process the upload unless the document never completed extraction or review.

Hubdoc support says a connected Hubdoc organization can publish to QuickBooks Online by creating a new transaction from the document data, and QuickBooks attaches a copy when the file is under its attachment threshold. Hubdoc support also documents BILL publishing and says that, when both QuickBooks Online and BILL are connected, paid transactions should go to QuickBooks Online while unpaid transactions should go to BILL to avoid duplicate transactions. That decision is bookkeeping workflow, not an email-forwarding setting.

Cloud storage is another distinct destination. Hubdoc documents publishing to Box, ShareFile, Dropbox, SmartVault, and Google Drive, either manually or with automatic publishing. It also warns that supplier-level automatic cloud storage publishing can skip the Review tab and archive new supplier documents once extracted. Confirm whether your team expected review, accounting software publishing, cloud backup, or all connected destinations.

Bank statements need their own branch of the diagnostic. Hubdoc documents bank statement extraction for organizations in Canada and the United States, where eligible PDF bank statements can be converted to CSV files for import to QuickBooks or Xero. That is not the same workflow as ordinary bill and receipt extraction.

Hubdoc lists statement-specific requirements, including that the statement must be a PDF, include all pages, contain one statement, be written in English, meet resolution and size requirements, and be a debit or credit statement. It also notes errors can occur when totals do not match or opening and closing dates cannot be extracted. If a bank statement fails, do not reuse the receipt troubleshooting path without checking those statement rules.

Destination expectations are different as well. The bank statement workflow produces CSV data for import, and large statement outputs can be split to meet import requirements. If the team expected a bank statement to become a bill, receipt, or published vendor transaction, reset the workflow around bank statement extraction instead of changing inbox forwarding.

Many Hubdoc processing complaints begin before Hubdoc gets a clean document: a vendor email had only a portal link, a broad mailbox rule forwarded the wrong message, a supplier sent to an old intake address, or a month-end catch-up missed an inbox. Hubdoc can process documents after they arrive, but teams still need a controlled way to decide what should be sent there.

Expensent fits that upstream layer. It connects to the inbox through OAuth, identifies likely receipt and invoice emails, shows exceptions for review, and lets you route selected messages to the Hubdoc intake address you configure. Future rules are created from reviewed email and subject patterns, which is safer than guessing a broad sender rule from memory.

That does not replace Hubdoc. Hubdoc still handles extraction, status, document storage, supplier rules, destination publishing, and the review path inside the Hubdoc account. Expensent helps make the inbox-to-Hubdoc handoff visible so missing or malformed source emails are easier to catch before they become Hubdoc processing tickets.

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.