When Nagaris composes a BAS workpaper, its engine checks the ledger and raises queries about what it finds. Queries come in two kinds:
Exceptions: something specific to this period that needs a reviewer's attention, like a credit note that needs chasing.
Confirmations: a standing position the engine restates on every run for this client, such as the reporting basis, the super guarantee rate, or BAS-excluded coding sitting outside the calculation by design. These aren't new findings, they're what a reviewer is asserting by signing off the workpaper.
The BAS list, the workpaper run history and a client's BAS card all show a "to clear" or "Queries" count. That count is exceptions only, confirmations are excluded so the number reflects real work left to do rather than a permanent floor that never reaches zero.
Open a BAS workpaper's findings to see:
Exceptions to clear, listed first. If the engine found none, the workpaper shows a confirmation that nothing needs clearing for this period.
Standing confirmations, folded under a collapsible "what signing this asserts" section below the exceptions. Expand it to see each confirmation and the reasoning behind it.
Clearing exceptions is what a reviewer needs to act on before approving a run. Standing confirmations stay visible for context but don't count against the workpaper as outstanding work.
