GR-R-001-4

What does this rule mean?

The invoice number of a Greek seller must carry a positive integer in its third segment.

Greece encodes the invoice number structurally so myDATA can attribute it without further data.

Where the rule applies

Syntax: UBL

Affected element (XPath):

• /ubl-invoice:Invoice/cbc:ID[$isGreekSender] | /ubl-creditnote:CreditNote/cbc:ID[$isGreekSender]

Technical test

The rule passes when this Schematron expression holds true:

string-length(normalize-space($IdSegments[3]))>0 and string(number($IdSegments[3])) != 'NaN' and xs:integer($IdSegments[3]) >= 0

How to fix it

A missing or incorrect business entry only you can supply. Add or correct it, then re-check.

Build the invoice number following the Greek segment scheme.

Correct the affected entry in your XML, then re-check the invoice. Validation runs locally in your browser — your file never leaves your machine.

Related rules

• GR-R-001-1When the Supplier is Greek, the Invoice Id should consist of 6 segments
• GR-R-001-2When the Supplier is Greek, the Invoice Id first segment must be a valid TIN Number and match either the Supplier's or the Tax Representative's Tin Number
• GR-R-001-3When the Supplier is Greek, the Invoice Id second segment must be a valid Date that matches the invoice Issue Date
• GR-R-001-5When Supplier is Greek, the Invoice Id in the fourth segment must be a valid greek document type
• GR-R-001-6When Supplier is Greek, the Invoice Id fifth segment must not be empty
• GR-R-001-7When Supplier is Greek, the Invoice Id sixth segment must not be empty