Table of Contents
IntroductionProcess flow
Pre-requisite
Features
Dependencies & Assumptions
Revision History
Version | Date | Author | Designation | Description of change |
1.0 | Senior Business Analyst | Draft |
...
Container Clearance is the process of clearing the containers out from the yard by booking the containers pickup and paying the container charges. Container clearance service is a bill presentment and payment settlement service that is developed to provide a unified solution for terminal users to query one or more container charges in real time, request and settle invoices through various payment channels and finally instruct the TOS system to release payment holds. Through this service, customers get visibility on their charges against the containers and initiate the invoice process which will block their PDA balance (handled in Zodiac). Once request is raisedrequest the invoice. Customers can pay for the invoices with the help of multiple payment methods (Bank receipt upload and via credit). Once the invoices are paid, entry will be made in the payment approval module where terminal users can view and take actions on the request and end users can view, edit and track their request. Through payment approval module, terminal admins will be allowed to take actions on the request (approve, reject and needs clarification) and intimate terminal to settle & generate final invoices and to release the holds on the containers.
...
In this manual, the steps to view quotes for containers(based on container number), generate invoices, pay invoices for container clearance and payment approval process to release the holds on the container are illustrated.
Process flow
Below figure depicts the process flow for the container clearance and payment approval services :
...
Pre-Requisite
Below are the pre-requisite for using container clearance :
Client Registration
a. Bill to code should be provide by user/TO at the time of client registration
Please refer mentioned URL for more details of Client Registration user manual : /wiki/spaces/DTD/pages/140345373
2. Export Booking services (Export containers)
a. Containers should be pre-register on this service, details should be approved by terminal operator team and same to be passed on to TOS for unit registration.
b. Bill to party’ provided at the time of document upload by user or Terminal operator will be used for Billing purpose (‘Bill to party’ cannot be changed on container clearance screens)
c. Uploader of the container document or the nominated ‘Bill to party’ alone will be allowed to transact for associated container in container clearance application.
Please refer mentioned URL for more details of Export booking user manual : /wiki/spaces/DTD/pages/700973409
3. Import Release (Import containers)
a. Container’s information and document should be provided and approved by Terminal operator before billing to initiate.
b. Bill to party’ provided at the time of document upload by user or Terminal operator will be used for Billing purpose (‘Bill to party’ cannot be changed on container clearance screens)
c. Uploader of the container document or the nominated ‘Bill to party’ alone will be allowed to transact for associated container in container clearance application.
Please refer mentioned URL for more details of Export booking user manual : Import Release - Cargoes by DP World - Confluence (atlassian.net)
Features
Below features will be the part of container clearance service :
...
User can view the quotation details by clicking on the quotation number hyperlink
...
| Info |
|---|
User will get the below validation error if |
...
:
|
...
|
User can view the remarks from the terminal for the invalid containers in view container popup screen as shown below.
...
...
| Info |
|---|
If user tries to generate the quotation for the same container number then user will get the below validation |
Business rules for fetching the container charges :
...
Once user will provide Type of service , bill to party and category, user will be allowed to fetch the draft/final invoices as shown below
...
...
| Info |
|---|
User can come to this screen to view the final invoices after payment request has been approved by the terminal admin. Refer to section 4 (Payment approval) for more details on payment approval flow of the request. |
| Info |
|---|
User can select multiple draft invoices for the payment and can click on proceed to pay for the invoices. User will be redirected to the draft invoice summary page as shown below. |
| Info |
|---|
User can also delete the invoices by clicking on the delete icon and can download the invoice by clicking on the download icon under ellipse. |
| Info |
|---|
User can download the receipts but only for the final invoices. |
...
Scenario | Notification to | Notification Type |
|---|---|---|
User submit the container clearance payment approval request | Terminal admin will be notified | Web and Email |
Terminal admin approved/rejects the request | User will be notified | Web and Email |
Terminal admin raises clarification | User will be notified | Web and Email |
Scheduler rejects the payment approval request based on the paid through date | User will be notified | Web and Email |
User raises the cancellation request | Terminal admin will be notified | Web and Email |
Comments raised by the user | Admin will be notified | Web |
Comment raised by the admin | User will be notified | Web |
Dependencies & Assumption
Dependencies
...
a. Client registration
i. Bill to code should be provide by user/TO at the time of client registration
b. Export Booking Service (Export containers)
i. Containers should be pre-register on this service, details should be approved by terminal operator team and same to be passed on to TOS for unit registration
ii. Bill to party is mandatory for billing and should be provide at the time of container registration .
c. Import Release (Import containers)
i. Container’s information and document should be provided and approved before billing to initiate.
ii. Bill to party is mandatory for billing and should be provide at the time of container registration.
d. TOS
i. API to support Query of charges, Draft Invoice creation
ii. API to Fetch final and draft invoice
iii. API to finalize Invoice and release payment holds
Assumptions
· TOS to perform all calculation for Invoice, CCS will not hold any logic for charge calculation
· Export booking will pass the data to TOS to allow billing process to continue.
...
Invoice finalization or settlement fails | User will be notified | Web and Email |