Skip to main content

How to fix e-conomic errors

Integration errors can occur when Corpay One tries to synchronize data to your e-conomic agreement. Find the fix here!

Once you have given Corpay One access to your company's e-conomic agreement, Corpay One will by default try to synchronize data to e-conomic when you add documents to Corpay One, when you pay invoices, and whenever you make other changes to documents in Corpay One. You can read more about that in this article.

From time to time, however, Corpay One runs into an error when trying to synchronize data to e-conomic.

When this happens, Corpay One can't synchronize to e-conomic and can't create new journal entries or update existing entries.

The cause of the integration error therefore has to be found and fixed before Corpay One can synchronize data to e-conomic again.

There can be many causes of integration errors, and just as many solutions. That is why we have collected the most common e-conomic integration errors in this article, along with instructions on how to fix them.

What does an integration error look like?

Every attempt Corpay One makes to synchronize data to e-conomic can be seen in the integration log on the Integrations tab of the individual document. This is also where you can see which error Corpay One ran into and what the error looks like

Some errors are self-explanatory, others are a little more cryptic. The latter can look like this, for example:
​

Economic.Api.Exceptions.AuthorizationException(E03040): To use this feature you must be authorized to use the Scanning add-on module. (id=4e5a8eb24b9a63d1-FRA)


You only need to look at the message in the middle: To use this feature you must be authorized to use the Scanning add-on module. This simply means that the Scanning add-on module is not enabled in e-conomic, and Corpay One therefore can't synchronize to e-conomic.

Common e-conomic integration errors

Once you have fixed an integration error, you can synchronize a document's data manually to send the missing data from Corpay One to e-conomic. If you can't find your integration error in the list, contact the Corpay One support team at supporteu@corpayone.com or via chat.

  • 💡 TIP! Press Ctrl + F on your keyboard to open the search field. Enter the message from the middle of the integration error there to quickly find the fix in the list below.


Economic.Api.Exceptions.AuthorizationException(E03040): To use this feature you must be authorized to use the Scanning add-on module. 

❌ Cause: The Scanning add-on module is not enabled in your company's e-conomic agreement.

✅ Solution: Go to e-conomic and enable the Scanning add-on module.


Economic.Api.Exceptions.IntegrityException(E06300): The date must be within a created accounting year. 

❌ Cause: The document's issue date or due date does not fall within an open or created fiscal year.

✅ Solution: Go to e-conomic and make sure that an open fiscal year has been created that matches the document's issue date and due date.


Object reference not set to an instance of an object.

❌ Cause: Internal error in Corpay One.

✅ Solution: Contact the Corpay One support team at supporteu@corpayone.com or via chat to get this error fixed.


Economic.Api.Exceptions.IntegrityException(E06000): The account '0' does not exist. 

❌ Cause: Vendor group 1 has not been created in e-conomic.

✅ Solution: Go to e-conomic and create vendor group 1.


Economic.Api.Exceptions.AuthorizationException(E02000): Access denied. UserBlocked

❌ Cause: The coworker is blocked or does not have access to the e-conomic agreement.

✅ Solution: Contact the administrator of your company's e-conomic agreement and make sure the coworker is given full access to e-conomic. e-conomic's support team can help with this too.


Economic.Api.Exceptions.ValidationException(E04000): Contra account is blocked for direct entries.

❌ Cause: The document's contra account is blocked for direct entries and therefore does not allow data to be synchronized.

✅ Solution: Go to e-conomic and allow direct entries on the contra account.


Economic.Api.Exceptions.AuthenticationException(E02250): The given token has been revoked.

❌ Cause: The coworker who set up the integration between Corpay One and e-conomic no longer has access to the e-conomic agreement. Corpay One's access to e-conomic has therefore expired.

✅ Solution: The existing integration has to be deleted in Corpay One under Integrations > e-conomic and set up again by a coworker who has access to the e-conomic agreement.


Bilagsnummeret i e-conomic matcher ikke den seneste regning der blev synkroniseret. Dette kan skyldes regningen er slettet eller bogført i e-conomic og en ny regning med samme bilagsnummer er blevet oprettet. Den nye post har følgende faktura nr.

❌ Cause: The entry belonging to the document in e-conomic has been changed manually or deleted, and it therefore no longer has the same document no. Corpay One can't identify the entry that belongs to the document.

✅ Solution: No solution available.


Economic.Api.Exceptions.ValidationException(E04010): Parameters (bankPaymentType, bankPaymentCreditorId, bankPaymentCreditorInvoiceId) must all be set or else null.

❌ Cause: The document was not read correctly.

✅ Solution: Contact the Corpay One support team at supporteu@corpayone.com or via chat to get this error fixed.


Economic.Api.Exceptions.ValidationException(E04030): OCR-linje skal være præcis 15 tegn.

❌ Cause: The document was not read correctly.

✅ Solution: Contact the Corpay One support team at supporteu@corpayone.com or via chat to get this error fixed.


Internal error - contact support

❌ Cause: Temporary server error at Corpay One.

✅ Solution: Wait 10 minutes and then synchronize the document manually. If that doesn't work, contact the Corpay One support team at supporteu@corpayone.com or via chat.


Economic.Api.Exceptions.ServerException(E00000): An internal error has occurred. 

❌ Cause: Temporary server error at Corpay One.

✅ Solution: Wait 10 minutes and then synchronize the document manually. If that doesn't work, contact the Corpay One support team at supporteu@corpayone.com or via chat.


Economic.Api.Exceptions.ValidationException(E04040): Amount <> AmountDefaultCurrency, this is not allowed when the entry is in the default currency.

❌ Cause: The document was not read correctly.

✅ Solution: Contact the Corpay One support team at supporteu@corpayone.com or via chat to get this error fixed.


You have not configured your Economic integration to receive receipts. Please re-configure under 'Integrations'.

❌ Cause: Your company's Corpay One account is not set up to support receipts.

✅ Solution: Set up your company's Corpay One account to support receipts. You'll find a guide here.


"Economic.Api.Exceptions.IntegrityException(E06240): Either the account, contra account or cost type must be supplied when the type is FinanceVoucher. 

❌ Cause: The receipt is missing a category, a contra account or other information in Corpay One.

✅ Solution: Make sure the receipt is fully categorized in Corpay One (that is, that a category, a contra account and any other list information have been selected on the receipt).


Error retrieving a list of suppliers from economic

❌ Cause: The coworker who set up the integration between Corpay One and e-conomic no longer has access to the e-conomic agreement. Corpay One's access to e-conomic has therefore expired.

✅ Solution: The existing integration has to be deleted in Corpay One under Integrations > e-conomic and set up again by a coworker who has access to the e-conomic agreement.


There was no endpoint listening at https://api.e-conomic.com/secure/api1/EconomicWebService.asmx that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

❌ Cause: Temporary server error at e-conomic.

✅ Solution: Wait 10 minutes and then synchronize the document manually. If that doesn't work, contact e-conomic's support team for more details about the problem.


Economic.Api.Exceptions.AuthorizationException(The agreement in question cannot be authorized): UserDeregistered.

❌ Cause: The coworker who set up the integration between Corpay One and e-conomic no longer has access to the e-conomic agreement. Corpay One's access to e-conomic has therefore expired.

✅ Solution: The coworker has to be added to the e-conomic agreement. Alternatively, the existing integration has to be deleted in Corpay One under Integrations > e-conomic and set up again by a coworker who has access to the e-conomic agreement.


An error occurred while receiving the HTTP response to https://api.e-conomic.com/secure/api1/EconomicWebService.asmx. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

❌ Cause: Temporary server error at e-conomic.

✅ Solution: Wait 10 minutes and then synchronize the document manually. If that doesn't work, contact e-conomic's support team for more details about the problem.


{"info":"Integration error","message":"Economic.Api.Exceptions.AuthorizationException(E03020): To use this feature you must be authorized to use the Project Management add-on module.

❌ Cause: The Project Management add-on module is not enabled in your company's e-conomic agreement.

✅ Solution: Go to e-conomic and enable the Project Management add-on module.


Journal entry has been already booked

❌ Cause: The corresponding entry in e-conomic has already been posted at an earlier point, so Corpay One can't update the entry.

✅ Solution: There is no fix for this, because e-conomic does not allow Corpay One to update posted entries. Corpay One can only update unposted entries in the journal.

Kunne ikke automatisk tildele bilagsnummer. Det tildelte bilagsnummer eksisterer ikke i kassekladdens nummerserie

❌ Cause: The entry falls outside the numbering of the journal.

✅ Solution: Extend the number series of the journal. This is done in the journal settings in e-conomic.

Validation failed. 1 error found

❌ Cause: Creating this type of entry is not allowed in the journal.

✅ Solution: Allow invoice, payment and general ledger entries to be created in the journal.

Perioden er blevet spærret

❌ Cause: This error occurs when you try to synchronize a document to a fiscal year or period that has been closed in e-conomic.

✅ Solution: The period has to be reopened in e-conomic so the entry can be posted, or the document's issue date has to be changed to an open accounting period or fiscal year in Corpay One.

Fejl: Den ønskede ressource blev ikke fundet i e-conomic.

❌ Cause: This error occurs when you delete the journal, or journals, that you originally chose to synchronize to.

✅ Solution: Reconfigure your integration in Corpay One and select existing journals in your integration setup.

Did this answer your question?