Working the findings

The findings screen is where the work happens. Tests beside the findings (above them, in a scrolling row, on a narrower screen) with their counts, and above both, what the list does not cover.

Open a finding before you answer it

A row says what was found. Opening it shows the vouchers behind it — number, date, party, amount, narration — and the reasoning the test recorded, including the threshold it applied. The three answers sit beneath that evidence, not above it.

The three answers

An exception

It is what it looks like. Your note says what you concluded.

Explained

There is an innocent explanation, and the note is where you write it. This answer is refused without one: an explanation nobody wrote down is a dismissal wearing a better word.

Not an exception

The test fired on something that is not one. Frequent, expected, and worth recording — next year the same finding arrives carrying what you said.

Any answer can be undone, which puts the finding back on the list.

The number that matters

Not how many exceptions there were, but how many nobody has answered for. That is the default filter, the count beside the run, and the figure the report prints.

Last year's answers

A finding that recurs arrives carrying the answer you gave in an earlier year, badged with that year and marked unconfirmed. It counts as still open until you confirm it.

That is deliberate. A note written about one March cannot discharge the next, confirming takes one click, and being counted as answered without one is how a scrutiny quietly becomes a rubber stamp.

Running again

Correct something in Tally, fetch again, run again. Findings are rebuilt from the books every time; your answers are not.

They are matched to the exception itself rather than to a row, so every unrelated answer stays attached, findings that no longer arise simply go, and genuinely new ones arrive unanswered.

An answer whose finding has stopped arising is kept rather than deleted, and the screen says how many there are. A corrected exception can come back, and you should not have to write the same explanation twice.