feat(aml): add API endpoints and services for manual journal entry referrals

2026-08-03 10:49:37 +05:30
parent c890faee78
commit 7773a9e9c6
9 changed files with 423 additions and 0 deletions
@@ -495,4 +495,5 @@
    <include file="parts/0440_seed_aml_test_alerts.xml" relativeToChangelogFile="true"/>
    <include file="parts/0441_add_aml_rule_limit_bands.xml" relativeToChangelogFile="true"/>
    <include file="parts/0442_seed_branch_offices.xml" relativeToChangelogFile="true"/>
+    <include file="parts/0443_seed_aml_manual_referral_rule.xml" relativeToChangelogFile="true"/>
 </databaseChangeLog>
@@ -0,0 +1,45 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements. See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership. The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License. You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied. See the License for the
+    specific language governing permissions and limitations
+    under the License.
+
+-->
+<databaseChangeLog xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
+                   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+                   xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.13.xsd">
+
+    <!--
+        m_aml_alert.rule_id is NOT NULL, so an alert a user raises by hand from the ledger still
+        needs a rule to hang off. MANUAL_REFERRAL is that rule.
+
+        It is seeded with is_active = false ON PURPOSE. AmlRuleEvaluationServiceImpl selects
+        candidates with findByActiveTrueAndAppliesTo, so an active ALL-scoped rule with a null
+        threshold would be evaluated against every live transaction. Inactive keeps it out of the
+        engine entirely; the referral service loads it by rule_code instead.
+    -->
+    <changeSet author="fineract" id="0443-1">
+        <preConditions onFail="MARK_RAN">
+            <sqlCheck expectedResult="0">SELECT COUNT(*) FROM m_aml_transaction_rule WHERE rule_code = 'MANUAL_REFERRAL'</sqlCheck>
+        </preConditions>
+        <sql>
+            INSERT INTO m_aml_transaction_rule (rule_code, description, applies_to, threshold_amount, rule_type, window_days, source_client_risk_rule_id, is_active)
+            VALUES ('MANUAL_REFERRAL', 'Marked suspicious by a user from the general ledger - no automated rule fired', 'ALL', null, 'THRESHOLD', null, null, false);
+        </sql>
+    </changeSet>
+
+</databaseChangeLog>