End of Day (Manifest)
At the end-of-day close, all open Rhenus shipments are consolidated into a single BORD512 manifest file and transmitted to Rhenus. This lets you report a day's shipments in one batch instead of individually.
Creating the manifest
You trigger the end-of-day close via the hub's central Manifest function. The connector consolidates all open, non-excluded shipments into one BORD512 file and (outside sandbox) uploads it to the Rhenus SFTP server via the Azure Function.
Manifest file structure
The consolidated file contains one transmission (@@PH … @@PT) with the records of all included shipments and a shared statistics record (J00). See BORD512 Format.
Including and excluding shipments
On the shipping label list, you control per shipment whether it is included in the end-of-day close:
| Action | Effect |
|---|---|
| Exclude from Manifest | Exclude the shipment from the close (the row is greyed out) |
| Include Manifest | Add a previously excluded shipment back |
Excluded shipments appear neither in the preview nor in the final manifest file.
Dashboard actions
The Rhenus Dashboard offers two additional manifest actions:
| Action | Description |
|---|---|
| Download Manifest Preview | Preview: the consolidated BORD512 file of all open (non-excluded) shipments — without transmitting |
| Download Last Manifest | Download the most recently created end-of-day file again |
Check before transmitting
Use Download Manifest Preview to verify content and completeness before you finally transmit the end-of-day close.
Internal packing list
In addition, the connector extends the hub packing list (report Internal Manifest) with the BORD512 package type and hides excluded shipments. This gives you a printed overview of the transmitted packages.
→ Next: Create a Shipment · BORD512 Format