Hubdoc Publishing Destinations: Xero, QuickBooks, BILL, or Storage?

Hubdoc is not a single-lane receipt inbox. After a document arrives, Hubdoc can extract key fields, keep the source document organized, and publish the document to the destination connected for that organization. The right destination depends on the accounting outcome you want after capture.

If the company keeps its books in Xero, Hubdoc-to-Xero is usually the natural path. If the company uses QuickBooks Online, publish into QBO only after the document is configured for the right transaction type. If the document is an unpaid bill that needs AP approval or payment, BILL may be the better destination. If the goal is document backup, cloud storage or storage-only archiving may be enough.

The mistake is treating "publish to accounting software" as one generic step. Hubdoc behavior changes by destination, file size, connected platform, supplier settings, and whether the document is paid, unpaid, already reviewed, or only being stored for evidence.

A document has to reach Hubdoc before destination choice matters. Hubdoc documents can arrive through manual upload, drag and drop, email to the organization intake address, mobile photo upload, ScanSnap, and other connected workflows. Hubdoc states that each organization has its own intake email address, so teams should copy the exact address shown in Hubdoc rather than relying on a guessed pattern.

Once the document is in Hubdoc, extraction and status matter. Hubdoc says new documents move through Processing, Review, Failed, and Archived states. Extraction can read core details such as supplier, date, total amount, invoice number, and due date, but Hubdoc also says line-item data is not extracted automatically. Review remains part of the workflow when accuracy matters.

There are also destination-specific attachment rules. Hubdoc lists a 35MB maximum for a single document in Hubdoc. Its help center also says QuickBooks Online attachments need to be under 25MB to show as attachments on the transaction, while Xero attachments need to be under 3MB to show as attachments; larger files show as links instead. That is a practical reason to test real documents before making a supplier rule permanent.

Xero is the cleanest destination when the company books live in Xero and Hubdoc is being used as the document capture layer. Xero describes Smart Document Capture as a way to capture, review, and publish receipt and document data into Xero. Hubdoc help also describes creating transactions in Xero after the document data has been extracted.

Use Xero for receipts, invoices, and supporting documents that belong directly in the Xero accounting record. This is especially appropriate when the bookkeeper wants the source file attached or linked near the accounting entry and then reconciled against bank activity inside Xero.

Be careful not to confuse Xero publishing with cloud storage or generic document backup. Publishing to Xero is an accounting action, not just a filing action. Someone still needs to review coding, tax, supplier, date, amount, and reconciliation. Hubdoc can prepare the record, but it does not replace the decision about where the transaction belongs in the chart of accounts.

QuickBooks Online is the Hubdoc destination when the company runs its accounting in QBO. Hubdoc says that after a document is uploaded and extracted, you configure the data and publish it to the QuickBooks Online organization. Hubdoc then creates a new QuickBooks transaction using the document data.

The important part is the document type. Hubdoc currently describes three QBO publishing types: Bill, Expense, and Supplier Credit. A paid card receipt and an unpaid vendor bill should not be treated as the same thing just because both arrived by email. The selected Publish As option determines which fields are required and how the transaction lands in QuickBooks.

QBO is also where multicurrency, supplier setup, account coding, and attachment behavior need attention. Hubdoc imports supplier and account data from QuickBooks, but the user remains responsible for reviewing required fields and correcting anything the destination cannot infer safely.

BILL is a different destination because the main job is accounts payable approval and payment, not simply filing a receipt against the ledger. Hubdoc says documents can be published to BILL manually or automatically by supplier after the Hubdoc organization is connected to BILL.

The paid-versus-unpaid distinction is the key decision. Hubdoc guidance for organizations connected to both QuickBooks Online and BILL says paid transactions should generally publish to QuickBooks Online so they can match a statement line, while unpaid transactions should publish to BILL. After approval in BILL, the BILL integration can create or sync the accounting transaction depending on the setup.

This matters because publishing the same bill through multiple paths can create duplicate work or duplicate transactions. If BILL is used for approval, use Hubdoc to send the unpaid bill there with the source document attached, then let the AP process own approval and payment.

Cloud storage is useful when the desired destination is not an accounting transaction. Hubdoc help says documents can be sent to Box, ShareFile, Dropbox, SmartVault, or Google Drive, either manually or through automatic publishing.

This is strongest for backup, document retention, client portals, and teams that want a folder structure outside the accounting product. Hubdoc says cloud storage publishing follows the Hubdoc folder path by default and can create matching folders if they do not exist. That makes storage a useful companion to accounting review, not necessarily a replacement for it.

The main caution is status and duplication behavior. Hubdoc says documents already flagged as published are ignored in future pushes, and moving or renaming folders in Hubdoc does not move or rename the corresponding folders in cloud storage. If you rely on storage for records, test folder naming and resend behavior before rolling it out across many suppliers.

Some documents should not become accounting transactions at all. Contracts, W-9s, lease documents, statements, warranty PDFs, and context files may need to be retained without creating a bill, expense, or supplier credit. For those documents, storage-only or archive handling can be the cleaner choice.

Hubdoc can store documents and organize them with folders and tags. It can also publish documents to cloud storage for backup. If a supplier-level cloud storage autosync is enabled, however, Hubdoc warns that all new documents from that supplier can skip the Review tab and be automatically archived once extracted. That is useful for low-risk backup workflows and risky for documents that still need accounting judgment.

A storage-only workflow should still have a review rule. Decide which document classes are safe to store without accounting action, which need a bookkeeper to review them, and which should never be automated because the email often contains portal links or mixed attachments.

Hubdoc can only process documents that reach Hubdoc. Many teams lose time before that point because receipts and invoices are still sitting in Gmail, Outlook, or another mailbox. Expensent fits upstream by finding likely invoice emails, showing what needs review, and forwarding selected messages to the Hubdoc intake address you configure.

That does not make Expensent a replacement for Hubdoc. Hubdoc still owns extraction, status, supplier configuration, publishing settings, Xero review, QuickBooks Online review, BILL approval, storage publishing, bookkeeping decisions, and reconciliation. Expensent helps with the inbox-to-Hubdoc handoff before those steps.

This upstream layer is most useful for email-heavy workflows, historical catch-up, multiple inboxes, and recurring sender-plus-subject patterns. A user can review real messages first, forward the right ones to Hubdoc, and create narrower rules for future arrivals instead of sending a broad inbox filter into a publishing workflow.

Start with one document class and one destination. For example, route paid card receipts to Xero, unpaid vendor bills to BILL, and non-transaction support files to cloud storage. Send a small sample through Hubdoc, then confirm the status, extracted fields, destination record, attachment or link behavior, and what still requires human review.

Next, set supplier-level settings only where the pattern is stable. A utility bill from one supplier may be safe to configure. A marketplace email that sometimes includes receipts, refunds, shipment notices, and portal links should stay in review. The destination should be a controlled choice, not an accidental result of a broad forwarding rule.

Finally, document the handoff for the person who reconciles the books. They should know which Hubdoc documents go to Xero, which go to QuickBooks Online, which go to BILL, which are archived, and which are routed by Expensent before Hubdoc. That prevents duplicate publishing and makes missing-document troubleshooting much faster.