Enterprise Banking CRM
In corporate banking the customer is not a single person but a group of companies; two different relationship managers talk separately to two companies in the same group. When the limit allocation ends and which collateral document is still missing, on the other hand, is information that is left to the renewal week.
A company is an account record; its subsidiaries hang on the same tree, and limit allocation end and collateral type are its fields. Renewals coming due fall into a list from the date field.
- Tie the parent company and its subsidiaries in a parent-child account relationship and see the group's total relationship with the bank in a single list
- Keep limit allocation end and collateral renewal dates as fields and tie renewals coming due to a task
- Write the company visit, the person met and the product discussed into the visit record; let the history stay with the organisation when a portfolio is handed over
- Mark products such as cash management, foreign trade and payroll in an account field and open a contact task for companies missing a product
| Group and Subsidiary Structure | A company is an account record; the parent company and its subsidiaries are tied together in a parent-child account relationship, and the group total is read from the report on that tree. |
|---|---|
| Relationship Manager Assignment | The owner of the account is a field; the assignment rule defined during setup drops a new company to the relevant manager by segment and region, and on handover the field changes while the history stays. |
| Limit and Collateral Calendar | The allocation end and the collateral type are fields on the account; dates coming due fall into a list, and missing documents are tracked as a request record. |
| Product Ownership and Visit Record | The products owned are a field on the account; a company visit is a task, and the person met and the product discussed are written into the same record. |
A relationship with a corporate company does not consist of a single meeting: cash management is discussed with the treasury manager, foreign trade transactions with the export officer and payroll with human resources. While these meetings sit in the diaries of different relationship managers, what the company's total relationship with the bank amounts to is only pieced together at the year-end review. And when a portfolio changes hands, what is handed over is a customer list; the history itself — which proposal was rejected and why — leaves with the person who leaves.
In Rapitek CRM the company is an account record and its subsidiaries are tied under the same tree; product ownership, the limit allocation end and the collateral status sit in the fields of that record. Renewals coming due fall into a list from the date field, and visit and meeting notes accumulate under the account; when ownership changes, only the field changes and the history stays with the organisation. We build the connection on the core banking and accounting side ourselves; there is no out-of-the-box module, the connection is set up specifically for the project over REST API, OAuth2 and webhooks.
The scope of the plans and the separately priced items are written on the pricing page.
