Small Business Network: Onboarding Process
Allianz adopts Luther's platform for Deep Process Automation at scale to automate the complex and critical onboarding process for their Safe Trade SME Network.

1. Executive Summary
Allianz Trade (AT), formerly Euler Hermes, a subsidiary of Allianz, is an international financial services enterprise offering a range of corporate financial services, monitoring the financial health of 80 million of these companies internationally. AT has access to information and internal credit ratings for 2,500,000 German SMEs. AT wanted to develop an “SME Connectivity Platform and Safe Trade Network” to realize the huge potential of this wider SME network. A key component of this SME network will be the company onboarding process, which will be used to integrate SMEs into the Safe Trade Network. Companies will need to be identified from AT’s database, invited to the network via a company representative, who must have their identity verified. Then the company identity is verified for regulatory and compliance reasons.

However, the process operates across siloed and separate participants, who change their operations as functions and technology change. Consequently, other teams are operating on constantly changing information, resulting in disjointed, inconsistent end-to-end operations which lead to delays and errors. Disjointed process operations require monitoring and reconciliation to correct errors, increasing operating costs. Using Luther’s Deep Process Automation technology to streamline SME onboarding, AT was able to reduce the estimated cost of the process by 50%. The estimated onboarding process time was reduced from 13 hours to just 3.5 hours.

AT operates the SME onboarding process as part of the client acquisition & management value chain. This process operates across 4 teams & 10 software systems. To operate the process end-to-end, each system performs the same cycle of steps; i) send data & info to the System, ii) receive response from System, iii) compute & validate response, iv) share & store execution of step, v) evaluate & initiate next step. For reliable operations, all teams & systems involved should operate the same end-to-end Process. They often don’t! Enterprises attempt to i) set up local connectors between directly linked systems in the process, ii) Develop local operations scripts to manage the process. Both bespoke connectors and operations scripts require regular updates as teams, process operations, and systems evolve. These updates are reactive and localized, without fully considering the entire process. This leads to operational & technical challenges, which make process operations unreliable. The opportunity is providing a platform to reliably operate the end-to-end process, across all teams & systems involved.
These teams and participants are: the AT Onboarding Team, the AT Communications Team, the Company Representative, and the AT Verification Team. These systems are: Onboarding Portal UI, Oracle Database, Email (SMTP), ServiceNow, Docusign, IDNow, Typeform, Handelsregister API, and AT Financial Portal.

Traditional solutions to end-to-end process operations are unreliable & expensive. Enterprise Operations are generally function-first, meaning they continue to improve functions & their systems in isolation. Processes are considered secondary. The thinking is that if we have great functions & systems, the business can operate any process! Luther's platform is designed process-first, & primarily focuses on end-to-end processes.
Reliable end-to-end process operations include consistent operation, and great functions & systems. Traditionally enterprises use bespoke connectors & local operations scripts for process operations, which are fragmented, siloed, and change separately, and so are ineffective for reliable process operations. To remedy this, enterprises use automation tools. However they are ineffective at end-to-end process operations, due to their limited scope and scale, and stitching them together also doesn’t solve the problem.
Luther’s unique value for reliable end-to-end Process Operations is providing i) standard connectivity & ii) a common operations script, across all teams & software systems. Luther’s platform vertically integrates; i) distributed system technology ii) optimal resource allocation & management, iii) real time event ordering & streaming, iv) deterministic event processing & execution, for reliable end-to-end process operations. Luther’s platform does this by i) connecting systems to standard platform nodes, rather than to each other, and ii) teams & systems can change the common operations script but all teams & systems have to know & agree to the change, so all teams & systems involved operate the same end-to-end Process all the time!
To implement the platform; i) Luther’s team mapped the Process, ii) identified teams & software systems in the process, iii) allocated nodes (servers) to teams, iv) connected nodes to systems, v) set up the Platform on the nodes, vi) AT’s team along with Luther’s team developed the Common Operations Script (code) for Process Operations, vii) the process went Live. The process can now be completed in less than 4 hours and operational costs have been reduced by 50%.
Beyond the commercial results, this led to operational benefits in production, i) reliable operations across the end-to-end process & over time, ii) 5X smaller Ops teams, iii) real-time monitoring, iv) enforced compliance checks, v) real-time and consistent updates across all teams, vi) reduction of reconciliation. Also, technical benefits during development, i) standard dev. process so developers can focus on operations, ii) 5X smaller Dev teams, iii) standard process connectors, iv) automated infrastructure and connectors setup, v) real-time and consistent updates with the rest of operations. Ultimately, this leads to reliable end-to-end process operations!
2. The Process
SME Onboarding process
A key aspect of AT’s operations is Client Acquisition & Management. This value stream involves SME Onboarding among other processes.

For operational reliability, financial efficiency, regulatory reporting, and to avoid delays which adversely impact customer experience, each step of the onboarding process must be operated, documented, validated and completed effectively and consistently. To complete the onboarding process, AT works with company representatives.


The SME onboarding process has these steps: i) AT Onboarding Team retrieve the SMEs information from its database, ii) AT Onboarding Team creates a new record of this company as part of their trade network, iii) AT Communications Team contacts the company representative and requests they complete initial onboarding and provide identity verification documents, iv) The Company Representative completes initial onboarding for the company, v) The Company Representative provides their identity verification documents, vi) AT Verification Team verifies the Company Representative, vii) AT Verification Team request the company verification information, viii) The Company Representative provides company verification information, ix) AT Verification Team verify the company’s identity and financial information, and approve, x) AT Verification Team provides the company with full access to the financial services and SME network.
Process Operations
Different teams have different operations, rules and governance and they also utilize and operate a variety of software systems in different ways. Each system operates a specific function for the process. To operate the process end to end, each function performs the same cycle of steps: i) send data & information to the System, ii) receive response from the System, iii) compute & validate response, iv) share & store execution of step, v) evaluate & initiate next steps.


3. Opportunity

Enterprises are complex organizations operating many processes. Enterprises operate Processes across fragmented and siloed teams and software systems resulting in disjointed, inconsistent and inefficient end to end operations, leading to high costs, delays and errors.

Specifically, operating processes across fragmented and siloed teams and software systems affect process operations both technically during the development phase & operationally once they go live in production.

AT’s SME Onboarding process encompasses multiple participants, who are fragmented and siloed throughout the process. Due to the siloed nature of the participants, teams will often change their operations without the knowledge of other teams operating the process. This often requires monitoring and reconciliation by AT to correct errors and ensure the process functions correctly, increasing operational costs of the process. Delays impact onboarding for customers, which decreases customer retention. The siloed process also increases the risk of identity fraud and makes verification more difficult.
4. Traditional Solutions to end to end process operations are unreliable
Enterprises have great individual functions & teams & software systems. However, for efficient process operations, effective end-to-end operations are as important as effective functions & teams & systems.

To operate an end to end process enterprises traditionally set up projects, with i) dedicated large teams, & ii) infrastructure set up, to iii) develop application (end to end process) code, & iv) set up maintenance systems. This bespoke approach results in high operations cost & multiple technical & operational problems.

Bespoke connectors and local operations scripts & why they are unreliable
Traditional solutions for operating enterprise processes are inefficient. They have disjointed local operations that are modified and maintained by teams that own specific parts of the process. As the process changes and evolves, local operations are often modified without fully considering its impact on the rest of the end to end process operations. They also deploy local and non-standard connectors between teams directly interacting with each other in the process. For more details please visit the Full Case Study.
Automation tools & why stitching them together is unreliable

To attempt to remedy the inefficiencies of this approach, enterprises use automation tools such as RPA and workflow automation tools to operate the process. These tools are effective at operating local task and workflow operations, usually for 1-2 teams - but do not scale to end-to-end process operations across multiple teams and software systems. This approach does not solve the problems of operational friction, inefficiencies, delays and errors. For more details please visit the Full Case Study.
5. Solution
The Luther Platform was used to develop the Safe Trade network for AT, a network to connect SMEs with each other and AT’s financial services. As part of this, Luther automated the SME Onboarding process, standardizing data entry and document formats for ID verification and significantly reducing manual reconciliation and checks.. The platform provides standard connectivity across all teams & systems, and consistent common operations script. Now, onboarding can be completed 4 times faster, improving customer retention, reducing onboarding delays for customers, and making fraud detection easier.


Implementation
The automated SME onboarding process is a product built on the Luther platform using Deep Process Automation Technology to automate the process of onboarding SMEs to the new Safe Trade Network developed by Luther with AT. The implementation steps included:
- Discover Phase (2 weeks):
- Platform Set-up (1 day): Luther's team deployed the platform on all nodes.
- Common Operations Script for Process Operations (10 weeks): AT's development team, in collaboration with Luther, developed the application code to operate the end-to-end process.
- Go Live (Production)

How it all comes together reliably, with the Luther Platform
Luther’s platform reliably operates the end-to-end SME Onboarding process by providing standard connectivity and common operations scripts.


6. Results
Estimated Commercial Results

Operational and Technical Results
The Luther Platform streamlines operations across enterprise processes, reducing process time and cost while maintaining transparency and flexibility.

Luther Systems
What we do and why

Luther platform Links
Find more information about Luther’s Platform Core Features here.
For a more detailed introduction to the Luther platform please visit Luther Deep Process Automation Primer
For a detailed introduction and documentation examples please see the Luther Platform website.
For more information about Luther’s platform please visit Luther Systems website.