Taxi and mobility bookkeeping: Trips, platforms, and payouts

What a mobility month usually contains

The system becomes difficult when these sources overlap. A platform statement may deduct cash collected by drivers. A driver settlement may contain amounts already represented in the platform activity. A card batch can arrive after month end. A fuel receipt can be paid privately and never match the business bank.

Build the monthly source map before uploading files

For each source, record expected frequency, period convention, account or vehicle scope, responsible person, original format, and matching money channel. This makes a missing report visible before the close.

Minimum monthly map:

• every provider and direct-booking source;
• every cash register or driver cash handover;
• every card or payment processor;
• every bank and cash account;
• each vehicle and its material contracts/cost sources;
• customer invoices and receivables outside platform activity;
• driver, contractor, and payroll evidence routed to the responsible workflow;
• refunds, complaints, chargebacks, tips, promotions, tolls, deposits, and owner movements.

Synthetic two-vehicle month

The following business and figures are invented.

Westhafen Mobility GmbH operates two vehicles in July. It has direct corporate trips, cash/card street trips, one Uber account, one card terminal, a main bank, a reserve bank, and external payroll processing.

The activity total is not the sum of bank deposits. Direct invoices include an open amount; cash was partly deposited later; Uber's payout already reflects cash and charges; the card processor nets fees. Each channel therefore gets its own bridge before the main bank is reconciled.

The cost side contains:

• 14 fuel receipts across both vehicles, two paid privately;
• one lease contract and two monthly insurance documents;
• a €1,480 repair for Vehicle 2 with a deposit paid in June;
• toll and cleaning evidence;
• driver time and payroll evidence sent to the external payroll workflow.

The source-to-result map should link fuel and repair evidence to the relevant vehicle context where available, preserve the June deposit against the July repair rather than recording it twice, route private payments explicitly, and leave employment or tax conclusions to the qualified reviewer.

This example demonstrates evidence flow. It does not prescribe VAT rates, vehicle-cost treatment, employment status, cash controls, or account codes.

The monthly mobility workflow

1. Confirm who operated each channel

Verify legal entity, provider accounts, vehicle/operator relationships, driver or fleet contracts, and invoice issuer. Do not assume that a brand name on the app identifies the legal seller or supplier.

2. Freeze trip and sales populations

Export direct, platform, card, and invoice activity for the complete period. Check unique IDs, service dates, cancellations, cash/card indicators, and late adjustments. Preserve original reports and extraction dates.

3. Reconstruct every settlement

For each platform or processor, separate gross activity, cash collected outside the payout, fees, refunds, tips, incentives, tolls, reserves or balances, and net bank settlement. Unknown rows stay open.

4. Reconcile cash

Connect recorded cash trips, driver handovers, cash spending, and deposits. A cash amount deducted from a platform payout still needs the business's own cash evidence. Do not create a fee merely to explain the lower bank amount.

5. Prepare vehicle and operating costs

Collect original invoices, receipts, contracts, payment evidence, vehicle or business context, and any deposit/prepayment relationship. Software can organise and compare; the owner explains private or business facts; the accountant decides material treatment.

6. Reconcile all banks and transfers

Check each account population separately. Match both sides of own-account transfers. Connect platform/card batches by identity, amount, currency, and value date. Keep open receivables and delayed settlements visible.

7. Prepare the review and handover

Show per-channel completeness, each settlement bridge, cash status, vehicle evidence gaps, owner answers, prepared proposals, and the exception list. A ready month can contain known professional blockers; it cannot hide unknown source gaps.

What DeinHans prepares

DeinHans can receive mixed mobility sources, route supported documents, keep source-related questions visible, reconstruct supported payout templates, prepare bank matching and booking proposals, and assemble a month for review. A mobility-oriented setup can reduce repetitive sorting while preserving the original evidence and responsibility boundary.

Limits are material. DeinHans does not operate dispatch or fleet management, calculate payroll, determine driver employment status, initiate payments, or support every taxi, card, or platform format. Template and workflow coverage must be verified for the files in use; unsupported or changed reports remain exceptions.

Who supplies, prepares, and decides

Review-ready mobility month

The month is prepared when every trip and sales channel is complete, every platform and processor payout has a reproducible bridge, cash activity rolls into cash records, bank accounts reconcile, vehicle and operating costs have source and payment context, open invoices and delayed settlements remain visible, and professional questions name the evidence and decision owner. This turns a pile of provider PDFs, receipts, and bank lines into one explainable operating month.