E_0517 — Check invoice for the services of price sheet A again

Step	Check	Result	Code	Note
1	Was the MSB able to refute all objections of the invoice recipient?	no	A25	Cluster: Rejection at header level The invoice recipient continues to refuse payment of the invoice because the MSB was unable to refute all objections of the invoice recipient. Note: The objection must be described in the response.
—	—	yes	→ Step 10	—
10	Does the invoice meet further requirements pursuant to §14 Abs. 4 UStG?	no	A01	Cluster: Rejection at header level Invoice does not comply with §14 Abs. 4 UStG Note: The rejection must be substantiated.
—	—	yes	→ Step 20	—
20	Is the invoice date ≤ the receipt date?	no	A02	Cluster: Rejection at header level Invoice date is in the future
—	—	yes	→ Step 30	—
30	Is the invoice date < the execution date/service period?	yes	A03	Cluster: Rejection at header level The invoice date is before the execution date/service period.
—	—	no	→ Step 40	—
40	Is the invoice based on an order placement?	no	A04	Cluster: Rejection at header level The invoice recipient refuses payment because the invoice is not based on any order placement.
—	—	yes	→ Step 50	—
50	Does the invoice number used in this invoice already exist from the invoice issuer?	yes	A05	Cluster: Rejection at header level Invoice number has already been used
—	—	no	→ Step 60	—
60	Is the amount due ≥ zero?	no	A06	Cluster: Rejection at header level No refund can arise in the billing of the MSB.
—	—	yes	→ Step 70	—
70	Is the due date deadline undercut? Note: undercut due date means: payment term ≤ 10 WT from the invoice receipt date	yes	A07	Cluster: Rejection at header level The payment term has been undercut.
—	—	no	→ Step 80	—
80	Is a valid price sheet “price sheet configurations” available for every point in time of the billed execution date/service period? Note: Several consecutive price sheets may exist for one billing period. Price sheet A of MSB is called price sheet configurations in PRICAT.	no	A08	Cluster: Rejection at header level The invoice recipient refuses payment. There is no valid price sheet.
—	—	yes	→ step 90	—
90	Has a previously unspecified error occurred in the header section of the invoice?	yes	A90	Cluster: Rejection at header level Other error at header level. Note: The identified problem must be described/named in the response. End of usability: 01.10.2026 00:00
—	—	no	→ Step 300	—
from 300	Starting with the first line item, the following checks are performed for each line item. If the first error occurs in a line item, the further checks are to be performed as well, as far as this is still possible. All errors found in the detail section are to be reported, naming the respective line item.	—	—	—
300	Was the article ID from the order placement used in the invoice line item?	no	A09	Cluster: Rejection at line item level The article ID from the order placement was not used in the invoice line item.
—	—	yes	→ Step 310	—
310	Was the service to be billed performed by the MSB?	no	A10	Cluster: Rejection at line item level The invoice recipient refuses payment because the service to be billed was not successfully performed by the MSB.
—	—	yes	→ Step 320	—
320	Does the price in the invoice line item match the price from the price sheet that is valid at the point in time of the execution date / for the billing period of the service to be billed?	no	A11	Cluster: Rejection at line item level The price in the invoice line item does not correspond to the price from the price sheet.
—	—	yes	→ Step 330	—
330	Is the correct VAT rate valid for this point in time/time period stated for the invoice line item?	no	A12	Cluster: Rejection at line item level The valid VAT rate for the invoice line item for this point in time/time period was not stated correctly.
—	—	yes	→ Step 350	—
350	Is the service period or the execution date of the invoice line item within the specified service period at header level?	no	A13	Cluster: Rejection at line item level The service period or the execution date of the invoice line item is not identical to the service period from the header section.
—	—	yes	→ Step 360	—
360	Does another invoice line item with an identical article ID and an identical or overlapping service period or an identical execution date exist in this invoice?	yes	A14	Cluster: Rejection at line item level This invoice contains a further invoice line item with an identical article ID and an identical or overlapping service period or identical execution date.
—	—	no	→ Step 370	—
370	Has the article ID already been billed in a previous, non-cancelled invoice for the identical service period or identical execution date?	yes	A15	Cluster: Rejection at line item level The article ID has already been billed in a previous, non-cancelled invoice for the identical service period or identical execution date. Note: the invoice number must be stated
—	—	no	→ Step 420	—
420	Is there a calculation error in the invoice line item?	yes	A20	Cluster: Rejection at line item level There is a calculation error
—	—	no	→ Step 430	—
430	Has a previously unspecified error occurred in the invoice line item?	yes	A99	Cluster: Rejection at line item level Other error at line item level. Note: The identified problem must be described/named in the response. End of usability: 01.10.2026 00:00
—	—	no	→ Step 440	—
440	Are there further invoice line items to be checked?	yes	→ Step 300	—
—	—	no	→ Step 450	—
450	Has an error occurred in at least one invoice line item?	yes	End	Note: All response codes detected at line item level must be transmitted for each detail section identified as faulty, stating the line item number.
—	—	no	→ Step 500	The check of the EBD is continued in the summary section.
from 500	The following check takes place at the summary level of the EBD, although it is a summary check of the line item level: since no line item number can be given when the line item number from the confirmed offer is missing, the REMADV structure for transmitting errors at summary level must be used to transmit the error.	—	—	—
500	Are line items still missing that are agreed via the confirmed quotation and are therefore expected in the invoice?	yes	A21	Cluster: Rejection at summary level Expected line item not present Note: The line items from the quotation that are not contained must be named, stating the line item number from the confirmed quotation.
—	—	no	→ Step 510	—
510	For the stated tax rate, does the taxable amount match the sums of the individual line items of this invoice with this tax rate?	no	A22	Cluster: Rejection at summary level The taxable amount named does not match the sum of the individual line items of the tax rate. Note: The tax rate (from DE5278) and the control category (from DE5305) of the SG52 TAX must be named.
—	—	yes	→ Step 520	—
520	For this tax rate, does the stated tax amount match the sum of all invoice line items (net) of this invoice to which this tax rate is assigned, multiplied by this tax rate?	no	A23	Cluster: Rejection at summary level The sum of all invoice line items (net) of this invoice to which this tax rate is assigned, multiplied by this tax rate, does not correspond to the tax amount stated for this tax rate. Note: The tax rate (from DE5278) and the control category (from DE5305) of the SG52 TAX must be named.
—	—	yes	→ Step 530	—
530	Are there further tax rates to be checked?	yes	→ Step 510	—
—	—	no	→ Step 540	—
540	Does the invoice amount match the sum of all invoice line items (taxable amount) plus the respective tax amount?	no	A24	Cluster: Rejection at summary level The invoice amount (taxable amount including tax amount) of the total is not correct.
—	—	yes	→ Step 550	—
550	Has a previously unspecified error occurred in the summary section?	yes	A96	Cluster: Rejection at summary level Other Note: The identified problem must be described/named in the response. End of usability: 01.10.2026 00:00
—	—	no	→ Step 560	—
560	Has at least one error occurred in the summary level?	yes	End	Cluster: Rejection at summary level Note: All response codes identified at summary level must be transmitted.
—	—	no	End	Cluster: Consent Announce payment of the invoice and take it into account in the payment run.