Response batching

Similar to the invoice request process, Google employs a batching mechanism for responses, which extends the UBL format to consolidate multiple responses into a single transaction. The batch includes a custom-defined header, yet every element within the batch strictly adheres to the UBL 2.4 Application Response schema.

Batch header

The header for a batch of responses contains critical metadata about the batch, including the name of the request file and the status of the file processing.

Details

Element	Description	Example
RequestFileName	The referenced request filename with the batch identifier token.	FileName_TokenID
FileStatus/StatusCode	The file processing status. See possible value here: list.	S
FileStatus/StatusDescription	Description of the file processing status.	Successfully Processed

Example XML

<ApplicationResponseBatch xmlns:ar='urn:oasis:names:specification:ubl:schema:xsd:ApplicationResponse-2'
                          xmlns:cac='urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2'
                          xmlns:cbc='urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2'
                          xmlns:ext="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2">
    <RequestFileName>FileName_TokenID</RequestFileName>
    <FileStatus>
        <StatusCode>S</StatusCode>
        <StatusDescription>Successfully Processed</StatusDescription>
    </FileStatus>
    <ar:ApplicationResponse>
        <!-- Application Response -->
    </ar:ApplicationResponse>
    <ar:ApplicationResponse>
        <!-- Application Response -->
    </ar:ApplicationResponse>
</ApplicationResponseBatch>