Request
Signal Dispatch's finance engineer needs an atomic account transfer with a durable local ledger record. Build a request table, apply a debit and credit together, and reconcile balances against the request. The fixture has no external payment service; the deliverable is the database transaction and its checked evidence.
Data
Use the fictional customers, orders, items, event documents and account records supplied in the workspace. No production data is connected.
Final output
Complete all six checked stages and leave the final SQL and result available for review. Each stage names its required object or output.
Signal Dispatch's finance engineer needs an atomic account transfer with a durable local ledger record. Build a request table, apply a debit and credit together, and reconcile balances against the request. The fixture has no external payment service; the deliverable is the database transaction and its checked evidence.
Build the requested result in six checked stages. Each stage keeps the earlier SQL in the editor so you can extend the same work. The next stage begins with your own submitted script; Start over restores the reference starting point for that stage. Read the output contract before adding a column or changing a filter.
Keep source rows intact unless the task explicitly asks for a write. Missing values and period boundaries are included deliberately. The checker reruns the work against changed source records, so a fixed visible total isn't a valid substitute for the query or database object.
A transfer request needs a stable replay key and a positive amount.