Skip to main content
GullySystem
Automotive

Invoice Management for Taxi operators

Record the customer’s taxi charge from the agreed fare basis and actual ride outcome without duplicate billing.

Finance & Accounting

Does this function belong in your operation?

For direct passenger and account rides requiring an authorised customer bill linked to the trip.

A completed journey or another accepted charge becomes billable under the operator’s actual terms.

Use the accepted fare basis and actual journey outcome to explain the customer charge. A direct ride and an account-billed ride have different collection records even when the same driver performs both. Retain toll, waiting or route-change evidence where the agreement requires it. Do not create duplicate office and driver bills for one obligation. A disputed addition or cancellation fee needs the appropriate decision before a charge or credit is issued.

Bring the records the workflow depends on.

  • Actual trip, customer or account debtor and fare agreement
  • Supporting waiting, toll or changed-route evidence where relevant
  • Previous bill, verified collection references and accountant-confirmed settings

Outputs to check

  • Trip-linked customer bill
  • Fare additions awaiting review and duplicate-document exceptions
  • Outstanding amounts and authorised correction history

Follow the invoice management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Identify the chargeable outcome

    Distinguish performed travel from cancellation or unsuccessful pickup. Apply only the accepted basis for that outcome rather than a completed-ride charge by default.

  2. 2. Review the fare evidence

    Compare the original agreement with actual additions and customer decisions. Keep an unsupported toll or waiting line in review instead of inventing evidence.

  3. 3. Check the billing channel

    Identify any driver-issued or external-platform document before creating an office bill. The same obligation must not become two customer charges.

  4. 4. Issue the reviewed document

    Use authorised numbering and the correct passenger or account details. Preserve trip and fare references behind each line.

  5. 5. Resolve payment and corrections

    Apply only verified receipt allocations and authorised credits. A cancelled charge, refund approval and returned money have separate records; driver remuneration follows its own agreement.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Fare reviewer

Matches actual trip evidence to the accepted basis and additions.

Billing clerk

Checks the correct debtor and previous document before issue.

Accounts approver

Authorises corrections and preserves separate collection and driver-account records.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Driver and office both prepare a bill

Identify the original charge and authorised issuer before creating or correcting another document.

Passenger disputes waiting or tolls

Retain the accepted terms and actual evidence for the decision owner; do not erase the disputed event.

Account ride shows no cash collection

Keep the agreed account debtor and uncollected balance without charging the driver as the passenger.

Cancelled trip incurred cost

Review the actual cancellation terms and authorised cost treatment; neither a full fare nor a refund is automatic.

Can this work independently?

Invoicing can use entered accepted fare and trip evidence without an automated meter or dispatch connection. Accounts determines tax and document treatment. Payment processing, bank reconciliation and external-platform settlement require separate verified processes.

Systems and records it connects with

  • Actual trip outcome and accepted fare terms.
  • Customer receipt and driver-issued document references.
  • Approved credit or refund decisions with actual payment evidence.

Configure, test and introduce the workflow.

  • Compare a direct paid ride, account journey and unsuccessful pickup.
  • Test duplicate billing and an unsupported waiting charge.
  • Review a cancellation correction without treating it as an executed refund or driver payment.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Each billed outcome has an accepted charge basis.
  • A direct ride is not billed twice through driver and office channels.
  • A bill does not establish customer payment or driver settlement.
Taxi operators

How the business operates.

The dispatcher takes a telephone booking while another driver reports a stand pickup. Both rides need a trip record, but only one passed through the reservation desk. A taxi operator must reconcile those operating records with what each driver collected and what reached the office. This scope covers directly managed taxi journeys from calls, a stand or permitted digital requests, including future reservations and accepted outstation work. It focuses on dispatch decisions, actual ride outcomes and shift collection records. App-origin work remains a separate source when the operator actually handles it. The workflow is a requirements proposal, not a claim that automated dispatch, live maps or payment processing are installed.

Booking and reservation desk

Record pickup details, intended passenger, fare basis and agreed payment method. Distinguish immediate requests from future reservations. A request is not a confirmed pickup until the operator has made and communicated its actual booking decision.

Dispatch and shift control

Keep driver availability, current assignment and vehicle identity aligned with reported events. Record an accepted dispatch separately from an offer or message. If a driver releases a future job or a ride runs beyond the planned end, review the next commitment instead of assuming capacity.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Booking source, passenger contact and pickup or destination details
  • Requested time, confirmation and later change history
  • Agreed fare basis, inclusions and payment method
  • Driver shift, vehicle identity and accepted dispatch

Operational bottlenecks to check

A future booking loses its driver

The assigned driver releases the job but no replacement accepts. Retain the unassigned state and customer communication decision instead of keeping a confirmed driver name from the earlier plan.

One ride produces two payment claims

A driver reports cash while the passenger says the office was paid. Compare the actual evidence and collector before changing either record or charging again.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Capture the ride request

    Record the pickup and destination with the agreed fare basis. A regular rider’s history is context; confirm the current journey instead of silently repeating an old destination.

  2. 2. Make the booking decision

    Check capacity for the requested work and communicate the actual decision. Future reservations remain subject to active allocation review; no message alone proves a driver has accepted.

  3. 3. Record the assigned trip

    Link driver, vehicle and source booking. Add direct-driver or stand pickups through the operator’s actual process so they do not disappear from shift reconciliation.

  4. 4. Preserve the actual outcome

    Record pickup, completion, cancellation or unsuccessful collection with the source evidence. Retain changed destinations and disputed additions separately from the original fare agreement.

  5. 5. Reconcile customer money

    Identify who collected the payment and how it was verified. Keep an account fare outstanding when nothing was collected, rather than requiring the driver to report cash that never changed hands.

  6. 6. Close the shift record

    Compare recorded trips, collections and actual office handover. Leave unexplained differences assigned for review; ending a shift does not settle driver pay, customer credit or a pending refund.

Industry reports to connect with

  • Requested rides awaiting a booking or dispatch decision
  • Future reservations with released or conflicting assignments
  • Completed, cancelled and passenger-not-found trip outcomes
  • Trip charges awaiting evidence or dispute review

Questions before implementation.

When should taxi operators consider invoice management?

For direct passenger and account rides requiring an authorised customer bill linked to the trip. A completed journey or another accepted charge becomes billable under the operator’s actual terms.

What should we bring to the requirements discussion?

Bring anonymised examples of Actual trip, customer or account debtor and fare agreement; Supporting waiting, toll or changed-route evidence where relevant; Previous bill, verified collection references and accountant-confirmed settings. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Record the customer’s taxi charge from the agreed fare basis and actual ride outcome without duplicate billing. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

The bill does not set official tariffs, establish pickup rights or decide driver wages, liability or refund entitlement.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Each billed outcome has an accepted charge basis. Use this check when reviewing the first working version.

Talk to us

Discuss invoice management for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements