Run a chargeback evidence register without losing the accounting trail

A chargeback register begins when the processor reports a dispute, not when a bank withdrawal appears. Capture the processor case number exactly, merchant account, customer, original transaction, dispute amount, reason code, notice date, response deadline, and current processor status. Add an internal due date early enough for review. Preserve the original notice because portal fields and labels can change as the case progresses. One chargeback should have one durable internal ID even if the processor later adds related references. The bookkeeper may open and maintain the case. A named risk, sales, or finance owner decides whether the business accepts the dispute or submits evidence.

Link the authorization, order or invoice, delivery or service record, refund history, terms accepted at purchase, and relevant customer communications. Evidence depends on the business and processor rules, so the register should not pretend every case needs the same attachments. Record what exists, what is absent, and who can supply it. Do not create a delivery assertion from a billing address or describe a phone conversation that was never documented. The FTC overview of card disputes is useful general context for how consumers may challenge charges, while the processor's current instructions govern the actual response format and timing.

Use separate fields for processor deadline, internal evidence cutoff, reviewer due date, submission date, and expected decision date. A single "due" column invites confusion. Sort the queue by the earliest actionable date and flag cases whose missing evidence threatens review time. The bookkeeper can send routine reminders from an approved template and escalate overdue owners. It should not submit an unapproved response merely to beat the clock. If the portal uses a different time zone, state it. Save submission confirmation and the exact packet sent; a working draft does not prove what the processor received.

Arrange the packet so a reviewer can connect the disputed claim to the relevant record. A duplicate-charge case needs both transactions and their distinct purpose. A canceled-service case needs the cancellation terms, request date, and subsequent activity. A merchandise-not-received case needs fulfillment records linked to the order. Use an index with file names, dates, sources, and brief relevance notes. Avoid promotional argument and irrelevant customer history. The decision owner approves the position and any customer-sensitive material. Bookkeeping services can provide disciplined assembly without taking ownership of legal strategy or customer relations.

Processors may remove funds, assess fees, issue temporary credits, reverse credits, or settle a final result. Record each movement as its own row tied to the case ID, processor settlement, bank deposit or debit, and ledger entry. Do not replace the original dispute amount with the latest net cash effect. The register should show gross dispute value, fees, provisional activity, recovered amount, final loss, and unresolved balance. This allows the bank reconciliation and revenue records to agree without obscuring the dispute history. The controller determines the proper accounts and period; the preparer supplies a complete movement schedule.

Check whether the original invoice remains open, a credit memo was issued, a refund occurred, or cash was removed only through the chargeback. Duplicate relief is a common risk: a customer may receive both a merchant refund and a processor credit if teams work in separate systems. Compare the chargeback register with the cash application exception log and the customer account. Tie aggregate movements to processor settlements and the bank. Any amount that does not match gets a cause, owner, and next review date rather than a balancing adjustment.

A submitted response is not a closed case. Closure requires the processor's final status, all related cash movements, approved ledger treatment, customer-account update, fees, and retained evidence. Record who reviewed the closeout and when. If the processor permits further appeal, identify whether management declined it or the deadline passed; do not mark the case won or lost prematurely. Accounts receivable management should receive the outcome when it affects collection activity or an open credit. Keep reopened disputes connected to the original ID while preserving each submission version.

Review volume and outcomes by reason code, sales channel, fulfillment method, product, and evidence gap. Use the results to find operational causes such as unclear descriptors, late cancellation handling, missing proof of delivery, or refunds that were never communicated. Win rate alone is a poor bookkeeping control because case mix and business decisions affect it. Better measures include cases opened promptly, packets reviewed before the internal cutoff, cash movements matched, and closed cases with complete support. Restrict the register to staff who need customer and payment data, and remove access when responsibilities change.

Use one completed case to test traceability and one active case to test queue behavior. For the completed case, a reviewer should move from the processor outcome back to every cash entry, submission version, approval, and original transaction. For the active case, the reviewer should see the deadline, missing evidence, current owner, and exact next action without asking the preparer. Compare portal access with the assigned role and remove any ability to issue refunds or alter bank destinations that the work does not require. Document how the team handles an unavailable approver, a portal outage, and evidence received after the internal cutoff. These tests reveal whether the register is a real control or simply a list. Repeat them after processor changes, staff turnover, or a material revision to the response procedure.