France (CII(CDAR)): Structured Rejection Note

You can add a rejection note to explain the reasons for the rejection.

In the rejected Lifecycle Document scenario, it is possible to provide a structured free-text note with the information about the rejection reason. To inform that, the following extension group can be used:

Elements

Name (Path)	Cardinality	Description
Clarification Information (`ApplicationResponse/DocumentResponse/Response/Status`)	0..1	A group of business terms to provide clarification information regarding the status of a referenced document.
Free-text note (`ApplicationResponse/DocumentResponse/Response/Status/UBLExtensions/StatusExtension/Note`)	0..1	Free-text reason for the rejection of a document.
Free-text note type (`ApplicationResponse/DocumentResponse/Response/Status/UBLExtensions/StatusExtension/Note/@code`)	0..1	Code identifying the type of free-text note. It needs to follow the UNTDID 4451 list.

Restrictions

In the event of a disbursement (negative payment), the Amount element vrbl:AdditionalStatusProperty/vrbl:Amount must contain the amount disbursed (negative net amount).

In this case, the reason for the cancellation must be specified in the comment field.

Example

Here is an example of a Structured rejection note group related to a rejected invoice.

<ubl:ApplicationResponse>    
    <!-- code omitted for clarity -->
    <cac:Status>
        <cec:UBLExtensions>
            <cec:UBLExtension>
                <cec:ExtensionContent>
                    <vrbl:StatusExtension>
                        <vrbl:Note code="AHN">Facture identique reçue sur une autre adresse</vrbl:Note>
                    </vrbl:StatusExtension>
                </cec:ExtensionContent>
            </cec:UBLExtension>
        </cec:UBLExtensions>            
    </cac:Status>
    <!-- code omitted for clarity -->
</ubl:ApplicationResponse>

Updated 3 days ago