Resolve an accounting issue
Issues, under Accounting, holds entries Yessort could not build — because there is no connection, or an account they need is not mapped.
Needs organisation-admin access.
Do not try to retry these
Worth knowing before you start, because it saves a wasted hour: a held entry was never sent. There is nothing to retry and no recover action, and looking for one is time spent on something that does not exist.
The fix is always configuration.
Do not work through it row by row either
Entries release themselves. Each account you map frees every entry waiting on it, so the count drops in steps.
Read the queue as a list of what configuration is missing, not a list of things to individually fix.
Steps
- Open Issues under Accounting.
- Read what the entries are waiting for — a connection, or a specific account.
- Supply it: connect a provider, or map the account.
- Leave it. The queue clears on its own.
When it clears
Held entries are re-attempted nightly, and a live attempt for the same thing will also clear them — whichever comes first.
So mapping an account late in the day usually shows results the next morning. If something recurs in the meantime, it may clear immediately.
What ends up here
Goods-receipt valuation journals — from receiving a delivery.
Supplier bills — from recording a supplier invoice.
COGS entries and count variances behave similarly, kept as subledger records until their account can be resolved.
All of them come from things that actually happened in the warehouse, which is why they are kept rather than dropped.
If an entry stays after you have mapped everything
Check the mapping is on the right provider — mappings are per provider, and one made against the wrong connection will not release anything.
Then check the connection is active rather than paused or in error.
Not the other two queues
An entry here was never sent. One that was sent and failed is in Failed posts; one that posted but does not tally is in Exceptions. See the three queues.