6.1 Choreography

This clause defines the method by which a company can provide batches of messages defined in Part 2 and Part 3 of the ECM standard to a business partner via (i) cloud-based storage server (such as an SFTP server) that is hosted by the message sender, (ii) a cloud-based storage server that is hosted by the message recipient or (iii) a cloud-based storage server that is hosted by a third party.

This Part of the ECM standard does not therefore define on whose hardware the files are being stored. This is determined in accordance with the bilateral agreement between the sender and the recipient of the messages.

The batched profile may only be used when exchanging JSON-formatted messages.

The choreography of the batched profile is as depicted in Figure 2 below:

Figure 2 – Choreography of the batched profile

The trigger to indicate that a batch is complete is a Manifest as defined in Clause 7 of this part of the ECM standard.

The Manifest and Acknowledgement are defined in Clause 7 .

The recipient of an Acknowledgement may remove it from the cloud-based storage server after an appropriate and mutually agreed period of time. The default period is one month.

The ECM standard does not define when the message sender shall start or finish uploading messages. Equally, this part of the ECM standard does not define when the message recipient shall start or finish the download of the messages in the batch.

The organisation of the server and the file naming convention for the batched profile are defined in Clauses 6.3 and 6.4 and an example provided in Clause 6.5 below.