Are you using a webservice and are you unable to export an invoice to the AFAS financial package? Then this can have various causes.
The cause may be translated into an error message that you can see in the export report. We get this error message back from the financial package and it indicates why it was not possible to export the invoice. Unfortunately, this error message often does not clearly indicate what needs to be done in order to get the invoice exported.
In this article we have collected a number of error messages with a possible explanation and what you can do to solve the problem.
AFAS Webservice
- Error Message: General message: There is no assignment for cost center '10575' with account '4108' or the assignment is blocked.
Possible Cause: There is no correct linkage between the mentioned values.
Possible Solution: These values need to be linked within AFAS.
- Error Message: (AntaObject) There is no value entered in mandatory field 'Rekeningnummer' (AcNr).
Possible Cause: In the administration in the Spend Cloud, one of the account numbers needs to be filled.
Possible Solution: Fill in the account number in the respective administration in the Spend Cloud. You can also compare how this is configured in other administrations.
- Error Message: (AFASFiEntry) VAT is not allowed for account [number].
Possible Cause: AFAS does not accept the VAT code used for the supplier or the ledger account.
Possible Solution: Check in AFAS whether the VAT code can be used for the supplier and ledger account.
- Error Message: General message: Invoice number [number] is already used in finance for Creditor [number].
Possible Cause: The invoice is already in AFAS. It's possible that the invoice was successfully exported to AFAS before, and this might have happened due to a connection error in a previous export.
Possible Solution: Verify if the invoice is already fully present in AFAS. If it is, you can use the option 'Mark invoice as exported.'
- Error Message: [invoice number]-Error Fetching http headers
Possible Cause: A connection error.
Possible Solution: You should check if the invoice is exported to AFAS or not. If the invoice is correctly exported, you can mark it as exported in the Spend Cloud. If the invoice is not exported, it's possible that the attachment size of the invoice is not accepted by AFAS. Read the following article on how to resolve this:
What to do when an invoice is too large for export- Error Message: (AntaObject) The foreign key does not exist in the database. FieldId=Rekeningnummer, ForeignkeyId=KnAnt1
Possible Cause: AFAS doesn't recognize the used creditor number.
Possible Solution: This error is usually caused because the creditor is no longer active in AFAS or because it hasn't been marked as a creditor in the system. You can check this by reviewing the creditor in AFAS and ensuring the 'Is creditor' option is checked.
- Error Message: (journal number) - The entered value for the 'Account Number' field does not exist. Use the search window to select a value.
Possible cause: The corresponding general ledger account number does not exist in AFAS, is blocked, or the 'Is Creditor' field is not checked in the properties of the corresponding creditor.
Possible solution: Verify if the general ledger account number exists in AFAS and is not blocked. If the GL account exists in AFAS and is not blocked, check whether the 'Is Creditor' field is checked for the corresponding creditor in AFAS.
- Error Message: (journal number) - The field 'Project' is not allowed for the selected type of dossier item.
Possible cause: You receive this message when the type of dossier item is configured such that the type can only be modified via the workflow.
Possible solution: Locate this specific type of dossier item in AFAS. Then go to the General tab and select the option W (Always allow editing outside the workflow) under the Handling section.
- Error Message: (journal number) - Total amount is not equal to the selected amount.
Possible cause: This message appears when the invoice amount in Spend Cloud does not match the amount in AFAS.
Possible solution: Enable the checkbox for 'select immediately' for 'Invoice reconciliation' in Profit.
Note! Is this an invoice that has been definitively disapproved in Spend Cloud? Then check if the amount for this invoice in AFAS is equal to the amount in Spend Cloud. If not, adjust the amount in AFAS so that it matches the amount in Spend Cloud.