AI is asking you to pay: getting the record corrected

When AI asks you to pay · Part 4

Read also: Part 1: decisions · Part 2: results · Part 3: asking for help.

A payment reminder can arrive after the bill has been paid. A dispute can be acknowledged without the underlying record being corrected. Drawing on collectors’ published procedures, a documented US case and French law, this fourth instalment follows the route from a customer’s message to the operations that must take it into account.

On its French website, Intrum says a payment may take several days to become visible to its services. When money has been paid directly to the original creditor, it asks for proof of payment. PAIR Finance also describes a possible delay before funds reach its account, depending on the payment method, and invites people still receiving reminders after a few days to get in touch. Receiving the money and updating the information used to manage a case are related, but distinct, operations. [1] [2]

Matching a payment to an invoice can take time. While that payment is being checked, which information will the next reminder use?

There is an additional issue when software interprets the reply. PAIR describes its generative AI as able to classify incoming requests, including disputes, select responses and route processing to an employee or to AI. Its configuration and results on French accounts still require independent verification. [3]

Understanding the risk requires following the process to completion. A message can be recorded and a decision made, but that decision still needs to reach the systems that act on the account. Each stage calls for a different check.

Start with the disputed facts

A request for more time is about arranging payment. A dispute asks a different question: whether the right person is being pursued, whether the debt exists, whether the amount is correct or whether it has already been paid. Offering instalments does not resolve mistaken identity.

In France, Article 1353 of the Civil Code allocates the burden of proof. A party seeking performance of an obligation must establish it; a party claiming to have discharged that obligation must substantiate the payment or other event that extinguished it. A collection system’s entry does not remove the need to examine the relevant evidence. [4]

The French consumer-protection authority, the DGCCRF, also explains that a claim must exist, be for a determined or determinable amount, and be due. Amicable collection is distinct from compulsory enforcement, which requires an enforceable instrument and compliance with the rules governing the particular measure. The wording of a reminder cannot change its legal status. [5]

Ability to pay and liability to pay must therefore remain separate. Someone may be able to afford an amount they do not owe. Conversely, a valid debt may be impossible to repay immediately. The first problem calls for verification; the second requires an assessment of the person’s circumstances and possible arrangements.

In its French help section on unfamiliar invoices, PAIR says it checks the matter with the contractual partner and stops the process if its payment demands prove unjustified. That describes the outcome of the check. It does not, on its own, specify which reminders are paused while the check is underway, or how long the investigation takes. [2]

An exception must have a way in

A service built around an existing account must also be able to receive a message from someone who says they are not the customer concerned. Authentication may protect personal information. A route that the person cannot actually use may prevent the error from being reported.

The US Consumer Financial Protection Bureau’s report on financial chatbots, published on 6 June 2023, reproduces a complaint illustrating this difficulty. A person disputing a debt described repeatedly being directed to log into an account they said they did not have. The regulator reports an individual complaint without ruling on the debt’s validity. Its scope remains that US customer’s experience; the precise technology involved is unknown. [6]

Intrum’s French dispute page directs users to messaging within its payment portal. The company also publishes a complaints procedure accepting email, post or telephone contact. Those pages do not specify how quickly someone can reach an employee or what authority that employee has over the case. [7] [8]

For requests concerning personal data, the EU General Data Protection Regulation (GDPR) requires the controller to facilitate the exercise of rights. Where there are reasonable doubts about identity, it permits the additional information needed to confirm it. Both requirements matter: protect a file from disclosure to the wrong person while enabling the right person to challenge an error. [13]

The right to human intervention also needs careful description. Article 22 addresses certain solely automated decisions with legal or similarly significant effects and provides specific safeguards in the relevant circumstances. The human intervention required under this provision therefore depends on the type of decision and the legal basis for automating it. [15]

An agreement can be undone elsewhere

A US case shows why the enquiry needs to go beyond the interface. In its order concerning Enova, issued on 15 November 2023, the CFPB described loan extensions approved and then automatically cancelled when an interim partial payment changed the balance. The conduct described covered 2011–2020. The system could then debit, or attempt to debit, the remaining loan balance rather than only the expected fee. A confirmed agreement was being undone by a subsequent computer check. [9]

These are the regulator’s findings in a matter resolved by consent, without admission or denial of the findings and legal conclusions, except as to jurisdiction. In its statement that day, Enova attributed the issues to unintended technical errors, said they had been addressed and disagreed with the CFPB’s characterisation. It described centralising payment processing and strengthening testing. Those remain the company’s representations. [9] [10]

An order filed on 2 September 2025 subsequently terminated the consent order and waived alleged non-compliance with it. The document records, among other things, payment of the $15 million civil penalty, the engagement of a consultant, and steps towards redress and corrective measures. [11]

The documented mechanism was a software balance check. The sources do not attribute it to generative AI. Its relevance here is the break between the agreement confirmed to a customer and the payment operation eventually initiated.

The grounds for pausing collection

A service complaint, a challenge to the debt and a personal-data request can exist together. They do not have interchangeable effects. Putting them behind the same button does not erase the legal distinctions.

In the United Kingdom, FCA rule CONC 7.14 requires firms within its scope to suspend recovery steps when a debt is disputed on valid or potentially valid grounds. It also requires an investigation and information for the customer on the outcome. Where the collector is not the lender or debt owner, information must flow back under the arrangements specified in the rule. This is a UK requirement within a particular regulatory scope, not a general rule governing French invoices. [12]

In France, a separate route concerns the accuracy of personal data. Under Article 18 of the GDPR, a person contesting that accuracy has the right to obtain restriction of processing while it is verified. Restriction limits use without necessarily deleting the data. The CNIL explains its purpose: keeping disputed information from continuing to be used while a correction is being examined. [13] [14]

The legislation nevertheless permits certain processing after restriction, including to establish, exercise or defend legal claims. It also requires notice before the restriction is lifted. A data request therefore neither extinguishes the debt nor replaces a challenge before the appropriate court. [13]

Its practical effect should be identifiable. Which information is covered? Which uses have stopped, and from when? A receipt acknowledging the request does not answer those questions. Equally, pausing a particular use does not concede that the entire debt is non-existent.

Taking a correction through the system

Article 5 of the GDPR requires accurate data and, where necessary, updates, with reasonable steps to rectify or erase inaccurate data without delay in light of the processing purpose. Article 19 addresses the next stage: relevant corrections and restrictions must be notified to recipients of the data, unless this is impossible or involves disproportionate effort. The person can ask to be told who those recipients are. [16] [13]

Article 16 also gives the individual a right to have inaccurate data corrected without undue delay. Following that correction through a collection process requires examining exchanges between the creditor, service provider and their systems. [13]

Consider a design example, not an incident attributed to an operator. A service corrects an invoice balance, but a reminder has already been prepared using the old amount. Updating the account record does not guarantee that the prepared message will be recalculated. It may need to be cancelled or checked again immediately before sending. The relevant test is the information actually used when the action takes place.

The same reasoning applies when a partner sends back an older copy of the record. A correct update could later be overwritten by stale information. Retaining the source, version and date of changes, and checking that they were applied, would help detect this kind of failure. These are proposed controls, not incidents observed at Intrum or PAIR.

A human handover must also have practical substance. Does the reviewer have the necessary evidence? Can they correct the information, or obtain action from the team authorised to do so? Access rights should fit the task without unnecessarily opening every customer file. The CNIL recommends limiting permissions and separating responsibilities along these lines. [17]

Computer logs can help establish what happened next: they record operations and when they occurred. The CNIL recommends recording changes with the actor’s identifier and a reference to the data concerned, while protecting the records. It also warns against excessive duplication of personal data in logs and keeping them indefinitely. Checking a correction does not justify copying a customer’s supporting documents everywhere. [18]

The deadlines run independently

Intrum’s published complaints procedure states that it will acknowledge a complaint within ten working days if it cannot provide a response within that period, and handle it within a maximum of two months from sending. This is the company’s stated timetable for that procedure. It is neither a universal debt-collection deadline nor a general two-month pause in collection. [8]

For a personal-data rights request, the GDPR requires information about action taken without undue delay and, ordinarily, within one month of receipt. A further two months may be allowed where the complexity and number of requests justify it; the extension and its reasons must be notified within the first month. That response deadline is not permission to wait until the last day before correcting inaccurate information. [13] [16]

Court proceedings have a different timetable. Under Article 1415 of the French Code of Civil Procedure, an objection to an injonction de payer, or payment order, is lodged with the registry of the court that issued it, using the prescribed procedure. A conversation in a collector’s messaging system is not a substitute. [19]

Article 1416 ordinarily allows one month after formal service of the order. If service was not made on the person, it provides different starting points, linked to the first document served personally or, failing that, the first enforcement measure making assets unavailable. The document received and the relevant procedure therefore matter; not every notification starts an identical countdown. [20]

The reform dated 16 February 2026, applicable in these respects to orders issued from 1 September 2026, changed matters including service and the registry’s notification of the creditor. It did not make the collector’s complaints team the recipient for a court objection. Article 1416 retains its own rules. [21] [19] [20]

These processes may need to proceed in parallel. Waiting for a commercial response before dealing with a court document is a confusion to avoid. This account explains general rules; an individual case requires checking the documents and dates and, where needed, obtaining professional legal advice.

Following a correction to completion

The companies’ help pages describe reconciliation delays. The Enova case, in another jurisdiction and over an earlier period, shows how operations after confirmation could also undo an agreement. Neither establishes an error rate for AI debt collection in France. [1] [2] [9]

An investigation using case files would match the original request and supporting evidence to the decision and subsequent actions. Was the challenge upheld, partly upheld or rejected? Was the decision explained? Where a correction was required, which records establish that it reached the relevant recipients and operations? These questions do not assume every dispute should end in the abandonment of a claim.

Automation could make this easier to verify if it preserves usable records and applies decisions consistently. It could also make an error harder to follow if no one can establish which system used which version of a file. The documentary evidence identifies that risk and useful controls; it does not establish which outcome prevails across the market.

The result to examine is specific: an understandable decision, corrected information where correction is required, and operations that actually use the up-to-date record.

Method and limitations

This documentary investigation has a cut-off date of 25 September 2026. Company pages describe published procedures or technology; they do not verify implementation. The Enova account distinguishes the CFPB’s findings, the company’s published position and the termination order. It is not presented as a French case or a demonstrated generative-AI failure.

No interviews, requests for comment, access to debtors’ accounts or platform tests have been undertaken. No individual French case file has been authenticated. The correction scenarios are design examples. The Enova diagram follows the mechanism described by the CFPB. Legal comparisons remain limited to the relevant jurisdictions and scope. No statistical result has been extrapolated.

Sources and reference points

[1] Intrum France. J’ai déjà payé. Undated page. Possible delay before a payment becomes visible; proof requested for payment directly to the creditor.

[2] PAIR Finance. Aide et soutien : France. Undated page. Arrival of funds and checks of a disputed invoice with the contractual partner.

[3] PAIR Finance. Intelligence artificielle. Undated page. Provider description of request classification and routing of responses.

[4] Légifrance. Code civil, article 1353. Version in force since 1 October 2016. Proof of the obligation and of payment or discharge.

[5] DGCCRF. Recouvrement amiable de créances : les règles à connaître. 24 October 2025. Requirements for a claim and distinction between amicable collection and compulsory enforcement.

[6] Consumer Financial Protection Bureau. Chatbots in consumer finance. 6 June 2023. A reported complaint about a route requiring an account the person said they did not have; not a ruling on that debt.

[7] Intrum France. Je ne suis pas d’accord avec cette dette. Undated page. Directs users to portal messaging; other channels are described in source 8.

[8] Intrum France. Je souhaite faire une réclamation. Undated page. Acknowledgement within 10 working days if no answer has been given; stated handling limit of 2 months from sending.

[9] Consumer Financial Protection Bureau. In the Matter of Enova International, Inc.: Consent Order, 2023-CFPB-0014. 15 November 2023. §§ 42–50: extensions confirmed and then automatically cancelled after a balance change. § 5: terms of consent. See termination in source 11.

[10] Enova International. Enova Reaches Agreement with CFPB on Consumer Loan Processing Errors. 15 November 2023. Enova’s published position: unintended errors, disagreement with the characterisation and stated corrective measures.

[11] Consumer Financial Protection Bureau. Order Terminating the Consent Order: Enova International, 2023-CFPB-0014, Document 3. Filed 2 September 2025. Terminates the order and records, among other matters, payment of the $15 million penalty and corrective steps.

[12] Financial Conduct Authority. Consumer Credit sourcebook, CONC 7.14: Settlements, disputed and deadlocked debt. CONC 7.14.1R–6R. UK rules within their scope on disputed debts, suspension, investigation and information. Clauses dated 1 April 2014, checked in 2026.

[13] CNIL / Règlement (UE) 2016/679. RGPD, chapitre III : droits de la personne concernée. Articles 12, 16, 18, 19 and 22: rights, deadlines, restriction and recipients. Conditions and exceptions continue to apply.

[14] CNIL. Le droit à la limitation du traitement : geler l’utilisation de vos données. Explanation of restriction. Read alongside the conditions and exceptions in Article 18, source 13.

[15] CNIL. Profilage et décision entièrement automatisée. 29 May 2018. Conditions and safeguards for solely automated decisions under the GDPR.

[16] CNIL / Règlement (UE) 2016/679. RGPD, chapitre II : principes. Article 5: accuracy and updates, reasonable steps, data minimisation and security.

[17] CNIL. Sécurité : gérer les habilitations. 13 March 2024. Role-appropriate permissions and separation of responsibilities.

[18] CNIL. Sécurité : tracer les opérations. 14 March 2024. Operation logs, protection and limits on the information retained in them.

[19] Légifrance. Code de procédure civile, article 1415. Opposition is made at the registry of the court that issued the order. Read the version and transitional provisions with source 21.

[20] Légifrance. Code de procédure civile, article 1416. Normally one month after service, with particular starting-point rules where service was not made personally.

[21] Légifrance. Décret n° 2026-96 du 16 février 2026 portant réforme de l’injonction de payer. Decree dated 16 February, published 17 February 2026. Articles 1 and 9: amendments and application to orders issued from 1 September 2026.

Documents consulted on 25 September 2026. Pages without an established date remain marked as undated. Several references come from the same organisation and are not independent validations.