BAS

BAS is the Ukrainian ERP platform built on the 1C:Enterprise core, with accounting, finance and the BAS Fleet Management module, installed on-premise at the customer. Dispatchers work trips in Cargofy, accountants keep the books in BAS, and both work from the same records. The logistics director of a company with a private fleet usually switches it on, together with the integrator who maintains the BAS installation and the IT admin who publishes the database.

What teams use it for

Dispatch a trip without re-keying it

The accountant creates the trip document in BAS. It appears in Load Hub with the vehicle, driver and route attached from the BAS catalogs. When the dispatcher reassigns a truck in Cargofy, the change is written back and the trip is posted in BAS. The trip is typed once.

Keep the fleet list in one place

The accountant marks a truck out of service in the BAS vehicle catalog. Cargofy reads the change over OData and the truck drops out of Fleet, so the dispatcher planning tomorrow's trips does not see it. New trailers, drivers on leave and route splits follow the same path: the change is made once in BAS, and the dispatcher plans against the list the accountant maintains.

See trip cost when the trip closes

Fuel balances, mileage and cost registers build up in BAS as the trip runs, yet the cost of a Kyiv to Lviv trip is often known only at month end. Cargofy reads the registers into Reports and Finance, and a digital worker builds the trip cost card when the trip closes: fuel, mileage and expenses against the trip's revenue. The AP clerk sees margin per trip.

File transport documents against the trip

After a Kyiv to Lviv trip, the accountant posts the transport document in BAS. Cargofy reads the posted document over OData, or through the HTTP service your integrator wrote for it, and attaches it to the trip in Documents with the status set to posted. When the customer asks for it a week later, the dispatcher sends it from Documents without asking the accountant. Both see one document with one status.

Report on the fleet without an export

Management wants fleet utilization, fuel per kilometre and cost per route every week, usually built by hand from BAS exports. With the registers in Reports, a digital worker produces the weekly view from the same data, filtered by vehicle, driver or route. The logistics director reads it Monday morning. If a number looks wrong, the source is the BAS register.

How it fits your stack

BAS stays the book of record. Cargofy reads counterparties, items, vehicles, drivers, routes, trip documents and cost registers, and writes trip documents and statuses back. It does not touch your chart of accounts or post accounting entries. Setup is per installation: your integrator publishes the database on a web server with OData enabled and HTTP authorization, and Cargofy maps your catalogs and registers and agrees any custom HTTP services. BAS has no cloud API, so the connection works only once the database is published.

Who it is for

Ukrainian shippers and carriers with a private fleet running BAS Fleet Management on-premise. Dispatchers work trips in Load Hub, the AP clerk reconciles costs in Finance, and the integrator and IT admin own the published database.