Check line-item arithmetic using exact decimal rules
Binary floating point produces an apparent mismatch on an otherwise consistent invoice.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Numeric correctness · Data validation
Estimated field mix
- Data engineering60%
- Applied AI40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional procurement team receives inconsistent supplier documents. It wants draft records that staff can review without treating model output as authoritative accounting data.
Setup prerequisites
- Author synthetic text invoices with ambiguous dates, currencies, and line items; use a deterministic provider double.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Use declared currency scale and rounding rules.
- Compare quantity, price, subtotal, and total consistently.
- Represent unresolved tax or discount differences as discrepancies.
Implementation constraints
- Never silently alter document totals to make arithmetic balance.
Verification to include
- Validate a rounding-boundary invoice.
- Flag inconsistent totals and unsupported precision.
Deliverables
- Arithmetic consistency checks.
Rollout and recovery
Show discrepancies to reviewers; do not promote inconsistent drafts automatically.
Value of the work
For the engineer: Practice schema constraints, numerical checks, review workflows, and safe model boundaries.
For the team: Produce an inspectable extraction prototype that can reduce manual transcription while preserving review control.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.