Skip to content

uid: T-184 title: "Pay with…" dropdown on Bank Access status: todo area: accounting created: 2026-07-25 updated: 2026-07-28 owner: girafeev1 related: T-178

T-184 β€” "Pay with…" on Bank Access

Why

From T-178's owner-revised build order, phase 7: a "Pay with…" dropdown on Bank Access, so an outbound payment can be originated against an existing document rather than typed free-hand.

The WOPC-first flow already exists in the other direction: POST /api/accounting/wopc/create-pending mints a WOPC before the bank transaction, returns a matching reference (#ERL-WOPC|JC-2026-007) for the transfer remarks, and wopc-auto-match.ts links the two when the transaction syncs. This task is the counterpart entry point on the Bank Access side.

Scope

  • A "Pay with…" affordance offering the documents that can originate a payment (unpaid WOPCs first; see T-186 for vendor invoices).
  • Reuse the existing matching-reference scheme rather than inventing a second linking mechanism.

T-185 stops the same document being paid twice through this or any other route.

Source

Split out of T-178's phase 7 on 2026-07-25 at the owner's request ("Split Phase 7 in T-178"). Phase 7 was a catch-all of three unrelated items; each now stands alone.

Source: Records (Infrastructure) Β· https://claude.ai/code/session_018RDB37kCqfouHdygVXTAtD

Assignment (2026-07-28)

Owner: "Regarding T-184, I think 'Bank Access (Diagnostics)' should be the most suitable agent to work on it" β€” this task is assigned to the Bank Access (Diagnostics) agent. It fits: the work is a Bank Access-side entry point ("Pay with…"), and the queue-at-issue step below needs the Airwallex transfer particulars that agent already owns. Source: Records (Infrastructure) Β· https://claude.ai/code/session_018RDB37kCqfouHdygVXTAtD

Note from T-178 (2026-07-28)

Reimbursement WOPCs joined the signature-release pipeline: a payment queued behind one now releases the moment the co-director signs, and the receipts settle themselves at that same moment (see T-178). What T-178 deliberately did NOT build is the queuing step at issue time β€” the queue's authorization design requires the creator to review the exact transfer (amount, saved beneficiary, source account), which the Reimbursements confirm doesn't collect. That is THIS task's scope: when "Pay with…" lands, reimbursement WOPCs should be offerable like fee WOPCs, and queuing one behind its signature completes the owner's "payment transaction submitted simultaneously" end to end. Source: Records (Infrastructure) Β· https://claude.ai/code/session_018RDB37kCqfouHdygVXTAtD