# Change log: revision 2

The original submission is kept unchanged in `output/submission-v1/`.

## Review checks performed
- I looked at both PNGs again and compared every transcribed value: supplier, invoice number, date, PO, currency, lines, subtotal, tax, shipping, total and bank suffix. I found no transcription errors.
- I recalculated all figures with `output/check.py`, which now uses assertions. Result: "ALL ASSERTIONS PASSED". Invoice 001083 is confirmed to be 10.00 too high (recalculated 319.20 against a stated 329.20). Invoice 000742 recalculates to 692.00, which matches.
- I checked the review note against the 400-word limit (counted with `output/wc.py`).

## Corrections
1. **review-note.md:** removed "following the AP bank-change procedure". No such procedure is in the inputs, so the reference was unsupported.
2. **invoices.json:** money fields are now JSON numbers instead of strings, so the file is easier to use in other tools. Identifiers (invoice_number, bank_account_suffix, po) stay as strings to keep leading zeros.
3. **invoices.json:** added `po_bank_suffix` and `bank_suffix_match` to each record's recalculation block. Exceptions now cite the CSV row and quote the invoice labels. The shipping item on 000742 is now marked low severity.
4. **check.py:** now asserts that the required fields are present, that identifiers are strings, and that the line, subtotal, tax, total, PO-match and bank-match results agree. Previously it only printed values.
5. **review-note.md:** clarified that check.py tests the JSON transcription, not the images.

None of the findings changed: 000742 needs only the shipping check, and 001083 stays on HOLD.
