The three queues
Three screens under Accounting collect things needing attention. Their names do not distinguish them, and all three read as "something went wrong" — but they represent three different stages, and the fix is different in each case.
| Queue | Stage that failed | What it holds | What fixes it |
|---|---|---|---|
| Issues | Building | Entries that could not be built — a missing connection or unmapped account | Configuration. Fixing it releases what was waiting |
| Failed posts | Sending | Entries sent to the provider that did not succeed | Remove the cause, then recover |
| Exceptions | Agreeing | Entries that posted fine but no longer tally with the provider | Work out which side is right |
If you take one thing from this page: retrying a held entry does nothing. It was never sent. Until the missing account exists there is nothing to retry.
Issues
Entries Yessort could not build. Usually there is no connection yet, or an account required by a goods-receipt valuation journal, a supplier bill or a COGS entry is not mapped.
Nothing here is lost. Every entry is kept with everything it needed, and replayed once the configuration appears — nightly, or on the next live attempt, whichever comes first.
So this queue clears itself as you complete your setup. A stack of issues after connecting is expected and does not need working through row by row. See hold, don't drop.
Failed posts
Entries that were sent and did not succeed — rejected by the provider, or retried until the attempts ran out.
Shown with the type and stream of entry, how many attempts were made, the error, and when it was last tried. Recover is the action once the cause is dealt with.
Read the error before recovering. A rejection for something structural — an account that does not exist at the provider, a period that is closed — will fail again identically until that is sorted out.
Exceptions
Reconciliation differences. These posted successfully; the two systems have since stopped agreeing.
Shown as our total against the provider total, with the difference, and provider total drift where the provider's figure has moved away from what was originally posted.
Drift is the column to read first when working out which side changed — it points at an edit made in the accounting system rather than at anything Yessort did.
Nothing failed here, so nothing needs retrying. See reconciling and tying out.
Telling them apart quickly
Ask what stage the entry reached.
- Never built → Issues
- Built and sent, but did not land → Failed posts
- Landed, but the numbers moved → Exceptions
Related pages
Resolve an accounting issue · Resolve a failed post · Resolve a reconciliation exception