Severa–Procountor

Error message / Code	Description	Proposed solution
API Timeout / 500 Internal Error	Technical disruption or timeout in data transfer.	Wait a moment and try the transfer again. If the error persists, check that the invoice does not contain very long row texts or exceptional special characters.
CLOSED_FISCAL_PERIOD	An attempt is made to transfer the invoice in Procountor to a fiscal year or tracking period that is already closed.	Check the invoice date and date of entry (found in the invoice Detailed information section) in Severa. Make sure that the month/period in question is open in Procountor or change the invoice date to an open period.
Could not add sales invoice 'xxxx' to Procountor Value of the 'deliveryAddress.country' cannot be blank.	The invoiced customer’s customer data is incomplete. The country information is missing in Severa.	Check that all required address information for the invoiced customer is correctly filled in Severa: street address, postal code, city and country. Make sure that the Postal address checkbox is selected for the address so that the customer data is transferred correctly with the sales invoice to Procountor.
Could not add X to Procountor, because another partner X with the same number and different VAT number already exists there.	The customer cannot be transferred if Procountor already contains a customer with the same name and the same customer number but a different vat number.	Check the vat number formatting and correct the data so that it matches between the systems.
Dimension mismatch	The Severa dimension (e.g. Cost center or Project) does not match the Procountor settings.	Make sure that the dimension name in Severa’s integration settings is written exactly the same as it is defined in Procountor tracking objects.
ERROR_BRN_CODE	The customer’s Vat number is in an invalid format or missing.	Correct the Vat number on the Severa customer card to the correct format (e.g. 1234567-8). Make sure there are no extra spaces in the number. Ensure that the vat number is in the same format in both Severa and Procountor.
HTTP 401 Unauthorized	The integration connection key (API key) is expired or invalid.	Search a new API key in Procountor and update it to Severa integration settings (Settings > Integrations > Procountor).
HTTP 403 Forbidden	The Procountor user whose key is used for the integration does not have sufficient rights.	Make sure that the integration user has at least edit rights in Procountor for invoicing, travel and expense invoices, and registers.
INVALID_DATA / INVALID_VAT_CODE	The invoice data contains invalid information or information that conflicts with Procountor rules (often a VAT code or tax rate).	Check that the VAT percentage used in Severa is also enabled in Procountor. Also verify the customer’s country information and tax handling (e.g. EU sales vs. domestic).
Invoice number does not match	The Severa invoice number is different from the Procountor invoice number.	This is an integration feature: Procountor always assigns its own running number to the invoice. The Severa initial invoice number can be found in Procountor in the Initial invoice number field.
Missing or invalid iban	Transferring Travel reimbursement requires a valid bank account number.	Add the user’s bank account number in IBAN format to Severa user settings.
Missing employee number	The transfer of Travel reimbursement fails because the person cannot be matched.	Check that an employee number is defined in Severa user settings and that it matches exactly the Procountor employee number.
SIZE_MUST_BE_BETWEEN_0_AND_100	The invoice contains rows where the maximum number of characters has been exceeded.	Check the field-specific limits and correct the data on the invoice.

Did you find it helpful? Yes No

Send feedback