Working through a stack
The part that eats the week. Anything arriving in volume is prepared as one batch you read before a penny moves, and every batch stays traceable and undoable afterwards.
You’d just say: “Here is the March Amex statement. Get it ready and show me what needs a decision.”
Zeno matches each line to the real names and accounts in the file and flags what needs a decision.
The table shows every line, its coding, and the reason anything is held back. Nothing is written yet.
Every batch in progress across every client, and whose move it is, without opening a company file.
A batch blocked on names you have not set up yet gets them created together, then re-checked.
Your answer is written down with your name, the time, and your own words — whether you gave it in chat or on the review screen.
A batch you refuse shows as rejected instead of sitting there looking untouched, and it cannot be posted until somebody looks again.
Posting is a separate action from preparing. A clean batch is not permission.
One instruction reverses everything a posting run put in the file.
Every batch this workstation has put into QuickBooks, newest first.
QuickBooks' own result for every entry, including the ones it refused and why.
Trace any transaction back to the batch, the person who approved it, and the document behind it.