Here is my POPLA appeal, I am planning to send it in tomorrow (day 32 of 33) so I welcome any feedback on it before then.
POPLA Verification Code: [Verification Code]
GROUPNEXUS PCN Number: [PCN Number]
Vehicle Registration: [Vehicle Registration]
Re: Appeal against GroupNexus Notice to Keeper
I am the registered keeper of the vehicle in question and I am appealing against the issue of this Parking Charge Notice on the following grounds:
1. The Notice to Keeper fails to identify the creditor as required by Paragraph 9(2)(h) of PoFA.
2. The NtK fails to clarify whether GroupNexus is acting as an agent or principal
3. The operator has not identified the driver and cannot rely on PoFA to transfer liability to the keeper.
4. The operator is put to strict proof that it holds a valid contract flowing from the landowner in accordance with PPSCoP Section 14.
5. The Notice to Keeper fails to inform the keeper of the reason behind the charge as per Paragraph 9(2)(a) and (b) of PoFA 2012
6. The Notice to Keeper does not comply with Paragraph 9(2)(e)(i) of Schedule 4 to the Protection of Freedoms Act 2012 – no invitation to the keeper to pay.
7. The driver made a reasonable attempt to pay
1. The Notice to Keeper fails to identify the creditor, as required by Paragraph 9(2)(h) of Schedule 4 to the Protection of Freedoms Act 2012
Paragraph 9(2)(h) of Schedule 4 to the Protection of Freedoms Act 2012 states:
“The notice must—identify the creditor and specify how and to whom payment or notification to the creditor may be made.”
This is a mandatory statutory requirement, and one which this NtK blatantly fails to meet. Nowhere in the Notice does it state who the creditor actually is. There is no sentence—nor even a vague attempt—to say: “The creditor is GroupNexus,” or any other entity to this effect, as required by law.
Instead, the Notice merely refers to “we” throughout, without defining who “we” actually is in a legal context. If the operator intends to rely on this ambiguous term to signify the creditor, then at the very least the Notice must state “we, the creditor” or “we, GroupNexus as the creditor.” It does not. The word “creditor” is not in fact even mentioned in the document.
The failure to explicitly identify the creditor means the NtK is not compliant with Paragraph 9(2)(h), and therefore the operator cannot hold the keeper liable. As keeper, I cannot be expected to respond to a notice that fails to state, even once, who is legally entitled to the charge.
Accordingly, I respectfully request that POPLA allow this appeal and instruct the operator to cancel the charge.
2. The NtK fails to clarify whether Groupnexus is acting as an agent or principal
Further compounding the breach of Paragraph 9(2)(h) of PoFA, the Notice to Keeper also fails to state whether GroupNexus is acting:
• as the principal, issuing the parking charge in its own name and right (in which case it must be clearly named as the creditor), or
• as an agent of the landowner, in which case the actual creditor is the landowner and must be identified.
There is no information in the NtK to clarify the capacity in which GroupNexus is acting. This creates a situation where the keeper is being pursued for a payment allegedly owed to an unknown party. This undermines the basic requirements of legal certainty and transparency.
POPLA and courts have consistently held that the operator must identify the creditor and clarify their legal standing in relation to the land. Without such clarification, the Notice is materially non-compliant, and keeper liability cannot be established.
Given these failures, GroupNexus has not complied with the requirements of PoFA, meaning they cannot transfer liability to the keeper. Without strict compliance with PoFA, GroupNexus cannot hold the keeper liable, and this charge is therefore unenforceable.
3. The operator has not identified the driver and cannot rely on PoFA to transfer liability to the keeper.
As GroupNexus cannot rely on PoFA 2012 Schedule 4 to transfer liability to the keeper, they must provide evidence that the keeper was the driver at the time of the alleged parking contravention.
GroupNexus have not provided any evidence to suggest that the registered keeper was the driver.
GroupNexus has made no attempt to prove the identity of the driver, and they have not demonstrated why they believe the registered keeper should be held liable without PoFA compliance.
As there is no evidence that I, as the registered keeper, was the driver, GroupNexus has no legal grounds to pursue this charge against me.
4. The operator is put to strict proof of landowner authority to issue PCNs in their own name
It is a well-established requirement under the Private Parking Single Code of Practice (PPSCoP) and longstanding POPLA precedent that a private parking operator must have clear, current, and contractual authority flowing from the landowner to manage parking and issue PCNs in their own name.
GroupNexus is therefore put to strict proof. The operator must produce, but not limited to:
• A contemporaneous, unredacted contract or agreement with the landowner (or the landowner’s agent, with written proof of such agency),
• Confirmation that the contract permits the operator to issue PCNs in their own name and to pursue unpaid charges,
• Proof that the contract is still valid and in force as of the date of the alleged contravention,
• Identification of the exact land covered (including “New Street Retail Park”),
• Disclosure of all material terms, including the scope, duration, enforcement conditions, and authority limits,
• Confirmation of any variations agreed since the contract was first executed.
Importantly, any redactions of critical parts of the contract—such as the validity term, the agreed parking conditions, the times of enforcement, or the names, signatures, and dates of the signatories—renders the evidence incomplete and unreliable. These elements are essential to proving that a valid, enforceable contract existed at the material time.
Excessive or unnecessary redactions serve only to raise suspicion that the operator has something to hide. It is not sufficient for an operator to say “there is a contract” or to supply a heavily redacted version that fails to meet the standards set out in Section 14 of the PPSCoP. That section sets clear expectations about what a compliant contract must contain.
A simple assumption that “there must be a contract because signs are in place” is not acceptable. That position shows a total disregard for the PPSCoP and POPLA’s evidential standards. Signage presence is not proof of legal authority. If the operator cannot prove that all required contractual points under Section 14 have been satisfied, then any suggestion that they have a valid contract must be treated as null and void.
Unless GroupNexus produces full, unredacted contractual proof meeting all the criteria of the PPSCoP, they cannot demonstrate any legal standing to issue or pursue this charge. The appeal must therefore be upheld.
5. The Notice to Keeper fails to inform the keeper of the reason behind the charge as per Paragraphs 9(2)(a) & (c) of PoFA 2012 Schedule 4
GroupNexus’ NtK also fails PoFA on the following points:
Paragraph 9(2)(a): The NtK must specify the relevant land on which the vehicle was parked. GroupNexus’ vague description of the location is insufficient under PoFA, as it does not clearly identify where the vehicle was allegedly parked, nor does it specify a defined area.
Paragraph 9(2)(c): PoFA requires that the NtK must inform the keeper of the reason for issuing the charge. In this case, GroupNexus fails to make the alleged breach of contract clear in their NtK. There is merely a vague reference to the “free parking period”. The NtK must inform the keeper why the parking terms were allegedly breached. Thus, this is not sufficiently communicated.
6. Notice to Keeper does not comply with Paragraph 9(2)(e)(i) of Schedule 4 to the Protection of Freedoms Act 2012 – no invitation to the keeper to pay.
It is important to emphasise that PoFA Schedule 4 Paragraph 9(2)(e)(i) sets out a mandatory and unambiguous requirement. It states that the Notice to Keeper must:
“state that the creditor does not know both the name of the driver and a current address for service for the driver and invite the keeper — (A) to pay the unpaid parking charges; or (B) if the keeper was not the driver of the vehicle, to provide the creditor with a statement...”
The key phrase here is “invite the keeper...to pay the unpaid parking charges.”
This requirement is not optional, and there is no allowance in law for this obligation to be met by implication or assumption. The law does not say that a notice may merely “imply” that the keeper is being invited to pay, nor does it say that the fact the NtK is addressed to the keeper is somehow enough. The statute uses the word MUST—meaning that an explicit, unambiguous invitation must be present within the wording of the notice itself.
In this case, the Notice to Keeper fails to meet that condition. It does not state anywhere that the keeper is invited to pay the charge. The only references made are to the effect that the keeper should either provide the driver’s details or pass the notice to the driver. There is no direct, clear statement inviting the keeper themselves to make payment. That is a fundamental omission.
To be absolutely clear for the avoidance of doubt:
• The Notice is not compliant simply because it is addressed to the keeper.
• It is not compliant because it implies that someone should take action.
• It is only compliant if it specifically and expressly invites the keeper to pay.
Adjudicators cannot rewrite or gloss over statutory language. Parliament deliberately included this requirement in Schedule 4 to ensure that the transition of liability from the unknown driver to the registered keeper only occurs when all strict statutory safeguards are met. These safeguards are not technicalities—they are legal thresholds.
Whilst some assessors choose to simply gloss over PoFA 9(2)(e), they fail to take into account that sub paragraph (i) is also required to be considered. It is a binary matter and here it is clear that it has not been complied with.
In failing to include the required wording, the operator has not met the requirements of PoFA Paragraph 9(2)(e)(i). It is irrelevant what the operator intended to imply. What matters is whether the statutory wording is present on the face of the notice. It is not.
Therefore, POPLA must find that the NtK does not comply with PoFA and that keeper liability has not been established. The charge cannot be enforced against the registered keeper.
7. The driver made a reasonable attempt to pay
Although this is not the main grounds upon which I am disputing this NtK, I believe it is worth noting that the driver (who I am under no obligation to identify) made a reasonable attempt to pay to extend their parking. The driver spent 7 minutes inside the parking app which is longer than almost any modern app would require to make a simple payment, but was inhibited in doing so by the app malfunctioning. If GroupNexus wants customers to use their app and not provide payment machines surely it would be in their interest to provide a good user experience in the app that makes making payments simple and quick.
The Parking Charge Notice fails on multiple substantive grounds, both statutory and procedural. GroupNexus has not complied with the Protection of Freedoms Act 2012 or the Private Parking Single Code of Practice or the BPA code of practice. As the operator has failed to establish keeper liability and has not evidenced a valid authority to issue the charge, I respectfully request that POPLA uphold this appeal and instruct the operator to cancel the PCN.
