Accounting integration errors, statuses and safe retries
How to distinguish pending data from an error, what to check before a retry and what to send Hanna support.
First distinguish three results
- A record saved in Hanna may be transferred to the accounting program later.
- Transfer has started or is pending processing. It may run in a queue, periodically or from a file.
- The other system accepted the record. If a status-return flow exists, its result may appear later.
Checks by symptom
| What you see | What to check |
|---|---|
| Only one data type is missing | Check that type’s activation, direction, organisation, start date and status filter. |
| Customer or product not found | Check the external code and matching. An identical name does not necessarily identify the same record. |
| Document is rejected | Compare VAT, currency, units, accounting accounts/journals, warehouse and required fields. |
| Payment is missing | Check the linked document first. For RoboLabs check the bank/cash journal; for AGNUM check pending invoice files. |
| Invoice cannot be edited | Check origin, payment and posting status. Rivilė ERP posted documents are protected in Hanna; RoboLabs imported or paid invoices may also be locked. |
| Not every field updates | Check overwrite protection and whether the flow returns a full document or only a status. BSS API statuses are not a full document import. |
| A whole batch is delayed | Check service availability, request limits and agreed processing. Do not start several imports of the same batch at once. |
| Old data remains after editing | Check whether the connector supports updates to an existing document rather than only creation. |
Safe retries
- Record the failed attempt’s time and record number. Check both systems: a request error or timeout does not prove that the destination created nothing.
- Resolve the specific cause: matching, missing field, status condition or expired access.
- If the record already exists at the destination, restore or check the link first. Do not erase its code or create another record just to force export.
- Retry only the failed record or an agreed small batch. Check that no second document or payment was created.
Before correcting or deleting a payment, cancelled document or posted document, check the workflow for your integration.
What to send Hanna support
- Connector name and variant (for example, Rivilė or Rivilė ERP), organisation, data type and direction.
- Attempt time, Hanna record number, external identifier if visible and the error text with secrets removed.
- Expected and actual results in both systems, and whether the record was transferred before.