Complaints reporting compared across six EU markets

Complaints is the reporting area where national divergence is widest and the EU floor is thinnest. Every market requires complaints to be handled within a deadline and routed to an out-of-court body if unresolved — but the deadline, the body, and what has to be reported or published differ in every one. For a firm operating across the EU, complaints is therefore six regimes rather than one, and the differences are operational rather than cosmetic.

1. The comparison

2. The clocks are the operational constraint

The EU floor comes from PSD2, which sets a reply deadline for payment-services complaints — Germany’s 15-day clock is that floor in national implementation. Several markets then apply a longer or differently framed period for complaints outside the payment-services perimeter: Luxembourg’s handling duty runs on a one-month response clock.

The practical consequence for a multi-market firm is that a single service-level target does not work. A complaint has to be classified — payment services or not, and in which market — before the applicable deadline is known, and the classification has to happen at intake rather than at review. A queue managed to one internal SLA will breach the shortest external clock while comfortably meeting the longest.

3. What has to be reported, and what published

Three distinct obligations recur, and firms frequently conflate them:

• Handling — resolving the complaint within the deadline, with a substantive reply.
• Reporting — periodic structured data to the supervisor on volumes, categories and outcomes. Spain’s regime is explicitly structured-data driven; France’s splits across authorities.
• Publishing — telling customers about the out-of-court route, which several markets require in the complaint response itself and in pre-contractual information.

The third is the cheapest to get wrong and the easiest to fix. A response letter that resolves the complaint but does not name the correct out-of-court body for that market is a conduct defect independent of the outcome.

4. Building one dataset for six regimes

The categories differ per market, so the durable design is a rich internal taxonomy mapped outward, rather than the union of six national category sets. Four attributes captured at intake serve all of them:

• Market — which determines the applicable clock and body;
• Subject matter — payment services, investment, insurance, credit, since this routes the complaint in at least three markets;
• Cause — on the firm’s own taxonomy, granular enough to map to any national category set;
• Outcome and date, including whether the customer escalated.

Those four make every national return a filter and an aggregation rather than a re-classification exercise — which is the difference between a reporting cycle that takes a day and one that takes a fortnight of manual recoding.

5. A worked case

Facts: a firm operating in five markets runs one complaints queue with one 30-day internal target and one category set derived from its ticketing tool.

What goes wrong: the 30-day target breaches the payment-services reply clock in every market that applies it. The ticketing categories do not map to the national reporting categories, so each return is recoded by hand. And response letters name a single out-of-court body, which is correct in at most one market.

What the practitioner does: classifies at intake on the four attributes above, sets the SLA from the classification rather than globally, and templates the response letter per market with the correct body named. None of that requires new systems — it requires the classification to happen at the front of the process rather than the back.

FAQ

Related: Complaints in Luxembourg · ACPR complaints · Complaints reporting in Spain