Connecting an accounting integration and matching existing records
Safe initial setup: data ownership, directions, matching existing records and a test transfer.
1. Confirm the connector and scope
Choose the software from the integration overview. Rivilė and Rivilė ERP are different integrations. Agree the connector and data to transfer with the Hanna team.
2. Agree which system owns each data type
Agree where customers, products and documents will be created and edited, the transfer start date and their organisation. Choose which fields will be updated in the other system.
| Area | What to agree |
|---|---|
| Customers and products | External identifiers, customer/product codes, existing duplicates and fields allowed to update. |
| Accounting settings | VAT mappings, currencies, units, numbering and, where used by the connector, journals and accounting accounts. |
| Organisations and warehouses | Which company owns the records; which warehouses and document types are exchanged. |
| Document lifecycle | When creation occurs, what updates, how a posted invoice is corrected and what cancellation or deletion means. |
3. Connect securely
Provide connection details only through the secure method specified by Hanna support. Do not copy passwords, API keys or complete credential-bearing URLs into an ordinary support email. Verify that access targets the correct company and permits the agreed operations.
4. Match existing records before documents
- Review existing customers and products in both systems. Match them using the connector’s codes or external identifiers, not names alone.
- Match warehouses and accounting reference data. Do not rename or change external codes while an import is running.
- Then transfer documents. Payments first require recognised invoices or proformas.
5. Run a limited test
Check one record in each direction actually enabled. Compare customer, lines, amounts, VAT, currency, warehouse, number and status. Test a later change separately if supported. Retry only after checking the previous attempt’s result; it must not create a duplicate.
Customer notifications. Before the initial payment import, review automatic payment emails and other related notifications. For example, RoboLabs payment import can trigger an invoice-payment email if sending is enabled.
6. Agree day-to-day monitoring
Agree how often each data type will update and who will monitor errors. Transfers may take longer when jobs are queued or the accounting program limits requests. Also agree how to pause a particular import or export when needed.