Exceptions

What this does

Accounting → Documents & Intelligence → Exceptions is a queue of things a person should look at. Some come from paper: a note written on a receipt. Some come from the ledger: a nightly check that found a number that doesn't tie. Each has a severity (Critical, High, Medium, Low, Info), a status, and a place to record what you did.

From documents

When the extractor reads handwriting or a stamp on a document it raises a flag rather than guessing what to do with it. The types you'll see: Return Flag (a "return" or "RMA" on a receipt), Customer Instruction (a note telling someone to do something), Customer Note, Payment Annotation ("paid cash," "check #"), Check Number, Price Correction (a crossed-out amount), Problem Flag, Quality Issue, Safety Flag, and Scheduling Flag. The document is linked; open it, act on the note, and resolve.

From the books

Nightly and on-event checks raise their own exceptions when something doesn't reconcile: the AR tie-out (open invoices vs. the receivables ledger), a money-in entry that didn't post, a bill that can't be posted, an unposted entry, a terminal balance that doesn't match, a Stripe payout that doesn't reconcile, a webhook that stopped reporting, or money that has sat in Undeposited Funds too long. These are the bookkeeper's morning list. Each names what it compared and by how much it's off.

Working the queue

Filter by status (Open, Acknowledged, In Review, Resolved, Dismissed), type, or severity. Acknowledge to say you've seen it. Move to In Review while working it. Resolve with a note saying what was done; multi-select for a batch that shares a cause. Dismiss for a flag that needed no action.

Common problems

The same exception comes back every night. The underlying condition hasn't been fixed. Resolving records what you did; it doesn't change the books. Fix the cause, then resolve.

I see exceptions assigned to a role that isn't mine. The assignment is a routing hint, not a filter; everyone with access sees the whole queue.