Record collections when they happen
Keep the original order amount separate from collections, tips and extra charges. If a client pays a previous trip today, record today's payment time. A trip's scheduled date should not move that collection into another day.
Link costs without changing their dates
An information fee or parking expense can be linked to a booking while retaining its own payment time. Transaction-level records make it possible to see what you received or paid on a particular day.
Separate money still owed
An added charge is not automatically a payment. Track unpaid overtime or money advanced for a client, then reconcile it against the amount collected. Transfer information fees should be identifiable as transfer fees, not the full transferred fare.
Review details at your desk
The Web workspace provides transaction-level income and expense lists alongside reports. Check the amount, currency, transaction time and linked booking. Review currencies separately rather than treating different currencies as one total.
Illustrative example
The fare is not the whole story
A $300 order can end with a different actual income. Tips add to it, information fees reduce it, and unpaid extras still need collecting.
- Fare collected
- 300
- Tip collected
- +50
- Information fee paid
- −30
- Income before other costs
- 320
Example only: the fare and tip have been fully collected and the information fee has been paid. Other costs are excluded. An uncollected extra charge does not become collected income.
Keep the order link. Keep the payment time.
If yesterday's ride is paid today, the collection belongs in today's transaction list. A fee paid later keeps its own timestamp too, even though it is linked to the same booking.