Accounting
Yessort records what happened — a sale, a dispatch, a delivery received — and sends the accounting consequences to your accounting system. Invoices, credit notes and journals appear there without anyone re-keying them.
Three stages, three things that can go wrong
Everything on these pages follows from one sequence:
Yessort books the event. The outbox posts it. A post records what actually happened.
Each stage can fail differently, and that is why there are three separate queues rather than one:
| If it failed at | The entry is | Where you find it |
|---|---|---|
| Building the post — a missing connection or ledger code | Held | Issues |
| Sending it — rejected, or retries exhausted | Failed | Failed posts |
| Agreeing afterwards — posted, but the totals differ | A reconciliation exception | Exceptions |
The names do not make the difference obvious, and the remedy is completely different in each case. The three queues sets them out side by side.
Nothing is silently dropped
If a post cannot be built because an account or a connection is missing, Yessort does not discard it. It keeps everything the post needed and replays it once the missing piece appears.
The practical consequence is worth knowing in advance: setting up the missing account does not only fix future entries, it releases the ones already waiting. See hold, don't drop.
Which providers you can connect
Two options ship.
Xero — connected through Xero's own sign-in. Yessort posts to it directly.
Manual accounting — no external provider. You still get Yessort's categories, tax handling and records of what would post, but nothing is sent anywhere. Because there is no external connection, there is no chart of accounts to draw on and nothing to re-authorise.
Where the screens live
All of it is organisation administration and needs organisation-admin access: the connection under Integrations, and the queues under Accounting.
Concepts
- How posting works — book, post, record, and the three failure modes.
- What Yessort posts — the invoices, credit notes and journals it produces.
- Hold, don't drop — why a post that cannot be built is kept rather than discarded.
- Accounting categories — matching revenue and expense to your accounts.
- Tax categories — matching tax to your provider's tax codes.
- Invoicing strategies — an invoice per order, or one a day.
- How COGS works — cost of goods sold, and when its account is decided.
- Reconciling and tying out — what is compared, and what a difference means.
- Payment methods and gateways — how a channel's payment names become yours.
- Gateway payouts — what landed in the bank against what was reported.
- Editing an order after posting — what happens to an invoice already sent.
How to
Start with connect Xero, choose a Xero organisation and finish onboarding.
The recurring work is resolving a failed post, resolving an accounting issue and resolving a reconciliation exception.