Solutions · Finance & CFO

Mobility is the last category you find out about afterwards.

Someone else commits the spend, the vendor prices it, and it reaches you as a payable weeks later with attribution assembled from booking references. This page is about moving all three of those upstream — to the point of request, where a control can still be applied.

Why the number is always late

Four structural reasons, none of them a discipline problem.

Every one of these is a consequence of where in the process the data is captured.

  • Spend arrives as an invoice

    Travel and ground transport are among the few categories where the commitment is made by someone else and the number reaches finance weeks later. By the time it is visible it is a payable, not a decision.

  • The rate card is a document

    You negotiated rates per city, vehicle class and distance slab. Nothing enforces them at the point a trip is allocated, so the invoice is priced by the operator and checked — if at all — by sampling.

  • Attribution is reconstructed

    Cost centre, entity and project are assigned after the fact from whatever the booking reference suggests. Allocation disputes consume the close, and the numbers that come out of it are defensible rather than right.

  • Credit and compliance leak quietly

    A ticket invoiced to an employee personally, a vendor invoice without a compliant reference, a hotel bill against the wrong registration. Each one is small and none of them are recoverable once the period closes.

What changes

Six controls, applied upstream.

The common thread: each one captures or enforces something at the point of commitment rather than reporting on it after payment.

Cost centre captured at the request

Entity, cost centre, project and approver are attributes of the trip from the moment it is raised, derived from the HRIS where they already exist. Nothing is allocated retrospectively and nothing is apportioned by guess.

The rate card becomes a control

Contracted rates by city, vehicle class and slab are held in the platform and applied when a trip is priced. An operator cannot bill off-card without producing an exception that names the difference.

Three-way match, automated

Trip as authorised, trip as actually run from the GPS trail, and trip as invoiced. Discrepancies are raised per line against the vendor before payment rather than found afterwards in a sample.

Tax details captured at booking

The company registration, entity and billing detail are attached when the booking is made, not reconstructed from a receipt an employee forwards in the following month. Eligibility is your advisers’ call; having the evidence in the right name is ours.

Leakage reporting by line

Off-card pricing, duplicate trips, wrong vehicle class, tolls billed twice, trips billed against cancelled shifts. Reported by vendor and site so the conversation has a number attached to it.

An export your ERP accepts

Journal-ready output with the dimensions your chart of accounts actually uses, reconciled before it leaves the platform. The point is that nothing in the close needs re-keying.

The cycle

Commitment to close, with nothing re-keyed.

The audit evidence for any journal line is the trip record behind it, which already exists.

  1. Commitment

    Spend is visible when it is committed.

    A trip carries its price basis, cost centre and approver at the point of request. Accruals come from authorised trips rather than from last month divided by twelve.

  2. Delivery

    What ran is recorded independently.

    The GPS trail, actual times and actual route are captured by the platform, not reported by the party being paid for them.

  3. Invoice

    Pricing is computed, then compared.

    The platform prices the trip from the contracted card and sets that against the vendor invoice. Variances are itemised and disputed before payment.

  4. Close

    The journal is already allocated.

    Dimensions were captured upstream, so the export does not need an allocation exercise. Audit evidence for any line is the trip record behind it.

What you can report on

Six numbers, produced rather than estimated.

We have not printed target values against these. A vendor page quoting your future off-rate-card percentage is quoting a number it has no way of knowing.

Spend per employee per month

Split ground and travel, by site and entity. Comparable across locations because the dimensions were captured the same way everywhere.

Off-rate-card share

The proportion of trips priced away from contract, by vendor. The first number to look at, and usually the largest single recoverable line.

Invoice match rate

Lines matching authorised and delivered without intervention, and the ageing of those that do not.

Cost per trip and per seat

Per vehicle class and city. Seat cost is the one that moves with pooling, which is why it is the one to hold vendors and routing against.

Policy exceptions, costed

What overriding policy actually cost in the period, by rule and approver. The input to deciding whether a rule is worth keeping.

Tax-compliant capture rate

The share of travel and transport spend where the invoice carries your registration and entity correctly at source. The precondition for any credit claim, whatever your advisers determine is eligible.

Free tool

Work out what input credit you are not capturing.

Credit on business travel depends on the invoice carrying your registration and entity correctly at the point of booking — and on most programmes a material share of bookings do not. This estimator takes your own spend and your own current capture rate and shows the arithmetic. It makes no claim about what is eligible for your business; that is a question for your advisers.

What this is not

Four things we are not going to claim.

Worth being explicit about, because two of them are claims this category makes freely.

  • It is not an ERP

    taSki produces allocated, reconciled journal output and hands it over. It does not keep your ledger, run your payment cycle or replace a system of record — and a mobility platform claiming to would be a bad sign.

  • It is not tax advice

    The platform captures registration and billing detail at source and reports on how completely it did so. Whether a given category of travel or transport spend yields recoverable credit for your business is a question for your own tax advisers, and the answer is conditional and subject to change.

  • It cannot fix a bad contract

    If the rate you negotiated is above market, enforcing it faithfully will not help. What the platform does give you is the per-city, per-class, per-slab evidence to renegotiate with — which is usually the harder half.

  • It cannot recover closed periods

    Leakage is caught by matching trips as they run. Spend already invoiced, paid and closed before the platform was in place is a historic audit exercise, not something this recovers.

Questions

From finance and procurement

Still unanswered? Our solutions team replies within one business day.

Talk to the team →

What is the actual mechanism for savings? Not the number, the mechanism.

Four, in roughly descending order of size. Enforcing the rate card you already negotiated, because the gap between the agreed card and the submitted invoice is the largest recoverable line in ground transport. Improving seat utilisation, because a four-seat cab carrying one employee costs the same as one carrying four and that is decided at allocation. Recovering invoice leakage through a three-way match. And enforcing fare policy at the point of booking rather than flagging breaches in a report. None of them require changing vendors.

How does the three-way match actually work?

Three records are compared per trip. The authorisation — who requested it, which cost centre, which approved vehicle class, which price basis. The delivery — the GPS trail, actual pickup and drop times, actual distance. And the invoice line the vendor submitted. The platform prices the trip independently from your contracted card and sets that against the invoice. Differences are itemised with the rule they breach, which is what makes them disputable rather than arguable.

We book travel through a TMC. Does this replace them?

It can, and it does not have to. taSki runs the booking and policy layer for flights, hotels and ground on one engine, which is the configuration where attribution and tax capture are cleanest because they are captured once. Where you keep an existing TMC for air, the ground programme still runs on taSki and the two reconcile — you give up the single capture point, which is the thing that matters most for allocation and tax detail.

What dimensions can you export, and in what format?

Entity, cost centre, project, site, employee, vendor, trip type, vehicle class and tax detail, as a journal-ready file or via API. The practical question is not what we can emit but what your chart of accounts expects and where the mapping is maintained — that is a half-hour conversation with whoever owns your close, and it is worth having before procurement rather than during implementation.

How do you price, and does it scale with spend?

Usage-based, per active employee or per trip depending on programme shape, with no implementation project to capitalise. It is on our pricing page. Deliberately not a percentage of spend: a vendor whose revenue rises with your travel bill is not aligned with reducing it.

What does due diligence look like?

taSki holds ISO/IEC 27001:2022 certification and has been through enterprise third-party risk review by listed customers. The security page covers controls, data residency and the certification detail, and we will complete your own TPRM questionnaire rather than offering a summary in place of one.

Model it on your own ledger

Bring one month of vendor invoices and your rate card.

We will price the same trips from your contracted card and show you the variance, line by line. If there is nothing in it for you, that is a short meeting and you will have the analysis either way.

  • Your invoices re-priced from your own rate card
  • Variance itemised by vendor and line
  • What a journal-ready export would look like

Request a demo

Three details, and we'll call you to arrange a time.

We'll only use these details to contact you about taSki. No newsletter, no list sharing. See our privacy policy.