@1aboveio/skills 0.20.2 → 0.20.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (85) hide show
  1. package/README.md +12 -5
  2. package/package.json +1 -1
  3. package/runtime/skills/distribution/generated/recipes.json +220 -25
  4. package/runtime/skills/distribution/scripts/bundles.mjs +49 -5
  5. package/runtime/skills/engineering/engineering-runtime/scripts/workflow-coherence.mjs +4 -0
  6. package/runtime/skills/engineering/engineering-runtime/scripts/workflow-policy.mjs +1 -1
  7. package/skills/compliance/compliance-audit/LICENSE +3 -0
  8. package/skills/compliance/compliance-audit/SKILL.md +466 -0
  9. package/skills/compliance/compliance-audit/references/findings-schema.md +290 -0
  10. package/skills/compliance/compliance-audit/references/vars-checklist.md +1068 -0
  11. package/skills/compliance/compliance-audit/references/vars-findings-schema.md +395 -0
  12. package/skills/compliance/compliance-audit/scripts/reconcile_tracker.py +454 -0
  13. package/skills/compliance/compliance-audit/scripts/test_validate_tracker.py +90 -0
  14. package/skills/compliance/compliance-audit/scripts/validate_tracker.py +752 -0
  15. package/skills/compliance/doc-authenticity/LICENSE +3 -0
  16. package/skills/compliance/doc-authenticity/SKILL.md +158 -0
  17. package/skills/compliance/doc-authenticity/references/agreement.md +66 -0
  18. package/skills/compliance/doc-authenticity/references/bank-statement.md +150 -0
  19. package/skills/compliance/doc-authenticity/references/forensic-signals.md +157 -0
  20. package/skills/compliance/doc-authenticity/references/image-signals.md +114 -0
  21. package/skills/compliance/doc-authenticity/references/invoice.md +66 -0
  22. package/skills/compliance/doc-authenticity/references/issuer-profiles.md +86 -0
  23. package/skills/compliance/doc-authenticity/references/verdict-and-report.md +95 -0
  24. package/skills/compliance/doc-authenticity/references/verdict.schema.json +81 -0
  25. package/skills/compliance/doc-authenticity/scripts/image_forensics.py +294 -0
  26. package/skills/compliance/doc-authenticity/scripts/pdf_forensics.py +401 -0
  27. package/skills/compliance/doc-authenticity/scripts/validate_codes.py +224 -0
  28. package/skills/compliance/doc-authenticity/scripts/validate_verdict.py +308 -0
  29. package/skills/compliance/report-writing/LICENSE +3 -0
  30. package/skills/compliance/report-writing/SKILL.md +206 -0
  31. package/skills/compliance/report-writing/references/audit-report-template.md +121 -0
  32. package/skills/compliance/report-writing/references/external-assessment-template.md +167 -0
  33. package/skills/compliance/report-writing/references/management-report-template.md +145 -0
  34. package/skills/compliance/report-writing/references/vars-report-template.md +224 -0
  35. package/skills/document-utils/doc-to-md/LICENSE +3 -0
  36. package/skills/document-utils/doc-to-md/SKILL.md +77 -0
  37. package/skills/document-utils/doc-to-md/scripts/convert.py +157 -0
  38. package/skills/document-utils/reg-parser/LICENSE +3 -0
  39. package/skills/document-utils/reg-parser/SKILL.md +201 -0
  40. package/skills/document-utils/reg-parser/references/checklist-schema.md +223 -0
  41. package/skills/document-utils/reg-parser/references/checklists/hk-amlo-checklist.json +1306 -0
  42. package/skills/document-utils/reg-parser/references/checklists/hk-amlo-checklist.md +469 -0
  43. package/skills/document-utils/reg-parser/references/checklists/hk-fi-corporate-onboarding-cdd-checklist.json +634 -0
  44. package/skills/document-utils/reg-parser/references/checklists/hk-fi-corporate-onboarding-cdd-checklist.md +233 -0
  45. package/skills/document-utils/reg-parser/references/checklists/hk-mso-guideline-checklist.json +2194 -0
  46. package/skills/document-utils/reg-parser/references/checklists/hk-mso-guideline-checklist.md +771 -0
  47. package/skills/document-utils/reg-parser/references/checklists/kyc-aml-checklist.md +258 -0
  48. package/skills/document-utils/reg-parser/references/checklists/visa-vars-checklist.md +1058 -0
  49. package/skills/document-utils/reg-parser/references/mandates/hk-amlo-cap615.md +389 -0
  50. package/skills/document-utils/reg-parser/references/mandates/visa-vars.md +205 -0
  51. package/skills/document-utils/reg-parser/scripts/compare_checklist.py +228 -0
  52. package/skills/document-utils/reg-parser/scripts/dump_checklist.py +348 -0
  53. package/skills/document-utils/reg-parser/scripts/preprocess-mandate.sh +171 -0
  54. package/skills/document-utils/reg-parser/scripts/test_quarantine.sh +102 -0
  55. package/skills/document-utils/reg-parser/scripts/validate_checklist.py +532 -0
  56. package/skills/document-utils/reg-parser/scripts/validate_mandate.py +242 -0
  57. package/skills/engineering/engineering-runtime/coherence/workflow.json +16 -16
  58. package/skills/engineering/engineering-runtime/scripts/workflow-coherence.mjs +4 -0
  59. package/skills/engineering/engineering-runtime/scripts/workflow-policy.mjs +1 -1
  60. package/skills/payment/similar-domain/LICENSE +3 -0
  61. package/skills/payment/similar-domain/SKILL.md +178 -0
  62. package/skills/payment/similar-domain/references/entities.md +58 -0
  63. package/skills/payment/similar-domain/references/fingerprints.md +82 -0
  64. package/skills/payment/similar-domain/references/pivots.md +66 -0
  65. package/skills/payment/similar-domain/references/report-template.md +76 -0
  66. package/skills/payment/similar-domain/references/scoring.md +61 -0
  67. package/skills/payment/similar-domain/references/terminology.md +37 -0
  68. package/skills/payment/similar-domain/references/workflow.md +79 -0
  69. package/skills/payment/tld-detection/SKILL.md +76 -21
  70. package/skills/payment/tld-detection/references/clean.md +1 -1
  71. package/skills/payment/tld-detection/references/clustering.md +21 -6
  72. package/skills/payment/tld-detection/references/decision.md +7 -2
  73. package/skills/payment/tld-detection/references/fx-conversion.md +229 -0
  74. package/skills/payment/tld-detection/references/report-template.md +63 -27
  75. package/skills/payment/tld-detection/references/streams.md +90 -0
  76. package/skills/payment/tld-detection/references/terminology.md +15 -7
  77. package/skills/payment/tld-detection/references/workflow.md +1 -1
  78. package/skills/payment/tld-detection/scripts/detect_streams.py +542 -0
  79. package/skills/engineering/ensure-coverage/evals/evals.json +0 -125
  80. package/skills/engineering/rush-issues/evals/evals.json +0 -65
  81. package/skills/engineering/rush-release/evals/evals.json +0 -58
  82. package/skills/fullstack/shadcn/evals/evals.json +0 -90
  83. package/skills/payment/fraud-analysis/evals/evals.json +0 -40
  84. package/skills/payment/tld-detection/evals/evals.json +0 -107
  85. package/skills/payment/tld-detection/tests/test_detect_ladders.py +0 -132
@@ -0,0 +1,469 @@
1
+ ```yaml
2
+ name: "HK AMLO Compliance Checklist"
3
+ regulation: "Anti-Money Laundering and Counter-Terrorist Financing Ordinance (Cap. 615), Hong Kong"
4
+ version: "1.0"
5
+ scope: "Customer due diligence, ongoing monitoring, special requirements (wire transfers, virtual asset transfers, correspondent banking, PEPs), prohibitions, and record-keeping obligations imposed on financial institutions and DNFBPs under Schedule 2 of Cap. 615 (consolidated 15-05-2026)"
6
+ date: "2026-05-15"
7
+ summary:
8
+ categories: 9
9
+ total_items: 31
10
+ critical: 23
11
+ major: 7
12
+ minor: 1
13
+ ```
14
+
15
+ ## CAT-01: Customer Due Diligence Measures
16
+
17
+ ### CAT-01-001: Identify and verify customer identity
18
+
19
+ - **Requirement:** Identify the customer and verify the customer's identity using documents, data, or information from a governmental body, the relevant authority/regulator, an equivalent foreign authority, a recognized digital identification system, or another reliable and independent source, before establishing a business relationship or carrying out a triggering occasional transaction.
20
+ - **Source:** Schedule 2, §2(1)(a), §2(1)(ab), §3(1)(a), Cap. 615
21
+ - **Severity:** critical
22
+ - **Verification:**
23
+ - [ ] Identification documents collected for each customer (natural person or entity)
24
+ - [ ] Source of the identifying documents/data falls within an approved source class (gov body, relevant authority, foreign equivalent, recognized digital ID system, or recognized reliable independent source)
25
+ - [ ] Verification completed before establishing the business relationship (or within the deferral conditions of §3(2))
26
+ - [ ] Verification date, method, and source of evidence recorded in the customer file
27
+ - **Evidence:**
28
+ - Copy of identification document
29
+ - Verification log entry citing source and officer
30
+ - Customer onboarding form with date of verification
31
+
32
+ ### CAT-01-002: Identify and verify beneficial owners
33
+
34
+ - **Requirement:** Where the customer has a beneficial owner, identify the beneficial owner and take reasonable measures to verify the beneficial owner's identity, including measures to understand the ownership and control structure of any legal person or trust customer.
35
+ - **Source:** Schedule 2, §2(1)(b), Cap. 615
36
+ - **Severity:** critical
37
+ - **Verification:**
38
+ - [ ] Beneficial owner(s) identified using the >25% ownership/voting threshold or "ultimate control" test in §1(1)
39
+ - [ ] For trust customers, beneficiaries, settlor, trustee, protector/enforcer, and ultimate controller all assessed
40
+ - [ ] Reasonable measures taken to verify each beneficial owner's identity
41
+ - [ ] Ownership/control structure of the legal person or trust mapped and recorded
42
+ - **Evidence:**
43
+ - Beneficial ownership declaration
44
+ - Group/trust structure chart with percentages
45
+ - Verification records for each identified beneficial owner
46
+
47
+ ### CAT-01-003: Obtain purpose and intended nature of the business relationship
48
+
49
+ - **Requirement:** Where a business relationship is to be established, obtain information on the purpose and intended nature of the business relationship, unless the purpose and intended nature are obvious.
50
+ - **Source:** Schedule 2, §2(1)(c), Cap. 615
51
+ - **Severity:** major
52
+ - **Verification:**
53
+ - [ ] Customer questionnaire or equivalent captures purpose and expected nature of the relationship
54
+ - [ ] Expected transaction types and volumes documented
55
+ - [ ] Determination recorded where the purpose is judged "obvious" and CDD measure (c) omitted
56
+ - **Evidence:**
57
+ - Completed onboarding questionnaire
58
+ - Account-opening memo
59
+
60
+ ### CAT-01-004: Verify persons purporting to act on behalf of the customer
61
+
62
+ - **Requirement:** Where a person purports to act on behalf of the customer, identify that person, take reasonable measures to verify their identity using the approved source classes, and verify their authority to act on behalf of the customer.
63
+ - **Source:** Schedule 2, §2(1)(d), Cap. 615
64
+ - **Severity:** critical
65
+ - **Verification:**
66
+ - [ ] Identity of representative captured and verified per §2(1)(d)(i) or (ia)
67
+ - [ ] Documentary evidence of authority to act obtained (power of attorney, board resolution, authorisation letter, etc.)
68
+ - [ ] Authorised-signatory record updated
69
+ - **Evidence:**
70
+ - Representative's identification record
71
+ - Authorisation document (POA, resolution, letter)
72
+ - Signatory list
73
+
74
+ ### CAT-01-005: Apply CDD at all statutory triggers
75
+
76
+ - **Requirement:** Carry out CDD measures before establishing a business relationship; before carrying out an occasional transaction at or above HKD 120,000 (or HKD 8,000 for a wire transfer or virtual asset transfer, including for licensed VAS providers); when there is a money-laundering or terrorist-financing suspicion; or when there is doubt about the veracity or adequacy of previously obtained identification information.
77
+ - **Source:** Schedule 2, §3(1), §3(1A), §3(1B), Cap. 615
78
+ - **Severity:** critical
79
+ - **Verification:**
80
+ - [ ] Onboarding workflow blocks relationship setup until CDD is complete (subject to §3(2) deferral)
81
+ - [ ] Transaction monitoring system flags occasional transactions at the relevant threshold (incl. linked-transaction aggregation)
82
+ - [ ] STR/SAR workflow triggers re-CDD on suspicion
83
+ - [ ] Process exists to re-verify when previously obtained information is doubted
84
+ - **Evidence:**
85
+ - System control documentation
86
+ - Sample onboarding/transaction logs showing CDD trigger points
87
+ - Re-verification case files
88
+
89
+ ### CAT-01-006: Refusal and termination when CDD cannot be completed
90
+
91
+ - **Requirement:** If unable to comply with §3(1), (1A), (1B), or (3), do not establish a business relationship or carry out the occasional transaction; if a relationship already exists, terminate it as soon as reasonably practicable.
92
+ - **Source:** Schedule 2, §3(4), Cap. 615
93
+ - **Severity:** critical
94
+ - **Verification:**
95
+ - [ ] Documented procedure for declining or exiting customers when CDD cannot be completed
96
+ - [ ] Cases logged where onboarding was refused or terminated on CDD-failure grounds
97
+ - [ ] Exit timeline tracked and reviewed
98
+ - **Evidence:**
99
+ - Refusal/termination procedure
100
+ - Refused-applicant log
101
+ - Termination case files with timing
102
+
103
+ ## CAT-02: Simplified Due Diligence
104
+
105
+ ### CAT-02-001: Apply SDD only where the customer or product qualifies
106
+
107
+ - **Requirement:** An FI or DNFBP applying Simplified CDD (limited to measures §2(1)(a)/(ab), (c) and (d)) must do so only where it has reasonable grounds to believe the customer falls within §4(3) (e.g. another FI, listed corporation, supervised investment vehicle, public body, or government in an equivalent jurisdiction) or the product falls within §4(5) (e.g. qualifying pension scheme, life policy under specified premium thresholds).
108
+ - **Source:** Schedule 2, §4(1), §4(3), §4(4), §4(5), Cap. 615
109
+ - **Severity:** major
110
+ - **Verification:**
111
+ - [ ] SDD eligibility test applied and documented before applying simplified measures
112
+ - [ ] Documentary basis for the qualifying customer/product category recorded
113
+ - [ ] Periodic review confirms the qualifying status still holds
114
+ - **Evidence:**
115
+ - SDD eligibility memo
116
+ - Listing/regulator confirmation for the qualifying customer
117
+ - Product spec showing premium/scheme limits
118
+
119
+ ## CAT-03: Ongoing Monitoring and Pre-existing Customers
120
+
121
+ ### CAT-03-001: Continuously monitor the business relationship
122
+
123
+ - **Requirement:** Continuously monitor the business relationship by reviewing customer documents and data to keep them up-to-date and relevant, conducting appropriate scrutiny of transactions for consistency with the customer's profile and source of funds, and identifying complex, unusually large or unusual-pattern transactions with no apparent economic or lawful purpose, and examining and recording the findings in writing.
124
+ - **Source:** Schedule 2, §5(1), Cap. 615
125
+ - **Severity:** critical
126
+ - **Verification:**
127
+ - [ ] Periodic review schedule established by risk rating
128
+ - [ ] Transaction-monitoring system scrutinises activity against customer profile and source of funds
129
+ - [ ] Unusual/complex/large-pattern transactions flagged, investigated, and findings recorded in writing
130
+ - [ ] Customer KYC refresh process keeps documents and data current
131
+ - **Evidence:**
132
+ - Periodic review records
133
+ - Transaction-monitoring alerts and dispositions
134
+ - Written findings memos on unusual-pattern transactions
135
+
136
+ ### CAT-03-002: Additional monitoring measures for higher-risk cases
137
+
138
+ - **Requirement:** Where the customer was not physically present for identification, the customer or beneficial owner is known to be a politically exposed person, or the case falls within §15 (high-risk situations), take additional monitoring measures to compensate for the elevated ML/TF risk.
139
+ - **Source:** Schedule 2, §5(3), §5(4), §5(5), Cap. 615
140
+ - **Severity:** critical
141
+ - **Verification:**
142
+ - [ ] Risk classification flags non-face-to-face, PEP, and §15 high-risk relationships for enhanced monitoring
143
+ - [ ] Enhanced-monitoring scope (frequency, depth, transaction thresholds) documented
144
+ - [ ] Former-PEP carve-out only applied after a documented risk assessment finds no high ML/TF risk
145
+ - [ ] Non-face-to-face carve-out only applied where a recognized digital ID system was used
146
+ - **Evidence:**
147
+ - Enhanced-monitoring policy
148
+ - Sample case files for non-face-to-face, PEP, and §15 cases
149
+ - Risk-assessment memos justifying any former-PEP carve-out
150
+
151
+ ### CAT-03-003: Trigger CDD on pre-existing customers when activity changes
152
+
153
+ - **Requirement:** For a pre-existing customer (excluding §7 pre-existing respondent banks), carry out CDD measures in addition to §3(1)(d) and (e) when a transaction with the customer is unusual or suspicious or inconsistent with the customer's known profile, or when a material change occurs in the way the customer's account is operated; terminate the relationship if unable to comply.
154
+ - **Source:** Schedule 2, §6(1), §6(2), Cap. 615
155
+ - **Severity:** critical
156
+ - **Verification:**
157
+ - [ ] Pre-existing-customer population identified and tracked
158
+ - [ ] Event-driven triggers (unusual/suspicious transaction or material change in account operation) feed CDD workflow
159
+ - [ ] Termination procedure invoked where CDD cannot be completed
160
+ - **Evidence:**
161
+ - Pre-existing-customer register
162
+ - Event-trigger procedure
163
+ - Triggered CDD case files
164
+
165
+ ### CAT-03-004: Pre-existing respondent banking relationships
166
+
167
+ - **Requirement:** An authorized institution must terminate a pre-existing correspondent banking relationship with a respondent bank on the commencement date of the Ordinance unless, before that date, it had carried out §14(1) measures and was satisfied with the respondent's AML/CFT controls; had documented the parties' respective responsibilities; and was satisfied as to the respondent's CDD and continuous monitoring of customers who can directly operate payable-through accounts.
168
+ - **Source:** Schedule 2, §7(1), §7(2), Cap. 615
169
+ - **Severity:** major
170
+ - **Verification:**
171
+ - [ ] Inventory of pre-existing respondent banking relationships maintained
172
+ - [ ] For each retained relationship, documented §14(1)-style assessment exists
173
+ - [ ] Responsibilities of both institutions documented
174
+ - [ ] Direct-operator CDD assurance from the respondent on file
175
+ - **Evidence:**
176
+ - Respondent bank inventory
177
+ - Pre-commencement assessment files
178
+ - Responsibilities matrix
179
+
180
+ ## CAT-04: Special Requirements (Enhanced Due Diligence)
181
+
182
+ ### CAT-04-001: Non-face-to-face customer measures
183
+
184
+ - **Requirement:** Where the customer has not been physically present for identification purposes, carry out at least one of the §9(1) measures: further verify identity using documents/data not previously used; take supplementary verification measures; or route the first payment through an account opened in the customer's name with an authorised institution or an equivalent foreign institution. Exempt only where identification was performed using a recognized digital identification system.
185
+ - **Source:** Schedule 2, §9(1), §9(2), Cap. 615
186
+ - **Severity:** critical
187
+ - **Verification:**
188
+ - [ ] Workflow routes non-face-to-face customers to the §9(1) measures
189
+ - [ ] Selected measure(s) recorded per customer
190
+ - [ ] Digital-ID exemption applied only when a recognized digital ID system per the relevant authority is used
191
+ - **Evidence:**
192
+ - Non-face-to-face onboarding procedure
193
+ - Per-customer record of §9(1) measure applied
194
+ - Digital ID system approval reference
195
+
196
+ ### CAT-04-002: PEP onboarding and continuation
197
+
198
+ - **Requirement:** Where the customer or a beneficial owner is known to be a politically exposed person, before establishing the relationship (or before continuing one where PEP status is later identified), obtain senior management approval and take reasonable measures to establish the customer's or beneficial owner's source of wealth and source of funds. Former-PEP carve-out only applies after a documented risk assessment finds no high ML/TF risk.
199
+ - **Source:** Schedule 2, §10(1), §10(2), §10(3), Cap. 615
200
+ - **Severity:** critical
201
+ - **Verification:**
202
+ - [ ] Screening procedure detects PEP status at onboarding and ongoing
203
+ - [ ] Senior-management approval recorded for each PEP relationship
204
+ - [ ] Source-of-wealth and source-of-funds inquiries documented
205
+ - [ ] Former-PEP carve-out backed by a risk-assessment memo
206
+ - **Evidence:**
207
+ - PEP screening hit reports
208
+ - Senior-management approval records
209
+ - SoW/SoF documentation
210
+
211
+ ### CAT-04-003: Insurance policy beneficiary requirements
212
+
213
+ - **Requirement:** Whenever a beneficiary (or new beneficiary) is identified or designated under an insurance policy, record the beneficiary's name if identified by name, or obtain sufficient information to be able to establish identity at the time of right-exercise or first payout if designated by description; verify the beneficiary's identity at the earlier of right-exercise or first payout, and where the beneficiary is a legal person or trust, identify its beneficial owners (taking reasonable measures to verify their identity where high ML/TF risk).
214
+ - **Source:** Schedule 2, §11(1), §11(2), §11(3), Cap. 615
215
+ - **Severity:** major
216
+ - **Verification:**
217
+ - [ ] Policy administration captures beneficiary name or sufficient identifying information at designation
218
+ - [ ] Verification triggered at the earlier of right-exercise or first payout
219
+ - [ ] Legal-person/trust beneficial-owner identification embedded in the payout workflow
220
+ - [ ] Risk-based beneficial-owner verification applied to high-risk beneficiaries
221
+ - **Evidence:**
222
+ - Beneficiary registration records
223
+ - Payout-time verification records
224
+ - Beneficial-owner identification for entity beneficiaries
225
+
226
+ ### CAT-04-004: High-risk situations beyond enumerated categories
227
+
228
+ - **Requirement:** In a situation specified in writing by the relevant authority or regulatory body, and in any other situation that by its nature presents a high ML/TF risk, obtain senior-management approval to establish or continue the relationship; for new relationships either take reasonable measures to establish source of wealth/funds or take additional risk-mitigation measures; for existing relationships, additionally verify any beneficial owner; for occasional transactions, take additional measures to mitigate the risk.
229
+ - **Source:** Schedule 2, §15, Cap. 615
230
+ - **Severity:** critical
231
+ - **Verification:**
232
+ - [ ] Procedure identifies §15 high-risk situations (incl. regulator notices and intrinsic high-risk indicators)
233
+ - [ ] Senior-management approval required for new and continuing high-risk relationships
234
+ - [ ] SoW/SoF or additional mitigation measures applied as appropriate
235
+ - [ ] Beneficial-owner verification reinforced for existing high-risk relationships
236
+ - **Evidence:**
237
+ - High-risk customer policy with regulator-notice register
238
+ - Senior-management approval records
239
+ - Mitigation-measure case files
240
+
241
+ ## CAT-05: Wire Transfers, Remittance and Virtual Asset Transfers
242
+
243
+ ### CAT-05-001: Originator and recipient information for wire transfers
244
+
245
+ - **Requirement:** Before carrying out a wire transfer as ordering institution, record the originator's name; the originator's account number with the institution (or unique reference number assigned to the transfer); the originator's address, customer ID, identification-document number, or (for an individual) date and place of birth (the latter optional below HKD 8,000); the recipient's name; and the recipient's account number with the beneficiary institution (or unique reference number). Apply the §12(2) exceptions only where they strictly apply (e.g. inter-FI on-own-behalf transfers, certain card transactions).
246
+ - **Source:** Schedule 2, §12(2), §12(3), §12(3A), Cap. 615
247
+ - **Severity:** critical
248
+ - **Verification:**
249
+ - [ ] Wire-transfer system captures the §12(3)(a)–(e) data fields before execution
250
+ - [ ] HKD 8,000 threshold logic governs collection of originator address/ID per §12(3A)
251
+ - [ ] §12(2) exception flags applied only with documented basis
252
+ - **Evidence:**
253
+ - Wire-transfer record specification
254
+ - Sample transfer audit trail
255
+ - Exception register
256
+
257
+ ### CAT-05-002: Transmit wire transfer information with the message
258
+
259
+ - **Requirement:** As ordering institution, must include in the message or payment form accompanying the wire transfer the §12(3) information per the applicable threshold. Where the §12(6) domestic shortcut is used, must supply the omitted §12(3)(a) and (c) information to the receiving institution or relevant authority within 3 business days of request. Where wire transfers are bundled in a batch file to a foreign recipient, must comply with the §12(7) batch-file rules.
260
+ - **Source:** Schedule 2, §12(5), §12(6), §12(7), Cap. 615
261
+ - **Severity:** critical
262
+ - **Verification:**
263
+ - [ ] Outbound message format carries the required fields per threshold
264
+ - [ ] Domestic-shortcut workflow can supply §12(3)(a)/(c) information within 3 business days on request
265
+ - [ ] Batch-file processing carries §12(3)(b) per transfer and §12(3) information at batch level
266
+ - **Evidence:**
267
+ - Message-format specification
268
+ - Request-response logs for §12(6) information requests
269
+ - Batch-file processing documentation
270
+
271
+ ### CAT-05-003: Intermediary and beneficiary obligations for wire transfers
272
+
273
+ - **Requirement:** Acting as intermediary, transmit all received information with the transfer onward. Acting as beneficiary institution: for domestic transfers missing §12(3)(b) information, obtain it from the sending institution as soon as reasonably practicable, and if it cannot be obtained, consider restricting or terminating the relationship or take reasonable risk-mitigation measures; for non-domestic transfers missing §12(3) information, apply the same obtain-or-mitigate logic; in either case, take risk-mitigation measures where the accompanying information is incomplete or meaningless.
274
+ - **Source:** Schedule 2, §12(8), §12(9), §12(10), Cap. 615
275
+ - **Severity:** critical
276
+ - **Verification:**
277
+ - [ ] Intermediary pass-through preserves all received originator/recipient fields
278
+ - [ ] Beneficiary-side procedure escalates missing-information cases for follow-up and risk decision
279
+ - [ ] Documented thresholds/criteria for restricting or terminating sender relationships
280
+ - **Evidence:**
281
+ - Intermediary message specification
282
+ - Missing-information case log
283
+ - Sender-restriction decision register
284
+
285
+ ### CAT-05-004: Licensed money service operator remittance information
286
+
287
+ - **Requirement:** A licensed money service operator carrying out a remittance transaction (other than a wire transfer) at or above HKD 8,000 must, before carrying it out, identify the originator, verify the originator's identity against an identification document, and record the originator's name; ID document number (and place of issue for travel documents); address; currency and amount; date and time of receipt of instructions; recipient's name and address; and method of delivery.
288
+ - **Source:** Schedule 2, §13(1), §13(2), Cap. 615
289
+ - **Severity:** critical
290
+ - **Verification:**
291
+ - [ ] MSO transaction system enforces verification before execution at or above HKD 8,000
292
+ - [ ] All §13(2)(c)(i)–(v) data fields captured
293
+ - [ ] Document-based verification step recorded
294
+ - **Evidence:**
295
+ - MSO remittance record specification
296
+ - Sample transaction file with §13(2) fields populated
297
+
298
+ ### CAT-05-005: Virtual asset transfer information (Travel Rule)
299
+
300
+ - **Requirement:** Before carrying out a virtual asset transfer as ordering institution, obtain and record the originator's name; originator's account number with the institution (or unique reference number); originator's address, customer ID, identification-document number or (for an individual) date and place of birth (the latter optional below HKD 8,000); recipient's name; and recipient's account number with the beneficiary institution (or unique reference number); submit the required information to the beneficiary institution per published codes/guidelines; as beneficiary, obtain and record the submitted information; as intermediary, transmit all received information onward.
301
+ - **Source:** Schedule 2, §13A(2), §13A(3), §13A(4), §13A(5), §13A(6), Cap. 615
302
+ - **Severity:** critical
303
+ - **Verification:**
304
+ - [ ] VA transfer system captures the §13A(2) fields before execution
305
+ - [ ] HKD 8,000 threshold logic governs collection of originator address/ID
306
+ - [ ] Information submitted to beneficiary institution per applicable codes/guidelines
307
+ - [ ] Beneficiary and intermediary roles preserve the received information set
308
+ - **Evidence:**
309
+ - VA transfer record specification
310
+ - Sample submission to beneficiary institution
311
+ - Intermediary pass-through documentation
312
+
313
+ ### CAT-05-006: Missing-information handling for virtual asset transfers
314
+
315
+ - **Requirement:** As beneficiary or intermediary institution in a virtual asset transfer, if the instructing institution does not submit the §13A(2) information, obtain the missing information as soon as reasonably practicable; if it cannot be obtained, consider restricting or terminating the business relationship with the instructing institution or take reasonable ML/TF risk-mitigation measures; where accompanying information is incomplete or meaningless, take risk-mitigation measures.
316
+ - **Source:** Schedule 2, §13A(7), Cap. 615
317
+ - **Severity:** critical
318
+ - **Verification:**
319
+ - [ ] Beneficiary/intermediary procedure escalates missing-information cases
320
+ - [ ] Decision criteria documented for restricting or terminating instructing-institution relationships
321
+ - [ ] Risk-mitigation actions recorded for incomplete/meaningless cases
322
+ - **Evidence:**
323
+ - Missing-information case log
324
+ - Restriction/termination register
325
+ - Risk-mitigation action records
326
+
327
+ ## CAT-06: Correspondent Banking and Prohibited Relationships
328
+
329
+ ### CAT-06-001: Pre-establishment correspondent banking due diligence
330
+
331
+ - **Requirement:** Before establishing a correspondent banking relationship with an institution outside Hong Kong carrying on a business similar to an authorised institution, collect sufficient information to fully understand the proposed respondent's business; determine from publicly available information its reputation and the quality of supervision in its place; and assess its AML/CFT controls. The relationship must not be established unless senior-management approval has been obtained, the AML/CFT controls have been judged adequate and effective, respective responsibilities have been documented, and the institution is satisfied as to the respondent's CDD of customers who can directly operate payable-through accounts.
332
+ - **Source:** Schedule 2, §14(1), §14(2), Cap. 615
333
+ - **Severity:** critical
334
+ - **Verification:**
335
+ - [ ] Correspondent due-diligence file covers business, reputation, supervision, and AML/CFT controls
336
+ - [ ] Senior-management approval recorded before activation
337
+ - [ ] Responsibilities matrix signed by both institutions
338
+ - [ ] Direct-operator/payable-through arrangements assessed
339
+ - **Evidence:**
340
+ - Respondent due-diligence file
341
+ - Senior-management approval record
342
+ - Signed responsibilities matrix
343
+
344
+ ### CAT-06-002: Prohibition on anonymous or fictitious-name accounts
345
+
346
+ - **Requirement:** Do not open or maintain any anonymous account or account in a fictitious name for any customer.
347
+ - **Source:** Schedule 2, §16, Cap. 615
348
+ - **Severity:** critical
349
+ - **Verification:**
350
+ - [ ] System controls prevent account opening without an identified customer
351
+ - [ ] Periodic sweep confirms no anonymous/fictitious-name accounts remain
352
+ - **Evidence:**
353
+ - Account-opening control documentation
354
+ - Periodic account-population audit report
355
+
356
+ ### CAT-06-003: Prohibition on correspondent banking with shell banks
357
+
358
+ - **Requirement:** An authorised institution must not establish or continue a correspondent banking relationship with a corporation incorporated outside Hong Kong that is authorised to carry on banking business in that place but has no physical presence there and is not an affiliate of a corporation with a physical presence in that jurisdiction.
359
+ - **Source:** Schedule 2, §17(1), §17(2), §17(3), Cap. 615
360
+ - **Severity:** critical
361
+ - **Verification:**
362
+ - [ ] Onboarding due diligence confirms physical presence and qualifying affiliation per §17(2)–(3)
363
+ - [ ] Annual reconfirmation that existing respondent banks are not shell banks
364
+ - **Evidence:**
365
+ - Shell-bank screening procedure
366
+ - Annual recertification records
367
+
368
+ ## CAT-07: Intermediaries and Internal Procedures
369
+
370
+ ### CAT-07-001: Use of intermediaries for CDD
371
+
372
+ - **Requirement:** Where CDD is carried out by an intermediary specified in §18(3), the intermediary must consent in writing to act, must be a permitted category (HK accounting/estate-agent/legal professional, TCSP licensee, certain FIs, equivalent-jurisdiction professionals/institutions meeting the §18(3)(c) tests, or a qualifying related foreign FI under §18(3)(d) and (3A)); the institution must immediately obtain the data/information collected and ensure the intermediary will supply copies of documents on request within the §20 retention period; in §18(3)(d) cases, take reasonable risk-mitigation measures. The institution remains liable for any CDD failure by the intermediary or any agent it uses.
373
+ - **Source:** Schedule 2, §18(1)–(7), Cap. 615
374
+ - **Severity:** major
375
+ - **Verification:**
376
+ - [ ] Written consent on file for each intermediary
377
+ - [ ] Intermediary category and qualifying basis documented (incl. group policy and supervision tests for §18(3)(d))
378
+ - [ ] Process to obtain underlying documents on request within the retention period
379
+ - [ ] Liability allocation acknowledged in internal policy
380
+ - **Evidence:**
381
+ - Intermediary register with categories
382
+ - Signed intermediary consent letters
383
+ - Document-request workflow documentation
384
+
385
+ ### CAT-07-002: Procedures for PEP detection and wire/VA transfer screening
386
+
387
+ - **Requirement:** Establish and maintain effective procedures for: (a) determining whether a customer or beneficial owner is a politically exposed person; (b) for FIs carrying out wire transfers, identifying and handling wire transfers where §12(5) has not been complied with; (c) for FIs carrying out virtual asset transfers, identifying and handling VA transfers where §13A(4) has not been complied with; and (d) for each kind of customer, relationship, product, and transaction, procedures (consistent with the Ordinance) for carrying out duties under §§3, 4, 5, 9, 10 and 15 of Schedule 2.
388
+ - **Source:** Schedule 2, §19(1), §19(2), §19(2A), §19(3), Cap. 615
389
+ - **Severity:** critical
390
+ - **Verification:**
391
+ - [ ] Documented PEP-detection procedure (lists, screening cadence, escalation)
392
+ - [ ] Wire transfer non-compliance handling procedure in place where applicable
393
+ - [ ] VA transfer non-compliance handling procedure in place where applicable
394
+ - [ ] CDD procedures cover each customer/relationship/product/transaction type
395
+ - **Evidence:**
396
+ - PEP-detection procedure document
397
+ - Non-compliant wire/VA transfer handling procedure
398
+ - Product-specific CDD procedure set
399
+
400
+ ## CAT-08: Record-keeping
401
+
402
+ ### CAT-08-001: Records of transactions and customers
403
+
404
+ - **Requirement:** Keep the original or a copy of documents and a record of data and information obtained in connection with each transaction carried out, and for each customer keep the original or a copy of identification and beneficial-owner verification documents/data, account files, and business correspondence with the customer and any beneficial owner.
405
+ - **Source:** Schedule 2, §20(1), Cap. 615
406
+ - **Severity:** critical
407
+ - **Verification:**
408
+ - [ ] Transaction-record set captures source documents, data, and information per Part 2
409
+ - [ ] Customer file holds identification/verification records, account files, and correspondence
410
+ - **Evidence:**
411
+ - Records inventory
412
+ - Sample customer file showing required record classes
413
+
414
+ ### CAT-08-002: Minimum retention periods
415
+
416
+ - **Requirement:** Keep transaction records for at least 5 years from the date the transaction is completed, regardless of whether the business relationship ends during that period; keep customer records throughout the relationship and for at least 5 years after it ends; for triggering occasional transactions (§3(1)(b), (1A), (1B)), keep customer records for at least 5 years from completion. Where a relevant authority or regulatory body specifies a longer period by notice, keep the relevant records for that longer period.
417
+ - **Source:** Schedule 2, §20(2), §20(3), §20(3A), §20(4), §20(5), Cap. 615
418
+ - **Severity:** critical
419
+ - **Verification:**
420
+ - [ ] Retention schedule encodes 5-year minimums for transaction and customer records
421
+ - [ ] Process exists to extend retention on receipt of a §20(4) notice
422
+ - [ ] Disposal controls prevent early deletion
423
+ - **Evidence:**
424
+ - Records-retention schedule
425
+ - Authority-notice register
426
+ - Disposal control documentation
427
+
428
+ ### CAT-08-003: Manner of keeping records
429
+
430
+ - **Requirement:** Keep document records as the original document, on microfilm, or in a computer database; keep data or information records on microfilm or in a computer database.
431
+ - **Source:** Schedule 2, §21, Cap. 615
432
+ - **Severity:** minor
433
+ - **Verification:**
434
+ - [ ] Approved storage media (original, microfilm, or database) documented
435
+ - [ ] System controls ensure integrity and retrievability of stored records
436
+ - **Evidence:**
437
+ - Records-management policy
438
+ - Storage-media specification
439
+
440
+ ## CAT-09: Group-wide Application and General Safeguards
441
+
442
+ ### CAT-09-001: Branches and subsidiaries outside Hong Kong
443
+
444
+ - **Requirement:** An FI or DNFBP incorporated in Hong Kong or that is a re-domiciled entity must ensure its overseas branches and same-business overseas subsidiary undertakings have procedures to ensure compliance, to the extent permitted by local law, with requirements similar to Parts 2 and 3 of Schedule 2 that apply to the FI or DNFBP. Where local law does not permit such application, inform the relevant authority (and, where applicable, the relevant regulatory body) and take additional measures to mitigate the resulting ML/TF risk.
445
+ - **Source:** Schedule 2, §22(1), §22(2), §22(2A), §22(2B), Cap. 615
446
+ - **Severity:** major
447
+ - **Verification:**
448
+ - [ ] Group AML/CFT policy applies equivalent Parts 2 and 3 requirements to overseas branches and same-business subsidiaries
449
+ - [ ] Conflicts-of-law review identifies jurisdictions where requirements cannot be applied
450
+ - [ ] Notifications to relevant authority/regulatory body on file for restricted jurisdictions
451
+ - [ ] Additional mitigation measures documented for those jurisdictions
452
+ - **Evidence:**
453
+ - Group AML/CFT policy
454
+ - Conflicts-of-law inventory
455
+ - Authority/regulator notifications
456
+
457
+ ### CAT-09-002: Reasonable measures to prevent contravention
458
+
459
+ - **Requirement:** Take all reasonable measures to ensure that proper safeguards exist to prevent a contravention of any requirement under Part 2 or Part 3 of Schedule 2, and to mitigate ML/TF risks.
460
+ - **Source:** Schedule 2, §23, Cap. 615
461
+ - **Severity:** major
462
+ - **Verification:**
463
+ - [ ] AML/CFT control framework documented with named owners
464
+ - [ ] Independent assurance (internal audit, compliance testing) reviews Part 2/3 controls on a defined cycle
465
+ - [ ] Training programme covers staff in AML/CFT roles
466
+ - **Evidence:**
467
+ - AML/CFT control framework
468
+ - Internal audit reports on Part 2/3 controls
469
+ - Training records