Back to the error catalogue
BR-DE-28BT-43
input

Germany

The seller contact email address is malformed

`Seller contact email address` (BT-43) should contain exactly one “at” sign, flanked by at least two characters on each side, and a dotted domain with no leading or trailing dot.

Only the issuer holds this value: Factlint reports it and never fabricates it. Test your invoice to find out whether it is affected.

The message your validator prints

Copied verbatim from the sealed artefact: this is the exact sentence the check prints when this rule fails.

[BR-DE-28] 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.

Quoted from schematron-xrechnung 3.0.2, licensed under Apache-2.0.

Common searches around this code

These phrases mirror what an integrator searches for: code, syntax, rule, business field and correction.

BR-DE-28 The seller contact email address is malformedBR-DE-28 XRechnung Schematron package (KoSIT)BR-DE-28 BT-43[BR-DE-28] 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.BR-DE-28 correction

Test your file with this error in mind

Upload the invoice involved: the report will say whether this code appears, where it appears in the document, and whether Factlint can only report it or also fix it.

To automate this check in an ERP flow, call the validation API and link every returned code to its public page.

Why this error happens

Like BR-DE-27, the check targets the field filled for appearances. It also catches the case where two addresses have been put in a field meant for one, separated by a comma or a semicolon.

How to fix it

Fill in a single valid address. Factlint does not correct it: splitting or choosing between two addresses would amount to deciding who gets the mail.

XML correction example

BEFORE (invalid)
<ram:URIID>kontakt(at)vendeur.example</ram:URIID>
AFTER (compliant)
<ram:URIID>[email protected]</ram:URIID>