How Frakt24 fits together
Get an overview of how a job moves through Frakt24, from setup and order to driving, invoice and accounting.
Goals and why
What you will learn
- the steps a job goes through, from order to invoice
- who does what: administrator, dispatcher, driver and finance
- where in the menu you find each step
- why what you do affects your colleagues
Everything in Frakt24 is connected. The administrator sets up prices and options. The dispatcher uses them when the order is entered and sent to a driver. The driver confirms in the app, and finance creates the invoice from what is on the order.
When you know where you are in the chain, you understand why some fields must be filled in, and where to look when something doesn't add up.
Key terms
Show me
First you see the main menu in Frakt24. Click a part of the image to see what it is used for. Below the image you can click through the steps in the chain.
Master data
AdministratorThe registers are the building blocks everyone else picks from: departments, vehicle types, goods types and service types.
Why it matters: If a service type or vehicle type is missing here, the dispatcher cannot choose it on the order.
Resources and vehicles
AdministratorWho drives and with what. Each resource has a communication channel: the driver app, email, EDI or manual.
Why it matters: The channel decides how an assigned order reaches the driver. The wrong channel is a common reason why “the driver didn’t get the order”.
Prices and products
Administrator and financePrice codes, price groups and products that price the orders automatically, plus the customers’ own price agreements.
Why it matters: The price groups control the VAT rate and accounting account. If something is posted wrong, this is where to look.
Order
Dispatcher, customer web or EDIThe order is built in five steps: Customer, Assignments, Description, Time and Product. It can also come in from the customer web or via EDI.
Why it matters: Everything that happens later, from price to invoice, builds on what is registered here.
Assignment and planning
DispatcherThe order lands in “All unassigned orders”. The dispatcher assigns it to a resource, plans it in the calendar or puts it on a route.
Why it matters: The goal through the day is to empty the list of unassigned orders.
Execution
Driver in the appThe driver accepts the order and confirms each stop in the app. Status and proof of delivery come back to the system in real time.
Why it matters: The dispatcher sees the progress without calling, and the customer can follow the shipment in the customer web.
Invoice
FinanceFully priced orders that are ready for invoicing become invoices. Credit notes and resending are done under Search invoice.
Why it matters: A completed trip that does not show up in invoicing is usually not fully priced or not ready for invoicing.
Accounting
FinanceInvoices and settlements are exported to the accounting system, to the right account and per department.
Why it matters: Export format, invoice numbering and KID (payment reference) are set in the client settings under Accounting.
Driver settlement
FinanceThe second money flow from the same trip: the settlement that pays drivers and subcontractors.
Why it matters: When the settlement is generated, the orders in it are locked so they are not paid twice.
Time and payroll
Time and payrollFor your own employees: daily reports are approved, checked against the tachograph and passed on to the payroll export.
Why it matters: The time the driver registers in the app is the basis. Approval happens per day and per period.
Try it yourself in Steptour
An interactive walkthrough recorded in Frakt24. You click through the steps yourself, and it opens on top of this page.
Try it yourself
Check yourself
All correct completes the lesson- Start every customer training here, whatever the role. It saves questions later.
- The framing for support cases: "Where in the chain did it stop?" Master data, resource, price, order, assignment, execution or invoice.