What Is Batch Delivery?
Batch Delivery is a tool that lets you streamline delivery of statements or similar files to your clients' SideDrawers.
Using SideDrawer metadata, the tool lets you quickly identify which file should go to which client/drawer, deliver all the files in one streamlined process, and identify and correct errors to complete the delivery for everyone.
Batch Delivery vs. Content Package
Content Package - send identical files to multiple clients.
Use for newsletters, welcome letters, instruction documents, anything where everyone's getting a copy of the same file.
Batch Delivery - send individualized files to multiple clients.
Use for statements, contracts, anything where everyone gets their own customized copy of a template file.
How Does it Work?
Batch Delivery is based on 4 elements:
The Content - the statements or files that you'll be delivering to your clients
The Source - a Drawer and Record where you will upload the Content to be delivered
The Destinations - client Drawers already created with metadata for each Drawer. This is where your Content will be delivered.
The Instructions - a .csv file listing the destination drawers with metadata, the Content files by name, and detailing which file should get delivered to which Drawer
The Batch Delivery process walks you through the steps to identify the Source where your documents are stored, and upload the Instructions csv file.
SideDrawer will then use your Instructions to deliver each document from the Source drawer to the client-facing Destination drawers.
Finally, the system will identify whether all documents were delivered successfully, and flag any errors that might have come up, letting you analyze and correct errors without having to run the entire delivery again.
Batch Delivery Video Example
Creating a Batch Delivery
Creating a Batch Delivery
This section outlines the steps for setting up your own Batch Delivery.
We've also created an example, delivering Q1 2022 statements to 8 client Drawers - the same example outlined in the video above.
We'll use references and screenshots to our example to illustrate the steps as we go.
Step 0 - Preparations
Step 0 - Preparations
Before you initiate your Batch Delivery, you'll need to have all 4 elements prepared: Source, Content Destinations, and Instructions.
Source:
A Drawer with a Record where you will load your Content, the files to be delivered.
This should be an internal Drawer, not client-facing, though you may need to also provide access to third-party professional users, if the Content documents are coming from outside your organization.
We like to label the Source as "Delivery Drawer" or "Source Drawer" - a name that makes it clear that it's a back-office resource, not accessible to clients.
It's also helpful to give the Source Record a name that makes it easy for you to identify, like "2025 Q4 Statements".
Content:
Once you have your Source Drawer and Record created, upload the files that you will be delivering.
Destinations:
Make sure all your client Drawers have been created, with the metadata values that will be used for the delivery
Instructions:
Fill out your .csv file with the details for the delivery.
The Instructions tell our system exactly which file(s) to deliver to exactly which Drawer(s), and what Tile and Record to store them in.
Column A: Metadata Key - this is the label for your metadata, telling the system what kind of information your metadata represents
For example, account ID, user number, etc.
When creating the SideDrawer metadata, the Metadata Key is the column header you entered.
Metadata Key will usually be the same for all items in your delivery.
Column B: Metadata Value - this is the unique identifier for each drawer, under the Metadata Key heading.
For example, if your Metadata Key is Account ID, then the Metadata Value will be the unique account number you've assigned to each Drawer.
Metadata Value is usually unique for each item in your delivery, if you're delivering each file to a different client's Drawer.
Column C: Destination Tile (recordType) - the Tile in the destination drawer that you want the delivery to go to, such as Investments or Taxes.
Make sure you enter the Tile name as it appears in the URL - for example, you can see in the image below that the Legal Documents Tile appears as 'legalDocs'
The system needs an exact match in order to understand where to deliver the files.
Destination Tile is usually the same for all items in your delivery, to ensure consistency across all clients' Drawers.
Column D: Record Type (recordSubTypeOthername) - the Record Type is a label, separate from the Record Name, telling you what kind of documents the folder contains.
For example, the Record in the image below has the Record Name 'Noam's Taxes 2025,' and the Record Type label on the right identifies it as a Tax Return:
Record Type is usually the same across all items in your Batch Delivery, to provide consistency.
Column E: Record Name - this is the name of the Record or Folder that holds the documents you're delivering.
Choose a Record Name that helps your clients immediately understand what the documents are - for example, '2026 Q1 Financial Statement'.
Record Name is usually the same across all items in your Batch Delivery, to provide consistency.
You can deliver documents to a Record that already exists!
The system will always perform a search - if the Record listed here already exists in the client's Drawer, then the new files will be delivered there.
If the Record does not exist, it will be created as part of the Batch Delivery.
Column F: File Name - this is the name of the file that you want to deliver.
Make sure that the name here is an exact match for the file name in your Source, otherwise you'll get an error.
NOTES:
SideDrawers can have multiple Metadata Keys and Values so you can facilitate the delivery of multiple documents into a SideDrawer from different Vendors with unique client identifiers
If you use the same SideDrawer (indicated by the Metadata in Rows A / B), Tile, Record Type and Record Name for multiple different documents, they will all be delivered to the same new Record being created. This can be useful for keeping things organized
Please save as a CSV (MS-DOS) for the process to work cleanly
Step 1 - Start Batch Delivery
Step 1 - Start Batch Delivery
In your Console, go to Productivity->File(s) Batch Delivery, then select Create your first Batch Delivery, or Create New Batch Delivery
Step 2 - Select Source
Step 2 - Select Source
Enter a Name for this delivery - the name is for your internal records, and will appear in your Batch Deliveries menu if you want to look up this delivery later on
(Optional) Add a Description to provide more details about this delivery
Choose the Source SideDrawer - use the Search/Filter bar to help locate the right drawer
Choose the Source Record - select the Record in your Source drawer where the files for this delivery are stored
Once you have your Source selected, click on Proceed to upload instructions
Step 3 - Upload Instructions CSV
Step 3 - Upload Instructions CSV
In this screen, upload your Instructions CSV by dragging and dropping the file into the centre box, or click to select the file and upload.
Optional: enter a Delivery Message
This message will appear in the email notification for the Batch Delivery, if you have this notification activated
If you don't already have the Instructions CSV completed (see Step 0, above), click on the lower left to download the CSV template and fill it out, then upload once it's completed.
Once your CSV Instructions are uploaded, click on Review CSV Instructions at the lower right to proceed to the next step:
Step 4 - Review and Deliver
Step 4 - Review and Deliver
This screen will display all entries in your CSV Instructions, so you can review the data before you move ahead to the delivery:
You can use the search field to spot-check specific entries, and use the fields button to select which fields to display, to make it easier to see individual items.
This display is read-only, so if you do spot an error, select Back to return to the previous screen, then correct the CSV and re-upload it.
If everything is correct, click on Submit for delivery to continue!
Step 5 - Manage Errors
Step 5 - Manage Errors
Error Management (Optional):
Once you submit your Batch Delivery, the system will process it and report back - in an ideal world, all items will be delivered perfectly, but sometimes, you'll see delivery errors reported.
Errors can include:
The Destination SideDrawer not existing
The file was not uploaded into the Source SideDrawer
the file name on the document doesn't match the CSV instructions
In our example, we see an Error occurred (see above)
After analysis, it was determined the SideDrawer for this statement was not created, so an Error occurred when processing the Batch Delivery
By searching for “Error” we could zero in on the specific item that had the issue (see above image)
Once the error has been corrected (by updating the details in the CSV, or by adding the necessary Content file, or by creating the correct Destination drawer), click Reprocess Item at the lower right to re-do this specific instance without re-sending the entire delivery:
Reviewing Batch Deliveries
Reviewing Batch Deliveries
You can review details of older Batch Deliveries from the Batch Deliveries menu in your Console.
All Batch Deliveries will appear in this menu, showing the Delivery Name and Description, the time that it was run, and the results - Total Items, Processed Items, Delivered Items, and Errors (if any).
Click on the 3 dots at the right of any delivery to bring up additional details: Delivery Status or View Source of Files.
Delivery Status
Delivery Status
Delivery Status & Details brings up the Instructions data for this Batch Delivery, as it appeared in Step 4 of the original delivery process.
This lets you confirm which items were sent, and check the overall details for that delivery.
You can also click the 3 dots to the right of any row and select Batch item details to view the specifics for that entry:
View Source of Files
View Source of Files
This option will open the Source SideDrawer, to let you view the original files that the Batch Delivery was drawing from.
Depending on the timing, and your own data retention practices, these files might not be retained, or they might have been moved from this location.
Accessing the drawer is based on the permissions logic for the platform - you need to be the Owner or the Source drawer, or a listed Collaborator in order to access it and view the files.