Fix Hubdoc publishing and sync errors with Xero

Identify the failure before applying a fix

A Hubdoc document will not publish, publishes to the wrong destination, lacks an attachment, or does not update an existing Xero transaction.

Record the complete message, affected organisation or company, user, date range, and last successful action. A precise symptom is more useful than trying several broad repairs at once.

Checks before changing data

• Confirm Hubdoc is connected to the intended Xero organisation; the connection is one-to-one.
• Verify the user has permission to publish documents.
• Open the document and note its status, type, size, contact, account code, and tax selection.

Resolution path

1. Validate the connection and role. Confirm the correct organisations are paired and the Hubdoc user can publish.
   • Do not disconnect a working organisation merely to test.
   • Check whether another user can publish the same document.
2. Complete the required document fields. Review contact, account code, document type, status, amount, date, and tax treatment before publishing.
   • Use the intended Xero account and contact.
   • Review line items rather than relying blindly on extracted data.
3. Check the existing Xero transaction. If the document was already published, inspect the original transaction before using republish.
   • Republish updates the original; it does not create a fresh transaction.
   • Some approved, paid, reconciled, deleted, or edited transactions cannot be republished.
4. Test one document and reconcile it. Publish one controlled document, locate it in Xero, confirm the attachment or link, and match it to the bank line.
   • Documents over the documented attachment threshold may appear as a link.
   • Disable autosync until the mapping is proven.

Verify the result

A disappearing error is not enough. Confirm the accounting and workflow outcome:

• The document reaches the intended Xero organisation once.
• Contact, account, tax, amount, and status are correct.
• The document is attached or linked as expected.

What to avoid

• Turning on supplier autosync before validating one document.
• Publishing a second copy when a republish or correction is required.
• Assuming extracted values are accounting-approved.

When to involve product support, IT, or your accountant

Stop making changes and escalate when any of these conditions applies:

• A document remains stuck after required fields and permissions are verified.
• The wrong organisation is connected.
• A reconciled or paid transaction needs correction.

Bring the exact error, screenshots, affected record IDs, timestamps, product version or region, and a description of every change already attempted. That evidence shortens the support path and reduces repeated or conflicting fixes.