When a Parking Receipt Becomes a Liability: The Southwark Forgery Case

Why This Case Should Make Every Driver Think Twice

Most of us have been there. You return to your car convinced you've paid for enough time, only to find a Penalty Charge Notice tucked under the wiper. The instinct is straightforward: dig out your receipt, prove you paid, and fight the ticket. It seems like an open-and-shut case. Receipt in hand, surely the council doesn't stand a chance?

Not so fast. A recent tribunal case from the London Borough of Southwark turns that assumption completely on its head — and it carries a warning that every driver who uses a parking app should read carefully. This isn't just a story about one driver losing an appeal. It's a story about digital evidence, the reliability of payment records, and what happens when the council's data tells a very different story to the one you're presenting.

What Happened

A driver parked in Southwark and was issued a Penalty Charge Notice for the contravention of "parked after the expiry of paid for time" — one of the most common parking offences in London, typically recorded under PCN code 82.

The driver appealed, and her case rested on a single piece of evidence: a PayByPhone receipt showing that she had paid to park between 14:30 and 16:30. On the face of it, that should have been enough. She had a timestamped receipt from a recognised payment platform. What more could you need?

The answer, as it turned out, was quite a lot.

The Arguments

The Driver's Case

The appellant's argument was simple and, in most circumstances, entirely reasonable. She produced a receipt from PayByPhone showing she had paid for a two-hour parking session running from 14:30 to 16:30. If the PCN was issued within that window, she argued, it should be cancelled.

The Council's Case

Southwark came back with something far more serious. The council didn't simply dispute that payment had been made — it alleged that the receipt the driver had produced had been digitally altered. In other words, it claimed the document was a forgery.

To support this, the council pointed to its own records of the driver's PayByPhone account. Those records — held by the payment platform itself — showed something different to what appeared on the receipt the driver had submitted. The council's position was that the receipt had been tampered with to show a different payment time or duration than what had actually been purchased.

This is an extraordinary allegation. But the council had the account data to back it up.

The Decision

The adjudicator refused the appeal.

The adjudicator found the council's evidence persuasive. Crucially, the driver had been given every opportunity to respond to the forgery allegation and had not done so. Silence, in a legal context, is rarely neutral — and here it weighed heavily against her.

But the adjudicator went further. They noted that it would be "very unlikely" for a PayByPhone account to record one set of details whilst simultaneously issuing a receipt showing something different. The two simply don't work that way. The platform's backend records and the receipts it generates are part of the same system — they should always match.

The adjudicator preferred the council's account record over the receipt, was satisfied that payment had not been properly made, and refused the appeal.

Perhaps most strikingly, the adjudicator added a pointed observation at the end of the decision: if the council stood by its allegation and could support it with expert evidence, it should consider reporting the matter to the police and potentially applying for a costs order against the appellant. That is an exceptionally serious step in a parking tribunal context, where costs awards are rare and reserved for cases involving unreasonable conduct.

The Legal Reasoning, Explained in Plain English

1. Digital account records carry significant weight

When you pay through PayByPhone, two things happen simultaneously: your payment is processed and logged in the platform's account database, and a receipt is generated. These are not separate, independent records — they come from the same transaction. If the receipt shows different information to the account record, one of them must be wrong. And it is far, far more likely that a receipt has been altered than that a payment platform has issued a receipt that contradicts its own database.

The adjudicator applied straightforward common sense here. The council's account records are contemporaneous, automated, and held by a third-party platform with no obvious reason to misrepresent the transaction. A receipt, by contrast, is a document that exists as a file — and files can be edited.

2. The burden of proof in parking appeals

In UK parking tribunal proceedings, the burden of proof shifts between parties depending on the stage of the appeal. Once the council produces credible evidence of a contravention — and here it produced account data directly contradicting the receipt — the driver must answer that evidence. Simply presenting a receipt and saying nothing more is not enough when the council has specifically alleged that the receipt has been tampered with.

The driver's failure to respond to the forgery allegation was, in the adjudicator's view, a significant gap. It left the council's case unanswered.

3. Costs and police referrals — a rare but real consequence

Costs orders in parking tribunal cases are genuinely unusual. They are reserved for situations where a party has behaved unreasonably or — as implied here — where there is evidence of deliberate misconduct. The adjudicator's suggestion that the council consider a police referral signals that this was not treated as a simple dispute about payment. It was treated as a potential case of fraud.

Lessons for Drivers

1. Your PayByPhone receipt and your account record must match — always

If you ever need to use a receipt as evidence in a parking appeal, check that it matches what your app history shows. Log into your PayByPhone account, find the transaction, and verify that the time, date, location, and duration all correspond exactly. Any discrepancy — even a minor one — could undermine your case.

2. Never alter or edit any document you submit as evidence

This sounds obvious, but it bears stating clearly. Submitting a digitally altered document to a tribunal is not just a way to lose your appeal — it is potentially a criminal act. Fraud by false representation under the Fraud Act 2006 carries a maximum sentence of ten years' imprisonment. The stakes are incomparably higher than any parking fine.

3. Screenshot your payment confirmation immediately

The moment you complete a PayByPhone transaction, take a screenshot. Do it before you walk away from the car. Screenshots are timestamped by your device and capture the screen as it appeared in real time. They are harder to dispute than a receipt that exists as a separate file.

4. Respond to every allegation the council makes

If the council raises a specific argument — particularly one as serious as document tampering — you must address it directly. Silence does not help you. If you genuinely cannot explain a discrepancy, say so and provide whatever context you can. Ignoring an allegation entirely leaves the adjudicator with no choice but to accept the council's version of events.

5. Contact PayByPhone directly if there is a genuine error

Payment platform errors, whilst rare, do occur. If you believe your receipt is correct and the council's records are wrong, contact PayByPhone's customer support and request written confirmation of your transaction details. A letter or email from the platform itself, confirming the payment, would carry far more weight than a receipt alone.

The Key Takeaway

A parking receipt is only as trustworthy as the account record it came from. Councils now have direct access to payment platform data, and that data will almost always outweigh a document you produce yourself. In the digital age, the parking tribunal is not just weighing your word against the council's — it is weighing your document against a database. Make sure they tell the same story.