Wrong number, wrong job, or a private trip logged by accident. All fixable — and worth fixing, because these totals go on your tax return.
4 August 2026 · 3 min read
Mileage logs feed straight into your HMRC figures, so an error left in place quietly becomes an error on your return. Correct it as soon as you spot it.
Say what was wrong in plain English — "that last trip was 24 miles not 42" — and GraftG amends it. Doing this immediately is much easier than untangling it at year end.
Ask for the list first: text MILES REPORT to see recent trips, then describe which one is wrong and what it should be. Referring to the date and destination makes it unambiguous.
If you logged a private journey, remove it rather than leaving it — claiming personal mileage is exactly the sort of thing that unravels badly if HMRC ever asks. Tell GraftG which trip to delete.
Two entries for one journey usually means the message was sent twice. Delete one; the totals correct themselves immediately.
Text MILES REPORT at month end and skim it. Thirty seconds of review catches the errors while you still remember the journeys — far easier than reconstructing them in January.
Yes. Tell GraftG what was wrong and what it should be — for a recent trip, a message like "that last one was 24 miles not 42" is enough. For older entries, pull up MILES REPORT first so you can identify the trip clearly.
Delete it. Business mileage claims must only cover business journeys, and a contemporaneous log with an obvious personal trip in it undermines the whole record if it is ever queried.
Keep reading