Rivilė ERP integration: data and document protection

Rivilė ERP is a separate connector from Rivilė. It covers customers, products, invoices, credit notes, payments and selected stock operations. A document’s origin and posting status determine what can be changed in Hanna.

When setting up the integration, we’ll agree which data to transfer and in which direction.

Data and transfer directions

Data Hanna → Rivilė ERP Rivilė ERP → Hanna Conditions and meaning
Clients and products Yes Yes Directions are enabled separately; initial matching is required for documents.
Sales invoices Yes Yes Importing a Hanna-origin document does not overwrite its entire contents.
Credit notes Yes Yes Document origin and posting protection apply.
Payments Yes Yes Correct document and organisation links are required.
Stock balances — Yes Balances use a separate import flow.
Stock transfers and write-offs Yes — Enabled separately after warehouse and operation mapping.
Proforma invoices — — Proforma invoices can be transferred through the Rivilė connector.

Before launch

  1. Agree Rivilė ERP access, organisation and each data type’s direction.
  2. Match customers and products, then test an invoice, credit note and payment in the enabled directions.
  3. Before starting, agree where documents are posted and how corrections will be handled.

Limitations and document changes

  • Invoices and credit notes posted in Rivilė ERP are read-only in Hanna. Editing shows a warning; the document can still be copied.
  • Importing a document created in Hanna leaves its lines and contents unchanged.
  • Cancellation, unposting and deletion are separate actions. After deleting a document in one system, check its status in the other.

If data is not transferred

  • If a document cannot be edited, first check its posting status in Rivilė ERP. Do not create a replacement duplicate just to bypass protection.
  • If balances differ, check the selected warehouse and the separate balance import result.

Related guides

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.