New Payhawk offices in Stockholm and Warsaw | Learn more

Error messages

Prev Next
How to resolve export failures to Exact Online, Oracle NetSuite, or Xero?
How to fix an invalid department issue when data cannot be exported to Oracle NetSuite?
How to resolve the issue of missing linked bank account configuration for supported ERPs when data export fails?
How to resolve the issue of a G/L account not being mapped to an expense when exporting data to Oracle NetSuite?
How to resolve the issue of enabling the variable exchange rate and variable currency options for the journal in Exact Online?
How to resolve the issue of missing employee when exporting data to Exact, Business Central, NetSuite, QuickBooks, and DATEV?
How to resolve the issue of the department not being provided?
How to resolve export issues caused by inactive employees or vendors in NetSuite.
This error occurs when the ERP system, such as Xero, Oracle NetSuite, or Exact Online, has rate limits on the number of API calls that can be made within a specific time period.
The export of an expense to Xero failed because the service date of the expense is before the period lock date set in your Xero organization.
The export of an expense to Xero failed due to a discrepancy in foreign exchange (FX) rates between Payhawk and Wise.
This error occurs when an attempt to export or update an expense from Payhawk fails because the corresponding document in Xero is already marked as paid or has a credit note applied to it.
This error occurs when Payhawk attempts to create a contact in Xero for an employee who needs to be reimbursed, but a contact with a similar name already exists.
This error occurs when Payhawk attempts to export an expense to Xero using a currency that is not enabled in your Xero organization.
This error occurs when the payment date and/or service period date of an expense in Payhawk falls before the Period Lock Date set in your Xero account.
This error occurs when the document date of the expense could not be validated against the pre-set date range in the integration service, which is five years in both directions (past and future).
This error occurs when the due date of the expense could not be validated against the pre-set date range in the integration service, which is five years in both directions (past and future).
This error indicates that the service or accounting period corresponding to the expense’s date has been closed in your integrated accounting system. Exports cannot be posted to a closed period.
This error occurs when one or more line items in the expense have an amount of 0 (zero). Expenses with line items that have zero amounts cannot be exported to your ERP integration.
This error occurs when one or more line items of the expense do not have a currency selected. All expense line items must have a defined currency to be exported to your ERP integration.
This error occurs when the total expense amount is 0 (zero). Payhawk cannot export expenses with a zero amount to your ERP integration.
Error message Please select expense currency. Affected ERP integrations DATEV Exact Online MS Business Central Microsoft Dynamics 365 Finance & Operations Oracle NetSuite QuickBooks Online Cause This error occurs when t...
Error message Sum of expense line items amount does not match expense amount. Affected ERP integrations DATEV Exact Online MS Business Central Microsoft Dynamics 365 Finance & Operations Oracle NetSuite QuickBooks Online ...
This error occurs when the document number exceeds the default maximum length of 20 characters allowed for export to Microsoft Dynamics 365 Finance & Operations.
This error occurs when the expense owner (employee) is not found as a vendor in Microsoft Dynamics 365 Finance & Operations. To successfully export employee expenses, the employee must exist as a vendor record in the ERP system.
This error occurs when the Advanced Bank Reconciliation feature is not enabled for the bank account specified in the Payhawk integration configuration within Microsoft Dynamics 365 Finance & Operations.
This error occurs when the integration connection was not configured properly. If the connection process was interrupted before a subsidiary was selected, or if the subsidiary information was not saved correctly, expenses will fail to export. In most
This error occurs when the expense contains a custom field (dimension) value that no longer exists in MS Business Central.
This error occurs when default dimensions are automatically applied in MS Business Central, creating a conflict with the dimensions Payhawk is attempting to set based on the expense's custom fields.
This error typically indicates an issue with the "No. Series" setup in MS Business Central. The system is unable to automatically generate unique identification numbers for objects like payments, which is required for successful export.
This error indicates that the version of the Purchase Credit Memo API in your MS Business Central environment is outdated and requires an upgrade to process the data being exported from Payhawk.
This error occurs when the original payment or document record related to the expense has been deleted directly within MS Business Central.
This error is related to a Romanian localization extension, specifically, the D394 package, installed on your MS Business Central account.
This error occurs when your Payhawk extension in MS Business Central is either outdated or missing. New features and changes in the integration require a specific minimum version of the extension to ensure that everything works as expected.
This error occurs when an expense was previously exported to MS Business Central, then returned for review in Payhawk, and reviewed again for re-export.
This error occurs when the Payment journal that was previously configured in Payhawk has been removed or renamed in MS Business Central.
This error occurs when the General Ledger (G/L) account that is mapped to the expense category in Payhawk is blocked in MS Business Central. Blocked accounts cannot be used for posting transactions.
This error occurs when you are trying to export a reimbursement expense. For reimbursements, Payhawk uses the employee who created the expense as the vendor in MS Business Central.
This error occurs when the vendor associated with the expense does not exist in Payhawk's synced supplier list from your accounting system.
This error occurs when the combination of VAT Business Posting Group, from the vendor, and VAT Product Posting Group, from the G/L account, used in the expense does not exist in the VAT Posting Setup table in MS Business Central.
This error occurs when the vendor's payment method in MS Business Central is configured to automatically create and post a payment when an invoice is posted.
This error occurs when your user account in MS Business Central doesn’t have the necessary permissions to allow the Payhawk integration to function properly.
This error can occur for all export types, including purchase invoices, payments, and journals, when MS Business Central is unable to assign a new number from the configured number series.
Error message Failed to export into Datev. An error occurred while uploading the documents. Please check if the attached file is valid. Affected ERP integrations DATEV Cause This error occurs because DATEV does not accept JPEG ( .jpg )...
Error message Failed to export into Datev. The selected cost category does not have an external ID associated with it. Affected ERP integrations DATEV Cause This error occurs when the cost category was selected before its external ID map...
Error message Failed to export into Datev.Account code should be between 1 and … characters long. Affected ERP integrations DATEV Cause This error occurs when the account code used in Payhawk does not match the length expected by your DA...
If a note is too long for DATEV, Payhawk now shortens it automatically during the export. This error can still show on expenses that failed to export before Payhawk started shortening long notes automatically. Error message Note should be betwe...
Error message Failed to sync Departments. Affected ERP integrations Exact Online Cause This error can appear during the initial connection or a manual sync when linking your Payhawk account to Exact Online. It occurs becaus...
This error occurs when the multi-currency option is not enabled in your QuickBooks Online account. Without this feature, QuickBooks Online cannot process transactions in multiple currencies.
This error occurs because in QuickBooks Online, each vendor (supplier) has a defined currency, and only vendor bills in that specific currency can be linked to that vendor.
This error occurs when you're trying to export an expense that has been marked as billable in Payhawk, but the corresponding expense account in QuickBooks Online is not configured to support billable expenses.
This error occurs when an expense line item has been marked as Billable in Payhawk, but the corresponding Customers or Projects custom fields have not been populated.
QuickBooks Online has specific restrictions on which account types can be used for billable expense transactions. If the mapped account type does not meet these requirements, the export will fail.
This error occurs when you're attempting to export an expense that involves deferred costs, but the deferred cost functionality has not been properly configured in your Exact Online account.
This error occurs when there is a specific Purchase G/L account linked directly to the supplier's account card in Exact Online.
This error occurs when the specific Purchase journal selected for exporting expenses in Payhawk is blocked for creating entries in Exact Online.
This error occurs when the Invoice Approval feature is enabled in your Exact Online account, but no approver has been designated for purchase invoices.
Without an existing payment condition, either Payhawk's default or another one set as default, Exact Online cannot process the purchase entry, which leads to the export failure.
This error occurs when the VAT code that has been applied to an expense in Payhawk is marked as Blocked in your Exact Online account.
This error occurs when the General Ledger (G/L) account in Exact Online, which is mapped to the selected expense category in Payhawk, has been marked as Blocked.
This error occurs when Payhawk attempts to update or modify a purchase entry in Exact Online that has already been processed and posted.
This error occurs when you are trying to export an expense associated with a supplier who has been marked as Blocked in your Exact Online account.
This error occurs when the supplier selected for an expense in Payhawk is not considered active in your Exact Online account. Exact Online cannot post transactions to inactive suppliers, which causes the export to fail.
This error occurs when you have selected a VAT code in Payhawk that is designated as No VAT or VAT 0% in Exact Online, but a custom VAT amount (greater than 0.00) has been entered for the expense in Payhawk.
This error occurs when you attempt to update the Document Date or Service Period for an expense in Payhawk that has already been exported to Exact Online, and your Exact Online account has the Period-date check setting configured as Mandatory.
This error occurs when Payhawk attempts to export an expense to an accounting period that has been closed by an accountant in Exact Online. Exact Online does not allow new entries or modifications to be made to closed accounting periods.
This error occurs when the user account that was used to connect Payhawk to Exact Online does not have the necessary rights and permissions in Exact Online.
This error occurs when the Exact Online division to which your Payhawk integration is connected has been marked as archived in Exact Online.
This error occurs when the user account that was used to connect the Payhawk integration to Exact Online has had their access to the connected division revoked.
This error occurs when the Exact Online division connected to Payhawk has been marked as blocked. A division can become blocked if an Active from or Active to date range has been configured for it, and the current date falls outside of that range.
As the error message suggests, this is an account-level problem caused by an expired license for your Exact Online subscription.
This error occurs when the user account that was originally used to establish the connection between Payhawk and Exact Online has since been deleted or deactivated in Exact Online.
This error occurs when the user account that was originally used to establish the connection between Payhawk and Exact Online has subsequently had their access revoked or blocked in Exact Online.
This error occurs when you attempt to export an expense from Payhawk to Exact Online, but Exact Online detects that an entry with a similar combination of key fields already exists.
This is an internal error that occurs when the Payhawk General G/L account or Fees G/L account, which are configured within Payhawk's Exact Online integration settings, are not found in the Chart of Accounts.
This error occurs when the bank journal selected for the currency of the expense being exported does not have the Variable: Exchange Rate option enabled.
Learn how to enable variable currency on your purchase journal or add the currency to Exact Online.
This error occurs when the General Ledger (G/L) account mapped to your expense category in Payhawk has specific restrictions on which cost centers can be used with it in Exact Online.
This error occurs when the General Ledger (G/L) account mapped to your expense category in Payhawk has specific restrictions on which cost units can be used with it in Exact Online.
This error occurs when the project selected for an expense in Payhawk has an Active from and Active to date range configured in Exact Online, and the current date falls outside of that range.
This error occurs when the cost unit selected for an expense in Payhawk has reached its End date in Exact Online.
This error occurs when the cost center selected for an expense in Payhawk has reached its End date in Exact Online.
Resolve the "Invalid Project selection in expense" error when exporting from Payhawk to Exact Online. Learn how to re-sync custom fields and select an active project, or update the project's active date range in Exact Online.
Resolve the "Invalid Cost Unit selection in expense" error when exporting from Payhawk to Exact Online. Learn how to re-sync custom fields and select an active cost unit, or extend the cost unit's End date in Exact Online.
Resolve the "Invalid Cost Centre selection in expense" error when exporting from Payhawk to Exact Online. Learn how to re-sync custom fields and select an active cost centre, or extend the cost centre's End date in Exact Online.
This error occurs when the document date or service period of the expense being exported from Payhawk corresponds to an accounting period that has not yet been defined in Exact Online's period date table.
This error occurs when the VAT code selected for an expense in Payhawk is not considered valid by Exact Online.
This error occurs when the VAT number provided for a supplier in Payhawk does not meet the validation criteria set by Exact Online.
This error typically indicates an issue with the integration setup, specifically concerning the purchase journal and the associated Accounts Payable (A/P) account.
This error occurs when Payhawk attempts to automatically create a purchase journal in Exact Online on your behalf, but the connected user account lacks the necessary permissions to perform this action.
This error typically indicates an issue with the integration setup, specifically concerning the purchase journal configuration.
This error occurs when an expense is being exported without any supplier information associated with it. Without a supplier attached to the expense, the ERP integration cannot process the transaction and the export will fail.
This error occurs when your Exact Online account is configured to automatically prepare Intrastat declarations, and you are trying to export an expense with an item that is missing its required Statistical code.
This error occurs when an account that was previously synced to Payhawk as a supplier has had its Supplier status disabled in Exact Online.
This error occurs when Payhawk attempts to send amortization data to Exact Online, but the required Accrued costs and/or Deferred costs G/L accounts have not been configured in your Exact Online Financial settings.
This error occurs when an expense in Payhawk uses an amortization schedule, but only one of the two required date fields, Amortization Start or Amortization End, has been filled in.
This error occurs when Microsoft Dynamics 365 Finance and Operations is not configured with a number sequence for Bank statement or Statement ID.
This error occurs when the expense category in Oracle NetSuite that is mapped to a G/L account in Payhawk has the Rate Required setting enabled.
This error occurs when the vendor selected for an expense has a default expense account set up in their Oracle NetSuite record, and this default account is not valid for the subsidiary that the Payhawk integration is connected to.
This error occurs when one or more fields that are marked as required in Oracle NetSuite have not been populated in the corresponding expense in Payhawk.
This error occurs when the document number assigned to an expense in Payhawk has already been used for another transaction with the same vendor in Oracle NetSuite.
Error message Invalid amortization end date. Please make sure you have selected correct amortization end date on each expense line. Affected ERP integrations Oracle NetSuite Cause The amortization end date on one or more expense line ite...
Error message We were unable to add expense / payment currency to the selected employee or vendor. Please add the currencies to the employee / vendor in NetSuite and try again. Affected ERP integrations Oracle NetSuite Cause When exporti...
Error message Update failed because an associated intercompany adjustment has already been created. Please check related records in NetSuite or revert your changes. Affected ERP integrations Oracle NetSuite Cause This error is returned b...
Error message Elimination settings for the journal line, account, and name do not match. Please, check your Intercompany Settings in NetSuite. Affected ERP integrations Oracle NetSuite Cause This error is returned by Oracle NetSuite when ...
Error message An update you have made to the expense is not allowed in NetSuite. Please revert the changes and try again. Affected ERP integrations Oracle NetSuite Cause This error is returned by Oracle NetSuite when attempting to update ...
Error message Unable to export payments for this expense. The bank account mapped to this balance is not valid. Please check its status in NetSuite. Affected ERP integrations Oracle NetSuite Cause This error occurs when the bank account ...
Error message Please check that the selected tax code have tax account set in NetSuite. Affected ERP integrations Oracle NetSuite Cause When exporting journals to Oracle NetSuite, if a tax code is selected on the expense, the tax code mus...
Error message Please verify that tax code is selected when tax amount is greater than 0. Affected ERP integrations Oracle NetSuite Cause When exporting journals to Oracle NetSuite (depending on your configuration), you cannot have a tax ...
Error message Please verify that tax amount is not greater than total amount Affected ERP integrations Oracle NetSuite Cause This error is returned by Oracle NetSuite when the tax amount on an expense is greater than the total expense am...
Error message The payment cannot be exported due to currency incompatibility. Please make sure that all expenses, related to this payment have their periods open in NetSuite to enable currency change. Affected ERP integrations Oracle NetSuite...
Error message An invalid value was provided for ${field}. Please select another value or check default values for the employees / vendors in NetSuite in case this field is not synced to Payhawk. Affected ERP integrations Oracle NetSuite Ca...
Error message Failed to create vendor with name ${vendor.name} because of required field(s) in NetSuite. Please create the vendor in NetSuite and try again. Affected ERP integrations Oracle NetSuite Cause This error occurs when exporting ...
Error message Failed to export into NetSuite. Payment date is outside of the accounting period which is not allowed by your NetSuite settings. Adjust the date on Payhawk or the accounting settings in NetSuite. Affected ERP integrations Oracle...
Error message The selected A/P account cannot be used with this subsidiary. Please update the wizard configuration or change the settings for the A/P account in NetSuite. Affected ERP integrations Oracle NetSuite Cause This error occurs ...
Error message Please update the A/P account on (vendor bill / vendor credit / expense report / journal entry) XXXX. Affected ERP integrations Oracle NetSuite Cause This error occurs when attempting to export a bulk payment where at least ...
Error message The connection to NetSuite has been invalidated, please try connecting again. Affected ERP integrations Oracle NetSuite Cause This error occurs when Payhawk receives an INVALID_LOGIN_ATTEMPT error from Oracle NetSuite. The...
Error message Document date is outside of the accounting period which is not allowed by your NetSuite settings. Adjust the date on Payhawk or the accounting settings in NetSuite. Affected ERP integrations Oracle NetSuite Cause In Oracle N...
Error message This expense has already been exported as Journal Entry. You are currently trying to export it as Vendor Bill. Please delete the expense in NetSuite and try again. Affected ERP integrations Oracle NetSuite Cause This error ...
Error message Could not create G/L account due to required fields in NetSuite. Please make them optional in NetSuite or select expense and bank accounts via the configuration wizard. Affected ERP integrations Oracle NetSuite Cause This er...
Error message Failed to export into NetSuite. Please check whether selected tax data is valid for this transaction. Affected ERP integrations Oracle NetSuite Cause This error occurs when the tax rate selected for the expense no longer exi...
Error message The selected tax code cannot be used for this type of entity. Affected ERP integrations Oracle NetSuite Cause This error occurs when the tax code or tax group selected in the expense is not valid for the type of record bein...
Error message Bill is within installment window, and cannot change its installments. Please delete the bill in NetSuite and try to export again. Affected ERP integlrations Oracle NetSuite Cause This error occurs when a bill uses Oracle Ne...
Error message The selected G/L account is mapped to multiple expense categories in NetSuite. It should be mapped to exactly one. Affected ERP integrations Oracle NetSuite Cause This error occurs because in Oracle NetSuite, multiple expens...
Error message Unable to export payments for this expense. Exported bill is pending approval in NetSuite. Affected ERP integrations Oracle NetSuite Cause This error occurs when the vendor bill has been exported to Oracle NetSuite but is p...
Error message Unable to export payments for this expense. Exported bill has a payment hold on it in NetSuite. Affected ERP integrations Oracle NetSuite Cause This error occurs when the bill was successfully exported to Oracle NetSuite, b...
Error message The specified supplier is still not exported to NetSuite. Please try again in a few minutes. Affected ERP integrations Oracle NetSuite Cause The supplier has not yet synced to Oracle NetSuite. This may be due to an ongoing ...
Error message The supplier creation in NetSuite failed. Please check supplier status. Affected ERP integrations Oracle NetSuite Cause This error occurs when the supplier could not be created in Oracle NetSuite due to a sync error. Solu...
Error message Invalid category item code. Affected ERP integrations Oracle NetSuite Cause This error occurs when the selected category has not been mapped to an item in Oracle NetSuite. Solution To resolve this issue: Check the cat...
Error message A required currency change cannot be executed because the accounting period does not allow G/L changes. Please open the period in NetSuite. Affected ERP integrations Oracle NetSuite Cause This error occurs when the expense ...
Error message Please check whether date fields are populated correctly in the expense and configured correctly in NetSuite. Affected ERP integrations Oracle NetSuite Cause This error occurs when a custom date field in Oracle NetSuite is ...
Error message This expense has already been exported with different data. Please delete the expense and try again. Affected ERP integrations Oracle NetSuite Cause This error occurs when the expense report was initially exported in the ex...
Error message Payment cannot be exported due to a changed supplier. Affected ERP integrations Oracle NetSuite Cause This error occurs when the expense was exported with one supplier, then the supplier was changed and the expense was paid...
Error message Payment cannot be exported. NetSuite does not support paying different suppliers with 1 payment. Please use the same supplier for all expenses related to this payment. Affected ERP integrations Oracle NetSuite Cause This err...
Error message We can not approve expense report in NetSuite because the expense account is not approved. Affected ERP integrations Oracle NetSuite Cause This error occurs when Payhawk has automatically approved expense reports in Oracle ...
Error message Please check whether the selected tax code is valid and available in NetSuite. Affected ERP integrations Oracle NetSuite Cause This error occurs when the tax code assigned to the expense is not valid or does not exist in Or...
This article covers common reasons for export errors when using the Payhawk-Microsoft Business Central integration and provides hints to prevent or resolve them. Issues related to general export Missing required fields - Ensure all required fiel...
This error happens because your company’s SAP configuration requires a specific field, such as a Branch, Profit Center, Assignment Number, or Text field, to be populated whenever a transaction hits this G/L account.
When exporting an expense, you may encounter an error indicating that the selected General Ledger (G/L) account does not exist or is not defined in the Chart of Accounts.
When exporting an expense, you may encounter an error indicating that direct postings are blocked for the selected cost center.
When exporting an expense, you may encounter an error indicating that the selected tax code is invalid, or that the tax code does not exist for the specified country or region's tax procedure.
When exporting an expense, you may encounter an error indicating that the vendor is not defined in the specified company code.
When trying to update, delete, or reverse an expense, you may encounter an error stating that the document has already been cleared.
When exporting an expense, you may encounter an error indicating that the chosen WBS element is not yet released.
When exporting an expense, you may encounter an error indicating that the selected WBS element is currently locked.
When exporting an expense, you may encounter an error indicating that the internal order assigned to the transaction is not released.
When exporting an expense, you may hit a roadblock stating that an entry is required in the House bank field for a specific General Ledger (G/L) account.
When exporting an expense, you may encounter an error indicating that name and city details are missing for a one-time account posting.
Error message Account xxx and house bank xxx is not a valid combination. Please select another G/L clearing account or check the bank account settings in SAP S/4HANA. Affected ERP integrations SAP S/4HANA® Cause When exporting a payment, ...
When exporting an expense, you may hit an error stating that there is no item category assigned to the selected General Ledger (G/L) account.
When exporting an expense, you may hit an error indicating that a tax statement item is missing for the tax code applied to the transaction.
When exporting an expense, you may encounter an error indicating that multiple true account assignments have been entered.
When exporting an expense, you may encounter an error indicating that direct postings are not allowed for the selected General Ledger (G/L) account.
When exporting an expense, you may hit an error indicating that the item category assigned to your G/L account is not allowed for this specific accounting transaction.
This error message appears in the Sync details panel when a supplier is skipped while syncing to your ERP because a supplier with the same name or tax number already exists there. The rest of the sync still completes, and the Suppliers row shows...
This error message appears in the Sync details panel when a supplier cannot be synced to your ERP because its email address fails validation. The supplier is not synced, and the Suppliers row shows Failed . Cause The email address on the supp...
This error message appears in the Sync details panel when a supplier sync cannot run because another sync is already in progress for the same integration. The supplier is not synced on this attempt, and the Suppliers row shows Failed . Cause ...