Skip to content

Approval workflowsPut a named decision behind every exception.

Approval queues for new customers, B/L issue before receipt, delivery order release or extension, and extra free days.

Container train running through an inland container depot

Platform

Overview

Some steps in a shipping office should not pass on one person's word. Sailix has four approval points: new customer registrations, issuing a B/L before its invoice is receipted, generating or extending a delivery order ahead of payment, and extra free days on containers. Each has its own queue of pending requests.

The B/L and delivery order queues open a gate that would otherwise refuse. The desk that is blocked raises a request, an approver writes a remark and approves or rejects, and the name and time are kept. The right to approve is granted per role, and the default member role does not have it.

Capabilities

What it does

  • Customer approvals

    Review new customer registrations with contact details, tax numbers and uploaded KYC documents. Approval needs at least one tax identifier, and rejection needs remarks.

  • B/L issue approval

    A B/L is issued once it is customer-confirmed and its export invoice is receipted. If the receipt is missing, the desk requests approval to issue.

  • Delivery order approval

    One queue answers both delivery order questions: releasing before payment, and extending validity while detention is still owed.

  • Free days approvals

    Extra free days set against a B/L or booking stay pending until the line approves them, or the agency approves on the line's behalf.

  • Remarks and decision record

    Each request stores the reason given, who asked, who decided, when, and the approver's remark. Decided requests stay listed below the pending ones.

  • Approve right per role

    Users with view rights can read a queue, but only roles holding the approve right can decide. Owners and administrators have it from the start.

Workflow

How it works

  1. First

    A gate refuses

    Issuing the B/L or extending the delivery order is blocked because the payment it depends on has not been receipted.

  2. Then

    The desk requests approval

    The user presses Request approval. Pressing it again returns the request already waiting instead of adding a duplicate.

  3. Next

    An approver decides

    From the Approvals menu, the approver reads the reason, writes a remark and approves or rejects the request.

  4. Finally

    The step goes ahead

    An approved request lets the blocked step through. A request that has been decided cannot be decided a second time.

Questions

Questions and answers

Can a B/L be issued before the invoice is paid?

Only with approval. Sailix issues a B/L when the customer has confirmed the draft and the export invoice is receipted. If the receipt is missing, the user requests approval, and someone holding the approve right on BOL Issue Approval can allow it with a remark.

What does Sailix check before approving a customer?

The customer must have at least one tax identifier on file: PAN, TAN, GSTIN, VAT or service tax number. Uploaded KYC documents are shown to the reviewer but are optional. A customer that fails the check can still be rejected with remarks and sent back for correction.

Who can approve free days in Sailix?

The shipping line can approve or reject free days requests for its own containers from the liner portal. The agency that raised the request can also approve it on behalf of the line. A rejection must carry a reason, and only pending requests can be decided.

Is there an audit trail for approvals?

Yes. Each B/L issue and delivery order request keeps who asked, the reason, who decided, the time of the decision and the remark. Customer records show who approved or rejected them, along with the rejection remarks where there are any.

Get started

Put your whole shipping desk on one system.

Create your workspace and run your first job from booking to settlement.