A review reason should survive the next question
Compare weak and useful notes for a refund, repeated sale and reported-rate difference, then test whether another reviewer can reconstruct the decision.
“Checked” is short, but it leaves almost everything to memory. A useful review reason makes a decision understandable after the person who made it has moved on to the next week. We used the fictional ten-row close to test what a note must contain, and what can safely stay in the surrounding source record.
Worked fictional example · amounts in AUD
The useful part
A durable reason identifies the evidence, the treatment and the financial effect. It should explain the decision without copying unrelated personal details into the record.
Your working files
Read the fictional decision registerCSV · Four concrete exception treatments with source references and calculated effects.Start with the question a later reviewer will ask
For refund A105, the later question is not whether someone clicked Approve. It is why this negative row belongs to this staff member and period, and how its amount relates to an original sale. For repeated A102, the question is which representation of the sale survived. For A106, it is which rate evidence justified departing from the source’s reported amount.
These are different decisions, so a single stock phrase cannot answer all of them. The note’s job is to connect the row to the missing explanation. Dates, source filename, reference, basis and calculated amount already exist in the record; the note should supply the reasoning those fields cannot express.
Three before-and-after examples
The stronger notes below come from the fictional case assumptions, not from real customer records. They are deliberately specific enough to challenge. Another reviewer can check the named original sale, retained copy or rate register and determine whether the decision follows from the evidence.
| Row | Weak note | Useful reason |
|---|---|---|
| A105 refund | Checked | A105 returns half of A100. Supplied basis −$50 at 40% gives −$20; include this adjustment. |
| Second A102 | Duplicate | Overlapping export repeats A102. Retain the first source copy; exclude this later representation. |
| A106 difference | Use our rate | Source reports $32 on an $80 basis at 40%. Confirmed case rule is 45%, so include $36; difference +$4. |
Evidence, treatment and effect do different jobs
Evidence identifies what was checked: an original sale, an overlapping file or a confirmed rate record. Treatment states what happens to this row: include the adjustment, exclude the copy or retain the calculation under a supplied rule. Effect makes the result concrete: −$20.00, zero contribution from the copy or a $4.00 difference.
Keeping all three prevents a common ambiguity. “Duplicate confirmed” could mean both copies were excluded, one was retained, or the warning was dismissed because the sale itself was genuine. A reason that names the retained representation closes that gap. The wording is useful because it constrains interpretation, not because it sounds formal.
The note must not outrun the evidence
“The provider calculated this incorrectly” is stronger than the A106 evidence supports. We know the source reports $32.00 and the supplied case rule yields $36.00. We do not know every setting or arrangement behind the source report. A precise note says which rule the reviewer confirmed and why that rule is used for this close.
Likewise, “refund must be deducted” would turn a arithmetic review note into a statement about treatment that the software cannot establish. Record the responsible reviewer’s confirmed decision without pretending the calculator determined a legal or contractual obligation. This makes the record more accurate and easier to revisit if new evidence appears.
Enough context does not mean every detail
A note does not need a customer’s phone number, health information, personal complaint or full appointment conversation to explain a commission calculation. Reference A100, the refunded portion and the confirmed treatment may be sufficient. Put supporting records in the appropriate authorised location and refer to them clearly when necessary.
Avoid repeating the entire source row in prose. Duplication creates another place for values to become inconsistent. The surrounding record already preserves calculated fields and parsed source values. A concise reason should explain the connection between those facts and the decision, leaving the facts themselves inspectable in their original places.
A draft decision can change when evidence changes
Suppose the reviewer initially believes A105 is a full return, then finds evidence that only half was returned. While the period is still a draft, revisit the row, inspect the source and correct the decision or source problem through the supported workflow. The revised reason should describe the evidence now used, not defend the first assumption.
Once a run is finalised, its saved row and note form part of the completed snapshot. The account server protects closed history from ordinary draft saves. A later correction should be handled as a new documented event or an explicit recovery process where appropriate, rather than silently rewriting what the earlier close said.
The useful test is a read-back
Give another reviewer the source row and note, then ask them to state which evidence was used, what treatment was selected and how the amount follows. If they need the original reviewer’s memory to answer, improve the note. If they can reconstruct the decision but disagree with it, the note has at least made the disagreement specific.
Use the ten-row decision download as a practice register. It contains four exception treatments, including the voucher exclusion. This is a writing and traceability exercise, not a claim that a note alone verifies a transaction. Good records expose the remaining question and make a later answer possible.
Put it to work.
Inspect source rows, supplied rates and review decisions in the sample workspace.
Explore the sample close