UBL-2-1-InvoiceApplicationResponse-In

The UBL-2-1-InvoiceApplicationResponse-In predefined message definition acknowledges receipt of an invoice and provides a status and reason for the status.

There are two lookup codes available in Receivables that contain a list of values that can be specified in the inbound payload for the UBL-2-1-InvoiceApplicationResponse-In message. You need to add values, which you expect to receive, to these lookups.

• XML_DELIVERY_ERROR

• XML_DELIVERY_STATUS

When a UBL-2-1-InvoiceApplicationResponse-In message is received, the columns XML Delivery Status and XML Delivery Error Message in Manage Transactions in Receivables are updated to reflect the values received in the message.

Data Mapping

This table shows the data mapping for the predefined message definition UBL-2-1-InvoiceApplicationResponse-In.

UBL-2-1-InvoiceApplicationResponse-In Payload	Invoice Acknowledgment Status
ApplicationResponse/ID	OriginalMessageReferenceID
ApplicationResponse/DocumentResponse/Response/EffectiveDate	ConfirmationDate
ApplicationResponse/DocumentResponse/Response/ResponseCode	Status Note: There's a DVM, STATUS_CODE, available on this field. If the DVM isn't populated, the codes are passed directly to the Receivables application.
ApplicationResponse/DocumentResponse/Response/Status/StatusReasonCode Note: If there are more than one StatusReasonCode, then the value MULTI is mapped.	ReasonCode Note: There's a DVM, REASON_CODE, available on this field. If the DVM isn't populated, the codes are passed directly to the Receivables application.

Sample Payload

Here's a sample payload:

<ubl:ApplicationResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:ubl="urn:oasis:names:specification:ubl:schema:xsd:ApplicationResponse-2" 
xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" 
xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" 
xmlns:ext="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2">
          <cbc:ID>789</cbc:ID>
          <cbc:IssueDate>2020-08-13</cbc:IssueDate>
          <cac:SenderParty>
               <cac:PartyIdentification>
                  <cbc:ID schemeID="098">456</cbc:ID>
               </cac:PartyIdentification>
          </cac:SenderParty>
               <cac:DocumentResponse>
               <cac:Response>
                  <cbc:ResponseCode listID="UNCL4343OpSubset">RE</cbc:ResponseCode>
                  <cbc:EffectiveDate>2020-10-25</cbc:EffectiveDate>
                  <cac:Status>
                       <cbc:StatusReasonCode listID="OPStatusReason">LEG</cbc:StatusReasonCode>
                  </cac:Status>
                  <cac:Status>
                      <cbc:StatusReasonCode listID="OPStatusReason">NON</cbc:StatusReasonCode>
                  </cac:Status>
               </cac:Response>
               <cac:DocumentReference>
                      <cbc:ID>XYZ-123</cbc:ID>  
               </cac:DocumentReference>
	         </cac:DocumentResponse>   
</ubl:ApplicationResponse>