# Invoice review: PO-1042 / PO-1043

Sources: `inputs/invoice-01.png`, `inputs/invoice-02.png` and `inputs/purchase-orders.csv` (rows PO-1042, PO-1043). Tax is recalculated at the 12% of merchandise stated on each invoice. No payment was made and no supplier was contacted.

## Invoice 000742 (Cedar Print, PO-1042, 2026-10-18, CAD)
- Line: Workshop handbooks, 80 × 7.50 = 600.00. This matches the PO for quantity, unit price and amount.
- Recalculation: 600.00 + 72.00 tax + 20.00 shipping = **692.00**. This matches the stated "Total due".
- Bank suffix 0412 matches the PO.
- **Check before approval (low):** the 20.00 shipping charge does not appear in the PO CSV, which has no shipping column. Confirm it was authorised.

## Invoice 001083 (Harbour AV, PO-1043, 2026-10-19, CAD): **HOLD**
1. **Arithmetic error:** 285.00 + 34.20 + 0.00 = **319.20**, but "Total due" is **329.20**. The stated total is 10.00 too high.
2. **Quantity over PO:** the invoice bills 3 microphone rentals, but the PO has 2. The extra unit adds 85.00 plus 10.20 tax. Stand rental (2 × 15.00) matches the PO.
3. **Bank details changed:** the invoice gives suffix **8891**, but the PO has **8821**. The invoice also says "Banking details updated on this invoice." This could be a payment-redirection attempt. Confirm the change through a supplier contact already held on file, not contact details printed on this invoice.
- PO-basis amount: 200.00 + 24.00 = **224.00**. The stated total is 105.20 over that (85.00 + 10.20 + 10.00).
- Next steps: get a corrected invoice or credit note, and get evidence that a 3rd microphone was received or authorised. If it was authorised, the correct total is 319.20. If not, it is 224.00.

## Extraction confidence
Both images were legible. I found no unreadable characters, so `uncertain_characters` is empty for both records. Invoice numbers and bank suffixes are stored as strings so the leading zeros stay (000742, 001083, 0412). Both images print "Tax is12%" with a missing space. I recorded the rate as 12%.

## Assumptions and limitations
- I treated the PO CSV as the authorised record. It has no shipping, tax or receiving data.
- Line items were matched to PO rows by exact description.
- Values were read visually from the images; no OCR software was used. `output/check.py` checks the JSON against the CSV, not against the images.
