E_0407 — Check grid usage settlement again

Step	Check	Result	Code	Note
0	Was the NB able to refute all objections of the LF?	no	AC1	Cluster: Rejection at header level The LF continues to refuse payment of the invoice because the NB was unable to refute all objections of the LF. Note: The objection must be described in the response.
—	—	yes	→ Step 1	—
1	Is the recipient of the invoice assigned to the stated market location for at least one day of the stated billing period?	no	A01	Cluster: Rejection at header level The LF is not assigned to the market location for a single day of the billing period.
—	—	yes	→ Step 4	—
4	Is the recipient of the invoice assigned to the stated market location for the entire stated billing period?	no	A02	Cluster: Rejection at header level The LF is not assigned to the market location for the entire billing period. Note: The LF states the expected billing period.
—	—	yes	→ Step 7	—
7	Has it been agreed with the NB that the recipient of the invoice is the payer of the invoice?	no	A03	Cluster: Rejection at header level The invoice recipient is not the payer of the invoice.
—	—	yes	→ Step 10	—
10	Is the NB assigned to the specified market location for at least one day of the specified billing period?	no	A04	Cluster: Rejection at header level The NB is not assigned to the market location for a single day of the billing period.
—	—	yes	→ Step 13	—
13	Is the NB assigned to the specified market location for the entire specified billing period?	no	A05	Cluster: Rejection at header level The NB is not assigned to the market location for the entire billing period.
—	—	yes	→ Step 16	—
16	Does the billing period contain at least one day of the calendar year in which an intra-year grid operator change was carried out at the market location?	yes	→ Step 17	—
—	—	no	→ Step 20	—
17	Is the start of the billing period ≥ 01.01.2026, 00:00?	yes	→ Step 18	—
—	—	no	→ Step 19	—
18	Is the MP-ID of the NBA specified in the grid operator prices segment (RFF+Z56)?	no	AF3	Cluster: Rejection at header level A grid operator change took place at the market location within the year during the service period, and the NBA of the market location was not stated in the grid operator prices segment (RFF+Z56).
—	—	yes	→ Step 20	—
19	Are only the prices of the NBA invoiced?	no	AF5	Cluster: Rejection at header level A grid operator change took place at the market location within the year during the service period, and at least one price is not identical to that of the NBA.
—	—	yes	→ Step 20	—
20	Is the invoice date ≤ the receipt date at the LF?	no	A07	Cluster: Rejection at header level Invoice date is in the future.
—	—	yes	→ Step 22	—
22	Is the invoice date < the end of the billing period?	yes	→ Step 23	—
—	—	no	→ Step 26	—
23	Is the invoice type an instalment invoice (ABS)?	no	A08	Cluster: Rejection at header level Although this is not an instalment invoice, the invoice date is < the end of the billing period.
—	—	yes	→ Step 24	—
24	Is the due date deadline met? Note: The due date must be ≥ 10 WT after the invoice date.	no	AC7	Cluster: Rejection at header level The deadline for the instalment invoice was not met.
—	—	yes	→ Step 25	—
25	Is the due date > the end of the billing period?	no	AC8	Cluster: Rejection at header level The requirement that payment be made in arrears was not met.
—	—	yes	→ Step 26	—
26	Does the invoice number used in this invoice already exist from the invoice issuer?	yes	A09	Cluster: Rejection at header level Invoice number has already been used.
—	—	no	→ Step 27	—
27	Does the invoice not meet further requirements pursuant to §14 Abs. 4 UStG?	yes	A06	Cluster: Rejection at header level Invoice does not comply with §14 UStG. Note: The rejection must be substantiated.
—	—	no	→ Step 28	—
28	Is the amount due ≥ zero?	yes	→ Step 31	—
—	—	no	→ Step 34	—
31	Is the due date deadline undercut? Note: undercut due date means: payment term ≤ 10 WT from the invoice receipt date	yes	A10	Cluster: Rejection at header level The payment term has been undercut.
—	—	no	→ Step 37	—
34	Is the due date deadline exceeded? Note: exceeded due date means: payment term > 10 WT from the invoice date. Under NNV/LRV § 8 Billing, payment and default, the issue date of the refund is decisive for refunds.	yes	A11	Cluster: Rejection at header level The payment term has been exceeded.
—	—	no	→ Step 37	—
37	Is the invoice a special invoice (SOR)?	yes	→ Step 40	—
—	—	no	→ Step 48	—
40	Is the message date of the special invoice ≤ 01.01.2023 00:00?	yes	A79	Cluster: Rejection at header level The message date of the special invoice is ≤ 01.01.2023 00:00
—	—	no	→ Step 43	—
43	Has the invoice underlying the special invoice already been corrected with at least one of the types of special invoice named in this invoice? Notes: Only the non-cancelled special invoices that refer to the same invoice as the present special invoice are relevant. The types of special invoice are to be taken from the INVOIC.	yes	A80	Cluster: Rejection at header level The type of the present billing has already been corrected in a previous special invoice. Note: All affected special invoices must be stated.
—	—	no	→ Step 46	—
46	Is the special invoice in order from the point of view of the invoice recipient?	yes	End	Cluster: Consent Announce payment of the invoice and take it into account in the payment run.
—	—	no	A95	Cluster: Rejection at header level From the invoice recipient's point of view, the special invoice is not in order. Note: The rejection must be substantiated.
48	Is the invoice type a 13th invoice (13R)?	yes	→ Step 54	—
—	—	no	→ Step 49	—
49	Is the billing period of the invoice already contained in a previous, accepted and not cancelled invoice (periodic invoice, interim invoice, final invoice, monthly invoice or integrated 13th invoice (13I))?	yes	A12	Cluster: Rejection at header level Billing period is billed twice. Note: The LF states the invoice number of the invoice in which part of, or all of, the period billed in this invoice has already been billed.
—	—	no	→ Step 52	—
52	Is the invoice type an instalment invoice (ABS)?	yes	→ Step 70	—
—	—	no	→ Step 55	—
54	Is the billing period of the invoice already contained in a previous, accepted and not cancelled integrated 13th invoice (13I)?	yes	AE1	Cluster: Rejection at header level Billing period is billed twice. Note: The LF states the invoice number of the invoice in which part of, or all of, the period billed in this invoice has already been billed.
—	—	no	→ Step 55	—
55	Does the invoice reference a received delivery note?	no	A13	Cluster: Rejection at header level The LF does not have a delivery note for the invoice.
—	—	yes	→ Step 58	—
58	Does the invoice reference a delivery note that has not been cancelled?	no	A14	Cluster: Rejection at header level The delivery note for the invoice was canceled.
—	—	yes	→ Step 61	—
61	Does the invoice reference a delivery note rejected within the deadline?	yes	→ Step 64	—
—	—	no	→ Step 62	—
62	Has the deadline for the response message to the delivery note referenced by the invoice already expired?	no	AE0	Cluster: Rejection at header level The grid operator transmitted the invoice before the deadline for the response message to the delivery note had expired.
—	—	yes	→ Step 67	—
64	Has the NB objected to the rejection of the delivery note and was it able to refute the reasons for rejection of the LF?	no	A15	Cluster: Rejection at header level The delivery note for the invoice was successfully rejected and was not contested and refuted by the NB.
—	—	yes	→ Step 67	—
67	Is the entire billing period of the invoice (JVR, ZVR, ABR, MVR, 13I, 13R) contained in the referenced delivery note?	no	A16	Cluster: Rejection at header level The referenced delivery note does not contain the entire billing period of the invoice. Note: The LF states the time period that is not contained in the referenced delivery note.
—	—	yes	→ Step 70	—
70	Does the invoice type (e.g. instalment invoice or monthly invoice) of the invoice to be checked for the transmitted time period match the grid usage billing variant stored at the market location (basic price/energy price or energy price/demand price), which is derived from the article ID or group article ID if the grid usage billing variant was not exchanged explicitly via corresponding codes? The following invoice types are possible for the grid usage billing variant basic price/energy price: final invoice (ABR) instalment invoice (ABS) periodic invoice (JVR) interim invoice (ZVR) The following invoice types are possible for the grid usage billing variant demand price/energy price: MVR monthly invoice (MVR) integrated 13th invoice (13I) 13th invoice (13R)	no	A17	Cluster: Rejection at header level Invoice type does not match the agreed grid usage billing variant.
—	—	yes	→ Step 73	Usage note: the invoice type (13th invoice) 13R can no longer be used for time periods ≥ 01.01.2023 00:00.
73	Is the end of the billing period ≥ 01.01.2023 00:00?	yes	→ Step 74	—
—	—	no	→ step 82	—
74	Is the start of the billing period ≥ 01.01.2026, 00:00?	yes	→ Step 75	—
—	—	no	→ Step 76	—
75	Is the invoice type an instalment invoice (ABS)?	yes	→ Step 76	—
—	—	no	→ Step 77	—
76	Is there an electronic price sheet grid usage for every point in time of the billing period in which NAD+MS is identical to NAD+MS of INVOIC?	no	AF4	Cluster: Rejection at header level The LF does not have a price sheet for grid usage.
—	—	yes	→ Step 79	—
77	Is there an electronic price sheet grid usage for every point in time of the billing period in which NAD+MS and RFF+Z56 are identical to NAD+MS and RFF+Z56 of INVOIC?	no	A18	Cluster: Rejection at header level The LF does not have a price sheet for grid usage.
—	—	yes	→ Step 79	—
79	Is the start of the billing period ≥ 01.01.2023 00:00?	yes	→ Step 80	—
—	—	no	→ step 82	—
80	Is the invoice type one of the following: periodic invoice (JVR) interim invoice (ZVR) final invoice (ABR) instalment invoice (ABS) monthly invoice (MVR) integrated 13th invoice (13I)?	yes	→ step 82	—
—	—	no	A19	Cluster: Rejection at header level This is an impermissible invoice type. Usage note: The invoice type 13th invoice (13R) can no longer be used for time periods whose start date is ≥ 01.01.2023 00:00.
82	Has a previously unspecified error occurred in the header section of the invoice?	yes	A90	Cluster: Rejection at header level Other error in the header data. Note: The identified problem must be described/named in the response. End of usability: open
—	—	no	→ Step 100	Note: The check at line item level starts here.
from 100	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.	—	—	—
100	Is the end date of the line item period in the invoice line item ≤ 01.01.2023 00:00?	yes	→ Step 105	Note: The present EBD E_0407_erneut Netznutzungsrechnung prüfen is not continued for this line item and no codes of this EBD are used. For this check step, this invoice line item is checked exclusively according to the check logic applicable before the use of the electronic grid usage price sheet, with the corresponding codes from code list S_0104. If errors are detected when applying code list S_0104, they must be noted. Once the check of the invoice line item against code list S_0104 has been completed, continue with the EBD E_0407_erneut Netznutzungsrechnung prüfen at check step 105.
—	—	no	→ Step 110	—
105	Are there further invoice line items to be checked?	yes	→ Step 100	—
—	—	no	→ Step 800	—
110	Is the invoice type one of the following: • periodic invoice (JVR) • final invoice (ABR) • interim invoice (ZVR) • monthly invoice (MVR) • integrated 13th invoice (13I)?	yes	→ Step 115	—
—	—	no	→ Step 125	Note: This is an instalment invoice (ABS).
115	Is the start of the line item period in the invoice line item < 01.01.2023 00:00?	yes	A20	Cluster: Rejection at line item level The line item has not been split into < and ≥ 01.01.2023 00:00.
—	—	no	→ Step 125	—
120	Is an article number used?	yes	A22	Cluster: Rejection at line item level No article number is permitted for the line item period and the invoice type.
—	—	no	→ Step 125	—
125	Is there a calculation error in the invoice line item?	yes	A23	Cluster: Rejection at line item level There is a calculation error. Note: The calculation error is stated in the rejection.
—	—	no	→ Step 130	—
130	Is the correct VAT rate valid for this time period stated for the invoice line item?	no	A24	Cluster: Rejection at line item level The VAT rate contained in the line item is not correct.
—	—	yes	→ Step 135	—
135	Is the end date of the invoice line item > the end date of the billing period?	yes	A25	Cluster: Rejection at line item level The end date of this line item is > the end date of the billing period.
—	—	no	→ Step 140	—
140	Is the invoice type an instalment invoice (ABS)?	yes	→ Step 200	—
—	—	no	→ Step 145	—
145	Is the invoice type one of the following: periodic invoice (JVR) final invoice (ABR) interim invoice (ZVR)?	yes	→ Step 300	—
—	—	no	→ Step 150	—
150	Is the invoice type a monthly invoice (MVR)?	yes	→ Step 400	—
—	—	no	→ Step 600	Note: This is the invoice type integrated 13th invoice (13I).
200	Is the instalment amount plausible? Note: For market locations with the metering classification kME/mME, plausibility is checked on the basis of the exchanged JVP. For market locations with the metering classification iMS, no JVP is exchanged, so the plausibility checks must be carried out on the basis of other criteria, such as historical values or information provided by the customer.	no	A26	Cluster: Rejection at line item level The instalment payment amount is not plausible. Note: The LF states the expected instalment payment amount.
—	—	yes	→ Step 205	—
205	Is the start date of the line item period < the start date of the billing period?	yes	A81	Cluster: Rejection at line item level The start date of the line item period is < the start date of the billing period.
—	—	no	→ Step 210	—
210	Is the billing period of the instalment invoice already contained in a previous, accepted and not cancelled invoice (periodic invoice, interim invoice, monthly invoice or 13I)?	yes	A27	Cluster: Rejection at line item level Billing period is billed twice. Note: The LF states the invoice number of the invoice in which part of, or all of, the period billed in this invoice has already been billed.
—	—	no	→ Step 215	—
215	Does the billing period of the instalment invoice overlap a preceding instalment invoice by more than 10 days?	yes	A82	Cluster: Rejection at line item level Overlap of the instalment period too large. Note: The instalment invoice with which the billing period overlaps must be stated.
—	—	no	→ Step 220	—
220	Is the article number valid for an instalment invoice?	no	A28	Cluster: Rejection at line item level The article number used in this line item is not valid.
—	—	yes	→ Step 225	—
225	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: open
—	—	no	→ Step 230	—
230	Are there further invoice line items to be checked?	yes	→ Step 100	—
—	—	no	→ Step 800	—
300	Is the start date of the line item period < the start date of the billing period?	yes	A83	Cluster: Rejection at line item level The start date of the line item period is < the start date of the billing period.
—	—	no	→ Step 305	—
305	Was the article ID used in the invoice line item exchanged in the master data for the entire line item period of this line item (either indirectly by stating the associated group article ID or by directly naming the article ID)?	no	A84	Cluster: Rejection at line item level The article ID used in the specified line item should not have been listed for the entire line item period. Note: Within the line item period the supplier states the time period in which this article ID is not valid.
—	—	yes	→ Step 315	—
315	From the point of view of the LF, must the article ID not be stated in this invoice because, from the point of view of the LF, it does not fit this market location and the metering locations assigned to it for the line item period?	yes	A85	Cluster: Rejection at line item level The master data item of the line item is incorrect from the point of view of the LF.
—	—	no	→ Step 320	—
320	Is the article ID permissible for this invoice type for this line item period?	no	A31	Cluster: Rejection at line item level This article ID is not permitted for this invoice type in the stated line item period.
—	—	yes	→ Step 322	—
322	Is this article ID 1-02-0-015?	yes	→ Step 345	—
—	—	no	→ Step 325	—
325	Are the surcharges and discounts exchanged in the master data taken into account correctly in the line item for the article ID? Note: If no surcharges or discounts are listed in the line item checked and none were exchanged/announced via master data, this question is to be answered with “yes”.	no	A32	Cluster: Rejection at line item level Surcharge or discount was not taken into account as exchanged in the master data.
—	—	yes	→ Step 326	—
326	Does the article ID to be checked belong to one of the following group article IDs: 1-10-4, 1-10-5, 1-10-6, 1-08-2-AGS-K and 1-08-5-AGS-KG?	yes	→ Step 327	—
—	—	no	→ Step 330	—
327	Is there at least one further resultant for the article ID under check with an article ID that belongs to the group article ID?	yes	→ Step 328	—
—	—	no	→ Step 330	—
328	Does the sum of the quantities from all the resultants formed for this group article ID match the quantities of the delivery note? Note: To do this, all resultants of the group article ID concerned must be formed. The quantity must be taken from each of these resultants. These quantities must be summed.	no	AE2	Cluster: Rejection at line item level The LF rejects the invoice because the sum of the quantities does not match the delivery note.
—	—	yes	→ Step 335	—
330	Do the individual items of the quantities in the delivery note match the quantity of the billed item of the invoice? Note: According to GPKE, the billing energy quantities stated in the grid usage invoice must match, in their amount and over the time period, the billing energy quantities previously transmitted by the NB at market location level in the delivery note.	no	A33	Cluster: Rejection at line item level The LF rejects the invoice with reference to the line item that does not match the quantities on the transmitted delivery note.
—	—	yes	→ Step 335	—
335	Are all plausible energy quantities from MSB required for the check available?	no	A34	Cluster: Rejection at line item level The energy quantity/quantities is/are missing and a claim has already been raised via ORDERS. Note: The LF states the business transaction number of the ORDERS with which the missing energy quantity was claimed.
—	—	yes	→ Step 340	—
340	Are all values required for the check available?	no	A39	Cluster: Rejection at line item level Values from the MSB are missing or incorrect values were sent by the MSB and a claim for these has already been raised via ORDERS. Note: The LF states the business transaction number of the ORDERS with which the missing or incorrect values were claimed.
—	—	yes	→ Step 345	—
345	Has a price been announced in the price sheet for the article ID?	no	→ Step 355	—
—	—	yes	→ Step 350	—
350	Was the correct price from the price sheet for the article ID used in the invoice? Note: For invoices whose billing period starts ≥ 01.01.2026, 00:00, this means that the price sheet to be used is the one in which the MP-ID in the segment grid operator prices (RFF+Z56) of the INVOIC is identical to the MP-ID in grid operator prices (RFF+Z56).	no	A35	Cluster: Rejection at line item level The price for the article is incorrect. Note: The LF communicates the expected price for the article ID.
—	—	yes	→ Step 395	—
355	Was the price for the article ID exchanged via the master data?	no	→ Step 365	Note: Maximum rates of the Konzessionsabgabenverordnung are exchanged neither via the price sheet nor via the master data.
—	—	yes	→ Step 360	—
360	Was the correct price from the previously exchanged master data for the article ID used in the invoice?	no	A36	Cluster: Rejection at line item level The price for the article is incorrect. Note: The LF communicates the expected price for the article ID.
—	—	yes	→ Step 395	—
365	Does the price for the article ID result from statutory levies and surcharges? Note: The following levies and surcharges are affected: § 19 StromNEV surcharge surcharge for interruptible loads offshore grid surcharge concession levy levy KWKG	no	A37	Cluster: Rejection at line item level The price was not stated (neither in the price sheet nor via master data) and is also not known from “legal requirements”.
—	—	yes	→ Step 370	—
370	Does the price of the article ID match the statutory requirement?	no	A38	Cluster: Rejection at line item level The NB used the incorrect price for the statutory levy or duty. Note: The LF states the expected price for the statutory levy or duty.
—	—	yes	→ Step 395	—
395	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: open
—	—	no	→ Step 399	—
399	Are there further invoice line items to be checked?	yes	→ Step 100	—
—	—	no	→ Step 800	—
400	Was the article ID used in the invoice line item exchanged in the master data for the entire line item period of this line item (either indirectly by stating the associated group article ID or by directly naming the article ID)? Note: In the case of a supplier switch during the year, the article IDs from the registration confirmation or master data change apply from 01.01. of the current calendar year and are also to be used for checking the invoice line items of the grid usage settlement for time periods before the supplier switch.	yes	→ Step 415	—
—	—	no	→ Step 405	—
405	Is the article ID used in the invoice line item the article ID for the special contract customer concession levy or for the municipality-specific special contract customer concession levy?	no	A46	Cluster: Rejection at line item level The article ID used in the specified line item should not have been listed for the entire line item period. Note: Within the line item period the supplier states the time period in which this article ID is not valid.
—	—	yes	→ Step 410	Note: The NB bills the concession levy for special contract customers even though the concession levy for tariff customers was agreed for this market location. This procedure is permitted because the article ID cannot be changed by means of a master data change.
410	Have one or more concession levy article IDs that do not correspond to the special contract customer concession levy been agreed via the master data over the line item period?	no	AC9	Cluster: Rejection at line item level The special contract customer concession levy is billed although no billing of the concession levy was agreed via the master data exchange.
—	—	yes	→ Step 430	—
415	From the point of view of the LF, must the article ID not be stated in this invoice because, from the point of view of the LF, it does not fit this market location and the metering locations assigned to it for the line item period?	yes	A43	Cluster: Rejection at line item level This article ID is not permitted for this invoice type in the specified line item period.
—	—	no	→ Step 420	—
420	Is the article ID permissible for this invoice type for this line item period?	no	A42	Cluster: Rejection at line item level This article ID is not permitted for this invoice type in the stated line item period.
—	—	yes	→ Step 422	—
422	Is this an article ID belonging to group article ID 1-07-1 or 1-07-2?	yes	→ Step 427	—
—	—	no	→ Step 424	—
424	Is this article ID 1-01-6-005 or 1-01-9-001 or 1-01-9-002 or 1-07-4-001, or an article ID belonging to group article ID 1-03-8 or 1-03-9?	yes	→ Step 430	—
—	—	no	→ Step 425	—
425	Have the surcharges and discounts (incl. municipal discount) that were previously exchanged via master data been taken into account for the article ID? Note: If no surcharges or discounts are listed in the checked line item and none have been exchanged/announced via master data, this question is to be answered with „yes“.	no	A44	Cluster: Rejection at line item level Surcharge or discount was not taken into account as exchanged in the master data.
—	—	yes	→ Step 427	—
427	Is physical power billed with the article ID?	yes	→ Step 491	Note: No resultant and no corresponding resultant is formed with a physical power.
—	—	no	→ Step 430	—
430	Is there more than one item with this article ID?	yes	→ Step 435	—
—	—	no	→ Step 445	Note: This line item is the resultant with which the further checks are carried out.
435	Is there at least one further item with this article ID but a higher item number?	yes	→ Step 595	Note: The last item with this article ID has not yet been reached and therefore the resultant is not yet determined.
—	—	no	→ Step 440	Note: The last item with this article ID has been reached. The resultant of this article ID can therefore now be determined and is determined.
440	Does the determined result cover exactly one gapless time period to which a quantity, a price and an amount are assigned? Note: The same price must be assigned to all line items with the same article ID.	no	A87	Cluster: Rejection at line item level Determination of the resultant with this article ID failed.
—	—	yes	→ Step 445	—
445	Is the start of the time period of the resulting invoice < 01.01.2023 00:00?	yes	A88	Cluster: Rejection at line item level The resultant is < 01.01.2023 00:00.
—	—	no	→ Step 450	—
450	Is physical work billed with the article ID?	yes	→ Step 455	—
—	—	no	→ Step 470	—
455	Is the quantity of the resulting item negative?	yes	→ Step 595	Note: The resultant formed here consists of reversal line items and is therefore what is required in check 460 as the corresponding resultant; it must therefore not be used as the resultant in the invoice verification process.
—	—	no	→ Step 458	—
458	Do the start and the end of the time period of the resultant fall in different calendar months? Note: If the end date is the first day of the month at 00:00 of the month following the month in which the point in time at which the time period of the resultant starts falls, then, for the purposes of the question above, the start and end points lie within one month.	yes	→ Step 460	Note: In order to be able to carry out check step 460, the corresponding resultant must also be formed for the resultant.
—	—	no	→ Step 470	Note: If the resultant covers at most one calendar month, there can be no corresponding resultant for the resultant.
460	Does the time period of the corresponding resultant start at the same point in time as the time period of this resultant, and does the time period of the corresponding resultant contain no time period of the month in which the resultant ends?	no	A89	Cluster: Rejection at line item level The resultant does not match the corresponding resultant.
—	—	yes	→ Step 465	—
465	Does the corresponding resulting document reverse all line items of the preceding invoices (MVR)?	no	AA1	Cluster: Rejection at line item level Not all line items of previous MVR invoices were reversed. Note: The invoice numbers of the MVR must be stated.
—	—	yes	→ Step 470	—
470	Is the calculated (invoiced) quantity a physical energy value?	yes	→ Step 471	—
—	—	no	→ Step 495	—
471	Does the article ID to be checked belong to one of the following group article IDs: 1-10-4, 1-10-5, 1-10-6, 1-08-2-AGS-KG and 1-08-5-AGS-KG?	yes	→ Step 472	—
—	—	no	→ Step 475	—
472	Is there at least one further resultant for the article ID under check with an article ID that belongs to the group article ID?	yes	→ Step 473	—
—	—	no	→ Step 475	—
473	Does the sum of the quantities from all the resultants formed for this group article ID match the quantities of the delivery note? Note: To do this, all resultants of the group article ID concerned must be formed. The quantity must be taken from each of these resultants. These quantities must be summed.	yes	→ Step 480	—
—	—	no	AE3	Cluster: Rejection at line item level The LF rejects the invoice because the sum of the quantities does not match the delivery note.
475	Do the individual items of the quantities in the delivery note match the absolute amount of the quantity of the resulting item of the invoice? Note: According to GPKE, the billing energy quantities stated in the grid usage invoice must match, in their amount and over the time period, the billing energy quantities previously transmitted by the NB at market location level in the delivery note.	no	A45	Cluster: Rejection at line item level The LF rejects the invoice with reference to the line item that does not match the quantities on the transmitted delivery note. Population note: „Identification of the line/item in the document“: The LF states the highest line item number of the article ID for which the resultant of the invoice does not correspond to the quantity from the delivery note.
—	—	yes	→ Step 480	—
480	Are the load curves at the market location from MSB available for the period of the resulting values, or, in the case of a supplier switch during the year, the energy quantity and up to two maximum demand values from NB? Note: If the load curves at the market location from MSB are not available for the period of the resulting values, a complaint about them must first have been raised by LF with MSB before this question may be answered with no.	yes	→ Step 495	—
—	—	no	→ Step 485	—
485	Are the load profiles at the market location from the MSB missing for the time period of the resulting time series and was a complaint raised with the MSB?	yes	AA2	Cluster: Rejection at line item level Values from the MSB are missing or incorrect values were sent by the MSB and a claim for these has already been raised via ORDERS. Note: The LF states the business transaction number of the ORDERS with which the missing or incorrect values were claimed.
—	—	no	→ Step 490	—
490	Are the maximum demand and the energy quantity of the market location from the NB missing for the time period of the resulting time series for the period of the year before the supplier switch?	yes	AA3	Cluster: Rejection at line item level Because of the supplier switch within the year, the maximum demand and the energy quantity for the part of the year before the supplier switch, which the NB should have sent, are missing.
—	—	no	→ Step 495	—
491	Is the physical power specified in the line item < 0?	yes	→ Step 495	Note: This is a reversal item
—	—	no	→ Step 492	—
492	Is the physical power specified in the line item = 0?	yes	→ Step 599	Note: This line item is irrelevant for the invoice verification because it does not cause any costs. It can therefore be skipped unchecked
—	—	no	→ Step 494	—
494	Does the maximum demand stated in the item match the maximum demand of the delivery note?	no	AA8	Cluster: Rejection at line item level The LF rejects the invoice with reference to the line item that does not match the maximum demand of the delivery note.
—	—	yes	→ Step 495	—
495	Has a price been announced in the price sheet for the article ID?	yes	→ Step 500	—
—	—	no	→ Step 505	—
500	Was the correct price from the price sheet for the article ID used in the invoice?	no	A47	Cluster: Rejection at line item level The price for the article is incorrect. Note: The LF communicates the expected price for the article ID.
—	—	yes	→ Step 502	—
502	Is the calculated (invoiced) quantity a physical power value?	yes	→ Step 595	Note: Check of an item with power
—	—	no	→ Step 530	—
505	Was the price for the article ID exchanged via the master data?	no	→ Step 513	Note: Prices of the affected article ID are exchanged neither via the price sheet nor via the master data.
—	—	yes	→ Step 510	—
510	Was the correct price from the previously exchanged master data for the article ID used in the invoice?	no	A48	Cluster: Rejection at line item level The price for the article is incorrect. Note: The LF communicates the expected price for the article ID.
—	—	yes	→ Step 530	—
513	Is this an article ID belonging to group article ID 1-07-1 or 1-07-2?	no	→ Step 515	—
—	—	yes	→ Step 528	—
515	Is the article ID one used to bill the maximum rates of one of the following defined levies and surcharges? Note: The following levies and surcharges are affected: § 19 StromNEV surcharge surcharge for interruptible loads offshore grid surcharge concession levy levy KWKG	yes	→ Step 525	—
—	—	no	A60	Cluster: Rejection at line item level The price was not stated (neither in the price sheet nor via master data) and is also not known from “legal requirements”.
525	Does the price of the article ID match the statutory requirement?	no	A50	Cluster: Rejection at line item level The NB used the incorrect price for the statutory levy or duty. Note: The LF states the expected price for the statutory levy or duty.
—	—	yes	→ Step 528	—
528	Is the calculated (invoiced) quantity a physical power value?	yes	→ Step 595	Note: Check of an item with physical power
—	—	no	→ Step 530	—
530	Is the billing period of the resulting invoice already contained in a previous, accepted and not cancelled periodic invoice or interim invoice or final invoice?	yes	A51	Cluster: Rejection at line item level Billing period of the resulting value is billed twice Note: The LF states the invoice number of the invoice in which this line item has already been billed.
—	—	no	→ Step 535	—
535	Did a change of connection user take place in the time period of the resulting time series? Note: If the change of connection user takes place at the start time or at the end time of the time period of the resulting time series, this question must be answered with „no“.	yes	AA4	Cluster: Rejection at line item level A change of connection user took place within the time period of the resultant.
—	—	no	→ Step 540	—
540	Does the article ID of the line items to be checked depend on the utilisation hours?	yes	→ Step 555	—
—	—	no	→ Step 560	—
555	Does this resultant bill a time period with this article ID that has already been billed with this article ID in a previous, accepted and non-cancelled MVR and has not been reversed in any previous, accepted and non-cancelled MVR?	yes	AA6	Cluster: Rejection at line item level The service to be billed has already been billed in a previous MVR. Note: The LF states the reference of the invoices (MVR) in which the service to be billed has already been billed.
—	—	no	→ Step 595	—
560	Is the article ID of the line items to be checked the article ID for the special contract customer concession levy or for the municipality-specific special contract customer concession levy?	yes	→ Step 561	—
—	—	no	→ Step 595	—
561	Is a concession levy line item with an article ID that does not correspond to the article ID for the special-contract customer concession levy billed with a positive quantity in the same invoice?	yes	AD0	Cluster: Rejection at line item level In the same invoice the concession levy is charged both for tariff customers and for special contract customers.
—	—	no	→ Step 563	—
563	Do the start and the end of the time period of the resultant fall in different calendar months? Note: If the end date is the first day of the month at 00:00 of the month following the month in which the point in time at which the time period of the resultant starts falls, then, for the purposes of the question above, the start and end points lie within one month.	yes	→ Step 565	Note: the article ID covers more than one billing month
—	—	no	→ Step 595	Note: the article ID covers at most one calendar month
565	Have all concession levy items for tariff customers been withdrawn from the previous MVR?	no	AA7	Cluster: Rejection at line item level The concession levy for tariff customers has already been billed in a previous MVR and has not been reversed. Note: The LF states the reference of the invoices (MVR) in which the concession levy has already been billed.
—	—	yes	→ Step 595	—
595	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: open
—	—	no	→ Step 599	—
599	Are there further invoice line items to be checked?	yes	→ Step 100	—
—	—	no	→ Step 800	—
600	Was the article ID used in the invoice line item exchanged in the master data for the entire line item period of this line item (either indirectly by stating the associated group article ID or by directly naming the article ID)? Note: In the case of a supplier switch during the year, the article IDs from the registration confirmation or master data change apply from 01.01. of the current calendar year and are also to be used for checking the invoice line items of the grid usage settlement for time periods before the supplier switch.	yes	→ Step 615	—
—	—	no	→ Step 605	—
605	Is the article ID used in the invoice line item the article ID for the special contract customer concession levy or for the municipality-specific special contract customer concession levy?	no	→ Step 607	—
—	—	yes	→ Step 610	—
607	Is the article ID used in the invoice line item the article ID for the tariff customer concession levy or for the municipality-specific tariff customer concession levy?	no	A77	Cluster: Rejection at line item level The article ID used in the specified line item should not have been listed for the entire line item period. Note: Within the line item period the supplier states the time period in which this article ID is not valid.
—	—	yes	→ Step 615	—
610	Have one or more concession levy article IDs that do not correspond to the special contract customer concession levy been agreed via the master data over the line item period?	no	AD1	Cluster: Rejection at line item level The special contract customer concession levy is billed although no billing of the concession levy was agreed via the master data exchange.
—	—	yes	→ Step 630	—
615	From the point of view of the LF, must the article ID not be stated in this invoice because, from the point of view of the LF, it does not fit this market location and the metering locations assigned to it for the line item period?	yes	A53	Cluster: Rejection at line item level This article ID is not permitted for this invoice type.
—	—	no	→ Step 620	—
620	Is the article ID permissible for this invoice type for this line item period?	no	A54	Cluster: Rejection at line item level This article ID is not permitted for this invoice type in the stated line item period.
—	—	yes	→ Step 622	—
622	Is this an article ID belonging to group article ID 1-07-1 or 1-07-2?	yes	→ Step 627	—
—	—	no	→ Step 624	—
624	Is this article ID 1-01-6-005 or 1-01-9-001 or 1-01-9-002 or 1-07-4-001, or an article ID belonging to group article ID 1-03-8 or 1-03-9?	yes	→ Step 630	—
—	—	no	→ Step 625	—
625	Have the surcharges and discounts (incl. municipal discount) that were previously exchanged via master data been taken into account for the article ID? Note: If no surcharges or discounts are listed in the checked line item and none have been exchanged/announced via master data, this question is to be answered with „yes“.	no	A55	Cluster: Rejection at line item level Surcharge or discount was not taken into account as exchanged in the master data.
—	—	yes	→ Step 627	—
627	Is physical power billed with the article ID?	yes	→ Step 676	Note: No resultant and no corresponding resultant is formed with a physical power.
—	—	no	→ Step 630	—
630	Is there more than one item with this article ID?	yes	→ Step 635	—
—	—	no	→ Step 645	Note: This line item is the resultant with which the further checks are carried out.
635	Is there at least one further item with this article ID but a higher item number?	yes	→ Step 795	Note: The last item with this article ID has not yet been reached and therefore the resultant is not yet determined
—	—	no	→ Step 640	Note: The last item with this article ID has been reached. The resultant of this article ID can therefore now be determined and is determined
640	Does the determined result cover exactly one gapless time period to which a quantity, a price and an amount are assigned? Note: The same price must be assigned to all line items with the same article ID.	no	AA9	Cluster: Rejection at line item level Determination of the resultant with this article ID failed.
—	—	yes	→ Step 645	—
645	Is the start of the time period of the resulting invoice < 01.01.2023 00:00?	yes	AB1	Cluster: Rejection at line item level The resultant < 01.01.2023 00:00.
—	—	no	→ Step 650	—
650	Is the calculated (invoiced) quantity a physical energy value?	yes	→ Step 651	—
—	—	no	→ Step 680	—
651	Does the article ID to be checked belong to one of the following group article IDs: 1-10-4, 1-10-5, 1-10-6, 1-08-2-AGS-KG and 1-08-5-AGS-KG?	yes	→ Step 652	—
—	—	no	→ Step 660	—
652	Is there at least one further resultant for the article ID under check with an article ID that belongs to the group article ID?	yes	→ Step 653	—
—	—	no	→ Step 660	—
653	Does the sum of the quantities from all the resultants formed for this group article ID match the quantities of the delivery note? Note: To do this, all resultants of the group article ID concerned must be formed. The quantity must be taken from each of these resultants. These quantities must be summed.	no	AE4	Cluster: Rejection at line item level The LF rejects the invoice because the sum of the quantities does not match the delivery note.
—	—	yes	→ Step 665	—
660	Do the individual items of the quantities in the delivery note match the absolute amount of the quantity of the resulting item of the invoice? Note: According to GPKE, the billing energy quantities stated in the grid usage invoice must match, in their amount and over the time period, the billing energy quantities previously transmitted by the NB at market location level in the delivery note.	no	A56	Cluster: Rejection at line item level The LF rejects the invoice with reference to the line item that does not match the quantities on the transmitted delivery note. Population note: „Identification of the line/item in the document“: The LF states the highest line item number of the article ID for which the resultant of the invoice does not correspond to the quantity from the delivery note.
—	—	yes	→ Step 665	—
665	Are the load curves at the market location from MSB available for the period of the resulting values, or, in the case of a supplier switch during the year, the energy quantity and up to two maximum demand values from NB? Note: If the load curves at the market location from MSB are not available for the period of the resulting values, a complaint about them must first have been raised by LF with MSB before this question may be answered with no.	yes	→ Step 680	—
—	—	no	→ Step 670	—
670	Are the load profiles at the market location from the MSB missing for the time period of the resulting time series and was a complaint raised with the MSB?	yes	AB2	Cluster: Rejection at line item level Values from the MSB are missing or incorrect values were sent by the MSB and a claim for these has already been raised via ORDERS. Note: The LF states the business transaction number of the ORDERS with which the missing or incorrect values were claimed.
—	—	no	→ Step 675	—
675	Are the maximum demand and the energy quantity of the market location from the NB missing for the time period of the resulting time series for the period of the year before the supplier switch?	yes	AB3	Cluster: Rejection at line item level Because of the supplier switch within the year, the maximum demand and the energy quantity for the part of the year before the supplier switch, which the NB should have sent, are missing.
—	—	no	→ Step 680	—
676	Is the physical power specified in the line item < 0?	yes	→ Step 680	Note: This is a reversal item
—	—	no	→ Step 677	—
677	Does the maximum demand stated in the item match the maximum demand of the delivery note?	no	AC6	Cluster: Rejection at line item level The LF rejects the invoice with reference to the line item that does not match the maximum demand of the delivery note.
—	—	yes	→ Step 680	—
680	Has a price been announced in the price sheet for the article ID?	yes	→ Step 685	—
—	—	no	→ Step 690	—
685	Was the correct price from the price sheet for the article ID used in the invoice?	no	A58	Cluster: Rejection at line item level The price for the article is incorrect. Note: The LF communicates the expected price for the article ID.
—	—	yes	→ Step 687	—
687	Is the calculated (invoiced) quantity a physical power value?	yes	→ Step 795	Note: Check of an item with physical power
—	—	no	→ Step 715	—
690	Was the price for the article ID exchanged via the master data?	yes	→ Step 695	—
—	—	no	→ Step 698	Note: Prices of the affected article ID are exchanged neither via the price sheet nor via the master data.
695	Was the correct price from the previously exchanged master data for the article ID used in the invoice?	no	A59	Cluster: Rejection at line item level The price for the article is incorrect. Note: The LF communicates the expected price for the article ID.
—	—	yes	→ Step 715	—
698	Is this an article ID belonging to group article ID 1-07-1 or 1-07-2?	no	→ Step 700	—
—	—	yes	→ Step 712	—
700	Is the article ID one used to bill the maximum rates of one of the following defined levies and surcharges: Note: The following levies and surcharges are affected: § 19 StromNEV surcharge surcharge for interruptible loads offshore grid surcharge concession levy levy KWKG	yes	→ Step 710	—
—	—	no	AC2	Cluster: Rejection at line item level The price was not stated (neither in the price sheet nor via master data) and is also not known from “legal requirements”.
710	Does the price of the article ID match the statutory requirement?	no	A61	Cluster: Rejection at line item level The NB used the incorrect price for the statutory levy or duty. Note: The LF states the expected price for the statutory levy or duty.
—	—	yes	→ Step 712	—
712	Is the calculated (invoiced) quantity a physical power value?	yes	→ Step 795	Note: Check of an item with physical power
—	—	no	→ Step 715	—
715	Is the billing period of the resulting invoice already contained in a previous, accepted and not cancelled periodic invoice or interim invoice or final invoice?	yes	A62	Cluster: Rejection at line item level Billing period of the resulting value is billed twice. Note: The LF states the invoice number of the invoice in which this line item has already been billed.
—	—	no	→ Step 720	—
720	Did a change of connection user take place in the time period of the resulting time series? Note: If the change of connection user takes place at the start time or at the end time of the time period of the resulting time series, this question must be answered with „no“.	yes	AB4	Cluster: Rejection at line item level A change of connection user took place within the time period of the resultant.
—	—	no	→ Step 725	—
725	Does the article ID of the line items to be checked depend on the utilisation hours?	yes	→ Step 730	—
—	—	no	→ Step 770	—
730	Are the utilisation hours (h/a) calculated from the demand and energy values of the delivery note for the time period of one connection user and the billing period ≥ 2.500 hours?	yes	→ Step 735	Note: The NB can only invoice article IDs from annual utilization hours ≥ 2.500 h/a.
—	—	no	→ Step 755	Note: The NB can only invoice article IDs from annual utilization hours< 2.500 h/a.
735	Was the article ID for a utilization hours duration of ≥ 2.500 hours per year used?	yes	→ Step 795	—
—	—	no	→ Step 740	—
740	Is the quantity of the resulting item negative?	no	AB5	Cluster: Rejection at line item level Incorrect article ID used.
—	—	yes	→ Step 765	—
755	Was the article ID for a utilization hours duration of < 2.500 hours per year used?	no	→ Step 760	—
—	—	yes	→ Step 795	—
760	Is the quantity of the resulting item negative?	no	AB7	Cluster: Rejection at line item level Incorrect article ID used.
—	—	yes	→ Step 765	—
765	Does the resultant with this article ID fully reverse what has already been billed with this article ID in all MVR belonging to this 13I?	no	A63	Cluster: Rejection at line item level One of the two error situations applies: 1) Too few or too many line items from the previous MVR are reversed. 2) The article ID was billed for the wrong utilisation hours.
—	—	yes	→ Step 795	—
770	Is this an article ID for the concession levy?	yes	→ Step 775	—
—	—	no	→ Step 772	—
772	Does this resultant bill a time period with this article ID that has already been billed with this article ID in a previous, accepted and non-cancelled MVR and has not been reversed in any previous, accepted and non-cancelled MVR?	yes	AB8	Cluster: Rejection at line item level The service to be billed has already been billed in a previous MVR. Note: The LF states the reference of the invoices (MVR) in which the service to be billed has already been billed.
—	—	no	→ Step 795	—
775	Is there a further article ID for a concession levy that differs from this article ID and with which a further resultant can thus be formed? Note: In check steps 775 to 794, the standard of always considering only the resultant under check is departed from in order to reduce the number of checks described.	yes	→ Step 781	—
—	—	no	→ Step 780	—
780	Does this resultant bill a time period with this article ID that has already been billed with this article ID in a previous, accepted and non-cancelled MVR and has not been reversed in any previous, accepted and non-cancelled MVR?	no	→ Step 794	—
—	—	yes	AD6	Cluster: Rejection at line item level The concession levy has already been billed in a previous MVR. Note: The LF states the reference of the invoices (MVR) in which the concession levy has already been billed.
781	Is at least one of the resulting items a reversal line item?	yes	→ Step 782	—
—	—	no	→ Step 786	—
782	Are all concession amounts already paid fully reversed by all resultants of the reversal line items with the corresponding article ID? Note: The reversal line item (there may also be several) may also use a resultant for the concession levy of this invoice other than the resultant under check. What matters is that the concession amounts already paid have been fully reversed.	yes	→ Step 784	—
—	—	no	→ Step 783	—
783	Is the resulting item of the reversal line item the resulting item under check?	yes	AD5	Cluster: Rejection at line item level The reversal line items do not fully reverse all concession amounts already paid.
—	—	no	→ Step 795	—
784	Does the resultant of the forward line item bill the correct concession levy for the calendar year? Note: The correct concession levy results from checking the power values and energy quantity against the criteria of the special-contract customer concession levy and from using the statutory price specifications or the municipality-specific concession levy of the grid operator.	yes	→ Step 794	—
—	—	no	→ Step 785	—
785	Is the resulting item of the forward line item the resulting item under check?	yes	AD3	Cluster: Rejection at line item level The wrong concession levy is billed for the calendar year.
—	—	no	→ Step 795	—
786	Is the result an article ID for tariff customer concession levy?	yes	→ Step 787	—
—	—	no	AD7	Cluster: Rejection at line item level The concession levy is billed incorrectly.
787	Is a concession levy line item with an article ID that does not correspond to a tariff customer concession levy billed with a positive quantity in the same invoice?	yes	AD8	Cluster: Rejection at line item level Concession levy is billed twice.
—	—	no	→ Step 788	—
788	Does the article ID to be checked belong to one of the following group article IDs: 1-08-2-AGS-K and 1-08-5-AGS-KG?	yes	→ Step 789	—
—	—	no	→ Step 793	—
789	Is there at least one further resultant for the article ID under check with an article ID that belongs to the group article ID?	yes	→ Step 790	—
—	—	no	→ Step 793	—
790	Does the sum of the quantities from all the resultants formed for this group article ID match the quantities of the delivery note? Note: To do this, all resultants of the group article ID concerned must be formed. The quantity must be taken from each of these resultants. These quantities must be summed.	no	AE5	Cluster: Rejection at line item level The LF rejects the invoice because the sum of the quantities does not match the delivery note.
—	—	yes	→ Step 795	—
793	Is the energy quantity of the resulting item plausible in relation to the energy quantity of the delivery note?	yes	→ Step 794	—
—	—	no	AD4	Cluster: Rejection at line item level The energy quantity of the resultant does not match the delivery note
794	Does the netted energy quantity of the concession levy match the delivery note? Note: The netted billed energy quantity is obtained by adding all energy quantities (taking their signs into account) of all resulting items for the concession levy of this invoice.	yes	→ Step 795	—
—	—	no	AD9	Cluster: Rejection at line item level The netted energy quantity of the resultant does not match the delivery note
795	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: open
—	—	no	→ Step 799	—
799	Are there further invoice line items to be checked?	yes	→ Step 100	—
—	—	no	→ Step 800	—
800	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 805	The check of the EBD is continued in the summary section.
from 805	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 article ID is missing, the REMADV structure for transmitting errors at summary level must be used to transmit the error.	—	—	—
805	Are article IDs still missing for invoice line items ≥ 01.01.2023 00:00 that were previously exchanged with the master data and were therefore expected in the invoice? Note: If the concession levy actually billed has changed compared with the concession levy exchanged in the master data, the article ID previously exchanged in the master data must not be transmitted as a missing article ID.	yes	A78	Cluster: Rejection at summary level Expected article ID not present in the invoice. Note: The expected article IDs must be named.
—	—	no	→ step 810	—
810	Are the grid fees calculated correctly, taking into account the flat-rate grid fee reduction under §14a EnWG?	no	AD2	Cluster: Rejection at summary level The grid fees taking into account the flat-rate grid fee reduction pursuant to §14a EnWG are not calculated correctly.
—	—	yes	→ step 815	—
from 815	Starting with check step 815, 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 NB as the result with the corresponding rejection codes. The following checks are to be performed for each combination of tax rate and tax category; this applies to all invoice types except the special invoice.	—	—	—
815	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	A66	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 816	—
816	Is the start date of the billing period ≥ 01.01.2023 00:00 German statutory time?	no	→ step 817	—
—	—	yes	→ step 820	—
817	For this tax rate, does the stated prepaid amount match the sum of the amounts actually paid with this tax rate?	no	AC3	Cluster: Rejection at summary level The sum of the prepaid amounts with this tax rate does not correspond to the prepaid amount with this tax rate stated in this invoice. Note: The tax rate (from DE5278) and the control category (from DE5305) of the SG52 TAX must be named.
—	—	yes	→ step 818	—
818	Does the prepaid tax match the sum of the taxes of the prepaid amounts with this tax rate?	no	AC4	Cluster: Rejection at summary level The sum of the taxes of the invoice does not correspond to the sum of the taxes of the prepaid invoices. Note: The tax rate (from DE5278) and the control category (from DE5305) of the SG52 TAX must be named.
—	—	yes	→ step 830	—
820	For this tax rate, does the stated prepaid amount match the sum of the amounts actually paid from the referenced invoices with this tax rate?	no	A67	Cluster: Rejection at summary level The sum of the prepaid amounts with this tax rate does not correspond to the prepaid amount with this tax rate stated in this invoice Note: The tax rate (from DE5278) and the control category (from DE5305) of the SG52 TAX must be named.
—	—	yes	→ step 825	—
825	Does the prepaid tax match the sum of the taxes contained with this tax rate in the amounts actually paid in the referenced invoices?	no	A68	Cluster: Rejection at summary level The sum of the taxes does not correspond to the sum of the prepaid taxes from the referenced invoices. Note: The tax rate (from DE5278) and the control category (from DE5305) of the SG52 TAX must be named.
—	—	yes	→ step 830	—
830	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	A69	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 835	—
835	Are there further tax rates to be checked?	yes	→ step 815	—
—	—	no	→ step 900	—
900	Does the invoice amount match the sum of all invoice line items (taxable amount) plus the respective tax amount?	no	A70	Cluster: Rejection at summary level The invoice amount (taxable amount including tax amount) of the total is not correct.
—	—	yes	→ step 905	—
905	Does the amount due of this invoice match the invoice amount less the sum of all prepaid amounts, where these are present, and less the municipal rebate/local authority rebate, where this is present?	no	A71	Cluster: Rejection at summary level The amount due is not correct.
—	—	yes	→ step 910	—
910	Does the municipal rebate/local authority rebate match the sum of the municipal rebate/local authority rebate amounts from the line item level?	no	A72	Cluster: Rejection at summary level The total of the municipal rebate is not correct.
—	—	yes	→ step 920	—
920	Is the invoice type one of the following: instalment invoice (ABS) monthly invoice (MVR) integrated 13th invoice (13I) 13th invoice (13R)?	yes	→ step 940	—
—	—	no	→ step 921	Note: This is the invoice type periodic invoice (JVR), final invoice (ABR) or interim billing (ZVR).
921	Is the start date of the billing period ≥ 01.01.2023 00:00 German statutory time?	no	→ step 922	—
—	—	yes	→ step 925	—
922	Is the prepaid amount identical to the sum of all previously paid instalment invoices whose billing period falls within the billing period of the invoice (JVR, ZVR, ABR)? Note: As soon as at least one day of the billing period of the instalment falls within the billing period of the grid usage invoice (JVR, ZVR, ABR) and has been paid, it must be offset, provided the instalment invoice has not already been taken into account in another invoice accepted by the LF and not cancelled.	no	AC5	Cluster: Rejection at summary level Not all previously paid instalment invoices are contained for the billing period of the invoice (JVR, ZVR, ABR) Notes: The LF states the invoice numbers of all instalment invoices it expected in this invoice.
—	—	yes	→ step 940	—
925	Are all references of the associated and previously paid instalment invoices contained for the billing period of the invoice (JVR, ZVR, ABR)? Note: As soon as at least one day of the billing period of the instalment falls within the billing period of the grid usage invoice (JVR, ZVR, ABR) and is paid, it must be credited, provided that the instalment invoice has not already been taken into account in another invoice accepted by the LF and not cancelled.	no	A74	Cluster: Rejection at summary level References to previously paid instalment invoices are missing. Notes: The LF states the invoice numbers of the instalment invoices that it expected in this invoice and that were not taken into account in this invoice.
—	—	yes	→ step 927	—
927	Does the stated prepaid amount match the sum of the amounts actually paid from the referenced invoices?	no	A73	Cluster: Rejection at summary level The prepaid amount stated is not correct.
—	—	yes	→ step 930	—
930	Have all instalment invoices taken into account in the invoice (JVR, ZVR, ABR) been confirmed by the recipient with a remittance advice?	no	A76	Cluster: Rejection at summary level At least one instalment invoice taken into account in this invoice was rejected or not answered by the LF. Instalment invoices requested but not settled must be cancelled by the NB. Note: The LF states the invoice numbers of the instalment invoices that should not have been taken into account in the present invoice.
—	—	yes	→ step 935	—
935	Has at least one of the referenced instalment invoices already been offset in another invoice?	yes	A75	Cluster: Rejection at summary level At least one referenced instalment invoice has already been offset. Note: In the rejection the LF states the instalment invoice(s) that have already been offset as well as the invoice(s) (in RFF+AFL) in which the instalment payment(s) (in FTX+Z14) were already taken into account.
—	—	no	→ step 940	—
940	Has a previously unspecified error occurred in the summary section?	yes	A96	Cluster: Rejection at summary level Other error in the summary section. Note: The identified problem must be described/named in the response. End of usability: open
—	—	no	→ step 990	—
990	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.