Record discrepancy decisions without editing source entries
Finance has confirmed that a 0.03 difference is a provider fee adjustment. They need to explain it without changing the settlement CSV or marking every mismatch resolved automatically.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Optimistic concurrency · Auditability · RBAC
Estimated field mix
- Backend60%
- Security20%
- Database engineering20%
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 subscription service invoices in USD and EUR. Finance currently compares a payment-provider CSV with database exports; late refunds and retried imports make the monthly close unreliable. Work on synthetic ledger entries only.
Setup prerequisites
- REST APIs
- SQL transactions
- Integer money representation
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- An authorized reviewer can append a reason and decision to one discrepancy.
- Concurrent decisions against the same revision produce one success and one conflict.
- Reports show the original difference and complete decision history.
Implementation constraints
- A decision changes review state, not the immutable amounts or provider provenance.
Verification to include
- Resolve and reopen a discrepancy while preserving both decisions.
- Reject stale revisions and an actor lacking finance-review permission.
Deliverables
- Discrepancy decision API and history contract
Rollout and recovery
Gate the command to a test finance role; disable writes while keeping history readable on rollback.
Value of the work
For the engineer: Practice monetary invariants, concurrent writes, reconciliation, and operational recovery across one service boundary.
For the team: Review how an engineer makes discrepancies explainable and recoverable before a financial workflow is trusted.
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.