R
Who fixes it148 codes
- ERP data
- 55
- Integration
- 35
- Seller's access
- 11
- Seller and buyer
- 40
- Buyer
- 4
- Platform
- 3
E-mail
[email protected]Rejection codes
Rejection codes, and who fixes each one.
Validators and tax platforms answer with a code, not an explanation. Each code below says what went wrong and which side fixes it.
Who fixes it
Every code belongs to one side.
Most rejections are fixed in the ERP data or in the integration. Knowing which saves a week of emails.
- 55ERP data
A field in the seller's ERP export or master data is missing or wrong.
- 35Integration
The mapping or the connection between the ERP and the route. With us, that is our work.
- 11Seller's access
The seller's registration, credentials or permissions on the route.
- 40Seller and buyer
A commercial or tax decision, usually with the buyer or the accountant.
- 4Buyer
Something on the buyer's side. The seller waits or follows up.
- 3Platform
The tax platform or network itself. Wait and send again.
1Does the message name a field or a business term, such as BT-48?
No code matches. Try part of the code, or a word from its meaning.
11 codes
EN 16931, every country
| Code | What it means | Who fixes it | What to do |
|---|---|---|---|
BR-CO-16 | The amount due (BT-115) is not the total with VAT (BT-112) minus the paid amount (BT-113) plus rounding (BT-114). | Integration | Fixed in the integration. Nothing changes in the ERP. |
BR-CO-15 | The total with VAT (BT-112) is not the total without VAT (BT-109) plus the VAT total (BT-110). | Integration | Fixed in the integration. Nothing changes in the ERP. |
BR-CO-25 | An amount is due (BT-115 positive) but there is neither a due date (BT-9) nor payment terms (BT-20). | ERP data | Export the due date or the payment terms. |
BR-CL-04 | The invoice currency code is not an ISO 4217 code. | ERP data | Use the three-letter ISO code, such as EUR, PLN or RON, in the ERP. |
BR-CL-23 | A unit of measure is not a UN/ECE Recommendation 20/21 code. | Integration | Fixed in the integration. Nothing changes in the ERP. |
BR-CL-25 | An electronic address scheme (BT-34-1 or BT-49-1) is not in the EAS code list. | ERP data | Correct the scheme in the customer or company record, for example 0208 or 9925 in Belgium. |
BR-06 | The seller name (BT-27) is missing. | ERP data | Add the legal name to the company settings. |
BR-50 | Payment by credit transfer needs the payment account (BT-84), and it is missing. | ERP data | Add the IBAN to the company's bank details. |
BR-IC-11 | An intra-EU supply (K) needs the delivery date or the invoicing period. | ERP data | Export the delivery date or the service period. |
BR-IC-12 | An intra-EU supply (K) needs the deliver-to country. | ERP data | Export the delivery address or at least its country. |
BR-O-02/03 | An invoice with 'not subject to VAT' (O) lines must not carry VAT numbers. | Seller and buyer | Check with the accountant: either the sale is outside the scope of VAT (remove the VAT numbers) or it needs another category. |
9 codes
Peppol
| Code | What it means | Who fixes it | What to do |
|---|---|---|---|
PEPPOL-EN16931-R003PEPPOL-R003 | Neither a buyer reference (BT-10) nor a purchase order reference (BT-13) is present. | ERP data | Export the buyer's reference or order number. |
PEPPOL-EN16931-R010PEPPOL-R010 | The buyer's electronic address (BT-49) is missing. | ERP data | Add the customer's Peppol ID (scheme and value) to the customer record; look it up in the Peppol directory. |
PEPPOL-EN16931-R020PEPPOL-R020 | The seller's electronic address (BT-34) is missing. | Seller's access | Use the Peppol ID the seller is registered under at its access point. |
PEPPOL-EN16931-CL008 | An electronic address scheme is not in the Peppol EAS code list. | ERP data | Correct the scheme, as for BR-CL-25. |
DE-R-005 | Peppol's German national rule: when seller and buyer are both in Germany, the seller contact's name (BT-41) is required, B2B included. | ERP data | Add the invoicing contact's name, as for XRechnung. |
DE-R-006 | Peppol's German national rule: when seller and buyer are both in Germany, the seller contact's telephone (BT-42) is required, B2B included. | ERP data | Add the invoicing contact's phone number, as for BR-DE-6. |
DE-R-007 | Peppol's German national rule: when seller and buyer are both in Germany, the seller contact's email (BT-43) is required, B2B included. | ERP data | Add the invoicing contact's email address, as for BR-DE-7. |
DE-R-015 | Peppol's German national rule: when seller and buyer are both in Germany, the invoice must carry the buyer reference (BT-10), B2B included. | ERP data | Export the buyer reference, as for BR-DE-15. |
REPEPPOL-MLR-RE | The receiver's system rejected the document at message level (schema, UBL or fatal business rule); its description says why, and line responses may carry BV (business rule) or SV (syntax) reasons. | Integration | Fixed in the integration. Nothing changes in the ERP. |
21 codes
Peppol: the buyer's response
A buyer's Invoice Response carries a reason and an action. These are business statuses, not file errors. Official source: Peppol Invoice Response
| Code | What it means | Who fixes it | What to do |
|---|---|---|---|
NONPEPPOL-REASON-NONBuyer status | No issue: a status update only. | Seller and buyer | Nothing to do. |
REFPEPPOL-REASON-REFBuyer status | References are missing or wrong (order, contract, buyer reference) needed for routing or approval. | Seller and buyer | Add the reference the buyer asked for and resend if the buyer asks for a new invoice. |
LEGPEPPOL-REASON-LEGBuyer status | The invoice does not meet legal requirements. | Seller and buyer | Check the legal content with the accountant; usually credit and reissue. |
RECPEPPOL-REASON-RECBuyer status | The addressee is not known to the buyer. | Seller and buyer | Check the buyer entity and its Peppol ID; credit and invoice the right entity. |
QUAPEPPOL-REASON-QUABuyer status | Item quality is not acceptable. | Seller and buyer | Settle with the buyer; a credit note may follow. |
DELPEPPOL-REASON-DELBuyer status | Delivery is not acceptable. | Seller and buyer | Settle with the buyer; a credit note may follow. |
PRIPEPPOL-REASON-PRIBuyer status | Prices differ from what the buyer expected. | Seller and buyer | Check the agreed price; credit or reissue. |
QTYPEPPOL-REASON-QTYBuyer status | Quantities differ from what the buyer expected. | Seller and buyer | Check delivered quantities; credit or reissue. |
ITMPEPPOL-REASON-ITMBuyer status | Items differ from what the buyer expected. | Seller and buyer | Check the items; credit or reissue. |
PAYPEPPOL-REASON-PAYBuyer status | Payment terms differ from what was agreed. | Seller and buyer | Check the terms; reissue if the buyer asks. |
UNRPEPPOL-REASON-UNRBuyer status | The buyer does not recognise the transaction. | Seller and buyer | Confirm with the buyer who ordered; credit if it was sent in error. |
FINPEPPOL-REASON-FINBuyer status | Finance terms differ. | Seller and buyer | Check the finance terms with the buyer. |
PPDPEPPOL-REASON-PPDBuyer status | Partially paid (used with PD). | Seller and buyer | Track the remaining amount. |
OTHPEPPOL-REASON-OTHBuyer status | Another reason, given as text. | Seller and buyer | Read the buyer's note. |
NOAPEPPOL-ACTION-NOABuyer status | No action is needed from the seller. | Seller and buyer | No action is needed from the seller. |
PINPEPPOL-ACTION-PINBuyer status | Send the missing information without reissuing the invoice. | Seller and buyer | Send the missing information without reissuing the invoice. |
NINPEPPOL-ACTION-NINBuyer status | Issue a new, corrected invoice. | Seller and buyer | Issue a new, corrected invoice. |
CNFPEPPOL-ACTION-CNFBuyer status | Cancel the invoice in full with a credit note. | Seller and buyer | Cancel the invoice in full with a credit note. |
CNPPEPPOL-ACTION-CNPBuyer status | Issue a partial credit note. | Seller and buyer | Issue a partial credit note. |
CNAPEPPOL-ACTION-CNABuyer status | Repay the amount already paid. | Seller and buyer | Repay the amount already paid. |
OTHPEPPOL-ACTION-OTHBuyer status | Another action, given as text. | Seller and buyer | Another action, given as text. |
6 codes
Germany: XRechnung and ZUGFeRD
| Code | What it means | Who fixes it | What to do |
|---|---|---|---|
BR-DE-5 | The seller's contact name (BT-41) is missing. | ERP data | Add an invoicing contact person or department to the company settings. |
BR-DE-6 | The seller's contact telephone (BT-42) is missing. | ERP data | Add the invoicing contact's phone number. |
BR-DE-7 | The seller's contact email (BT-43) is missing. | ERP data | Add the invoicing contact's email address. |
BR-DE-15XRechnung BR-DE-15 | The buyer reference (BT-10) is missing. For public buyers it must be the Leitweg-ID (public-sector routing is parked). | ERP data | Export the reference the buyer gave with the order. |
§14(4) Nr.2 UStG | A German invoice needs the seller's Steuernummer or USt-IdNr. | ERP data | Add either number to the company settings. |
PDFA-6.2.4.3 | The PDF paints in a device colour space without an output intent, so it is not PDF/A-3B. | Integration | Fixed in the integration. Nothing changes in the ERP. |
16 codes
France: platform rules
| Code | What it means | Who fixes it | What to do |
|---|---|---|---|
BR-FR-01/02 | The invoice number is longer than 35 characters, or uses characters other than letters, digits and - + _ /. | ERP data | Change the ERP number series for French invoices. |
BR-FR-05 | Every invoice needs three notes: PMT (the EUR 40 recovery indemnity), PMD (late-payment penalties) and AAB (early-payment discount). | Integration | Fixed in the integration. Nothing changes in the ERP. |
BR-FR-08 | The billing frame (BT-23: B1, S1, M1 and the other allowed values) is missing or not allowed. | ERP data | Classify each invoice as goods, services or mixed, so the billing frame can be set. |
BR-FR-10 | The seller's SIREN is missing, or not active in the national directory. | Seller's access | Add the SIREN to the company settings, and check the company is registered with its platform in the directory. |
BR-FR-11 | A domestic B2B invoice needs the buyer's SIREN, active in the national directory. | ERP data | Add the SIREN to the customer record. |
BR-FR-12 | The buyer's electronic address (BT-49) is missing. The invoice and the statuses meant for the buyer go there. | ERP data | Take the buyer's address from the national directory and store it on the customer record. |
BR-FR-13 | The seller's electronic address (BT-34) is missing. | Seller's access | Use the address the seller registered through its platform. |
BR-FR-16 | The VAT rate is not one of the rates the rule lists, such as 20, 10, 5.5 and 2.1. | Seller and buyer | Check the tax code with the accountant and correct it in the ERP. |
BR-FR-CO-05 | A credit note must cite at least one earlier invoice (BT-25, with its date BT-26), in the header or on every line. | ERP data | Export the number and date of the invoice being credited. |
BR-FR-CO-12 | A French invoice in another currency needs the accounting currency EUR (BT-6) and the VAT total in EUR (BT-111). | Integration | Fixed in the integration. Nothing changes in the ERP. |
BR-FR-CDV-15 | A status that needs a reason (fr:206 partly approved, fr:207 disputed, fr:208 suspended, fr:210 refused) was sent without one. | Integration | Fixed in the integration. Nothing changes in the ERP. |
BR-FR-CDV-CL-09 | The reason code is not one of the 51 AFNOR codes, or is not allowed with that status (for example QTE_ERR with a refusal). | Integration | Fixed in the integration. Nothing changes in the ERP. |
BR-FR-CDV-CL-11 | An amount in a status uses a type outside the 14 allowed (MEN, MPA, RAP, ESC, RAB, REM, MAP, MAPTTC, MNA, MNATTC, CBB, DIV, DVA, MAJ). | Integration | Fixed in the integration. Nothing changes in the ERP. |
C. com. L441-9 | The late-payment penalty rate is not stated. | Seller and buyer | State the late-payment penalty rate on the invoice. |
C. com. L441-10 | The EUR 40 fixed recovery indemnity is not stated. | Seller and buyer | State the EUR 40 fixed recovery indemnity on the invoice. |
C. com. R123-237Warning | The seller's legal form and share capital should appear on the invoice. | ERP data | Add the legal form and share capital to the company settings. |
51 codes
France: lifecycle reason codes
The reason a French platform or buyer gives with a status: a file not accepted (501), data rejected (213), or a buyer's dispute, suspension or refusal. Official source: impots.gouv.fr
- 200
- Déposée (deposited)
- 206
- Approuvée partiellement (partly approved)
- 207
- En litige (disputed)
- 208
- Suspendue (suspended)
- 209
- Complétée (completed)
- 210
- Refusée (refused)
- 213
- Rejetée (rejected)
- 501
- Irrecevable (not accepted)
| Code | What it means | Who fixes it | What to do |
|---|---|---|---|
IRR_ANTIVIRUSContrôle anti-virus | The file failed the platform's security scan.Statuses: 501 | Integration | Fixed in the integration. Nothing changes in the ERP. |
IRR_EXT_DOCContrôle de l'extension des PJ de chaque fichier du flux | An attachment has a file type the platform does not accept.Statuses: 501 | ERP data | Export the attachment as PDF (or another allowed type) and resend. |
IRR_NOM_FContrôle du nom de fichier contenu dans le flux | A file name breaks the platform's naming rules.Statuses: 501 | Integration | Fixed in the integration. Nothing changes in the ERP. |
IRR_NOM_PJContrôle du nom des PJ de chaque fichier du flux (absence de caractères interdits) | An attachment name breaks the naming rules.Statuses: 501 | ERP data | Rename the attachment (no special characters) and resend. |
IRR_SYNTAXContrôle syntaxique des fichiers du flux | The invoice file is not valid XML or PDF.Statuses: 501 | Integration | Fixed in the integration. Nothing changes in the ERP. |
IRR_TAILLE_FContrôle de taille max des fichiers contenus dans le flux | A file is larger than the platform allows.Statuses: 501 | Integration | Fixed in the integration. Nothing changes in the ERP. |
IRR_TAILLE_PJContrôle de taille des PJ de chaque fichier du flux | An attachment is larger than the platform allows.Statuses: 501 | ERP data | Compress or split the attachment and resend. |
IRR_TYPE_FContrôle de type et extension des fichiers du flux | The invoice file has a type or extension the platform does not accept.Statuses: 501 | Integration | Fixed in the integration. Nothing changes in the ERP. |
IRR_VIDE_FContrôle de non vide sur les fichiers du flux | A file in the submission was empty.Statuses: 501 | Integration | Fixed in the integration. Nothing changes in the ERP. |
IRR_VID_PJContrôle de PJ non vide de chaque fichier du flux | An attachment was empty.Statuses: 501 | ERP data | Re-export the attachment from the ERP and resend. |
REJ_SEMANRejet pour erreur sémantique | One or more invoice fields break the French rules (the platform names the rule, e.g. BR-CO-16).Statuses: 213 | Integration | Fixed in the integration. Nothing changes in the ERP. |
REJ_UNIRejet sur contrôle unicité | This invoice was already submitted: same seller, number and year.Statuses: 213 | ERP data | Do not send it again. If it is really a new invoice, give it a new number in the ERP. |
REJ_COHRejet sur contrôle Cohérence de données | Some invoice data do not agree with each other, or the seller is unknown to the platform.Statuses: 213 | Integration | Fixed in the integration. Nothing changes in the ERP. |
REJ_ADRRejet sur Contrôle d'adressage | The buyer's e-invoicing address is not in the national directory.Statuses: 213 | ERP data | Get the buyer's current address from the directory, update the customer record and resend. |
REJ_ASS_PJRejet sur Erreur d'association de la PJ | An attachment could not be matched to the invoice.Statuses: 213 | ERP data | Check that each attachment is referenced in the invoice and the file names match, then resend. |
REJ_CONT_B2GRejet sur Contrôles métier B2G | A public-sector business check failed, for example the commitment number.Statuses: 213 | ERP data | Get the public buyer's required references (commitment number, service code), correct and resend. |
REJ_REF_PJRejet sur Référence de PJ | An attachment reference is wrong.Statuses: 213 | ERP data | Correct the attachment reference in the invoice and resend. |
CMD_ERRN° de COMMANDE Incorrect ou manquantBuyer status | The order number is wrong, missing, unknown or already invoiced.Statuses: 206207208210210 (B2G) | ERP data | Get the right order number from the buyer and send a corrected invoice. A refusal on this ground is only valid if the buyer gave the order number before invoicing. |
NON_TRANSMISEDestinataire non connectéBuyer status | Filed with the tax administration but not delivered: the buyer has no approved platform yet.Statuses: 200 | Buyer | Nothing to fix. Send the buyer a readable copy directly and keep proof. |
RETRAIT_MAN_SERVRetraitement manuel par les servicesBuyer status | The public buyer is processing this invoice by hand.Statuses: 210 (B2G) | Buyer | Wait for the buyer; no action unless they ask for something. |
CONTACT_ACHTRAutres : contacter votre acheteurBuyer status | The buyer asks you to contact them.Statuses: 210 (B2G) | Seller and buyer | Call the buyer; the reason is not in the message. |
COORD_BANC_ERRErreur de coordonnées bancairesBuyer status | The bank details on the invoice are wrong.Statuses: 207208210 (B2G) | Seller and buyer | Correct the IBAN in the ERP; issue a credit note and a new invoice. |
DEST_ERRErreur de destinataireBuyer status | The invoice went to the wrong recipient.Statuses: 207210210 (B2G) | ERP data | Check who the buyer entity is; issue a credit note and invoice the right entity. |
DOUBLE_FACTDOUBLE FACTUREBuyer status | Duplicate: same number, same seller and same year already received.Statuses: 207210210 (B2G) | ERP data | Do not resend. Check the ERP numbering if it was meant to be a new invoice. |
JUSTIF_ABSJustificatif absent ou insuffisantBuyer status | A supporting document is missing. The invoice is on hold (fr:208).Statuses: 208 | Seller and buyer | Send the missing attachment back with status fr:209 Complétée; no new invoice is needed. |
LIVR_INCOMPProblème de livraisonBuyer status | The buyer reports a delivery problem: incomplete or not as ordered.Statuses: 206207210 (B2G) | Seller and buyer | Agree the facts with the buyer; credit what was not delivered as ordered. |
ST_CT_NON_DECLARSous-traitant / Co-traitant non déclaréBuyer status | The sender is not a declared subcontractor or co-contractor on this contract.Statuses: 210 (B2G) | Seller and buyer | The prime contractor must declare the subcontractor before invoicing. |
SUPPR_COMP_AVOIRSuppression pour compensation d'avoirsBuyer status | Cancelled because it is offset against a credit note.Statuses: 210 (B2G) | Buyer | Reconcile with the matching credit note; no resend. |
TRANSF_PMNT_REGIETransfert pour paiement en régieBuyer status | The public buyer will pay this through a local cash office (régie).Statuses: 210 (B2G) | Buyer | No action; payment follows by another route. |
TX_TVA_ERRTaux de TVA erronéBuyer status | The buyer says a VAT rate is wrong.Statuses: 207210210 (B2G) | ERP data | Check the tax code mapping in the ERP; issue a credit note and a corrected invoice. |
AUTREAutreBuyer status | Other reason; read the buyer's note.Statuses: 206207210 (B2G) | Seller and buyer | Read the note; contact the buyer if it is empty. |
ROUTAGE_ERRErreur de routageBuyer status | The routing details were out of date (directory lag or a platform error). | ERP data | Once the buyer's directory entry is corrected, resend the same invoice unchanged. |
CALCUL_ERRErreur de calcul de la factureBuyer status | The buyer found a calculation error (line totals or rounding).Statuses: 207210210 (B2G)213 | Integration | Fixed in the integration. Nothing changes in the ERP. |
NON_CONFORMEMention légale manquanteBuyer status | A legal mention is missing from the invoice.Statuses: 207210210 (B2G) | Integration | Fixed in the integration. Nothing changes in the ERP. |
DEST_INCDestinataire inconnu | The recipient does not exist in the directory.Statuses: 213 | ERP data | Check the buyer's SIREN and directory entry; if the buyer has no platform yet, send a readable copy. |
TRANSAC_INCTransaction inconnueBuyer status | The buyer does not recognise the delivery or service.Statuses: 207210210 (B2G) | Seller and buyer | Send proof of delivery or talk to the buyer before reissuing. |
EMMET_INCEmetteur inconnuBuyer status | The buyer does not know the seller (anti-spam refusal).Statuses: 207210210 (B2G) | Seller and buyer | Confirm the business relationship with the buyer, then resend. |
CONTRAT_TERMContrat terminéBuyer status | The contract has ended; no more invoices are accepted under it.Statuses: 207210210 (B2G) | Seller and buyer | Check the contract with the buyer; issue a credit note if billed in error. |
ADR_ERRL'adresse de facturation électronique erronéeBuyer status | The buyer's e-invoicing address (BT-49 or BT-34) is missing or wrong.Statuses: 207210210 (B2G)213 | ERP data | Update the buyer's electronic address in the ERP and resend. |
SIRET_ERRSIRET Erroné ou absentBuyer status | The buyer's SIRET is wrong or missing where required.Statuses: 206207208 | ERP data | Correct the SIRET in the customer record and resend. |
CODE_ROUTAGE_ERRCODE_ROUTAGE Absent ou ErronéBuyer status | The buyer's routing code is wrong or missing where required.Statuses: 206207208 | ERP data | Ask the buyer for the routing code, update the customer record and resend. |
REF_CT_ABSENTRéférence contractuelle nécessaire pour le traitement de la facture manquanteBuyer status | A reference the contract requires is missing (e.g. contract, delivery note, buyer or project reference).Statuses: 206207208210210 (B2G) | ERP data | Add the reference named in the note and send it back (fr:209 if suspended, otherwise a corrected invoice). |
REF_ERRRéférence incorrecteBuyer status | A reference on the invoice is wrong; the note says which.Statuses: 206207208 | ERP data | Correct that reference in the ERP; issue a corrected invoice. |
PU_ERRPrix Unitaires incorrectsBuyer status | A unit price is not the one the buyer expected.Statuses: 206207 | Seller and buyer | Check the price list or quote with the buyer; credit note and new invoice if needed. |
REM_ERRRemise erronéeBuyer status | A discount is missing or not the expected one.Statuses: 206207 | Seller and buyer | Check the agreed discount; credit note and new invoice if needed. |
QTE_ERRQuantité facturée incorrecteBuyer status | A billed quantity is not the one the buyer expected.Statuses: 206207 | Seller and buyer | Check the delivered quantity; for a partial approval, credit the not-approved amount. |
ART_ERRArticle facturé incorrectBuyer status | A billed item is wrong.Statuses: 206207 | Seller and buyer | Check the order; credit note and new invoice. |
MODPAI_ERRModalités de paiement incorrectesBuyer status | The payment terms (for example the due date) are not the agreed ones.Statuses: 206207 | ERP data | Correct the payment terms in the ERP; issue a corrected invoice. |
QUALITE_ERRQualité d'article livré incorrecteBuyer status | A delivered item is defective.Statuses: 206207 | Seller and buyer | Handle the quality claim with the buyer; credit what is not accepted. |
DOUBLONFacture en doublon (déjà émise / réçue)Buyer status | Duplicate invoice: same number, seller and year already received.Statuses: 207210210 (B2G)213 | ERP data | Do not resend. Check the ERP numbering if it was meant to be new. |
MONTANTTOTAL_ERRMontant Total ErronéBuyer status | One of the invoice totals is wrong, for example the amount due.Statuses: 207210210 (B2G)213 | Integration | Fixed in the integration. Nothing changes in the ERP. |
20 codes
Poland: KSeF
| Code | What it means | Who fixes it | What to do |
|---|---|---|---|
Art.106e VAT Act | A Polish invoice needs the seller's NIP, and the buyer's NIP for a domestic buyer. | ERP data | Add the NIP to the company or customer record. |
Art.106e(1)(18a)Warning | The invoice is PLN 15,000 or more: check whether split payment applies to the goods or services (Annex 15). | Seller and buyer | Ask the accountant whether split payment applies. |
440KSEF-440 | KSeF already holds an invoice with the same seller NIP, invoice type and number, and keeps that key for 10 years. The answer gives the KSeF number of the copy it accepted first. A number KSeF rejected with 430 or 450 is not held and can be used again. | Integration | Do not send it again: KSeF already accepted this number. |
9105KSEF-9105 | KSeF rejected the XAdES signature on the login request. | Integration | Fixed in the integration. Nothing changes in the ERP. |
405KSEF-405 | Invoice processing cancelled because the session failed ('Przetwarzanie anulowane z powodu błędu sesji'). | Integration | Fixed in the integration. Nothing changes in the ERP. |
410KSEF-410 | The identity used to log in has no permission to issue invoices for this seller ('Nieprawidłowy zakres uprawnień'). | Seller's access | The seller grants that identity the invoice-issuing permission in KSeF. |
415KSEF-415 | The invoice has an attachment, and attachments are not enabled for this seller ('Brak możliwości wysyłania faktury z załącznikiem'). Attachments go only in batch sessions after being enabled in e-Urząd Skarbowy. | Seller's access | Send without the attachment, or have the seller enable attachments in e-Urząd Skarbowy and use a batch session. |
430KSEF-430 | KSeF refused the file itself ('Błąd weryfikacji pliku faktury'). In KSeF's test environment it answered 430 for a UTF-8 byte-order mark and for a declared size or hash that did not match the file. KSeF does not register the number. | Integration | Fixed in the integration. Nothing changes in the ERP. |
435KSEF-435 | KSeF could not decrypt the invoice file ('Błąd odszyfrowania pliku'). | Integration | Fixed in the integration. Nothing changes in the ERP. |
450KSEF-450 | KSeF refused the content ('Błąd weryfikacji semantyki dokumentu faktury'); the details name the problem. In KSeF's test environment it answered 450 for an issue date after the day of receipt and for FA(3) schema errors. KSeF does not register the number. | Integration | Fixed in the integration. Nothing changes in the ERP. |
500KSEF-500 | Unknown error in KSeF ('Nieznany błąd'). | Platform | Retry later; if it repeats, open a ticket with the Ministry's support. |
550KSEF-550 | KSeF cancelled the operation for internal reasons ('Operacja została anulowana przez system'); the documentation says to retry. | Platform | Retry with back-off. |
HTTP 429KSEF-429 | Too many requests: the API rate limit for this context and IP was exceeded (for example sending is 10 per second, 30 per minute, 180 per hour in production). The response carries Retry-After. | Integration | Wait for the time the answer gives, then send again. |
21184KSEF-21184 | The session is temporarily unavailable, for example during maintenance ('Sesja tymczasowo niedostępna'). | Platform | Open a new session and resend. |
Login 460KSEF-AUTH-460 | Authentication failed on the certificate: invalid, revoked, suspended or with an untrusted chain. | Seller's access | The seller renews the certificate, or issues a new KSeF certificate or token. |
Login 450KSEF-AUTH-450 | Authentication failed on the KSeF token: invalid, expired, revoked or not usable in this context. | Seller's access | The seller issues a new KSeF token with the right permissions. |
Login 415KSEF-AUTH-415 | KSeF login failed: the token or certificate has no permissions for this context. | Seller's access | The seller grants the permissions in KSeF for the company's NIP and issues the token again. |
Login 425KSEF-AUTH-425 | KSeF login refused: the authentication was revoked by the user, together with its refresh tokens. | Seller's access | The seller issues a new KSeF token. |
Login 470KSEF-AUTH-470 | KSeF login failed: the credential belongs to a person KSeF lists as deceased. | Seller's access | The company issues a KSeF token under a person who may act for it. |
Login 480KSEF-AUTH-480 | KSeF blocked the login on a suspected security incident. | Seller's access | The seller contacts the Ministry of Finance to clear the block, then sends again. |
11 codes
Romania: RO e-Factura
| Code | What it means | Who fixes it | What to do |
|---|---|---|---|
BR-RO-001 | The specification identifier (BT-24) is not the CIUS-RO value. | Integration | Fixed in the integration. Nothing changes in the ERP. |
BR-RO-100BR-RO-100/101 | A seller in Bucharest (county RO-B) must have SECTOR1 to SECTOR6 as its city (BT-37). BR-RO-101 is the same rule for the buyer (BT-52); its message text also says BR-RO-100. | ERP data | Store the sector as the city for Bucharest addresses (SECTOR1 to SECTOR6). |
BR-RO-101 | The buyer version of BR-RO-100: a buyer in Bucharest needs SECTOR1 to SECTOR6 as its city (BT-52). The message text reads [BR-RO-100]. | ERP data | Store the sector as the city on the customer record. |
BR-RO-110BR-RO-110/111 | A Romanian seller's county (BT-39) must be an ISO 3166-2:RO code, such as RO-B or RO-CJ. | ERP data | Add the county code to the company address. |
BR-RO-111 | The buyer version of BR-RO-110 (BT-54). The message text reads [BR-RO-110]. | ERP data | Add the county code to the customer address. |
BR-RO-120 | The buyer's legal registration number (BT-47) or VAT number (BT-48) must be present. | ERP data | Add the buyer's CUI or registration number. |
ERRIdentifANAF-ERRIdentif | ANAF does not accept the seller's CUI ('CUI vanzator incorect'). ANAF checks that the number exists, not only its check digit. | ERP data | Correct the CUI; check it in ANAF's public register. |
nokANAF-NOK | ANAF found errors and did not process the invoice (stareMesaj 'nok'). The downloaded zip holds the error file and ANAF's signature; the invoice does not reach the buyer. | Integration | Fixed in the integration. Nothing changes in the ERP. |
XML cu eroriANAF-XML-ERRORS | The file was refused at upload ('XML cu erori nepreluat de sistem'); the error came back in the upload response. | Integration | Fixed in the integration. Nothing changes in the ERP. |
ExecutionStatus 1ANAF-UPLOAD-REFUSED | The upload was refused on the spot: the HTTP status is 200 but ExecutionStatus is 1. Causes include a wrong standard, a file over 10 MB, a non-numeric CIF, or no SPV rights for this CIF. | Integration | Fixed in the integration. Nothing changes in the ERP. |
HTTP 429ANAF-429 | More than 1,000 calls per minute to the ANAF API, or a daily query limit reached (100 status checks and 10 downloads per message per day). | Integration | Wait, then send again at a slower pace. |
3 codes
Greece: myDATA
| Code | What it means | Who fixes it | What to do |
|---|---|---|---|
202MYDATA-202 | myDATA rejects an invalid Greek VAT number (AFM). | ERP data | Correct the AFM in the company or customer record. |
228MYDATA-228 | Duplicate: an invoice with the same UID (issuer AFM, date, branch, type, series and number) is already registered. | Integration | Do not send it again: myDATA already holds this invoice. |
238MYDATA-238 | On the provider channel the issue date must be today; myDATA rejects any other date. | Integration | Issue the invoice on the day it is sent through the provider. |
Contact
A rejection you cannot place?
Send the code with an anonymised sample. We will tell you what it means and who fixes it.
- Your ERP and version
- The first country route and legal entity
- An anonymised sample invoice and where the credentials stand
30-minute call
Choose a time