The developer should store the relevant data in Orchestrator as follows:
* Upload individual invoice data as Specific Data in Queue Items. The Specific Data is a collection of key-value pairs that can store additional information for each queue item, such as the invoice number, date, amount, etc. The Specific Data can be added to the queue items using the Add Queue Item activity in the Dispatcher workflow. The Specific Data can be retrieved from the queue items using the Get Transaction Item activity in the Performer workflow. The Specific Data can be used to process each invoice separately in the finance system as a single unit of work3.
* Create an asset for the finance team's email address. An asset is a global variable that can store a specific value, such as a text, a number, a boolean, or a credential. An asset can be created and managed in Orchestrator, and accessed by the robots using the Get Asset activity. An asset can be used to store a value that is common for all the queue items, such as the finance team's email address. The asset can be used to email the unique output ID to the finance team after each invoice is processed in the finance system4.
References: About Queues and Transactions and About Assets from UiPath documentation.