LF (54)
E_1009 — Check invoice for a miscellaneous service again (Based on electricity EBD: E_0505_Check invoice for a miscellaneous service again)
check invoice for another service again (Based on electricity EBD: E_0505_Check invoice for a miscellaneous service again)
| Attribute | Value |
|---|---|
| Designation | Check invoice for a miscellaneous service again (Based on electricity EBD: E_0505_Check invoice for a miscellaneous service again) |
| Market role | LF |
| Regulatory determination / chapter | Disconnection processes gas |
| Section | 17.1.3: AD: Billing of a miscellaneous service |
| Check identifiers | Response: 33002 |
| EBD version | 4.3 |
| As at | — |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 10 | Was the invoice issuer able to refute the objection of the invoice recipient? | no | A01 | After re-examination, the invoice recipient still considers the non-payment advice to be justified. Note: The objection must be described in the response. |
| — | — | yes | → Step 20 | — |
| 20 | Are there further errors in the invoice? | yes | A02 | Invoice is still rejected because of errors not yet reported. Note: The errors must be described in the response. |
| — | — | no | End | Approve invoice and take it into account in the payment advice |
Result codes
| Result code | Cluster | Meaning |
|---|---|---|
A01 | — | After re-examination, the invoice recipient still considers the non-payment advice to be justified. Note: The objection must be described in the response. |
A02 | — | Invoice is still rejected because of errors not yet reported. Note: The errors must be described in the response. |
Notes on this page
Role of the numbers: »response« are the check identifiers that list this tree in the ebd_code column of the check identifier table (knowledge-collection · FV 202610); »checked« is the difference set to it from the return path of the process steps.
Not checked against a process
No consistency check was carried out for this decision tree — no generated BPMN found. Whether the MACO APP implements this tree completely is therefore not evidenced here.