A supplier invoice export can look ready to pay while still containing duplicate lines, missing job codes or charges above the approved amount. This original Sheetstead Studio demo checks those cases against a purchase-order export and keeps each source row visible for review.
RESULTS
The 10 fictional invoice lines totalled £831.50. Two matched for £187.50, one exact duplicate accounted for £125.00 and seven exceptions accounted for £519.00. The three groups reconcile to the input total. One invoice claimed £210 against a £200 purchase-order line, so the report shows a £10 variance.
HOW THE CHECK WORKS
Python matches supplier, order number and line number, so two suppliers can reuse the same invoice or order reference without a false match. It keeps conflicting versions visible and flags split billing for review. Each result retains its original row, rule outcome, input amount and expected amount where available. Rerunning the same two exports reproduces the same output.
WHAT A CLIENT RECEIVES
A repeatable check, a row-level exception report and control totals that can be reviewed without connecting to a live accounting system. Matching keys, tax basis, tolerance and split-billing rules are agreed first. The client retains payment approval.
Original studio demonstration using fictional data and AI-assisted development. No client records or paid engagement are represented.
0 likes · 1 view · Nov 11, 2026
Python checks for duplicate supplier invoices, purchase-order mismatches and missing job codes, with an £831.50 fictional control total.