[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F9932K5P6K4DM1AX0JEE6N":3,"skill-same:01M7F9932K5P6K4DM1AX0JEE6N":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M7F9932K5P6K4DM1AX0JEE6N","managing-wire-transfer-operations",null,"Structures wire transfer processing with verification, OFAC screening, and exception handling. Use when processing wires, managing wire operations, or handling wire exceptions.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fmanaging-wire-transfer-operations\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: managing-wire-transfer-operations\nlanguage: en\ndescription: Structures wire transfer processing with verification, OFAC screening, and exception handling. Use when processing wires, managing wire operations, or handling wire exceptions.\ntags:\n  - management\n  - commercial-banking\nmetadata:\n  author: casemark\n  practice_areas:\n    - Commercial Banking\n    - Trade Finance\n    - Lending\n  document_types:\n    - Management Report\n  skill_modes:\n    - Management\n    - Coordination\nsource: \"https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills\"\nsource_repository: \"CaseMark\u002Fskills\"\nsource_path: \"skills\u002Ffinance\u002Fmanaging-wire-transfer-operations\u002FSKILL.md\"\nlicense: \"Apache-2.0\"\nimported_at: \"2026-09-20\"\n---\n# Managing Wire Transfer Operations\n\nStructures wire transfer processing workflows including initiation verification, OFAC\u002Fsanctions screening, beneficiary validation, exception handling, and end-of-day reconciliation for domestic and international wires.\n\n## When To Use\n\n- Processing or reviewing individual wire transfer requests (Fedwire, SWIFT, CHIPS)\n- Building or auditing wire operations procedures and controls\n- Managing wire exception queues (OFAC hits, name mismatches, incomplete beneficiary info)\n- Coordinating same-day or time-critical wire processing (e.g., loan fundings, real estate closings, trade settlements)\n- Generating daily wire activity reports or investigating wire discrepancies\n- Onboarding repetitive\u002Fstanding wire instructions for commercial clients\n\n## Inputs To Gather\n\n- **Wire request details**: originator name and account, beneficiary name\u002Faccount\u002Fbank (ABA or SWIFT\u002FBIC), amount, currency, purpose\u002Freference, value date\n- **Authorization records**: dual-control signatures, callback verification logs, approved signor lists\n- **Screening context**: OFAC\u002FSDN list version date, any prior screening results, country-risk classification\n- **Client profile**: wire agreement on file (yes\u002Fno), repetitive wire template ID if applicable, daily\u002Ftransaction limits\n- **Exception details** (if applicable): hold reason, screening hit details, missing fields, prior resolution attempts\n\n## Workflow\n\n1. **Validate wire request completeness**\n   - Confirm all required fields: originator, beneficiary name, account number, routing (ABA for domestic \u002F SWIFT BIC + intermediary for international), amount, currency, purpose\n   - Verify wire authorization against approved signor list and confirm dual-control sign-off\n   - For phone-initiated wires, confirm callback verification was completed to a number on file\n\n2. **Screen for sanctions and compliance**\n   - Run originator and beneficiary through OFAC\u002FSDN, EU sanctions, and any institution-specific restricted-party lists\n   - Flag transactions involving high-risk jurisdictions [VERIFY against current institution country-risk list]\n   - For international wires, verify compliance with FATF travel rule requirements — originator and beneficiary information must accompany the payment message\n   - Document screening results with timestamp and analyst ID\n\n3. **Process or escalate exceptions**\n   - **OFAC potential match**: Place wire on hold, document the hit details, escalate to BSA\u002FAML officer for true-match determination within required timeframe [VERIFY institution-specific SLA, typically 2–4 hours]\n   - **Beneficiary mismatch**: Contact originator for corrected details; do not process with unverified beneficiary information\n   - **Limit breach**: Escalate to authorized approver for override or request client provide updated wire agreement with higher limits\n   - **Cutoff time miss**: Notify originator of next-business-day processing; document reason for delay\n\n4. **Execute wire transmission**\n   - Release wire through payment platform (Fedwire, SWIFT) with dual-control release\n   - Capture confirmation number \u002F IMAD (Input Message Accountability Data) for Fedwire or SWIFT message reference\n   - Provide originator with confirmation including reference number and expected value date\n   - For international wires, confirm intermediary bank routing and any applicable correspondent charges (OUR\u002FBEN\u002FSHA)\n\n5. **Reconcile and report**\n   - Match outgoing wires against general ledger wire clearing account at end of day\n   - Investigate and resolve any unmatched items before next-business-day processing\n   - Generate daily wire activity report: total count, total dollar volume, exceptions processed, wires held\u002Frejected\n   - File all wire documentation (request, authorization, screening results, confirmation) per record retention policy [VERIFY retention period — typically 5 years under BSA]\n\n## Output\n\n- **Wire processing log**: Chronological record of each wire with status (completed, held, rejected, pending), confirmation references, and exception notes\n- **Exception summary**: List of all flagged items with resolution status, escalation path taken, and time-to-resolution\n- **Daily reconciliation report**: Wire clearing account balance, matched vs. unmatched items, variance explanations\n- **Compliance documentation**: Screening results, OFAC disposition records, and any SAR referral notes\n\n## Quality Checks\n\n- Every wire has documented dual-control authorization before release\n- OFAC screening results are timestamped and tied to the specific transaction — no batch-and-assume\n- Beneficiary account and routing details match exactly; partial matches are treated as exceptions, not approvals\n- International wires include complete originator and beneficiary information per travel rule requirements\n- Cutoff times are enforced consistently; any exceptions are documented with approver sign-off [VERIFY Fedwire cutoff — typically 6:00 PM ET for standard, 6:30 PM ET for settlement]\n- Wire clearing account reconciles to zero (or known pending items) at end of each business day\n- All records retained per BSA\u002FAML requirements and institution retention schedule\n","# Managing Wire Transfer Operations\n\nStructures wire transfer processing workflows including initiation verification, OFAC\u002Fsanctions screening, beneficiary validation, exception handling, and end-of-day reconciliation for domestic and international wires.\n\n## When To Use\n\n- Processing or reviewing individual wire transfer requests (Fedwire, SWIFT, CHIPS)\n- Building or auditing wire operations procedures and controls\n- Managing wire exception queues (OFAC hits, name mismatches, incomplete beneficiary info)\n- Coordinating same-day or time-critical wire processing (e.g., loan fundings, real estate closings, trade settlements)\n- Generating daily wire activity reports or investigating wire discrepancies\n- Onboarding repetitive\u002Fstanding wire instructions for commercial clients\n\n## Inputs To Gather\n\n- **Wire request details**: originator name and account, beneficiary name\u002Faccount\u002Fbank (ABA or SWIFT\u002FBIC), amount, currency, purpose\u002Freference, value date\n- **Authorization records**: dual-control signatures, callback verification logs, approved signor lists\n- **Screening context**: OFAC\u002FSDN list version date, any prior screening results, country-risk classification\n- **Client profile**: wire agreement on file (yes\u002Fno), repetitive wire template ID if applicable, daily\u002Ftransaction limits\n- **Exception details** (if applicable): hold reason, screening hit details, missing fields, prior resolution attempts\n\n## Workflow\n\n1. **Validate wire request completeness**\n   - Confirm all required fields: originator, beneficiary name, account number, routing (ABA for domestic \u002F SWIFT BIC + intermediary for international), amount, currency, purpose\n   - Verify wire authorization against approved signor list and confirm dual-control sign-off\n   - For phone-initiated wires, confirm callback verification was completed to a number on file\n\n2. **Screen for sanctions and compliance**\n   - Run originator and beneficiary through OFAC\u002FSDN, EU sanctions, and any institution-specific restricted-party lists\n   - Flag transactions involving high-risk jurisdictions [VERIFY against current institution country-risk list]\n   - For international wires, verify compliance with FATF travel rule requirements — originator and beneficiary information must accompany the payment message\n   - Document screening results with timestamp and analyst ID\n\n3. **Process or escalate exceptions**\n   - **OFAC potential match**: Place wire on hold, document the hit details, escalate to BSA\u002FAML officer for true-match determination within required timeframe [VERIFY institution-specific SLA, typically 2–4 hours]\n   - **Beneficiary mismatch**: Contact originator for corrected details; do not process with unverified beneficiary information\n   - **Limit breach**: Escalate to authorized approver for override or request client provide updated wire agreement with higher limits\n   - **Cutoff time miss**: Notify originator of next-business-day processing; document reason for delay\n\n4. **Execute wire transmission**\n   - Release wire through payment platform (Fedwire, SWIFT) with dual-control release\n   - Capture confirmation number \u002F IMAD (Input Message Accountability Data) for Fedwire or SWIFT message reference\n   - Provide originator with confirmation including reference number and expected value date\n   - For international wires, confirm intermediary bank routing and any applicable correspondent charges (OUR\u002FBEN\u002FSHA)\n\n5. **Reconcile and report**\n   - Match outgoing wires against general ledger wire clearing account at end of day\n   - Investigate and resolve any unmatched items before next-business-day processing\n   - Generate daily wire activity report: total count, total dollar volume, exceptions processed, wires held\u002Frejected\n   - File all wire documentation (request, authorization, screening results, confirmation) per record retention policy [VERIFY retention period — typically 5 years under BSA]\n\n## Output\n\n- **Wire processing log**: Chronological record of each wire with status (completed, held, rejected, pending), confirmation references, and exception notes\n- **Exception summary**: List of all flagged items with resolution status, escalation path taken, and time-to-resolution\n- **Daily reconciliation report**: Wire clearing account balance, matched vs. unmatched items, variance explanations\n- **Compliance documentation**: Screening results, OFAC disposition records, and any SAR referral notes\n\n## Quality Checks\n\n- Every wire has documented dual-control authorization before release\n- OFAC screening results are timestamped and tied to the specific transaction — no batch-and-assume\n- Beneficiary account and routing details match exactly; partial matches are treated as exceptions, not approvals\n- International wires include complete originator and beneficiary information per travel rule requirements\n- Cutoff times are enforced consistently; any exceptions are documented with approver sign-off [VERIFY Fedwire cutoff — typically 6:00 PM ET for standard, 6:30 PM ET for settlement]\n- Wire clearing account reconciles to zero (or known pending items) at end of each business day\n- All records retained per BSA\u002FAML requirements and institution retention schedule\n",{"name":5,"tags":24,"source":27,"license":15,"language":28,"metadata":29,"description":7,"imported_at":40,"source_path":41,"source_repository":42},[25,26],"management","commercial-banking","https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills","en",{"author":30,"skill_modes":31,"document_types":34,"practice_areas":36},"casemark",[32,33],"Management","Coordination",[35],"Management Report",[37,38,39],"Commercial Banking","Trade Finance","Lending","2026-09-20","skills\u002Ffinance\u002Fmanaging-wire-transfer-operations\u002FSKILL.md","CaseMark\u002Fskills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Ffinance\u002Fmanaging-wire-transfer-operations","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-wire-transfer-operations",{"tool":55,"command":56},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-wire-transfer-operations",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-wire-transfer-operations","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fmanaging-wire-transfer-operations\u002FSKILL.md",true,[],[64,72,79,86,93,100],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]