eSets Status
A shipment during its entire life cycle goes from one stage to another based on the operation performed over it. Inbox and Filed are the two primary categories where the shipment majority of the time during its lifetime. Based on the user roles, the available eSets may vary accordingly.
Role: Drafter
| eSet Location | Status | Description |
|---|---|---|
| Inbox | Match data and create CargoDocs | This status refer to an eSet that has just been pushed into CargoDocs via the interface. The user will have to go through the data matching screen and confirm the matching. Once the data has been matched, the eSet will be created in the inbox with the status of To be Released and Signed. |
| Inbox | Awaiting Draft Approval | The eSet has been shared with other parties to be approved. During this process, the parties involved can propose changes and/or approve the draft. Once every party agrees on the draft, the final version can be created by the drafter and the status will then be changed to: To be Released and Signed. Shipment with this status can also be found in a Carrier and/or Agent and/or Exchange user inbox when the user has been requested to review and approve the draft. |
| Inbox | To be Released and Signed | The eSet has been reviewed and approved by all parties and it is now ready to be sent to the Carrier and/or the Agent for signing. Once the drafter sends the eSet to the Carrier and/or the Agent, the status will change to Awaiting Signatures. |
| Inbox | Awaiting Signatures | The eSet is now sitting in the Carrier and/or Agent’s inbox awaiting either the Master, the HQ Carrier user or the Agent to sign it electronically and Issue it to the Shipper. |
| Inbox | To be Issued | This status appears when the eSet has already been signed by the Carrier or the Agent and will be released to the identified party in the chain which will be holding the original documents. |
| Inbox | To Be Reviewed and Re-Released or Deleted | This status applies to an eSet that has been Rejected by the Carrier and/or Agent at the signing stage and it’s been sent back to the drafter to be amended and Re-Released for signing or Deleted and Re-Drafted |
| Filed Folder | Draft completed | This status apply to an eSet which has been drafted without going through the collaborative drafting process. Once the final eBL has been created and it sits on the Inbox with the status of To Be Released and Signed, a copy is saved in the Filed Folder with the status of Draft Completed. The Drafter can select the Active Copy option to replicate the eSet. |
| Filed Folder | Completed Drafting | This status applies to an eSet that has gone through the collaborative drafting process. Once the approval has been received from all parties and the final version is created a copy of the draft is saved in the Filed Folder with the status of Completed Drafting. |
| Filed Folder | Deleted | This status applies to an eSet which has been deleted before Issuance by selecting Delete from the Other Option list of actions. |
| Filed Folder | Issued | Once the final version of the eSet has been created, signed and Issued to the title holder, a copy of the original document is saved in the Filed Folder with the status of Issued. |
Role: Exchange
| eSet Location | Status | Description |
|---|---|---|
| Inbox | Title Held | Once the eBL has been signed and Issued by the Carrier and/or the Agent, the Consignor will receive it with the status of Title Held, meaning the Consignor has title and full control of the eSet and can endorse and transfer it to a bank, a bearer holder, the named consignee on the eBL (if any) or the final buyer of the cargo. |
| Inbox | Transfer Drafted | When transferring title (either to a Bank or endorsing it to the buyer), the platform offers the functionality to draft the transfer and complete it as a 2nd action. This is because users can be given permissions in DocEx to be able to action Drafting, Sign and Send, or both. The status Transfer Drafted refers to an eSet for which a transfer has been drafted and saved. The next action to be taken will be to sign and send the transfer by a user authorized to take such an action. |
| Inbox | Amendment Requested | When holding title, the user will still be able to request amendments to the eBL by selecting Consignor Recut, Consignor Split and Consigee Recut and Split from the “Other Actions” selection in the inbox. Once the changes have been requested, the Carrier and/or Agent will have to approve or reject the request. Until that moment, the eSet will have the status of Amendment Requested. Once the Carrier and/or Agent and/or Shipper accept the request, a new eBL will be created, signed, and re-issued to the Amendment requester depending on which party generated the request and the old one will be voided and filed in the Filed Folder. |
| Filed Folder | Amendment Requested | |
| Filed Folder | Transfer sent | |
| Filed Folder | Produced | |
| Filed Folder | Convert Locked | |
| Filed Folder | eUCP Present Sent | |
| Filed Folder | Amendment Cancelled | |
| Filed Folder | eDC present Sent |
Updated 10 months ago