GR-R-002:myDATA reporting required
Greek invoices must be reported to myDATA (AADE).
Engine Classification
Financial or legal field · Modification blocked by policy
Reason: Greek invoices must be reported to myDATA (AADE tax authority system). This requires integration with the myDATA API and cannot be done by modifying the invoice XML. Use invoicing software with myDATA reporting capability.
What is GR-R-002?
GR-R-002 is a fatal validation rule defined in the ubl-2.1 specification (GRC national rules). It validates the myDATA API integration element in the UBL invoice XML.
When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.
Target path: myDATA API integration
Why This Error Matters
Greek law requires myDATA reporting.
GR-R-002 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.
Validator Behavior
- ·Causes invoice rejection
- ·Fails UBL schema validation
- ·Error returned: GR-R-002
- ·Specification: ubl-2.1
How to Fix It
Submit to myDATA
Via AADE platform or API
Get MARK
Unique authentication code
Add to invoice
Include MARK reference
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Triggers validation error --> <myDATA API integration></myDATA API integration>
<!-- Corrected --> <myDATA API integration>VALID_VALUE</myDATA API integration>
Technical Reference
myDATA API integrationCommon Causes
- ·Not submitted to myDATA
- ·Missing MARK
Seeing this in production? The API handles GR-R-002 automatically. See the fix response →
Frequently Asked Questions
Greek invoices must be reported to myDATA (AADE).
Submit invoice to myDATA and include MARK. This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.
Yes, GR-R-002 is a critical error that must be fixed.
Related Content
Last updated: 3 March 2026
Detect GR-R-002 Before Submission
This error involves a financial or legal field that cannot be auto-modified. The compliance engine flags it immediately with a clear diagnosis so your team can fix it at the source.