UK-registered +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. Why Does Invoicing Our Taxi Account Customers Take Days Every Month and Still Get Queried?
Problems We Solve

Why Does Invoicing Our Taxi Account Customers Take Days Every Month and Still Get Queried?

Taxi account invoicing drags when journeys lack PO numbers, cost centres and passenger names. We build account billing that checks jobs and sends invoices.

Updated 4 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer: TL;DR

Account invoicing takes days because the details each customer needs, such as passenger name, cost centre, purchase order and waiting time, are missing or inconsistent on the journeys, and they are fixed by hand at month end. We build account billing that checks each completed job against that customer's requirements as it happens, flags the gaps while the driver and controller still remember, and produces invoices in the format each account expects.

The last week of every month

Your account customers are the steady part of the business: a hospital trust's staff journeys, a solicitors' firm, a couple of hotels, a company that sends visitors from the station to its offices. They pay on invoice, and each of them wants that invoice their own way.

So at month end, someone in the office exports the account jobs from the dispatch system into a spreadsheet and starts going through them. One customer needs a purchase order number on every line. Another wants journeys split by department. A third will not pay for any journey without a passenger name. Waiting time was added by some drivers and not others. A few journeys were booked on the account by someone who was not authorised to book.

The invoices go out late. A week later, the queries start coming back.

Why the details are missing in the first place

The information is missing at the moment the job is booked, and nothing asks for it until the invoice is being built.

Missing detailWhy it is missingWhen it is noticed
Purchase order or referenceCall handler did not know the account needs oneAt month end, or when the customer rejects the invoice
Cost centre or departmentBooked by a PA who did not sayWhen the customer's finance team cannot allocate it
Passenger nameBooking made in the booker's nameWhen the customer queries who travelled
Waiting time and extrasDriver added it in different waysWhen the fare looks wrong to the customer
Authorised bookerNo list of who may bookWhen the customer refuses to pay for the journey

Each account's rules usually live in one person's head, or in a note pinned to the wall. When that person is off, the rules are forgotten.

The cost of late and disputed invoices

Late invoices mean late payment, and your cash flow depends on account money coming in, because you are settling with drivers every week for account work they have already done. Queried invoices are worse: the customer holds the whole invoice while one or two journeys are argued over, and your office spends hours finding the booking, the driver's record and the timing to answer them.

There is a quieter cost too. Journeys that cannot be proved, such as an unauthorised booking or an unrecorded wait, are often written off to keep the customer happy. That is money for work your drivers really did.

Account billing that checks each job as it happens

What we build keeps each account's rules in one place and applies them from booking to invoice.

  1. Each account gets a profile: required fields such as PO number, cost centre and passenger name, the list of authorised bookers, the agreed tariff or fixed prices for regular routes, and how the customer wants invoices laid out.
  2. When a job is booked on an account, the booking screen or web form asks for those fields. If your dispatch system cannot enforce this, our tool checks new account bookings through its API and flags any that are missing details to the controller the same day.
  3. When a journey completes, it is matched to its booking, and waiting time, extra stops and parking are recorded in the same way whichever driver did the job.
  4. Jobs that break an account's rules, such as an unknown booker or a fare that does not match the agreed price, go on an exceptions list for the office to sort while the details are fresh.
  5. At month end, or weekly if the account prefers, invoices are produced with the lines, grouping and references each customer needs, and a spreadsheet backup in their format if they ask for one.
  6. Invoices and payments are posted to your accounting system, such as Xero or QuickBooks, so you can see what each account owes and chase it.

Month end, most of it done already

By the last day of the month, the account journeys have been checked all month. The office clears a short list of exceptions, not a spreadsheet of hundreds of lines. Invoices go out on time and look the way each customer expects.

When a customer queries a journey, the answer is one search away: who booked it, who travelled, when the car arrived, how long it waited and what was charged. That makes it much easier to hold firm on journeys that are genuinely owed, and to credit the rare one that is not.

A new account is set up once, with its rules, rather than being learnt by trial and error over the first few invoices.

Signs your account billing needs this

  • Account invoices go out a week or more after month end.
  • Customers reject invoices for missing PO numbers or passenger names.
  • Each account's billing rules are known by one person.
  • Waiting time is recorded differently by different drivers.
  • Disputed journeys get written off because you cannot prove them.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly. A senior engineer reads every question.

Ask about your project

Will this replace our dispatch system's invoicing?

Not necessarily. If your dispatch system invoices well but lacks the checks, we add the checks. If its invoices cannot match what customers need, we produce them from its data instead.

Can it handle fixed prices for regular routes?

Yes. Agreed prices for routes such as station to office are part of each account's profile, and fares that do not match are flagged.

Does it work with Xero or QuickBooks?

Yes, both have APIs we post invoices and payments to. Other accounting systems depend on what they allow.

What drives the cost?

How many accounts have unusual requirements, what your dispatch system exposes through its API, and how invoices need to reach each customer.

What do we need to give you?

A list of accounts and their rules, a sample of a normal month's account jobs, and access to your dispatch and accounting systems.

Keep reading

More on Problems We Solve

Start here

Tell us where your taxi office loses time

Describe the bookings, the drivers and the paperwork that are causing trouble, the dispatch system you run and the accounts you invoice. We will tell you what we would build around your existing setup and what we would leave alone, and if your dispatch system already does the job with a setting you have not switched on, we will say so.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate, with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →