ERP Integration
ERP integration consists of two parts:
Reading from ERP
Writing into ERP
(Data synchronization)
Each part can be implemented in numerous ways, and it is possible to combine different reading and writing methods according to your requirements.
Please note that the list of ERP systems given below is not exhaustive. In case your ERP is not yet supported by CashManager, we will help you choose the best integration model that fits your ERP system and your requirements.
Most often one of the following six integration models is used.
(a) Read: SQL; Write: import/export files
ERP systems
Epicor iScala (Scala), Microsoft Dynamics NAV (Navision), Ting Hsin (鼎新), etc.
Reading from ERP
The necessary data from the ERP system is read via SQL. For an even better security, your system administrator can white–list SQL tables for the CashManager’s SQL user according to the list that we will provide to you.
Writing into ERP
The data is synchronized using the import/export procedures available in your ERP system. The file format generated by CashManager depends on the ERP system and on the settings set in CashManager according to the user environment.
(b) Read: SQL; Write: API calls
ERP systems
Microsoft Dynamics AX (Axapta), SAP Business One, Visma
Horizon (Apvārsnis), etc.
Reading from ERP
The necessary data from the ERP system is read via SQL. For an even better security, your system administrator can white–list SQL tables for the CashManager’s SQL user according to the list that we will provide to you.
Writing into ERP
The data is synchronized using the API procedures available in your ERP system according to the settings set in CashManager.
(c) Read: API calls; Write: API calls
ERP systems
Microsoft Dynamics AX (Axapta), SAP Business One, Visma Horizon (Apvārsnis), etc.
Reading from ERP
The necessary data from the ERP system is read using the API available in your ERP system. Please note that API reading is usually slower than SQL reading. In case data loading speed is crucial to you, we recommend to use the integration model (b) instead.
Writing into ERP
The data is synchronized using the API procedures available in your ERP system according to the settings set in CashManager.
(d) Read: SQL; Write: SQL
ERP systems
Custom–made ERP systems, old ERP systems, small and local ERP systems, for which other integration methods are not possible or have serious limitations.
Reading from ERP
The necessary data from the ERP system is read via SQL. For an even better security, your system administrator can white–list SQL tables for the CashManager’s SQL user according to the list that we will provide to you.
Writing into ERP
The data is synchronized using direct SQL writing into your ERP database. Please note that we generally do not recommend this method if other writing methods are available for your ERP system.
(e) Read: import-export files; Write: import-export files
ERP systems
ERP systems with a proprietary database, such as HansaWorld (Hansa Financials) or 1C.
Reading from ERP
The necessary data is read via import/export files generated by your ERP system. Please note that additional programming might be needed for your ERP system in this case.
Writing into ERP
The data is synchronized using the import/export procedures available in your ERP system. The file format generated by CashManager depends on the ERP system and on the settings set in CashManager according to the user environment.
(f) No integration (External file update)
In this case, CashManager reads and updates external Excel or Calc files. This method is also used for businesses that do not have an ERP system on premises, but would like to use CashManager for better debit and credit control and faster cash management.
Something not entirely clear? Please visit the FAQ section or contact us for more information.