Notify issuers of invalid e-invoices

Report invalid e-invoices back to the issuer automatically

An e-invoice that fails the formal check is not a proper invoice. The issuer has to correct and resend it. Instead of writing to every supplier by hand, let the program do the feedback: a profile detects invalid invoices and sends the issuer an email with the result, the list of findings and the validation report as an attachment.

This guide shows where the recipient address comes from (CSV mapping, invoice or fallback recipient), how to build the message with the validation placeholders and how to check the sending via the draft folder first.

At a Glance

  • Difficulty: Advanced
  • Time required: about 20 minutes
  • Prerequisites: Automatic X-Invoice Processor version 2.5 or later; email sending set up (Menu → Options... → Email sending, see chapter 40.4); validation enabled (see the how-to "Validate e-invoices and save validation reports")
  • Features used: "Validation result" filter criterion, "Send file" task (recipient from CSV mapping with fallback to the invoice address, attach validation report), placeholders <ValidationSummary> and <ValidationFindings>, draft folder

Video tutorial: Notify issuers of invalid e-invoices (with narration and optional subtitles)


Step 1: Decide where the recipient address comes from

The program can determine the issuer's address in three ways. They can be combined:

  1. From the invoice: Many e-invoices name a seller contact email (BT-43) or an electronic address (BT-34). The program takes the contact email first, otherwise the electronic address if it is an email address.
  2. From a CSV mapping: A text file maps a property of the invoice - for example the seller's VAT ID - to an email address. This way you decide yourself who receives the feedback. Example recipients.csv:
DE123456789;invoices@supplier-a.example
DE987654321;accounting@supplier-b.example
  1. Fallback recipient: If neither the CSV file nor the invoice provides an address, the message goes to an internal mailbox such as clarification@my-company.com. From there you forward it manually.

Recommendation: CSV mapping for the most important suppliers, fallback to the address from the invoice, fallback recipient for the rest.


Step 2: Create a profile for invalid invoices

  1. Click New profile... and name it, for example, "Feedback to invoice issuers". Choose the same processing mode and the same monitored folder as in the regular profile.
  2. Filter page: Add, property Validation result (group Validation), operator is, value Invalid. Add a second line with OR and the value Schema error. Invoices with warnings are valid and get no feedback.
  3. Make sure the profile is placed before the regular profile in the profile list. Profiles are applied in list order; the list is sorted by name.
  4. If the invalid invoice should not end up in the normal archive afterwards, add the Move file task to a clarification folder and check Do not apply further profiles after successful processing with this profile on the General page (see the how-to "Validate e-invoices and save validation reports", step 4). Without this option, the regular profile processes the file afterwards as usual.

Step 3: Set up the "Send file" task

Click Add → Send file in the task list and fill in the Message tab:

  1. Type: Email address from CSV mapping. Enter the CSV file, <SellerVATaxRegistration> as the placeholder, ; as the delimiter, column 1 for the placeholder value and column 2 for the email address. If you only want to use the address from the invoice, choose the type Fixed email address instead and enter <SellerContactEmailAddress>.
  2. Check If no match: use the email address from the invoice.
  3. Enter the internal mailbox as the fallback recipient, for example clarification@my-company.com.
  4. The preview shows the address that would apply to the profile's first example invoice - with the source in brackets, such as DE123456789 → invoices@supplier-a.example or ... → office@supplier.example (address from the invoice).
  5. BCC: your internal mailbox, so every feedback message also reaches you.
  6. Subject: for example Your invoice <InvoiceId> dated <InvoiceDate>: formal check failed
  7. Message: Use the placeholders <ValidationSummary> (result with counts) and <ValidationFindings> (list of findings). Both are in the placeholder menu under Invoice data → Validation. An example:
Dear Sir or Madam,

Your e-invoice <InvoiceId> dated <InvoiceDate> did not pass the formal check according to EN 16931.
Result: <ValidationSummary>

Findings:
<ValidationFindings>

Please find the complete validation report attached. Kindly send us a corrected invoice.

Kind regards
Accounting, My Company Ltd.
  1. Check Attach validation report (HTML). For every finding, the report names the rule, the rule text and the location as well as the hash of the checked data; the issuer can reproduce it with the KoSIT validator.
  2. For the introduction, also check Do not send message, but only save it in the draft folder. This way you review the first feedback messages before anything leaves the house.
Send file task with Message tab, recipient, subject and message

If you format the message as HTML (Format message as HTML), the program inserts the list of findings with line breaks (<br>). In plain-text messages, every finding is on its own line.


Step 4: Test with drafts

  1. Open the profile's Result preview with an invalid example invoice. The Validation line shows the result, the Send file task shows the recipient and the suffix + ...-ValidationReport.html.
  2. Place an invalid invoice in the monitored folder. After processing, the Email drafts (1) button appears in the toolbar. Open the draft and check recipient, text, list of findings and attachments (see chapter 50.4).
  3. In the log, the result column shows the recipient - after a fallback with the source in brackets, for example clarification@my-company.com (fallback recipient).

Step 5: Enable sending

Remove the check mark Do not send message, but only save it in the draft folder. Keep the BCC recipient. If you send many feedback messages, the pause between email transmissions in the program options helps against your provider's sending limits (see chapter 40.4).


Good to know

  • The feedback only concerns invalid invoices and schema errors. Invoices with warnings are valid.
  • <ValidationFindings> lists errors before warnings, at most 50 findings; notes are omitted. Further findings are in the attached validation report.
  • For ZUGFeRD PDFs, the report also contains the result of the PDF envelope (PDF/A-3, Factur-X metadata, embedding; see chapter 50.5.4). Findings BR-HYBRID-... have to be fixed by the sender's invoicing software.
  • The formal check does not replace a check of the content. Whether an invoice is rejected is still decided by your accounting department.
  • The internal message Send message for invalid e-invoices (Options → Processing, see chapter 40.6.6) works independently and informs your own team.
  • A missing CSV file remains an error in the log; the fallbacks do not hide configuration errors.

Common issues

Problem Solution
The log reports "Invalid recipient email address" No CSV match and no fallback: check If no match: use the email address from the invoice or enter a fallback recipient
The log reports "CSV file of the recipient mapping not found" Check the path; with the Windows service, use a UNC path instead of a mapped drive letter (see chapter 60.1)
The message contains no findings <ValidationFindings> lists errors and warnings only; check that validation is enabled and that the profile only captures invalid invoices
List of findings in the HTML message without line breaks Check Format message as HTML - then every finding is on its own line
A supplier receives feedback for invoices with warnings Check the filter: only Invalid and Schema error, not Valid with warnings
Feedback should only go to certain suppliers Use the CSV mapping only, fallback to the invoice off, internal fallback recipient - then external parties are reached only via the addresses in the CSV file

Further reading

Start your no-obligation, 30-day free trial of Automatic X-Invoice Processor now ...     Download