Valid format for the seller contact’s email address

Warning BR-DE-28 XRechnung

BT-43 should contain exactly one @ sign, which should not be flanked by a space or a dot, but should be flanked by at least two characters on both sides. A dot should not be at the beginning or at the end.

Recommendation: The invoice remains valid but should be corrected so that it can be processed automatically.
What is wrong

The value in ram:URIID does not match the expected email format. It must contain exactly one @, have at least two characters on each side of it, and must not start or end with a dot. A dot or whitespace must not be directly next to the @.

What the rule means

BT-43 contains the seller contact’s electronic address. A correctly structured email format is needed for the contact address to be identifiable as an email address.

Affected fields BT-43
Please provide a valid email address for the seller’s contact

The seller contact’s email address does not match the expected format. Update the address in the seller’s contact details.

What to do
  1. Correct the seller contact’s email address.
  2. Check the value for Contact.EmailAddress or the call to SetSellerContact(...).
  3. Ensure there is exactly one @, at least two characters on each side, and no dot at the beginning, at the end, or directly next to the @.
  4. Generate the invoice again and validate it once more.
What it looks like
✗ Triggers the message
<ram:EmailURIUniversalCommunication>
  <ram:URIID>a@b.de</ram:URIID>
</ram:EmailURIUniversalCommunication>
✓ Correct
<ram:EmailURIUniversalCommunication>
  <ram:URIID>ab.cd@example.de</ram:URIID>
</ram:EmailURIUniversalCommunication>
Check in FactoorSharp
  • Contact.EmailAddress (SellerTradeParty/ DefinedTradeContact: BT-43)
  • FacturXInvoice.SetSellerContact(name, orgunit, emailAddress, phoneno, faxno) (emailAddress: BT-43)
Technical details

The test normalizes whitespace in ram:URIID and checks the value against $XR-EMAIL-REGEX.

Where the rule applies

The email address of the seller’s contact in ram:DefinedTradeContact.

Original message from the Schematron
In BT-43 soll genau ein @-Zeichen enthalten sein, welches nicht von einem Leerzeichen, einem Punkt, aber mindestens zwei Zeichen auf beiden Seiten flankiert werden soll. Ein Punkt sollte nicht am Anfang oder am Ende stehen.
Context (rule/@context)
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ ram:SellerTradeParty/ram:DefinedTradeContact
Test expression (assert/@test)
matches(normalize-space(ram:EmailURIUniversalCommunication/ram:URIID), $XR-EMAIL-REGEX)