Accounting software error messages

Below is a list of errors received in the Hanna system from accounting programs and their solutions:

• Rivile system error messages
• Pragma system error messages

Rivile system error messages

1. No client code specified- for a contact whose invoice is issued, the Rivilė code is not indicated on the contact card:

To enter the Code in Rivile on the contact card, create an excel document and specify the company code and the Rivile code:

Select import contacts and upload the prepared file. Link the boxes, check the boxUpdate existing contactsand select Import:

2. Department code not entered- after choosing System settings - Employees - select the employee who is the seller of the account and indicate to himDepartment code:

3. You need to choose a buyer client- the type of contact displayed by the error message must be specified in the contact card. If the contact is created in the Hanna system, then the changes must be made in the Hanna system, if the contact is created in the Rivile system, then the changes must be made in the Rivile system.

4. No such record / Such transaction code not found- the error is received when the account is deleted from the Rivile system, then there are no more links between the generated account.

5. Product/service code not found- the system displays an error when the product is manually entered into the generated invoice. When generating invoices in the system, goods should be added from the Items module. 

6. Current balances will become negative- an error is displayed in the system when there is no product balance. If the product balance is positive in the Hanna system, then this product balance is no longer available in the Rivilė system.

7. No unit of measure found- an error is returned when the unit of measurement is not found in the system. It should be noted that when specifying units of measurement, it is very important to take into account upper and lower case letters. If you receive this error, you should check the units of measurement entered in the Rivile system with those entered in Hanna.

8. Product code not found - the error message informs that the product code is not specified, in this case the invoice must be checked for all product codes, they must match those in the Rivilė system, taking into account lowercase and uppercase letters.

9. This document number already exists — a document with that number is already present in accounting. Compare the organization, document, and integration mapping. Before retrying, establish with the accountant and integration administrator whether an update, mapping correction, or another supported action is needed. Do not delete the Invoice merely because of this message.

10. Unavailable period - informs that the period specified in the invoice belongs to the period for which it is no longer possible to create/edit invoices. This period is locked in the Rivile system.

11. The tax code has expired- an error on the part of Rivile is returned, in this case you should contact the representatives of Rivile.

12. There is no such sales manager- an error message is displayed when the customer's assignee does not have the specified Rivilė code on the employee's card.

13. The following customer code exists — check that the customer already present in Rivile is the same customer and that its Rivile code is correctly mapped in Hanna. Deleting an existing customer is not a routine mapping fix. Agree the next action with the accountant and integration administrator.

14. The selling price is out of range — compare the Item price with the limits configured in Rivile. Do not disable price controls merely to make an export succeed. A price or control-rule change must be approved by the person responsible for pricing and accounting.

15. Manager selection is prohibited in this module!- In the Rivile system, the manager's card should be adjusted and a check mark should be placedSales:

16. The product/service code has expired- there is a mark on the product card in RivileTimedand specified due dates.

17. There is no such client- the error informs that the client has been deleted in the Rivile system or such a client with the specified Rivile code does not exist in the Rivile system.

1. A document with this document ID already exists (Pirkwazid=*****)- the system informs that such a document with such a document ID already exists in the Pragma database. Such a situation occurs when a document is not transferred for the first time and since such a record already exists in Pragma, then the web service no longer accepts it. The PurkVazID specified in the message is the record ID of the Pragma system document - it confirms that such a document already exists.

If Pragma reports that a document already exists, compare its ID and contents with the Hanna document first. Repeated creation may be rejected; the available update or correction path depends on the integration in use. Agree any deletion or recreation with the accountant and integration administrator before acting.

2. ERROR: The product is not in the product list- the generated sales document contains an item that no longer exists in the Hanna or Pragma system.

When is it safe to retry sending to accounting software?

First determine whether the error means invalid data, an existing document, or an uncertain transfer outcome.

1. Preserve the exact error and compare the document number and organization in both systems. If the document already exists in accounting, deleting it is not an automatic error fix.
2. For a customer, seller, Item, or subdivision code error, check that specific object and its mapping. A similar name does not prove that the codes match.
3. If the transfer is still running or the document is locked for integration processing, do not send several retries. When the outcome is uncertain, check the accounting system before retrying.
4. Retry one corrected document using the actions supported by your integration and check its result. Integration direction, creation, and updates of existing documents may differ.

Agree document or customer deletion and changes to accounting controls with the responsible accountant and integration administrator first. If the issue remains, provide the document link, integration, attempt time, and exact error; do not send passwords.