CII-SR-307: Leave the project description out of the invoice

What it means

The project block of the invoice (SpecifiedProcuringProject, in the agreement part of the file) can hold the project reference (BT-11). This rule checks that it has no Description element as well. The project reference itself is fine.

Why it matters

EN 16931 defines a project reference but no project description, so the recipient's software has no field to put the text in. The invoice is not rejected, but the text is likely to be dropped and the buyer may never see it.

How to fix it

Open the project or reference section of your invoicing software and look for a long project description. Keep the project number as the project reference, and put any wording the buyer needs in the invoice note (BT-22). If the software writes the description on its own, choose the EN 16931 profile instead of a fuller one such as Extended, or ask the software supplier to stop exporting it. It is worth fixing if you want a clean file; otherwise the invoice goes through as it is.

The rule as published

Description should not be present

Where this rule applies