A complete example
Training example: ABC Trading ships 1 × 40HC of consumer goods from Port Klang to Jakarta. Amounts are made-up practice figures.
One page to see it all: when to open a Booking, when to work in a Shipment Job, when to make a Bill of Lading, and when you can finally raise an Invoice — plus the most important question: why use this plugin at all.
A forwarder's daily headache: one shipment's information is scattered across Excel, email, WhatsApp and AutoCount — retyped, easy to get wrong, and hard to tell if you made money at month-end. Orivia Shipping pulls it all into one place, inside AutoCount.
In one line: less typing, fewer mistakes, operations-to-accounts in one flow, every shipment clear, always traceable.
Remember this one line and you're set. The first half is "arranging", the second half is "getting paid"; each step carries its data forward.
When a customer gives you the job and you haven't started detailed work yet — record the request (customer, ports, vessel, estimated dates).
The real operation starts here. Containers, cargo, documents and charges all live here — the master file for this shipment.
When the cargo is going on board and needs a proper transport document, make the B/L from the Job; prepare SI and VGM for the carrier.
When the charges are all checked and it's time to bill the customer, raise the Invoice in AutoCount. This is the one that gets you paid.
| Document / record | When to use | Who | Remember it as |
|---|---|---|---|
| Booking | Just got the job, no detailed work yet — record the request | Customer service | Got the job? Write it down |
| Booking Confirmation | After the Booking is confirmed + a Job is created — show the customer the arrangement | CS / Docs | The arrangement on one page |
| Shipment Job | Real operation begins; schedule, containers, docs, charges all here | Ops / Docs / Finance | The master file |
| SI / VGM | Give the carrier document instructions; declare the loaded container weight | Docs / Ops | Instructions + weight for the carrier |
| Bill of Lading | Cargo going on board, needs a formal transport document | Documentation | The cargo's transport document |
| Invoice | Charges checked, time to bill the customer | Finance | The bill that gets you paid |
The invoice is the last step and the strictest. Once these four are in place, raise it in AutoCount.
You can also go SO → Invoice directly, depending on your flow. It uses AutoCount's official transfer, not retyping.
Training example: ABC Trading ships 1 × 40HC of consumer goods from Port Klang to Jakarta. Amounts are made-up practice figures.
No. The B/L is the cargo's transport document; to collect you raise an Invoice in AutoCount, and actually getting paid is another matter.
A Booking is "recording the request" (the intention; CS records it first). A Shipment Job is "doing and filing it" (the operations hub where all later work hangs). Create the Job from the Booking and the data carries over.
Not necessarily — you can create a Shipment Job directly. But to produce a Booking Confirmation, you first need the Booking confirmed and linked to a Job.
No. You can go SO → DO → Invoice, or SO → Invoice directly, depending on your flow and settings.
No. Shipping data sits in the plugin's own tables (it doesn't touch AutoCount's core accounts); SO / DO / Invoice are still created and managed properly by AutoCount.
Your gross profit will be overstated. Put both BUY costs and SELL charges on the same Job so Revenue − Cost = Gross Profit is accurate.