Bill waiting time and loading charges per shipper
From driver logs, dispatch sheets, and tachograph records, pick out waiting and loading work per shipper that draft invoices miss. Staff decide what to bill.
- Runs on your own PCs and servers
- Use Azure OpenAI, Amazon Bedrock, Google Vertex AI, or an in-house model
- Its engine is Descarty's open-source Dagu (GPL-3.0)
The problem today
At month end, invoices for each shipper are made from driver logs and dispatch sheets. The log may say "waited 2 hours" or "hand-loaded," but it never reaches whoever writes the invoice, so waiting-time and loading charges go unbilled.
The workflow in Kitewell
- Collect driver logs and dispatch sheets (Excel) and tachograph records (CSV)Automatic
- AI picks out waiting time and loading or unloading work per trip and per shipperAI judgment
- Compare with each shipper's agreed rates and list what the draft invoices missAutomatic
- Dispatch and accounting review and approve the items to billApproval
- Add the approved items to each shipper's invoice lines (Excel)Automatic
What AI does
Reads the different ways drivers write it, such as "wait 2h" or "120 min waiting," and picks out waiting and loading work per trip and per shipper, quoting the log entry behind each.
Where people decide
Staff decide what to bill under each shipper's contract and agreements.
Prove Kitewell on your own systems
Try it free for 14 days on your own PC. To see it working first, ask for a 30-minute demo. There is also a one-month onboarding (¥500,000 before tax), where we build your first job together.
What to check when you try this work
- Whether waiting and loading work are picked out across different writing styles
- Whether each shipper's agreed rates can become matching rules
- Whether gaps between tachograph records and log times are shown
How the onboarding runs
- Week 1Requirements and success criteria
- Weeks 2 to 3Build
- Week 4Verify on production screens
- Final dayReport
One-month onboarding
- Length
- One month
- Cost
- ¥500,000 (tax excluded). Your staff build, with the developer beside them
- If you go on to a license
- The onboarding fee is credited to the first year's contract
- Without the onboarding
- At Team scale, start on Team monthly (¥14,800 per computer a month, tax excluded), and cancel in any month
You can try it first on your own PC, in the free 14-day trial.
Frequently asked questions
- Do our documents and screens leave the company?
- Kitewell runs on your own PCs and servers, and Descarty never receives your business data. You choose the AI model: a cloud API, or an in-house or local model with an OpenAI-compatible API. With an in-house model, no data leaves the company. With a cloud model, what the AI reads is sent to the model's provider.
- What if the AI misreads something?
- A person checks what the AI produced before the work goes on. In a sheet, every value the AI reads shows the quote it came from, and rows below your confidence threshold go to a person. Reviewers can send work back with notes on what to fix, and who approved what is kept in the run history.
- What happens when a screen changes or a run stops?
- When a screen changes, the AI reads it again, relearns the step, and carries on. The relearned step is saved, and later runs repeat it. If a run still stops, ask the assistant right there, and it finds the cause and proposes a fix. A proposal is not saved until a person applies it.
- What happens to the RPA and systems we use today?
- Keep them. Kitewell operates screens the way a person does, so it works with systems that have no API. Move the robots that keep stopping and the work you gave up automating because it needs judgment, and leave fast, fixed processing in your current RPA.
- What does it cost?
- ¥14,800 per computer per month, or ¥148,000 per computer when paid yearly, before tax. A computer costs the same whether it builds or runs. You can try it free for 14 days. The one-month onboarding, where we build your first job together, is ¥500,000 before tax, credited to the first year if you go on.
Related use cases
Reconcile freight invoices
Match carriers' freight invoice lines against shipment records, and send lines with weight, distance, or surcharge differences for approval.
Look up tracking numbers in bulk
For an Excel list of shipments, delivery status from each carrier's site goes into each row, and the shipments that need action are shown.
Book truck arrival slots in each shipper's system
For each trip on the dispatch sheet, enter the slot, truck, and driver in each shipper's or warehouse's booking system and write the booking number back.
See this work in a demo
A 30-minute demo shows this workflow running. The 14-day free trial lets you check it on your own systems.