Skip to main content
GullySystem
Automotive

Receipts Management for Airport taxi services

Record money received and allocate it to customer balances.

Finance & Accounting

Does this function belong in your operation?

Use when payments need matching to bills or customer advances.

A payment arrives.

Choose a transaction associated with “Airport pickup with flight tracking” that requires this accounting function. Trace its supporting documents through review and posting with your finance team.

Bring the records the workflow depends on.

  • Customer references
  • Payment details
  • Allocation rules

Outputs to check

  • Numbered receipt record
  • Invoice allocation statement
  • Unallocated and uncleared payment list

Follow the receipts 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 payment

    Capture payer, date, method and transaction reference.

  2. 2. Verify the evidence

    Distinguish reported payment from cleared or settled money.

  3. 3. Issue the receipt

    Use the authorised numbering and preserve the original details.

  4. 4. Allocate the amount

    Apply it to bills or retain a named advance.

  5. 5. Reconcile exceptions

    Resolve unmatched payments, reversals and overpayments through approved adjustments.

Who uses the module, and who approves?

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

Collection agent

Issues receipts on the route from a phone, so the customer holds proof before the agent reaches the office.

Accounts assistant

Sees the day’s collections by mode, cheques waiting to clear, and advances that still have no bill against them.

Owner

Sees what came in today and this week, and which customer paid after three reminders.

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.

Payment has no invoice reference

Keep it as an identifiable unallocated amount pending investigation.

Cheque or transfer reverses

Record the reversal and restore the affected outstanding balance.

Customer overpays

Retain the excess as an approved advance or route a refund through the payment process.

Can this work independently?

Receipts can be entered independently with customer balances supplied by accounts. Invoice connections support allocation; bank reconciliation confirms clearance or settlement. The receipt module records money reported as received but should not treat an unverified screenshot as final bank evidence.

Systems and records it connects with

  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Customer ledger: Invoice balances, allocated receipts and approved credits.
  • Your accounting software: Posted financial entries and reconciliation references.
  • Card, wallet and payment gateways: Authorised payment attempts, outcomes and settlement references.

Configure, test and introduce the workflow.

  • Show us the receipt book and cash routine. We write back the payment modes and number series you need.
  • You choose the receipt format and who may issue. A sample receipt arrives for your approval. Invoices come from your records. A trial lets you settle a few against receipts.
  • Counters and collectors take receipts on the screen. The paper book is put away when they are trained.

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.

  • Receipt numbers are unique.
  • Partial payments leave accurate balances.
  • Unallocated money remains visible.
Airport taxi services

How the business operates.

An airport taxi operator takes advance bookings, counter requests or travel-desk orders and allocates suitable cars and drivers to pickup times. The passenger, the person booking and the paying organisation can be different people. Flight changes, terminal instructions and waiting charges affect dispatch and billing. This illustrative operating model fits an operator managing bookings and trips; a marketplace matching independent drivers requires a different commercial and technical scope.

Booking desk and account service

Record passenger and booker contacts separately, alongside flight, terminal, destination, vehicle class and fare agreement. A hotel or corporate account needs its billing reference and the person authorised to change a booking.

Dispatch and holding-lot coordination

Allocate a driver and car against pickup time and availability. Where the operator runs a holding-lot queue, keep entry and release decisions visible. A revised arrival time needs acknowledgement rather than an assumed change.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Booking number, booker, passenger and payer contacts
  • Flight, terminal, pickup point, destination and vehicle class
  • Fare rule, waiting allowance and approved extra charges
  • Driver allocation, vehicle assignment and acknowledgement

Operational bottlenecks to check

The flight changes but dispatch does not

A new arrival time is useful only if the dispatcher and assigned driver receive and acknowledge it. Define how the desk responds when a feed or message is unavailable.

Booker and passenger receive different information

A family member or travel desk can hold the booking while the traveller's phone is offline. Specify which details reach each contact and who is authorised to request a change.

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 and confirm the booking

    Record who is travelling, who booked and who pays. Confirm the pickup instructions and fare basis before treating the car request as accepted.

  2. 2. Review arrival changes

    Update the expected arrival through the agreed manual process or supported feed. Record who acknowledged the changed pickup time and whether the original car and driver remain available.

  3. 3. Allocate the car and driver

    Check availability and the operator's readiness criteria before dispatch. A reassignment needs a recorded reason and updated information for the people relying on the earlier confirmation.

  4. 4. Perform and record the trip

    Capture pickup, destination and completion against the same trip number. Waiting, tolls and other extras need the agreed evidence and approval treatment rather than an unlabelled amount added at settlement.

  5. 5. Reconcile the shift

    Compare trip records with coupons, collected fares and approved expenses. Keep an unexplained difference visible with an owner instead of changing the fare retrospectively to make the cash total fit.

  6. 6. Bill accounts and resolve exceptions

    Prepare corporate or hotel statements from the agreed trip records. Follow disputed charges, cancellation adjustments and missing trip evidence before marking the account period complete.

Industry reports to connect with

  • Bookings and completed trips by pickup period, destination and vehicle class
  • Unassigned, reassigned, cancelled and missed-pickup bookings
  • Driver and vehicle availability against committed trips
  • Shift settlement differences and unapproved extra charges

Questions before implementation.

When should airport taxi services consider receipts management?

Use when payments need matching to bills or customer advances. A payment arrives.

What should we bring to the requirements discussion?

Bring anonymised examples of Customer references; Payment details; Allocation rules. 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 money received and allocate it to customer balances. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

A receipt entry does not establish bank clearance.

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. Receipt numbers are unique. Use this check when reviewing the first working version.

Talk to us

Discuss receipts 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