Best Practice: Expenses, Mileage & Travel Recharge
"Do we charge for that?" sounds like one question, but it's actually two, and conflating them is where most expense and mileage policies get confused. The first question is what you owe the engineer for using their own vehicle, time, or money on the business's behalf — a fairness and often legal obligation, independent of any client. The second is what you charge the client — a commercial decision about what's included in your pricing and what isn't, independent of what the engineer is owed.
An engineer driving to a client site should be reimbursed for that mileage regardless of whether you decide to recharge the client for it. Whether you recharge the client is a completely separate call, and the two don't have to move together — you might reimburse every mile an engineer drives while only recharging the client for travel beyond a certain allowance, or recharge travel time but never mileage itself. This guide covers how to think about both decisions, and how MSP Pulse keeps them genuinely separate rather than quietly tangled together.
1. Reimbursing the engineer is a fairness question, not a billing decision
If an engineer uses their own vehicle for work travel, reimbursing them for that cost isn't a perk — it's compensation for the genuine use of their personal property on the business's behalf, and in many jurisdictions there's a legal or tax dimension to getting the rate right. Treat this decision as settled policy, not something negotiated per trip or per engineer.
Set one mileage rate and apply it consistently, rather than leaving it to informal arrangement. A published, consistent rate removes any sense that reimbursement is a favour being granted rather than an obligation being met. MSP Pulse has one tenant-wide default rate, and also lets you give an individual engineer their own rate (for example for an electric vehicle or a different engine size). Use that override because a real cost differs, not as a way to negotiate.
Measure from a fixed, defensible reference point — typically the office, not the engineer's home. Starting from home varies wildly between engineers for reasons that have nothing to do with the work (where someone happens to live), and a policy that implicitly rewards or penalises engineers for their commute invites exactly the kind of fairness dispute reimbursement policy exists to avoid.
Decide whether reimbursement depends on what you bill the client, and be clear that it shouldn't. An engineer's fuel and vehicle wear don't change based on whether that particular trip happens to be billable to the client — the obligation to reimburse is about what the engineer spent, not about what you recover.
2. Whether to recharge the client is a separate commercial decision
Once the engineer's owed their reimbursement, the second question — whether any of that cost gets passed to the client — is purely about your pricing model, and there's no single right answer. A few common approaches, each defensible depending on your business:
A free allowance, chargeable beyond it. Treat a short trip as a cost of doing business, baked into your rates, and charge for travel beyond it. This is easy for clients to understand and easy for you to apply consistently.
Bill actual travel time rather than mileage. Many experienced MSP operators prefer this over a flat per-mile charge, because an engineer's real cost is their time, not the distance itself — and traffic affects time far more than it affects distance. Ten miles in light traffic and ten miles in rush hour cost you very differently in engineer time, even though the mileage reimbursement is identical either way.
A flat trip charge. Simple to administer and easy for a client to budget against, at the cost of being inaccurate in both directions — you'll undercharge some trips and overcharge others. Reasonable for a business that values simplicity over precision.
Whichever model you choose, set it out in the agreement before the first chargeable trip happens, not after a client questions an invoice. A travel charge that surprises a client reads as a hidden fee, even when it's entirely reasonable — the problem is usually that it wasn't communicated, not that it exists.
Itemise it separately on the invoice rather than folding it into the labour line. A client who can see exactly what they're paying for travel is far less likely to dispute it than one looking at a single inflated-looking labour charge with no explanation.
3. How MSP Pulse keeps reimbursement and recharge separate
This isn't just policy advice — it's built into how the data is stored. Mileage and general expenses each carry their own two independent settings: what the engineer is owed, and what (if anything) the client is charged. Travel time is billed through its own mechanism. Setting one never implies or requires another.
| Reimbursement (the engineer) | Recharge (the client invoice) | How it works | |
|---|---|---|---|
| Mileage | Reimbursed through payroll, for engineers you've switched mileage on for | Never — mileage is not a client-billable line | Distance is measured office → site (a one-way distance you enter on each client site), multiplied by the number of travel legs on the visit |
| Travel time | Not a reimbursement: it is the engineer's time | Governed by a scheme: charge or no charge, resolved site → agreement → tenant, with a free allowance per leg | The scheme decides whether a leg is charged; the engineer's labour role decides how much, as a multiple of the normal onsite rate or a flat hourly rate |
| Parking, tolls, other expenses | Reimbursed when the engineer paid out of pocket; nothing owed if paid on a company card | Recharged when policy says so, resolved agreement → tenant, and frozen when recorded | Logged as an expense on the ticket, with the two settings chosen independently |
A few details are worth knowing before you rely on this.
Mileage is switched on per engineer, and it needs a travel leg. An engineer can claim mileage only if mileage is enabled on their Employment tab, and the claim is attached to the travel legs of an onsite visit. If the visit has no travel leg, the site has no distance entered, or no rate applies, MSP Pulse refuses the claim with a clear message instead of silently skipping it. The claim then goes through an approve, then paid, workflow on the Reimbursements page, which only owners and admins can action. There is no receipt step for mileage.
Because mileage is never a client line, you recover travel from the client through the travel-time mechanism. That matches the general preference in Section 2 for billing time rather than distance.
Travel time needs two things set up to bill. The scheme must be set to charge, and the engineer's labour role must have a travel rate. If a scheme says charge but the role has no travel rate, the leg is logged as non-billable rather than blocking the engineer, so check this when you set it up. Billable travel appears on the invoice as its own "Travel" line for the site.
Payroll is based on scheduled hours, not logged time. MSP Pulse hands your payroll runner each person's scheduled hours, leave, overtime and approved reimbursements. Mileage and out-of-pocket expenses appear as reimbursements to pay. MSP Pulse does not store pay rates, so what you pay your engineers for travel time is a matter for your payroll.
Expense, mileage and payroll data are kept out of the AI Assistant's reach. This is a deliberate boundary, the same one that applies to the password vault.
4. Parking, tolls, and other incidental expenses
Unlike mileage, there's no inherent reason parking, tolls, or a similar out-of-pocket cost can't be passed to the client — and in general practice, many MSPs do recharge these, since they're actual receipted costs tied directly to a specific site visit. The simplest approach is to recharge the actual amount, with a receipt, rather than building a rate table for something that's already a clean, specific figure.
In MSP Pulse, these are logged as expenses on a ticket, with a category, an amount and how it was paid, and a receipt can be attached. The reimbursement and recharge settings are independent. Approval of a reimbursement normally requires a receipt.
The recharge policy resolves agreement → tenant, the same narrowest-first pattern used elsewhere in MSP Pulse's billing, so a specific client's agreement can override your general policy without changing the default for everyone else. There are three choices: no charge, at cost, or cost plus a markup percentage. On a single expense an engineer can choose to recharge or not, which is useful for the occasional exception.
The recharge is frozen when the expense is recorded, consistent with the platform's broader rates-frozen-at-logging principle: a later change to your policy doesn't alter an expense that was already logged. Once an expense has been invoiced, or its reimbursement approved or paid, it is locked against editing.
A recharged expense reaches the client on the normal invoice. It is picked up by Load pending and appears as a separate line named "Expense — Category (ticket number)", using your normal invoice tax. Two limits: expenses on project service tickets are not billed through the project invoice run, and VAT you could reclaim on the receipt isn't tracked.
Treat your first real recharged expense as worth a close look. Walk it through end to end — logged, approved, picked up in Load pending, shown on the invoice — before you rely on it for every job.
5. Set the travel scheme deliberately, once — don't re-decide it per ticket
The charge/no-charge decision for travel time resolves through a scheme (site → agreement → tenant), and the whole point of that chain is that an engineer logging time never has to personally judge whether a trip is billable — the system already knows, because someone decided it deliberately in advance. New tenants start on no charge, so travel is only billed once you choose to turn it on.
Set it where the decision really sits. The tenant default and the engineer rates are under Settings → Labour Roles; an agreement can override it on its Travel & Expenses tab; and an individual client site can override both. A per-site setting is how you handle the one distant location without changing how you treat a client's other sites.
This is the same principle as the Agreements guide: if a client could reasonably ask "is this covered?", the answer should already exist in configuration, not be worked out fresh by whoever happens to be handling the ticket. Travel is one of the easiest things to get inconsistent if it's left to individual judgement — one engineer charges for a short trip, another doesn't, and the client notices the inconsistency long before anyone internally does.
Set the free allowance per leg thoughtfully, not as an afterthought. It applies to each leg separately: the first so many minutes of every leg are free and only the excess is billed. A sensible allowance (the first 15 minutes of any trip, say) absorbs the genuinely trivial trips without friction, while still letting a longer or more frequent travel pattern become billable once it's no longer trivial.
Review the scheme per client as part of the same renewal cadence as everything else — a client's site portfolio changes, a new location gets added, and a travel policy that made sense for one site may not fit a second one twenty minutes further away.
6. Keep the rates current, on both sides
Two different figures drift independently here, and both need their own periodic check.
The mileage reimbursement rate is often tied to fuel prices, vehicle running costs, or a published statutory rate depending on your jurisdiction — it's not a number you set once and forget. If it's been a year or more since anyone looked at it, it's worth confirming it still reflects what it actually costs an engineer to drive. Remember that any engineer with their own rate needs reviewing too. And because the distance is entered by hand on each client site, check it whenever a client moves or adds a location.
The travel rate on each labour role is a commercial pricing decision like any other rate — it should move when your other labour rates move, not sit untouched while everything around it is reviewed and adjusted.
Pair both reviews with the same cadence already established across the other guides — agreement renewal, catalogue review, account-code review. A mileage or travel rate that's quietly stale for two years is the same category of problem as a price that no longer reflects your costs: invisible until someone goes looking, and only ever found by accident otherwise.
Pre-flight checklist for expenses, mileage and travel
- [ ] Mileage reimbursement rate set once and applied consistently; personal rates used only for a real cost difference
- [ ] Mileage switched on for the engineers who should claim it
- [ ] Mileage measured office → site, with the one-way distance entered on every client site that gets visits
- [ ] Clear that client recharge decisions never affect whether an engineer is reimbursed
- [ ] A deliberate choice made between a free allowance, billed travel time, or a flat trip charge — not defaulted into
- [ ] Travel policy set out in the agreement before the first chargeable trip, not discovered by the client on an invoice
- [ ] Travel scheme set to charge where intended (it starts on no charge), with a travel rate on each labour role that should bill it
- [ ] Free allowance per leg configured per site, agreement or tenant, so engineers never have to judge billability themselves
- [ ] Parking, tolls and other incidental expenses have a clear recharge policy (none, at cost, or cost plus markup), with the agreement able to override the tenant default
- [ ] First real recharged expense followed through to the invoice rather than assumed correct
- [ ] Mileage rate and travel rates reviewed on the same cadence as other agreement and catalogue reviews