Error message
An expense with the same document date, document number, and amount has already been exported.Affected ERP integrations
Exact Online
Cause
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. Exact Online performs a validation check for duplicate entries based on a matrix of the following fields: Account, Your Ref (document number), Invoice Date (document date), and Amount.
The system is designed to prevent duplicate postings, and if the combination of these fields matches an existing entry, the new export will be blocked.
The validation matrix is as follows:
Account | Your Ref | Invoice Date | Amount | Result |
|---|---|---|---|---|
Same | Same | Same | Same | Error is returned |
Same | Empty 1st | Same | Same | No error first time |
Same | Empty 2nd | Same | Same | Error is returned |
Same | Same | Same | Different | No error |
Same | Same | Different | Same | No error |
Same | Different | Same | Same | No error |
Different | Same | Same | Same | No error |
Same | Same | Different | Different | No error |
Same | Different | Same | Different | No error |
Same | Different | Different | Same | No error |
Different | Same | Same | Different | No error |
Different | Different | Same | Same | No error |
Different | Different | Different | Different | No error |
Solution
To resolve this issue, adjust the expense details in Payhawk to ensure it is not a duplicate according to Exact Online's validation rules, or confirm that the expense is indeed a duplicate and must not be exported.
Check the expense details in Payhawk: document date, document number (Your Ref), associated vendor (Account), and amount.
Compare with existing entries in Exact Online by logging into Exact Online and searching for existing entries that match the expense's details.
Adjust conflicting fields:
If you find an existing entry that is identical and the Payhawk expense is a true duplicate, you must either mark the expense as non-exportable in Payhawk or delete it if it was created by mistake.
If the Payhawk expense is legitimate and distinct from an existing entry, but still triggering the error, you need to modify one of the conflicting fields to pass Exact Online’s validation, for example, add a unique identifier to the document number if possible, or adjust the date slightly if it's not material.
Attempt to export the expense again from Payhawk. The export must now be successful.