Corporate Banking Enterprise and Automation systems need to designed with Deep And Differentiated Separation of Concern (DaD-SOC) Design Pattern. To achieve real DaD implementations, Patterns team has used following tenets in enterprise and hyper automation software design and development:
1. Comprehensive Customer Information Model Design with NTC (Narrow the Core) Hyper Automation: a customer information model that supports continuous evolvement with support for structured and unstructured data. All customer registry and account related operations including customer registry maintenance and updates, account opening, account maintenance, KYC, Trade / Commercial License Renewals, Risk Grading, etc automated using Hyper Automation.
2. Customer Facilities with Centralized Limits and Structured Covenants – Digital Customer Sanctions and Agreements: Sanction and agreement covenants to be maintained as human and machine-readable rules organized by transaction group for pre-transaction instant human and process referral and compliance. To be maintained using SOPs automated using hyper automation
3. Centralized Customer Preferences, Special Pricing, arrangements: Customer preferences, special prices and customer arrangements not supported by core and enterprise systems to be maintained using NTC Hyper Automation.
4. Real Time Risk Grading of Transactions and Services: Pre-Transaction Risk analysis to be done using knowledge of customer financial and non-financial behaviour patterns and bank’s risk policy configuration using a real time transaction monitoring risk grading bot worker.
5. Multi Laning: Design to support multiple concurrent transactions to an account, limit utilization balances, exposure balances, etc. Multi Laning can be implemented using Quantum Locks, Aspect Oriented Locks, Combination Proxy Locks and Long Running Pickup Locks.
6. Bulk Transaction Processing: Implementation of a bulk transaction processing design pattern which classifies the entries in bulk processing as funding debits, credits and dependent debits and then implements a logically nested transaction where the child transaction does not lock and hold accounts, but credits posted can be locked till the entire bulk transaction is committed.
7. Self-Capacity Monitoring with Look Ahead Processing, Deferred Processing and Run Time Reuse Processing: Corporate Banking system need to monitor current system load and available capacity and then use this information to push more transactions using the Look Ahead Processing (LAP) Design Pattern or use the Deferred Processing Design Pattern if system load has crossed the threshold levels. In addition to these two, corporate banking system must implement a Run Time Re-Use (RTRU) Design Pattern to prevent wasteful re-execution of validation logic when underlying data has not changed.
8. Comprehensive Statement Capabilities – Financial, Non-Financial, Exceptions and Long Term: Corporate Banking systems must be able to provide financial statements with breakdown of entries for consolidated posting entries, display of connected documents / customer request letters / cheque images for a transaction with support for statements for 10 years or more. Systems should provide non-financial statements detailing all non-financial operations on an account like KYC Falling Due, KYC renewed, Signatory Deleted, Signatory Added, Mandate Rules Changed / Superseded, Director Added, Director Removed, Board Superseded, Risk Grading Done, Cheque Book Issued etc. A statement of exceptions must be available for internal use by the management providing TODs, EOLs, Cheque Returns, Minimum Balance Not Maintained, Cheque Returned, etc.
9. 100% Digital Operations (Fully Document Aware Operations) : All documents from customers must be received digitally, processed digitally, communicated digitally and stored in the Bank’s DMS with image plus document classification, expiry date (if applicable) searchable / indexed extracted electronic data. Automated Extraction of data from Customer Financial Statements Stock Statements, Turnover / Sales Statements and Bank Statements must be supported.
10. Automated Liquidity Management with Fund Transfer Capabilities: Corporate Banking system must provide very comprehensive look at the corporate balances (liabilities and asset) and provide efficient and comprehensive fund transfers between account at EOD, EOW, EOM, EOQ, EOH and EOY.
