DIGITAL BRAID | THE BORING PARTS OF AI WORKFLOWS
Fictional test inputs and expected behavior

All records are invented for this article. They contain no client data.
Four scenarios use five rows because the duplicate scenario requires two inputs.
Amounts are USD. Matching and conflicting examples assume no tax, discounts,
or additional charges. Real workflows need their own confirmed rules.

INV-041: 1200.00 + 800.00 = 2000.00. Arithmetic check passes.
This does not authorize payment or confirm the document's authenticity.

INV-042: 1200.00 + 800.00 = 2000.00. Printed total is 2100.00.
Difference: 100.00. Preserve all source values. Hold for review.
Do not overwrite the printed total or invent another charge.

INV-043: Labor amount is missing. Do not treat it as zero and do not infer
800.00 by subtracting from the printed total. Hold for source clarification.

INV-044: Two rows share an identifier. Flag both as a potential duplicate
and prevent double counting pending review. A real workflow should define
identifier scope, such as supplier plus invoice number, and revision handling.

No batch is approved by this example. This is a small teaching fixture,
not a production validation suite or an executable automation.