Foreign Check Deposit Processing
Non-Canadian foreign checks cross three systems, two compliance checkpoints, and a manual GL entry. Most institutions take nine days for what should take two.
The failure pattern
The check arrives at the branch and enters a manual corridor: a correspondent portal submission (requiring specialized access), an exchange-rate lock that happens at a different point than the GL posting, and a weekly batch reconciliation that surfaces discrepancies days late. Reg CC hold-notice timing compresses as manual steps stretch, increasing compliance risk.
Regulatory context
Regulation CC (funds availability and hold notices), BSA/AML screening for cross-border items, general GL accuracy requirements. Verify your specific hold schedules and screening thresholds locally.
The target state
Exchange-rate lock and GL posting happen in the same transaction. Reg CC hold notices generate automatically from the deposit event. Correspondent submission does not require specialized physical presence. Reconciliation runs daily with same-day exception surfacing.
Our approach
A Workflow Fit read identifies the specific handoff gaps. A Prove It Sprint maps the process end-to-end, quantifies the delay at each handoff, and defines the build boundary — which steps to automate and which to leave to human judgment. The sprint produces a decision package before any code is written.
Why do foreign check deposits take so long at credit unions?
The process crosses three systems (core, GL, correspondent portal), requires specialized access for correspondent submission, and typically relies on weekly batch reconciliation. Each handoff creates delay that compounds.
What compliance risks exist in foreign check processing?
Reg CC hold-notice timing requirements, BSA/AML screening obligations for cross-border items, and GL accuracy requirements. When manual processing extends the timeline, hold-notice windows compress and compliance risk increases.
Can foreign check deposit processing be automated?
Key steps can be: rate-lock-to-posting synchronization, automatic hold-notice generation, and daily reconciliation. The build boundary defines which steps should remain with human judgment.
Verify locally. This page characterizes the workflow at framework level. Specific regulatory thresholds, timing windows, and requirements should be verified by your compliance team against current guidance.
General operational information, not legal or compliance advice. Verify locally.
Get a fit read on this workflow.
Tell us about your version of this workflow and we’ll give you an honest read on whether it’s ours to take.
