How posting works
Between something happening in Yessort and an entry appearing in your accounts, there are three stages.
Yessort books the event. The outbox posts it. A post records what actually happened.
Understanding them as separate is what makes the queues make sense, because each stage fails in its own way and needs a different fix.
Book
Something happens — an order is invoiced, goods are received, stock is sold — and Yessort works out the accounting consequence. It needs to know which account and which tax code apply, so it draws on your accounting categories and tax categories.
If it cannot build the entry, because there is no connection or a required account is not mapped, the entry is held rather than discarded. It waits in Issues until the missing piece exists. See hold, don't drop.
Post
Built entries go into an outbox, and a dispatcher works through it.
Each entry moves through: pending, then in flight while the provider is being called, then either success or failed. Failed means retries were exhausted or the provider rejected it outright.
If sending fails, the entry lands in Failed posts, with the error and how many attempts were made.
The outbox exists so a provider being slow or briefly unavailable does not lose anything or block the warehouse. Work carries on; the entries queue.
Record
A successful post is recorded: what was posted, as which kind of document, and against which order or receipt. This is what makes "what did we send for this order?" answerable months later.
Records are kept independently of which provider you use — the provider is a property of the connection, not of the record.
If the records and your provider later disagree, that surfaces in Exceptions as a reconciliation difference. Nothing failed here: the post went through. The two sides simply do not tally, which is a different problem needing a different fix. See reconciling and tying out.
Why this matters when something goes wrong
The three queues correspond exactly to the three stages:
| Queue | Stage | What it means |
|---|---|---|
| Issues | Book | Could not be built. Usually a missing account or connection |
| Failed posts | Post | Was sent and did not succeed |
| Exceptions | Record | Posted, but does not tally |
The remedies differ completely. An issue is fixed by configuration. A failed post is fixed by removing the cause and retrying. An exception is fixed by finding out which side is right.
Reaching for the wrong one wastes time — retrying a held post does nothing until the account exists. The three queues sets them out side by side.