Match settlement lines without combining currencies
Provider reference pay_204 exists on a EUR invoice, but a malformed USD settlement row shares the reference. The current join marks the invoice paid.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- SQL · Domain modeling · Data integrity
Estimated field mix
- Backend60%
- Database engineering40%
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
- Match only within merchant, reference, and currency boundaries.
- Represent matched, unmatched, and conflicting lines separately.
- Calculate batch totals independently for each currency.
Implementation constraints
- A reference match with a currency mismatch is a conflict, never an exchange-rate conversion.
Verification to include
- Match a complete EUR batch to its invoices.
- Keep same-reference USD and cross-merchant rows unresolved.
Deliverables
- Reconciliation query and currency-conflict fixture
Rollout and recovery
Compare dry-run classifications with the synthetic finance baseline before switching reports.
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.