If the rejection reason is not listed in this article, it is an error reported by the recipient. If you have any doubts about this, you should contact the destination organization.
Below are the most common rejection errors that can be of two types:
- Rejection errors for commercial reasons are those defined by the body receiving the invoice; these error codes and/or literals are foreign to the e-FACT, for this reason, these types of errors are not described in this FAQ. It is necessary to contact the receiving organization in case of doubt.
- Rejection errors for technical reasons are those that the tool generates automatically when performing certain internal validations.
Any errors involving invoice correction must be corrected by re-generating the XML and re-signing it. If a change is made to the content of an XML that was signed, the invoice signature will become invalid.
Below we describe the most common technical rejection errors:
FORMAT ERROR
| Code | literal | what does it mean | How to fix it? |
|---|---|---|---|
| The invoice is not in the correct format | This error appears when an invoice is uploaded to the delivery mailbox and it does not respect the invoice format. |
Validate the invoice , check if the format is correct and correct possible errors. The most common format error reasons are as follows: – In the PersonTypeCode field you are putting a "J" for a legal person and therefore the CIF of a legal person must be put in, if you put "F" for physical you must put the NIF of a natural person. – The header does not contain the expected format. Every invoice must start with: – The format of one of the identity documents (issuer TIN/CIF, recipient CIF, third party CIF...) is incorrect. It cannot contain any spaces or dashes. |
|
| HF01 | Bad filename format | The file format does not follow the guideline given in the integration guide | The format indicated in the integration guide should be reviewed and amended. |
| HF08 | Scheme validation error | The submitted invoice schema has not passed syntactic validation and/or the published extensions have not passed validation . | The invoice must be generated in invoice format 3.2 and 3.2.1. |
REGISTRATION ERROR
| Code | literal | what does it mean | How to fix it? |
| HRE1 | Error registering document | The invoice could not be posted correctly, because there is an item that is not reported correctly. |
Validate the XML of the invoice, if you pass the validation try to send it again. If the error persists, talk to the target organization to see if they have an error in their registration system. |
| EV02 | Duplicate invoice | The invoice has already been sent. |
Verify that the invoice has not been sent previously. You can check the status of the invoice in the Delivery Mailbox |
| DF01 | The receiving organism has rejected t the invoice manually | Error detected by the receiving body of the invoice | You must contact the recipient of the invoice to obtain more details of the commercial rejection of the invoice. |
| HS01 | Broadcast platform code unknown | For example, if the invoice is delivered from an issuing platform that does not adhere to the e-FACT service | See dherides platforms in the e-FACT service : Create and send invoices |
| HR01 | Unknown receiving platform code | Unknown invoice receiving platform code. That is, it was sent to a platform code that does not exist in e-FACT | The recipient platform code of the invoice is unknown. The recipient code must be reviewed or confirmed with the recipient. |
| HS02 | Broadcast platform disabled | The broadcasting platform is not properly configured. |
You need to check the configuration of the sending platform and if you think the configuration is correct, please send us the error, indicating the platform from which it is sent and attaching the invoice xml and the error xml : |
| EG01 |
Generic error in the invoice receipt process | There was an error uploading your invoice. | Reload your bill after a few minutes. If it persists, please contact us via the Support Form |
SIGNATURE ERROR
| Code | literal | what does it mean | How to fix it? |
| HF04 | The file does not contain an electronic signature | An attempt was made to send unsigned XML to the platform |
Sign is required the XML to respect the invoice format |
| HV01 | Error verifying signature/certificate | The invoice has not passed the issuer's digital certificate validation (expired or unrecognized certificate) or the electronic signature of the invoice could not be validated (incorrect format). |
Check that the SigningTime field in the XML contains the signing time of the invoice without any odd numbers or characters. If you see, for example, a +2 or a Z, you must redo the signature of the invoice and send it again. If there is nothing to alter this field, you need to review the certificate used to sign the invoice through Signasuite. |
| HV02 | Signature/certificate validation could not be performed | The number of retries set to validate the signature and certificate of an invoice has been exceeded , and therefore the invoice will be rejected |
The invoice must be sent again . If it persists, please contact us via the Support Form |
CONTENT ERROR
| Code | literal | what does it mean | How to fix it? |
| HR11 | Recipient Social Reason not indicated or reported | It is missing to indicate the social reason in the XML. |
This point must be corrected and the invoice sent again. |
| HD01 | Error sending the message to the destination platform | Attempting to send an attachment for which we do not have a previous invoice associated with it. |
The invoice for the associated attachment must be sent in advance. |
| HS09 | NIF issuer not indicated in document | The invoice does not contain the NIF of the issuer |
Check that the XMl of the invoice contains this data (NIF of the issuer) |
| HR09 | Receiver NIF not indicated in document | The invoice does not contain the NIF of the receiver | Check that the XMl of the invoice contains this data (NIF of the receiver) |
| HR10 | The recipient NIF indicated on the invoice does not match the destination entity | The invoice does not correctly report the recipient's TIN | It is necessary to review the NIF indicated in the XML of the invoice |
| HR04 | Received file content not supported by target platform | Delivery of an invoice with an unaccepted version of the invoice format. For example, invoice generated with version 3.oo 3.1. | The invoice must be generated in invoice format 3.2 and 3.2.1 . |
| HF03 | Received file content not supported by the Hub | The content of the file is not correct mainly because it is not a invoice format | The invoice must be generated in invoice format 3.2 and 3.2.1 . |
| HF07 | Only Invoices with a single invoice are accepted | The file . XML contains more than one invoice and only invoice files with a single invoice are supported | The XML needs to be regenerated in a single invoice. |
ERROR WITH ADDRESSING CODE
| Code | literal | what does it mean | How to fix it? |
| HS05 | Bad sender address code (invalid check digit) | Issuing platform incorrectly reported check digit (last number) of sender address code (sender identifier) |
The format indicated in the integration guide should be reviewed and amended. |
| HR05 | Bad receiver addressing code (invalid check digit) | The check digit (last number) of the receiver addressing code (receiver ID) is not correct, as per the format given in the integration guide |
The format indicated in the integration guide should be reviewed and amended. |
| HR08 | Receiver addressing code is not an AAPP | The recipient's address code (recipient identifier) does not correspond to a public body |
The format indicated in the integration guide should be reviewed and amended. |
| HR06 | Receiver addressing code does not exist | Receiver addressing code (receiver ID) does not exist (see integration guide ). |
See the integration guide and if you think it's correct, send us the error, attaching the invoice xml and the error xml : |
| HS06 | There is no ref. previously indicated in the attachment | The attachment is rejected because a registered invoice with the same reference as the attachment is not located |
See the "Management of attached documents" section of the integration guide |
RCF ERROR HF09
Below are defined the new rejection codes added as a result of the new validations incorporated by the necessary adaptations of the e-FACT to comply with the requirements required of the PGEs as established by Order HAP/1650/2015, of July 31, which amends Order HAP/492/2014, of March 27, which regulates the functional and technical requirements of the accounting register of invoices of entities within the scope of Law 25/2013 , of December 27, promoting electronic invoicing and creating the accounting register of invoices in the public sector, and Order HAP/1074/2014, of June 24, which regulates the technical and functional conditions which must meet the general entry point for electronic invoices : https://www.boe.es/diario_boe/txt.php?id=BOE-A-2015-8844
How are the RCF rejects returned to the PGE?
When an invoice is rejected for not complying with the validation rules, all these errors have been grouped into the code = HF09 and the specific code of the error and its description are included in the description. All detected errors are returned in the following format:
- “Error code: Description | error code: Description”
For example in an invoice with detected validation errors RCF05002 and RCF05004 would be returned as a rejection comment:
- RCF05002: Issuer: The NIF does not conform to the rules and criteria of its formation. Rule number 5b of Annex II of Order HAP / 1650/2015 is breached | RCF05004: Issuer: First name and last name are required. Rule number 5d of Annex II of Order HAP / 1650/2015 is breached |
Description of validation errors
| error | Code | Error description | Field that needs to be amended in the invoice XML and/or how to fix it? |
|
HF09 |
RCF03001 | "The invoice number is mandatory. Rule 3a of Annex II of Order HAP/1650/2015 is not complied with " | 3.1.1.1.InvoiceNumber
Indicate an invoice number in this field. |
| RCF04001 | "Rectification invoice with rectification criterion other than 01,02,03,04. Rule 4a of annex II of Order HAP/1650/2015 is not complied with " | 3.1.1.5.6.CorrectionMethod
Indicates one of the possible rectification criteria: 01,02,03,04 |
|
| RCF04002 | For rectification invoices with rectification criterion 01 or 02, the invoice number of the issuing issuer is mandatory. Rule 4b of Annex II of Order HAP/1650/2015 is not complied with | 3.1.1.5.1.InvoiceNumber
Indicate the invoice number of the correcting issuer in this field. |
|
| RCF05001 | Issuer: The code of type of person, physical \"F\" or legal \"J\" is mandatory. Rule 5a of annex II of Order HAP/1650/2015 is not complied with | (2.1.1.1.PersonTypeCode)
Indicate code “F” or “J” in this field. |
|
| RCF05002 | Issuer: The NIF does not conform to the rules and criteria of its formation. Rule 5b of annex II of Order HAP/1650/2015 is not complied with | 2.1.1.3.TaxIdentificationNumber
Amend taking this criterion into account: If the first two characters of the NIF are letters, it will be assumed that they are equivalent to the country, and the rest to the NIF. In another case, the code indicated will be equivalent to the NIF and it is assumed that the code is Spain. |
|
| RCF05003 | Issuer: The country code (two first characters of the NIF when they are letters) when it exists, will be adjusted to what is established in the Invoice scheme itself. Rule 5c of Annex II of Order HAP/1650/2015 is not complied with | 2.1.1.3.TaxIdentificationNumber | |
| RCF05004 | Issuer: The number and first name are mandatory in the case of a natural person. Rule 5d of annex II of Order HAP/1650/2015 is not complied with | 2.1.4.2.1.Name
2.1.4.2.2.FirstSurname Fill in these fields |
|
| RCF05005 | Issuer: The company name is mandatory in the case of a legal entity. Rule 5e of annex II of Order HAP/1650/2015 is not complied with | 2.1.4.1.1.CorporateName
Fill in this field |
|
| RCF05006 | Assignee: The code of type of person, physical \"F\" or legal \"J\" is mandatory. Rule 5a of annex II of Order HAP/1650/2015 is not complied with | 1.6.1.1.1.PersonTypeCode
Indicate code “F” or “J” in this field. |
|
| RCF05007 | Assignee: The NIF does not conform to the rules and criteria of its formation. Rule 5b of annex II of Order HAP/1650/2015 is not complied with | 1.6.1.1.3.TaxIdentificationNumber
Amend taking this criterion into account: If the first two characters of the NIF are letters, it will be assumed that they are equivalent to the country, and the rest to the NIF. In another case, the code indicated will be equivalent to the NIF and it is assumed that the code is Spain. |
|
| RCF05008 | Assignee: The country code (two first characters of the NIF when they are letters) when it exists, will be adjusted to what is established in the Invoice scheme itself. Rule 5c of Annex II of Order HAP/1650/2015 is not complied with | 1.6.1.1.3.TaxIdentificationNumber | |
| RCF05009 | Transferee: The number and first name are mandatory. Rule 5d of annex II of Order HAP/1650/2015 is not complied with | 1.6.1.2.2.1.Name
1.6.1.2.2.2.FirstSurname Fill in these fields |
|
| RCF05010 | Assignee: The company name is mandatory. Rule 5e of annex II of Order HAP/1650/2015 is not complied with | 1.6.1.2.1.1.CorporateName
Fill in this field |
|
| RCF06001 | In the invoices issued in euros, some of the line amounts have more than two decimal places or are not numeric. Rule 6a of Annex II of Order HAP/1650/2015 is not complied with | The amount fields that are validated are the following:
3.1.6.1.17. TotalCost 3.1.6.1.18.1.3. DiscountAmount 3.1.6.1.19.1.3. ChargeAmount 3.1.6.1.21.1.3.1. TaxableBase.TotalAmount 3.1.6.1.21.1.4.1. TaxAmount.TotalAmount 3.1.6.1.22.1.4.1. TaxAmount.TotalAmount NOTE : Verify that the fields do not contain spaces after the amount. |
|
| RCF06002 | In invoices issued in euros, the total cost of each line must be equal to the product of the number of units by the unit price rounded with the common method of rounding to two decimal places. Rule 6a of Annex II of Order HAP/1650/2015 is not complied with | If there were more than two decimals, the ones after the second must be zero:
3.1.6.1.17.TotalCost = RoundingA2decimals (3.1.6.1.14.Quantity*3.1.6.1.16.UnitPriceWithoutTax) |
|
| RCF06003 | In invoices issued in euros, the gross amount of each line must be the sum of the total cost plus the sum of surcharges minus the sum of discounts. Rule 6a of annex II of Order HAP/1650/2015 is not complied with | Check that:
3.1.6.1.20.GrossAmount is equal to 3.1.6.1.17.TotalCost minus SUM(3.1.6.1.18.1.3.DiscountAmount) plus SUM(3.1.6.1.19.1.3.ChargeAmount) |
|
| RCF06004 | In the invoices issued in euros, some of the amounts at the invoice level, except the tax rates or the percentages to be applied, have more than two decimal places or are not numerical. Rule 6b of annex II of Order HAP/1650/2015 is not complied with | The amount fields that are validated are the following:
3.1.5.1. TotalGrossAmount 3.1.5.3.1.3. ChargeAmount 3.1.5.7. TotalTaxOutputs 3.1.5.10.1.3. SubsidyAmount 3.1.5.11.1.2. PaymentOnAccountAmount 3.1.5.12.1.6. ReimbursableExpensesAmount 3.1.5.13. TotalFinancialExpenses 3.1.5.15. TotalPaymentsOnAccount 3.1.5.16.3. WithholdingAmount 3.1.5.18. Total ReimbursableExpenses 3.1.3.1.3.1. TaxableBase.TotalAmount 3.1.3.1.5.1. SpecialTaxableBase.TotalAmount 3.1.3.1.6.1. SpecialTaxAmount.TotalA 3.1.3.1.8.1. EquivalenceSurchargeAmount.TotalAmount 3.1.4.1.3.1. TaxableBase.TotalAmount 3.1.4.1.4.1 TaxAmount.TotalAmount NOTE : Verify that the fields do not contain spaces after the amount. |
|
| RCF06005 | In invoices issued in euros, the total gross amount of the invoice must be the sum of the gross amounts of the lines. Rule 6b of Annex II of Order HAP/1650/2015 is not complied with | 3.1.5.1.TotalGrossAmount = SUM(3.1.6.1.20.GrossAmount of the lines) | |
| RCF07002 | The date of issue of the invoice is mandatory and must be a valid date. Rule 7a of annex II of Order HAP/1650/2015 is not complied with | 3.1.2.1.IssueData
Indicates a date prior to or equal to the current date and greater than or equal to the date the invoice was issued. |
|
| RCF09002 | There are invoice lines without content in the description. Rule 9b of annex II of Order HAP/1650/2015 is not complied with | 3.1.6.1.13.ItemDescription
Check that there are no blank rows in this field. |
|
| RCF01001 | The invoice does not comply with the "Facturae" XSD scheme of the corresponding version (3.2 or 3.2.1). Rule 1 of annex II of Order HAP/1650/2015 is not complied with | Validate that the format of the invoice complies with the “Facturae” scheme: | |
| RCF02001 | Invalid signature: Certificate currently expired in a non-long-lived signature. Rule 2 of annex II of Order HAP/1650/2015 is breached | Validates that the signature conforms to the signature policy in force associated with the “Facturae” format: | |
| RCF02002 | Invalid signature: Certificate currently revoked in a non-long-lived signature. Rule 2 of annex II of Order HAP/1650/2015 is breached | Validates that the signature conforms to the signature policy in force associated with the “Facturae” format: | |
| RCF02003 | Invalid signature: Invalid certificate. Rule 2 of annex II of Order HAP/1650/2015 is breached | Validates that the signature conforms to the signature policy in force associated with the “Facturae” format: | |
| RCF02004 | Invalid signature: Untrusted certificate. Rule 2 of annex II of Order HAP/1650/2015 is breached | Validates that the signature conforms to the signature policy in force associated with the “Facturae” format: | |
| RCF02005 | Invalid signature: Integrity error. Rule 2 of annex II of Order HAP/1650/2015 is breached | Validates that the signature conforms to the signature policy in force associated with the “Facturae” format: | |
| RCF02006 | Invalid signature: Invalid signature format. Rule 2 of annex II of Order HAP/1650/2015 is breached | Validates that the signature conforms to the signature policy in force associated with the “Facturae” format: | |
| RCF02010 | The invoice does not contain signatures: Rule 2 of Annex II of Order HAP/1650/2015 is not complied with | Validates that the signature conforms to the signature policy in force associated with the “Facturae” format: | |
| RCF09001 | The registration number assigned at the general entry point for electronic invoices is mandatory. Rule 9a of annex II of Order HAP/1650/2015 is not complied with | ||
| RCF07001 | The date of entry in the administrative register is mandatory, it must be valid, prior to or equal to the current date and greater than or equal to the date of issue of the invoice. Rule 7a of annex II of Order HAP/1650/2015 is not complied with | 3.1.2.1.IssueDate |