Export failed
Fix a stalled cloud-storage export or a rejected accounting push from expired access, no retry, missing mapping, a document already in your ledger, or a changed document type.
An export to Google Drive, Google Sheets, OneDrive, QuickBooks, Xero, or Dynamics 365 Business Central did not go through. Work through the causes below in order.
Integration disconnected or token expired
Symptom. Exports stop reaching a connected target, and the integration shows a disconnected or error state.
Cause. Inbox Ledger refreshes its access to each provider using a stored token. If you removed Inbox Ledger's access in the provider's account, or the provider voided the grant, the refresh fails and exports cannot run.
Fix. Open Settings, then the Integrations tab, find the affected provider, and click Connect to re-authorize. A fresh token is stored.
Confirm. Run the export again from the document. It should complete.

A manual export failed and did not retry
Symptom. You ran an export by hand and it failed, and nothing happened afterward.
Cause. A manual export does not retry on failure. Only auto-export targets fire again on the next new document.
Fix. Re-run the export from the document. Open Documents, open the row menu, and pick the export again. For several documents, reselect them and use the batch bar button.
Confirm. The export completes on the second run.
Accounting push rejected for a missing mapping
Symptom. A push to QuickBooks Online, Xero, or Dynamics 365 Business Central is rejected, with an error about a vendor or an account.
Cause. The push needs a vendor and an account mapping to create the Bill or Purchase Invoice. If a vendor or expense account is not mapped, the provider rejects the record.
Fix. An admin opens Settings, then the Integrations tab, and sets the missing vendor or account mapping for that provider.
Confirm. Push the invoice again. It posts to your ledger.
Push held back because the document is already in your ledger
Symptom. A manual push opens the Push to QuickBooks again? dialog, or its Xero or Dynamics 365 version, instead of pushing. A batch push counts some documents as already pushed.
Cause. An earlier push already created a record for this document in that provider. Inbox Ledger holds the push back so the document is not booked twice.
Fix. Open the existing record from the link in the dialog and check it. If it is correct, click Cancel. If you need a second record, click Push again. When the dialog says the record is incomplete, an earlier push created it but failed before it finished. Delete or finish that record in your accounting system, then click Push again.
Confirm. Your accounting system holds one complete record for the document.
Push stopped because the document type changed
Symptom. A push fails with this message:
The document type changed after this push was queued. Review it and push it manually.
Cause. The document changed between an invoice and a credit note after the push was queued, for example when a reprocess finished between your click and the push. The push stops so a credit note is not booked as a bill, or a bill as a credit.
Fix. Open the document, check the type and the amounts, and push it by hand.
Confirm. The push creates the record that matches the document type.
Business Central push refused because of the tax amount
Symptom. A push to Dynamics 365 Business Central fails with a message that the tax on the document is not between zero and its total.
Cause. Business Central receives the amount before tax and adds VAT itself, so Inbox Ledger subtracts the tax from the total first. When the extracted tax is negative, equal to the total, or larger than it, that amount would be wrong, so the push stops before anything is created.
Fix. Open the document, correct the Tax or Total field so it matches the PDF, click Save, and push it again.
Confirm. The purchase document in Business Central shows the same total as the PDF.
Push refused because the total is negative
Symptom. A push to QuickBooks Online, Xero, or Dynamics 365 Business Central fails with a message that the total on the document is negative.
Cause. Accounting records carry a credit in their type, not in the sign of the amount. A credit note is pushed as the provider's credit record with a positive total, so a negative total on the document would book the credit the wrong way round.
Fix. Open the document, enter the Total as a positive amount that matches the PDF, click Save, and push it again. If the document is a supplier credit, check that its type is Credit note.
Confirm. The record in your accounting system shows a positive total of the right type.
Still stuck
Email support@inboxledger.app with your organization name, the export target, and the error text shown on the document.
Related
Exports overview
How every export target works.
Push to QuickBooks, Xero, and Dynamics
Set up accounting field mapping.
Email not syncing
Fix the capture side of the pipeline.
Ready to try this?
Inbox Ledger turns your inbox into clean accounting data. The free tier includes 10 credits, refilled every 30 days.
Start freeWebhook not delivering
Your endpoint is not receiving its JSON? Fix dead deliveries, signature verification failures, and endpoints rejected as not publicly reachable.
Invite link says persona mismatch
Fix a firm connect, claim, or join link that is refused because the account opening it is the wrong persona.