Finish accounting onboarding
A connection on its own posts nothing. Yessort still needs to know which accounts and tax codes to use, and until it does, entries are held.
Under Integrations in your organisation's settings; needs organisation-admin access.
Expect a stack of issues, and do not work through it
Before mapping is complete, entries that cannot be built pile up under Issues. That is the system working as intended — nothing was lost.
Do not clear them row by row. They release themselves as you complete the mapping: each account you map frees every entry waiting on it. Working the list individually is effort spent on a queue that is about to empty on its own.
Steps
- Confirm the connection and the Xero organisation are right.
- Map your accounting categories to accounts — see map an accounting category.
- Map your tax categories to tax codes — see map a tax category.
- Set up payment methods and map the gateways your channels report — see set up payment methods.
- Check the Issues queue. What remains tells you what is still unmapped.
What to map first
The accounts that block entries: inventory and goods received not invoiced for receipts, your expense accounts for supplier bills, and cost of goods sold. These are the ones producing held entries.
Sales revenue uses your organisation's default revenue account, so it does not need per-category mapping to start posting.
When entries are released
Nightly, or on the next live attempt for the same thing — whichever comes first. There is no replay button, and none is needed.
If you map an account and want to see it work, the simplest check is the Issues count the following day.
Tax codes are worth finishing
Unlike a missing account, a missing tax code does not hold anything. The entry posts and the line lands at the account's own default treatment.
That means an incomplete tax mapping is invisible: no error, no queue, just a treatment nobody chose. Finish these before volume builds up. See tax categories.
When it is done
Issues settles to empty or near it, and new entries move through the outbox to success. From there the recurring work is the three queues — see the three queues.