E_0259 — Process invoice

Step	Check	Result	Code	Note
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 end of the billing period/execution date?	yes	A03	Cluster: Rejection at header level The invoice date is before the end of the billing period/execution date.
—	—	no	→ Step 40	—
40	Is the recipient of the invoice assigned to the stated metering location for at least one day of the stated billing period/execution date?	no	A04	Cluster: Rejection at header level The MSB is not assigned to the metering location for a single day of the billing period/execution date.
—	—	yes	→ Step 50	—
50	Is the recipient of the invoice assigned to the stated metering location for the entire stated billing period/execution date?	no	A05	Cluster: Rejection at header level The MSB refuses payment. A rejection of the payment is substantiated by the MSB. Note: The MSB states the expected billing period/expected execution date.
—	—	yes	→ Step 60	—
60	Does the invoice number used in this invoice already exist from the invoice issuer?	yes	A06	Cluster: Rejection at header level Invoice number has already been used
—	—	no	→ Step 70	—
70	Is the billing period/execution date of the invoice already contained in a previous, accepted and not cancelled invoice?	yes	A07	Cluster: Rejection at header level The invoice contains a time interval already billed/ a point in time already billed.
—	—	no	→ Step 80	—
80	Is the amount due ≥ zero?	no	A08	Cluster: Rejection at header level No refund can arise in the billing.
—	—	yes	→ step 90	—
90	Is the due date deadline undercut? (payment term ≤ 10 WT from the invoice receipt date)	yes	A09	Cluster: Rejection at header level The payment term has been undercut.
—	—	no	→ Step 100	—
100	Is this a device takeover (purchase/ transfer of use)?	yes	→ Step 110	—
—	—	no	→ Step 130	—
110	Was the quotation of the MSB named in the invoice confirmed in the order confirmation in the device takeover process for this metering location?	no	A10	Cluster: Rejection at header level The quotation of the MSB in the order confirmation in the device takeover process for this metering location was not confirmed.
—	—	yes	→ Step 120	—
120	Is the order placement specified in the invoice the most recent confirmed order placement that begins exactly at this point in time?	no	A11	Cluster: Rejection at header level The reference is not to the most recent order placement at this point in time.
—	—	yes	→ Step 130	—
130	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.04.2027 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	Is this a device takeover (purchase/ transfer of use)?	yes	→ Step 310	—
—	—	no	→ Step 320	—
310	Does the invoice line item match the confirmed quotation?	no	A12	Cluster: Rejection at line item level The invoice line item does not match the confirmed quotation.
—	—	yes	→ Step 320	—
320	Is the correct VAT rate valid for this time period stated for the invoice line item?	no	A13	Cluster: Rejection at line item level The valid VAT rate for the invoice line item for this time period was not stated correctly.
—	—	yes	→ Step 330	—
330	Is the end date of the invoice line item equal to or after the end date of the billing period / execution date?	yes	A14	Cluster: Rejection at line item level The end date of the invoice line item is equal to or after the end date of the billing period/ execution date.
—	—	no	→ Step 340	—
340	Is the start date of the invoice line item before or equal to the start date of the billing period? Note: When the execution date is used in the invoice, answer the check step with yes.	yes	A15	Cluster: Rejection at line item level The start date of the invoice line item is before the start date of the billing period.
—	—	no	→ Step 345	—
345	Does the invoice line item bill the correct billing period?	no	A25	Cluster: Rejection at line item level The wrong billing period is billed. Note: The LF states the expected billing period.
—	—	yes	→ Step 350	—
350	Does the price in the line item match the agreed price?	no	A16	Cluster: Rejection at line item level The price in the invoice line item does not match the agreed price.
—	—	yes	→ Step 360	—
360	Is there a calculation error in the invoice line item?	yes	A17	Cluster: Rejection at line item level There is a calculation error.
—	—	no	→ Step 370	—
370	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.04.2027 00:00
—	—	no	→ Step 380	—
380	Are there further invoice line items to be checked?	yes	→ Step 300	—
—	—	no	→ Step 390	—
390	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 agreed line items missing in the invoice?	yes	A18	Cluster: Rejection at summary level Expected line item not present. Note: Missing line items must be described in the free text field.
—	—	no	→ Step 510	—
from 510	Starting with check step 510, the following checks are performed for each summary line. If the first error occurs in a summary line, the further checks are to be performed as well, as far as this is still possible. All errors found in the summary section are transmitted to the MSB as the result with the corresponding rejection codes. The following checks are to be performed for each combination of tax rate and tax category.	—	—	—
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	A19	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	A20	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	A21	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.04.2027 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.