A cardholder writes in about a charge. Someone has to decide what kind of dispute it is, because that sets the deadline, the evidence and the letter that goes back. On a credit card, the rules sit in Regulation Z, and the clock starts when the written notice arrives.
This guide is for dispute operations leaders at US card issuers, banks and credit unions. It is the credit card companion to our piece on Reg E dispute investigation automation, which covers debit and electronic transfers.
How do you automate Reg Z billing error disputes without missing a deadline?
What counts as a billing error under Reg Z?
Section 1026.13(a) lists seven situations (12 CFR 1026.13):
- A charge not made by the consumer or by someone with actual, implied or apparent authority to use the card.
- A charge not identified properly on the periodic statement.
- A charge for property or services the consumer did not accept, or that were not delivered as agreed.
- A failure to credit a payment or other credit properly.
- A computational or accounting error by the creditor.
- A charge the consumer asks for more clarification on, including documentary evidence.
- A failure to mail or deliver the statement to the last known address, if the creditor received that address in writing at least 20 days before the end of the billing cycle.
The "not delivered as agreed" category is narrow. The official commentary says it covers the wrong quantity, late delivery or delivery to the wrong location, but not a dispute over the quality of goods or services the consumer accepted. Acceptance is decided under state or other applicable law. A complaint that a product was poor quality is therefore not a billing error, though it may be a claim or defense under 1026.12(c).
What does the cardholder have to send, and by when?
A billing error notice is a written notice the creditor receives no later than 60 days after it transmitted the first periodic statement showing the alleged error (1026.13(b)). It must arrive at the address the creditor disclosed for billing error notices, and it must let the creditor identify the consumer's name and account number. To the extent possible, it states why the consumer believes an error exists, plus the type, date and amount.
Two intake rules follow. The 60 days run from the statement, not the transaction date, so the system needs the transmission date of the first statement showing the item. And intake should record whether each dispute meets 1026.13(b) before the regulatory clocks are assumed to apply.
What are the Reg Z investigation deadlines?
Section 1026.13(c) sets two clocks that run from receipt of the notice:
- Acknowledgment within 30 days.
The creditor mails or delivers a written acknowledgment, unless it has already completed the resolution procedures in that window. - Resolution within 2 complete billing cycles, and no later than 90 days.
The creditor either corrects the error under 1026.13(e) or explains its findings under 1026.13(f).
A cycle-based deadline depends on each account's statement dates, so compute it per account, cap it at 90 days from receipt, store both dates and work to the earlier one.
What happens to the account while the dispute is open?
Section 1026.13(d) restricts collection while a billing error is pending:
- The consumer need not pay, and the creditor may not try to collect, any part of a required payment related to the disputed amount, including related finance charges.
- For a cardholder on the issuer's automatic payment plan, the issuer must not deduct the disputed amount if the notice arrives up to 3 business days before the scheduled payment date.
- The creditor may not make or threaten an adverse credit report, or report the account or amount as delinquent, because the consumer did not pay the disputed amount.
- The creditor may not accelerate the debt or restrict or close the account solely because the consumer exercised these rights in good faith.
The creditor may still collect the undisputed portion and show the disputed amount on the statement if the statement says payment of it is not required.
A dispute open in the case system but invisible to collections, autopay or bureau reporting is how a billing error becomes a compliance finding. The AI employee should write the dispute flag to those systems at intake and clear it only on resolution.
How does Reg Z differ from Reg E?
Debit and ACH disputes follow Regulation E (12 CFR 1005.11). Our Reg E guide covers the 10-business-day determination, the 45-day extension and the provisional credit, and our glossary has a plain definition of Regulation E. The contrasts that matter to operations:
- Clock unit.
Reg E counts business days, then days. Reg Z counts 30 days for acknowledgment and complete billing cycles, capped at 90 days, for resolution. - Interim relief.
Reg E uses a provisional credit when the investigation runs long. Reg Z has no provisional credit step. Instead, 1026.13(d) lets the consumer withhold the disputed amount and bars collection and delinquency reporting. - Notice.
Reg Z requires written notice at the billing error address.
Some accounts straddle both. Section 1026.13(i) applies Regulation E error resolution instead of the corresponding Reg Z paragraphs when, for example, credit is extended incident to an electronic fund transfer under an overdraft agreement. The classifier needs the product type, not just the intake channel.
How should you separate billing errors, claims and defenses, and fraud?
Three things get filed as "dispute," and each follows a different path:
- Billing error (1026.13).
Written notice, the 60-day window, the 30-day and 90-day clocks and the collection protections above. - Claims and defenses (1026.12(c)).
When the merchant fails to resolve a dispute about property or services bought with the card, the cardholder may assert claims and defenses against the issuer, other than tort claims, and withhold payment up to the amount outstanding for that purchase (12 CFR 1026.12). The right depends on a good faith attempt to resolve the dispute with the merchant. In many cases the purchase must also exceed $50 and occur in the cardholder's home state or within 100 miles of the current address. - Unauthorized use (1026.12(b)).
Cardholder liability cannot exceed the lesser of $50 or the value obtained before the issuer is notified, and applies only if conditions such as adequate notice of the maximum liability are met. An unauthorized charge is also a billing error under 1026.13(a)(1), so one dispute can trigger both rules.
One letter often mixes these. "I never bought this, and the item I did buy never came" is two disputes. The classifier should split the line items, open a clock for each and send ambiguous wording to an analyst. For the fraud side of that triage, see our guide to fraud alert review with AI employees.
What does the investigation workflow look like?
Step | Deadline | Automated work | Human decision |
|---|---|---|---|
Intake | Notice due within 60 days of the first statement showing the item | Capture the notice, match account and statement, record the received date and whether it meets 1026.13(b) | Accept edge cases, such as a notice sent to the wrong address |
Classification | Same day | Tag each line as billing error, claim or defense, unauthorized use or other; start a clock per line | Confirm mixed or ambiguous disputes |
Collection hold | At intake through resolution | Flag the amount in autopay, collections and bureau reporting | Approve exceptions for undisputed balances |
Acknowledgment | Within 30 days | Draft and send the letter; log the date | Review non-standard cases |
Evidence | Inside the resolution window | Pull transaction, authorization, delivery and merchant records into one case file | Judge whether the evidence is sufficient |
Merchant or network | Inside the resolution window | Prepare the merchant inquiry or network dispute package | Decide whether to pursue the merchant or absorb the loss |
Resolution | 2 complete billing cycles, no later than 90 days | Draft the correction notice or explanation; apply the credit once approved | Approve the outcome; sign adverse findings |
After resolution | Per 1026.13(g) | Draft the amount-owed notice and track the payment window | Approve any delinquency report |
How do merchant and network steps fit in?
Reg Z sets the cardholder-facing clock. The merchant side runs on the card network's own rules, with separate time limits, reason codes and evidence formats. This guide does not restate them, so confirm current timelines in your network rulebook and processor agreement, and set your internal deadline so the network step finishes well before the Reg Z limit. A pending chargeback does not stop the Reg Z clock.
For the evidence work, see our guides to chargeback representment and chargeback automation.
What must the resolution letters say?
If the error occurred as asserted, 1026.13(e) requires the issuer to correct it, credit the disputed amount and related charges, and send a correction notice within the 1026.13(c)(2) limits.
If, after a reasonable investigation, the issuer finds no error or a different error, 1026.13(f) requires an explanation of the reasons it believes the alleged error is incorrect in whole or in part. It must also furnish copies of documentary evidence of the consumer's indebtedness if the consumer asks, and if a different error occurred, correct it and credit the account.
When the consumer is found to owe some or all of the amount, 1026.13(g) requires prompt written notice of the amount and when payment is due. The issuer may report delinquency only after the payment period, which is any period disclosed in the account terms or 10 days, whichever is longer. If the consumer writes back in that window to say part of the error is still disputed, the issuer cannot report delinquency unless it also reports the dispute, tells the consumer in writing whom it reported to, and reports any later resolution.
The weak point is the "no error" explanation, which must give reasons specific to the case. The AI employee should draft them from the evidence file, and an analyst should approve every adverse letter.
How long should dispute records be kept?
Section 1026.25(a) requires creditors to retain evidence of compliance with Regulation Z for two years after the date the action was required to be taken, and regulators may require longer (12 CFR 1026.25). Keep the notice, evidence file, letters and timestamps together. Disputes that escalate to a regulator are covered in our guide to CFPB complaint handling automation.
How Zamp Approaches Dispute Investigation Work
Zamp builds AI employees that run jobs end to end, with human approval gates and a full audit trail. For disputes, the AI employee owns the repetitive parts: intake, classification, the deadline clock, evidence collection and letter drafts. Every adverse finding and credit decision stops at a named reviewer, and each step is logged so an examiner can see what was done and who approved it. We have no published dispute case study, so this guide makes no performance claims. See also our guide to AI employees in banking and financial services.
