If a settlement hasn't been sent to Xero or QuickBooks, work through these checks in order. Most have a quick fix.
1. Is auto post turned on for this sales channel?
Auto post is set separately for each sales channel, so check the channel the settlement belongs to.
Switch to the sales channel the settlement belongs to.
Go to Settings → Settlement Settings → Automation.
Check auto post is turned on.
If you've set a start date or end date, check the settlement's date falls between them. Auto post only sends settlements inside those dates.
If auto post is off, settlements are only sent when you send them yourself. To send them automatically, turn it on here. It will send new settlements from the date you turn it on, or from the start date you choose. See How to automatically post settlements.
If auto post is on, check your connections next.
2. Are your sales channel and Xero or QuickBooks connected?
Auto post can't fetch or send settlements if either connection has dropped. This often happens after a password change or turning on two-factor authentication.
How to check
Sales channel: select the channel. If it has disconnected, you'll see an orange banner at the top of your Settlements dashboard. The banner only shows on the affected channel.
Xero or QuickBooks: go to Settings → Account Settings. If the connection has dropped, you'll see Disconnected next to it.
If either one is disconnected, reconnect it:
Click Reconnect in the orange banner, or go to Settings → Account Settings, open the Action dropdown next to the disconnected connection and choose Reconnect.
Follow the prompts to sign in and approve the connection.
Once a sales channel is reconnected, any settlements you missed while it was disconnected are imported automatically. Auto post then picks up any that are Ready to Send on its next run.
If you don't want to wait for the next run, open the settlement's Action menu and choose Refresh. It will then send.
Managing a client's account? Reconnecting a sales channel needs the client's own sales channel login, so your client has to do it. For Walmart, only the main Walmart account login can approve it.
Step-by-step help, including what to do if it still shows as disconnected:
If both are connected, check for missing mappings next.
3. Are any account or tax mappings missing?
If any line on a settlement has no account or tax rate mapped, auto post holds the settlement so it isn't posted with gaps. You'll see this message on the settlement, and a notification in the bell:
"This settlement is on hold because some of its lines have no account or tax rate mapped. It cannot be auto-posted until they are mapped in Account & Tax Mappings."
How to check
On the Settlements dashboard, open the settlement's Action menu and choose View. On the sales and fees tab, look for any line with a missing account or tax rate.
Or go to Account & Tax Mappings for that sales channel. Missing entries are flagged there. Open each section and look at the lines underneath: the top level can look complete while a line further down is missing.
Missing mappings often appear when a marketplace adds a new fee or adjustment that wasn't there when you set up. They can also appear when an account has been removed from your chart of accounts in Xero or QuickBooks.
If anything is missing, map it:
Switch to the sales channel the settlement belongs to.
Go to Account & Tax Mappings, find the line flagged as missing, choose the account and tax rate, and save.
Not sure which account to use? Open an earlier settlement that sent fine (Action → View) to see where that line went before.
The hold lifts by itself once everything is mapped, and you'll see "Hold released: account and tax mappings are now complete." Auto post then picks the settlement up as normal, as long as it falls inside your auto post dates.
If nothing is missing, check the settlement for an error message.
4. Is there an error message on the settlement?
If auto post tried to send the settlement and Xero or QuickBooks refused it, the settlement shows an error, or a status such as Auto Post Retrying, on the Settlements dashboard. Click or hover over the error to see the full message.
Find the message below and follow the fix. If you're getting help from us, send a screenshot of the error. The exact wording tells us what's wrong.
If the error mentions… | What it means | How to fix it |
a lock date, closed period or "period has closed" | The settlement falls in a period you've locked in Xero or QuickBooks | |
an invoice or transaction limit | Your Xero or QuickBooks plan has hit its monthly invoice cap | |
"Refresh OAuth 2 Access token … failed" or invalid_grant | The Xero or QuickBooks connection has expired | Reconnect, as in step 2 above |
"You are not permitted to access this resource" | A Xero permission or connection problem | |
missingTreeData or "Missing … in Tree" | Usually follows a settings or tax mapping change | |
API Rate Limit, Method Lock or "Xero API Error" | Xero received too many requests at once | |
"You can only use one foreign currency per transaction" | A QuickBooks three-currency conflict | |
"Contact name already assigned" | A contact with the same name already exists in Xero or QuickBooks | |
"Invoice due date out of range" | The invoice due date falls outside what Xero allows | |
"A send is already in progress for this settlement" | A send for this settlement has already started. Sends go out in batches of 5–10 every 10 minutes, so this usually clears by itself | Don't click Send again. Wait about 30 minutes, then choose Action → Refresh. If it's still showing, check your connections (step 2) |
"Fill out at least two detail lines" (QuickBooks) | One part of a split settlement is £0.00, with nothing to post. QuickBooks won't accept an entry with fewer than two lines | The £0.00 part doesn't need to go to QuickBooks. Open the settlement (Action → View) and send the other parts using their own Send Invoice buttons |
"Page Data No Longer Valid", "Debit Credit Balance Error", "Document Total Too Small", "not ready to be sent", "could not be processed", or another processing error | The settlement isn't in a valid state to send |
Other things that stop auto post
The settlement was rolled back. Rolled-back settlements are held for you to review, unless you've turned on auto post after rollback. See auto-post after rollback.
Products are still in your Default group and you use Hold on Catch-All. See Hold on Catch-All.
Part of the settlement has already been sent. Auto post skips it. See Partially sent settlements.
Auto post stopped trying after repeated failed attempts. After several failed attempts, auto post stops retrying that settlement, even once the cause is fixed. Fix the cause using the checks above, then send that settlement yourself from your Settlements dashboard. Your other settlements carry on auto posting as normal.