Chart of account maintained in the system
Not alongside it
Powered by STOS, the Smart Terminal Operating System
Terminal billing that posts straight to the ledger
Accounts is where handling turns into money. Tariffs are assigned against the services a container actually consumed, billing runs from the same records operations worked in, and the position per party is live rather than reconstructed at month end.
How the module runs
● 5 stages
Service recorded
01Tariff applied
02Invoice raised
03Receipt
04Ledger
05
Why it exists
Re-keying operations into accounts is where the money leaks
In most terminals the operational system records what happened and the accounting system records what was billed, and the two are joined by somebody exporting a spreadsheet. Everything that was done but not billed disappears in that gap. Accounts closes it by billing from the movement record itself, so a service that was recorded is a service that gets invoiced.
What Accounts covers
Tariff assigning per party
Service and container type
Terminal billing generated from movements already recorded
AR and AP ageing reported without a separate extract
Party balance visible to operations as well as to finance
Settlements and adjustments recorded against party and container
Set up
Rates that reflect the agreement
Every party has its own commercial terms. The tariff structure is what keeps that from becoming a manual calculation.
Chart of account
Maintained inside the platform, so postings land where finance expects them without a mapping step.
Tariff assigning
Rates set per party, per service and per container type, which is how terminal agreements are actually written.
Charge structure
The services a container can consume, priced so that billing is a lookup rather than a judgement.
Billing
Invoices from the movement record
Nothing is re-keyed. The invoice is produced from what operations already recorded.
Terminal billing
Generated from recorded handling, storage and services, against the tariff assigned to that party.
Invoices and adjustments
Raised, adjusted with a reason and settled, each posting kept against the party and the container.
Settlements
Receipts and payments applied to the party account, so the balance moves as money moves.
Position
Where every party stands, now
Finance and operations look at the same balance, which is what stops a container being released against an unpaid account by accident.
AR ageing
Receivable by party and age, reported from the ledger rather than from an extract.
AP ageing
Payable by vendor and age, over the same data the Procurement module feeds.
Party balance
The live position per party, visible to operations as well as to finance.
Roles
Who sees what
Access is granted per module and per role, so two people signed into the same platform see different work.
| Role | What the role works with |
|---|---|
| Billing clerk | Terminal billing runs, invoices, adjustments with reason |
| Receivables | AR ageing, receipts, settlement against party accounts |
| Payables | AP ageing against vendor invoices from Procurement |
| Finance manager | Chart of account, tariff assigning, period control |
| Operations | Party balance, so release decisions are informed |
| Administrator | Role access and assignment |
How it fits
Billed from the same record operations worked in
Accounts is not a finance system that receives a file. It reads the handling, storage and service records STOS core produced, prices them against the tariff assigned to that party, and posts the result. There is no export and no reconciliation step between the two.
- Single sign-on with STOS core and every other module
- One party master shared with CRM and with terminal operations
- Vendor invoices arriving from Procurement against approved orders
- Storage and depot charges billed in the same run
FAQ
Questions buyers actually ask
It handles terminal billing, the party ledger and AR and AP ageing against the operational record. Many operators run it alongside a general ledger and post summary entries across; others run it as the ledger. Which fits depends on your audit arrangements.
Tariffs are assigned per party, per service and per container type, which is the shape terminal agreements are written in. Billing then applies the assigned rate rather than asking someone to remember it.
Party balance is visible to operations, not only to finance, which is the control that makes that an informed decision rather than an accidental one.
From the Procurement module, against an approved purchase order and a goods receipt, so AP ageing reflects commitments that were actually authorised.
Billing sits at the centre of the platform and Accounts is where it is administered. It is licensed as a module like the others.
See Accounts on your own terminal data
Bring your own customers, tariffs and volumes and we will walk the module end to end on a live system.