Managing NAV Connection and Error Handling

Interrupted NAV Connection

An interrupted NAV connection can occur due to various reasons, such as:

• Changes to the VAT number or other company details
• Updates to the technical user account

When the connection is restored and the user saves the updated connection details, the system will check the provider’s invoices for the current year. This ensures any invoices created during the inactive connection period are identified and processed.

 A cron job will process the NavQueue list and specifically look for:

• Invoices with status = unsuccessful,
• AttemptNr = 3, and
• InvoiceStatus = NULL.

If any invoices meet these criteria, the cron job will reset the AttemptNr parameter to 2. This allows the system to retry sending them to NAV during the next check.

Unsuccessful Invoice Submission – NAV Warning Messages

When an invoice submission to NAV fails, the system may generate one of the following warning messages, depending on the issue:

• INVALID_VAT_DATA: The tax percentage applied to the invoice is incorrect.
• INVALID_SECURITY_USER: The authentication data provided is incorrect.
• SCHEMA_VIOLATION: An error occurred during the invoice validation process.
• WRONG_TAX_NUMBER: The tax number on the invoice is incorrect.
• INVALID_USER_RELATION: The username either belongs to another company or the user information provided is incorrect.
• INVALID_REQUEST_SIGNATURE: The request signature is invalid.
• NOT_REGISTERED_CUSTOMER: The taxpayer specified in the request is not registered.
• INVALID_CUSTOMER: The taxpayer specified in the request is invalid.