Sanctions-Blocked Payments Liquidity Architecture Director

The mandate

Cash is accumulating in several service entities while headquarters funds payroll, parts and field engineers elsewhere. Management describes the entire balance as sanctions trapped, yet transaction reviews reveal different causes: true legal prohibitions, bank-risk decisions, missing end-use evidence, inconsistent names, unsupported intercompany invoices and payment messages routed through unsuitable correspondents. Treating every rejected transfer alike has obscured recoverable liquidity, encouraged unsafe workarounds and produced entity buffers unrelated to actual clearance times.

The deliverables are a payment-blockage taxonomy, transaction-and-bank evidence ledger, corridor cash map, lawful routing decision tree, entity-buffer methodology, bank engagement pack, control design and implementation roadmap. Each item must distinguish legal restriction, institution appetite, documentation fault, message-format failure and commercial dispute. The architecture must cover inbound customer receipts, supplier payments, service reimbursements, intercompany funding, dividends and refunds without proposing evasion, stripping payment information or fragmenting transactions.

Four milestones govern the engagement: week three accepts the fact base and sample design; week seven validates root causes with counsel, banks and affected entities; week twelve approves the future routing, buffer and escalation principles; and week seventeen accepts the implementation backlog, ownership model and executive decision record. Billing follows those four milestones, and unresolved counsel opinions will be visibly isolated rather than converted into consultant assumptions.

Acceptance requires compliance and treasury to reconcile every sampled case to evidence, affected finance leads to operate the decision tree in a supervised simulation, and two relationship banks to comment on proposed documentation packs without being treated as legal arbiters. The final design must quantify genuinely unavailable cash, potentially releasable cash, expected clearance time, operational funding need and residual bank-concentration risk by corridor and entity.

The client provides transaction messages, rejection notices, screening cases, invoices, contracts, entity balances, bank correspondence, KYC files, counsel opinions, system access and named regional owners. The consultant will not issue sanctions opinions, direct banks to process transactions, recommend concealment, execute payments, select customers, approve counterparties or restructure ownership. Legal interpretation remains with counsel; transactional decisions remain with authorised officers.

Why this is external work

Compliance can identify prohibited conduct, treasury can see stranded balances and local teams can describe failed payments, but no owner currently joins those facts into a usable liquidity design. Banks also explain their own appetite rather than the group’s corridor architecture. A specialist outside commercial pressure can separate restriction from remediable friction and create a lawful operating answer without weakening financial-crime controls.

What you will own

• Classify blocked and delayed transactions by legal prohibition, bank appetite, documentation defect, message failure, dispute and unknown cause.
• Reconcile entity cash, rejected-payment queues, operational obligations and corridor clearance times into one restricted-liquidity map.
• Design evidence packs for customer, supplier, intercompany and refund payments, including ownership, purpose and end-use support.
• Establish routing and escalation rules that preserve complete payment data and prohibit transaction splitting, concealment or informal value transfer.
• Calculate entity buffer needs from evidenced clearance distributions, operational criticality, currencies, bank concentration and funding alternatives.
• Facilitate counsel, bank and business validation while recording disagreements, unanswered questions and conditions attached to institutional feedback.
• Deliver the prioritised implementation backlog, system changes, control owners, management indicators and board-level residual-risk paper.

Candidate qualifications

• Has redesigned treasury operations where sanctions screening, correspondent appetite and cross-border payment evidence materially constrained liquidity.
• Understands SWIFT messages, payment repair, bank processes, beneficial ownership, trade documentation, intercompany funding and bank escalation.
• Can separate binding legal restrictions from risk-based bank refusals and operational defects without offering unauthorised legal conclusions.
• Has converted transaction-level failure data into corridor buffers, bank strategy, control changes and executive funding choices.
• Brings credible experience working jointly with sanctions counsel, financial-crime teams, relationship banks and operational finance leaders.
• Can demonstrate an architecture that recovered lawful cash while preventing circumvention, stripped data and unsupported payment narratives.

Non-negotiables

• Can maintain the Vienna hybrid cadence and participate in both correspondent-bank workshops plus affected-entity interviews.
• Will never propose message stripping, transaction fragmentation, proxy payers or any other technique intended to bypass controls.
• Brings hands-on restricted-payment and treasury architecture experience; policy drafting without transaction operations is insufficient.
• Will disclose relationships with relevant banks, screening vendors, advisers and customers before receiving case-level information.

1. 49 words maximum. Which evidence would distinguish a sanctions prohibition from a correspondent bank’s risk-appetite refusal?
2. 49 words maximum. How would you size an entity buffer when rejected-payment causes have materially different clearance times?
3. 49 words maximum. Name one proposed liquidity workaround you would reject immediately and explain the control reason.