Every load, from the yard to the ledger.
Dispatch, the driver’s phone, billing, settlements, payroll and accounting on one record. Built in Canada for carriers who haul in two currencies and answer to CRA.
- Port of Vancouver05:40 Picked up at the terminal. Pre-trip signed on the driver’s phone.
- Coquihalla, BC08:10 Rolling. Position and ETA reach the board without a phone call.
- Trans-Canada, Rockies14:30 On schedule. Hours of service checked against the appointment.
- Calgary, AB19:05 Delivered with signed proof. Invoiced and posted by 19:20.
Everything a trucking company runs on.
Dispatch, the driver’s phone, billing, pay, payroll, maintenance and the books — one product, one record. These are real screens from a demo carrier; click any of them to see it full size.
Every load by status, lane, driver and revenue — who needs a driver, what is rolling, which ETAs are at risk.
Watch one load move.
Loaded at the yard, driven under the Rockies, unloaded at the receiver, signed for. Alongside it is the driver’s phone at each step, and every tap on it lands on the dispatcher’s board as it happens.
Loading
On the road
At the receiver
Delivered
Sound familiar?
The problems carriers bring to us are rarely about software. They are about money that leaks between the dispatch board, the office and the books.
Loads sit delivered for days before anybody bills them.
The board shows Ready to invoice the minute a load delivers, and batch billing invoices them in one pass.
Detention you never charged for.
Arrival and departure stamp themselves at the gate, and drivers file detention from the app, so the hours have a timestamp behind them.
Every settlement turns into an argument.
Driver pay is built from the loads they ran, and drivers see their own settlements and stubs on their phone.
IFTA week.
Miles by jurisdiction and fuel purchases are already in the system. The quarterly return is a report, not a project.
Month end takes a week because nothing agrees.
Dispatch, billing, payroll and the ledger are one system, posting as the work happens.
You find out about margin after the quarter.
The owner cockpit shows margin per load and per mile as loads deliver.
Follow one load through the system.
Six screens, in the order a load lives through them. Every one is the real product running on a demo carrier.
Step 1 of 6
Price the lane and send the quote
Rate cards and lane history price it. When the customer says yes, the quote becomes the load. Nothing is typed twice.
See it from your seat.
Owner, dispatcher, office and driver use the same system, and each sees the part of it that is their job.
Know where the money is today, not at quarter end.
- Margin per load and per mile, as loads deliver
- Cash on hand, what customers owe and what you owe
- On-time delivery against the appointment
- Answers without waiting on the bookkeeper
Surrey to Calgary
Left the site 07:02
Appointment 18:00–20:00
The trip runs from the driver’s phone.
A driver app built around the job, not a portal squeezed onto a small screen. It keeps working where the signal does not.
Inspections that stand up
Pre-trip and post-trip DVIRs, with defects tracked through repair and sign-off.
Stops stamped at the gate
Arrival and departure recorded by geofence, so detention has a timestamp behind it.
Paperwork in one photo
Bills of lading and proof of delivery, signed and attached to the load.
Works offline
Every action queues on the phone and sends when the truck finds signal.
Dispatch in one thread
Messages with read receipts. No personal numbers, no lost texts.
Pay they can see
Pay stubs, settlements and expense claims, with hours of service read from your certified ELD.
For iPhone and Android.
The back office, without the second system.
No nightly export to QuickBooks and no payroll service on the side. The ledger posts as the work happens, so month end is a review rather than a rebuild.
Accounting
A real general ledger, not a summary of one.
- Double-entry postings in real time
- Bank reconciliation and deposits
- Receivables aging, statements and collections
- Payables, vendor credits and fixed assets
- GST/HST returns from the posted figures
Payroll and people
Drivers, shop and office on one payroll.
- Withholding checked against CRA’s own calculator
- Per-mile, hourly and salaried pay
- T4, ROE and PD7A remittances
- Provincial statutory holidays and overtime
- Time clock, rosters, leave and policies
Fleet and compliance
The paperwork that keeps trucks on the road.
- IFTA fuel tax by jurisdiction
- ACE and ACI eManifests, built from the load
- Preventive maintenance, work orders and parts
- Driver qualification files and training
- EDI 204, 210 and 214 with your shippers
Built in Canada, for the border you cross.
For carriers who run Surrey to Seattle on Monday and Calgary to Regina on Tuesday, the details that decide whether the books are right are Canadian ones.
- Two currencies, kept apart
- CAD and USD on the same books, never added into one meaningless total.
- Sales tax split at posting
- GST, HST and PST land in the right accounts, ready for the return.
- Payroll by edition date
- CRA’s tables as they stood on the pay date, including mid-year changes.
- Both sides of the border
- ACI into Canada and ACE into the United States, built from the load you already entered and filed through BorderConnect.
Moving over without stopping the trucks.
You do not have to wait for year end. Pick a conversion date and bring your books across as they stand on that day.
Bring your books across
Open invoices, vendor and carrier bills, your fleet with its depreciation, and outstanding bank items, loaded as of your conversion date.
Run both side by side
Compare against your old system’s trial balance until the two agree, line by line.
Go live when it matches
Switch over when the numbers agree. If something turns up, going live can be rolled back rather than patched over.
One system instead of three.
What changes when the TMS, the books and payroll are the same product.
| Task | A TMS, QuickBooks and a payroll service | Alba365 |
|---|---|---|
| Billing a load | Re-keyed from dispatch into accounting, then checked. | The delivered load becomes the invoice. |
| Paying drivers | Miles exported, pay calculated in a spreadsheet, entered again. | Settlements built from the loads they ran. |
| Payroll | A separate service with its own employee list. | The same people, the same hours, the same ledger. |
| Month end | Three systems reconciled against each other. | One ledger that posted as the work happened. |
| A question from the owner | Wait for the bookkeeper. | Margin, cash and receivables on the cockpit, now. |
Questions carriers ask us.
Does it replace our ELD?
No. Alba365 reads hours of service from your certified ELD and shows it to dispatch. It is not an ELD itself, and you do not have to change devices.
Does the driver app work without signal?
Yes. Inspections, stop times, photos and messages queue on the phone and send when the truck finds signal again. Nothing a driver does is lost to a dead zone.
We haul into the United States. Does it handle US dollars?
Yes. Customers, invoices and payments can be in US or Canadian dollars, kept apart on the same books, with the exchange difference booked when you are paid. ACE and ACI eManifests are built from the load and filed through a connected BorderConnect account.
Can our accountant keep working the way they do?
Yes. Give them a login with the permissions you choose, or export the ledger to QuickBooks IIF or CSV if they prefer to work there.
How is our data kept separate from other carriers?
Each company’s data is isolated in the database itself, so one carrier’s records can never appear in another’s, even if a screen had a bug.
How much work is it to set up?
Mostly your own data. Trucks, parts and rate cards import from spreadsheets, and your open invoices, bills and fleet come across from your old system on the date you choose.