Deploying a global origination system poses both compelling advantages and significant challenges. There’s clear appeal to delivering universal core functionality, but regional differences must be accommodated. As you may expect, successful implementation requires collaboration. Working together, the central organization, regional offices and a systems partner must start with a core system that is later adapted for localized needs. The benefits include operational consistency, standard enforcement, and simplified maintenance, outweighing the ease of deploying country-specific systems which can be less efficient and more costly in the long run.

The key to a successful global system lies in its flexibility, the willingness to invest in development, and a methodology for identifying core versus localized functionalities. While operational needs take priority over technical ones during the system's development, defining these core requirements requires input from both corporate and local entities. The goal: provide enterprise-wide benefits -- such as consistent operations, standardization and centralization of processes -- within a core system that requires minimal adjustments for regional needs.

Developing and deploying such a system is a large-scale change management project, calling for thorough planning, stakeholder buy-in, and recognition of cultural differences. To oversee it, a steering committee and user group, including representatives from the regions where the system will be deployed, would ensure that core functionalities meet common needs and allow for local customizations.

Typical Core Functionality Typical Local Functionality
Workflow Language
Security templates and functions Currency
User entry process Pricing configuration
Lease types Lease documents
Most, if not all, business standards and rules Accounting and tax implications
Automatic notification options Local web services
Pricing options Country-specific field displays
Internal documents  
Credit decision engine  
Some web services, e.g. external security checks and address validation  
Form template configurations  
Equipment catalogues  
General system build  

Table 1: Identification of core and local functions

Identification of core and local functions

Core vs Local

Core functionalities can typically represent up to 90% of the system's operations (dependent upon the organization’s commitment to consistency), with the remainder tailored during localization to meet specific regional requirements.

For the core system: Development and implementation involves setting clear objectives, assembling a cross-regional team, securing initial approvals, defining project phases, evaluating user needs, documenting core functionalities, and undergoing thorough review and testing phases to ensure the system meets both global and local needs effectively.

For the local system: Implementation follows a structured approach, starting with a project initiation meeting and proceeding through local requirement definitions, documentation of requested changes, feasibility reviews, system configuration, and user acceptance testing, culminating in the system going live.

This meticulous approach ensures that the global origination system not only meets organizational goals but also addresses local concerns, ultimately enhancing efficiency, controlling costs and providing a strategic boost to operations. Best of all, when development includes systemwide cooperation and partnership, all stakeholders benefit.

Please contact Tamarack’s Professional Services team for assistance with any of these situations.

Written by

Theresa Eichten

Senior Consultant

In her role as a senior consultant on Tamarack’s professional services team, Theresa Eichten guides the successful implementation of client projects with global experience in the US, EMEA and APAC markets. Extensive experience with financial software products within the leasing and equipment finance industry.


« Back
Get Started
  • Should be Empty: