Skip to main content
GullySystem
Automotive

Purchase Order Management for Airport taxi services

Control purchases for an airport taxi operation, with distinct acceptance evidence for fleet equipment, supplies and outsourced trips.

Inventory Management

Does this function belong in your operation?

Use for supplier commitments. Expenses without orders belong in expense recording. Owned-fleet purchasing applies only where the operator acquires vehicles.

The operator requests a vehicle, spare part, equipment item or an outsourced trip service that needs a formal supplier commitment.

Not every operator owns cars. Vehicle purchases need asset and acceptance records; subcontracted trips need service confirmation and trip-level billing evidence. Establish the operating model before configuring purchasing.

Bring the records the workflow depends on.

  • Purchase request with fleet, store or outsourced-service purpose
  • Item specification or agreed transport-service description
  • Supplier quote, price, delivery or service terms
  • Authorised approver and the evidence required for acceptance

Outputs to check

  • Open purchases by vehicle, supply or outsourced-service purpose
  • Physical deliveries or trip-service evidence awaiting acceptance
  • Supplier invoices with disputed extras or missing supporting references

Follow the purchase order 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. Purchase request

    Identify whether the requirement concerns an owned vehicle, a part, operating equipment or outsourced trips. An operator using subcontractors must not be forced into a vehicle-purchase workflow.

  2. 2. Manager approval

    The authorised operations and purchase reviewers check need, cost and terms. Capital purchases and subcontracted transport can have different decision owners and acceptance evidence.

  3. 3. Purchase order

    Issue the agreed supplier commitment with the item or service description and relevant reference. For outsourced transport, specify the agreed service scope rather than treating a trip as warehouse stock.

  4. 4. Supplier confirmation

    Record availability and accepted terms. A changed vehicle specification, part or subcontracted service arrangement returns for approval before the commitment is amended.

  5. 5. Goods receipt

    Use goods receipt for physical deliveries and record inspection or acceptance. For outsourced trips, use an authorised service-completion record instead; do not create fictitious stock movements.

  6. 6. Invoice matching

    Accounts match the supplier bill to the order and accepted delivery or service evidence. Compare trip references and agreed extras for subcontracted work, or item and quantity for physical goods.

  7. 7. Payment and closure

    Finance authorises payment separately and retains any disputed charge or supplier credit. Vehicle registration in the asset system and trip settlement are distinct hand-offs from purchase-order closure.

Who uses the module, and who approves?

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

Fleet or operations requester

States the equipment, supply or outsourced-service requirement and acceptance criteria.

Purchase authority

Approves the commitment, supplier terms and subsequent amendments.

Receiving or service reviewer and accounts

The assigned reviewer confirms supply or service; accounts resolve the bill and control payment.

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.

Partial deliveries

Retain the undelivered parts or equipment balance. For a service order, record the accepted completed trips separately from the remaining commitment.

Cancelled purchase orders

Record the cancelled remainder and review deposits or completed services. Cancelling an order must not erase a subcontractor's already accepted trip evidence.

Supplier price changes

Return changed vehicle, part or service rates to the authorised reviewer before accepting the revised commitment.

Invoice mismatches

Hold unapproved waiting charges, duplicate trip references, wrong quantities or price differences with an identified reviewer.

Approval limits

Apply the operator's purchase-value and purpose rules; a dispatcher does not gain authority for a vehicle purchase simply by arranging trips.

Can this work independently?

Ordering can run independently. Physical stock needs goods receipt; vehicle purchases need asset records; outsourced trips need service evidence. Finance owns invoice posting and payment.

Systems and records it connects with

  • Stores and goods receipt for physical items
  • Fleet assets or accepted trip-service records according to the purchase type
  • Accounts for invoices, advances, credits and supplier payments

Configure, test and introduce the workflow.

  • Separate physical purchasing, vehicle acquisition and outsourced-service commitments in the initial scope.
  • Pilot one relevant purchase type, then test a cancellation, changed price and disputed invoice.
  • Train operations and accounts on the evidence required for each type before adding further suppliers or branches.

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.

  • Physical goods use delivery evidence while outsourced trips use accepted service records.
  • A supplier bill retains the relevant item, vehicle or trip references without mixing their quantity meanings.
  • Unapproved substitutions and extra charges remain visible before an order is closed.
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 purchase order management?

Use for supplier commitments. Expenses without orders belong in expense recording. Owned-fleet purchasing applies only where the operator acquires vehicles. The operator requests a vehicle, spare part, equipment item or an outsourced trip service that needs a formal supplier commitment.

What should we bring to the requirements discussion?

Bring anonymised examples of Purchase request with fleet, store or outsourced-service purpose; Item specification or agreed transport-service description; Supplier quote, price, delivery or service terms; Authorised approver and the evidence required for acceptance. 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. Control purchases for an airport taxi operation, with distinct acceptance evidence for fleet equipment, supplies and outsourced trips. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

The order does not approve road use, driver eligibility or dispatch. Fleet readiness, transport permissions, service acceptance and payments stay with their responsible owners.

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. Physical goods use delivery evidence while outsourced trips use accepted service records. Use this check when reviewing the first working version.

Talk to us

Discuss purchase order 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