How Qualified-Lead Disputes and Account Credits Should Work

Who this guide is for

This guide is for SellersGPT customers, finance and revenue operations teams, product and support owners, procurement reviewers, and audit owners. It explains a product process in plain language. Binding terms, the effective product rule, and applicable law control a specific case.

Contents

1 Define the dispute boundary 2 Build the Dispute Evidence Packet 3 Run the Billable-Event-Review-Resolution Audit Trail 4 Apply timing and billing controls 5 Review the effective rule, not later outcomes 6 Record approval, denial, or more-evidence decisions 7 Reconcile charge, no-charge, and conditional credit outcomes 8 Recalculate an illustrative ledger 9 Measure process quality 10 Handle corrections and edge cases 11 Common mistakes 12 Limits 13 Frequently asked questions 14 Sources and methodology

1. Define the dispute boundary

A Qualified Lead dispute concerns whether a billable unit satisfied the governing qualification and billing rule. Valid categories can include:

• a required fit criterion failed;

• evidence was missing, stale, ambiguous, or below the agreed standard;

• identity or company relationship was incorrect;

• the record was a duplicate under the agreed person-account-pursuit-time boundary;

• an Existing Customer block applied;

• the event path was ineligible or invalid;

• the wrong rule or price version was applied;

• a processing defect created an unsupported state, billable event, or posted charge. These are not the same as dissatisfaction with a downstream result. No reply, no meeting, no opportunity, loss to a competitor, budget delay, or failed purchase does not by itself show that the original Qualified Lead state was wrong. A SellersGPT Qualified Lead is not a promise of those outcomes. The process also differs from a card-payment chargeback, cash refund, withdrawal, tax correction, or legal remedy. A product dispute controls whether and when the fee posts. Account credit is a conditional ledger correction only when a prior posted charge requires it under the applicable rule. Public Knowledge explains the mechanism; it does not replace contractual terms.

2. Build the Dispute Evidence Packet

The packet should be a structured record, not a free-form complaint alone. Field Required content Validation Lead and billing item Qualified Lead ID, billable-event ID, any posted-charge ID, account/tenant Must resolve to one lifecycle and ledger trail Filing Submitted time, submitter, channel Compare with applicable window Rule Qualification version, effective date, event time Use historical effective rule Price Pricing key, currency, effective record Verify exact charged value Allegation One or more reason codes and criteria Must name a testable rule Customer evidence Source, observation date, attachment/reference, explanation Preserve original form and provenance Original evidence Criterion results and evidence packet used for qualification Immutable reference or controlled snapshot Controls Existing Customer, Suppression, duplicate, identity, event eligibility Evaluate each under its own scope Review Reviewer, requested evidence, decision, reason, time Enforce authorization and independence Resolution Pending hold, charge/no-charge outcome, clear/solved month, and any conditional correction Apply one financial treatment to the disputed amount Do not ask the customer to prove fields that were never part of the governing rule. Do not accept a vague statement such as bad lead as the final reason; route it to a specific criterion or explain that downstream satisfaction is outside the dispute boundary.

3. Run the Billable-Event-Review-Resolution Audit Trail

Use five immutable or append-only stages: 1 Qualification event: record enters Qualified Lead under rule version Q. 2 Billable event: exact pricing-system value P and pricing version V are linked to the unit without implying that a disputed fee has been deducted. 3 Dispute event: customer files reason R with evidence at time T; the disputed fee remains pending and is not deducted while review is open. 4 Review decision: authorized reviewer records Upheld, Rejected, or More Evidence with rationale and a clear or solved time when final. 5 Billing resolution: a rejected dispute posts in the clear or solved month; an upheld dispute is not charged if it has not posted. Only an already-posted charge that requires correction receives a linked account-credit entry under the applicable rule. The original qualification, billable event, dispute, evidence, decision, and any posted charge or correction remain visible. This pattern supports gross, pending, resolved-charge, no-charge, conditional-credit, and net reporting without erasing what happened or applying the adjustment twice. NIST's log-management guide addresses policies and procedures for generating, transmitting, storing, accessing, and disposing of log data. NIST SP 800-92, "Guide to Computer Security Log Management" It is cybersecurity guidance, not a sales-billing standard. The narrow operational lesson is that material automated and financial decisions need durable, access-controlled records.

4. Apply timing and billing controls

The latest effective product decision in the supplied SellersGPT billing archive is dated May 8, 2026: do not deduct a disputed fee while review is open; if the dispute is rejected, bill it in the month the case is cleared or solved. That archive also marks billing implementation NOT VERIFIED. This article therefore states the approved decision but must not claim production verification until QA supplies evidence. Where the approved SellersGPT product rule and effective terms apply, the current public workflow uses a five-day dispute window. Before publishing or enforcing that statement, bind it to:

• rule version and effective date;

• clock start event and time zone;

• calendar-day definition;

• allowed submission channel;

• service outage or exception treatment;

• notice and acknowledgement record. This draft leaves the binding product-version and reviewer fields unassigned, so it remains ready_for_review. The five-day statement is conditional, not a universal legal right. When a filing appears late, preserve it and record the eligibility decision. Do not delete it. An authorized exception, if allowed, needs reason, owner, scope, and audit event.

5. Review the effective rule, not later outcomes

The reviewer should reconstruct the original decision: 1 Which rule was effective at the event and qualification time? 2 Which criteria were applicable? 3 Which evidence passed each required criterion? 4 Did identity, completeness, and event eligibility pass? 5 Did a hard stop apply at the relevant time? 6 Was the record distinct under deduplication rules? 7 Did the pricing system return the correct effective value? 8 Does the new evidence establish that the original decision was unsupported or incorrectly processed? Later evidence can have different meanings. If a person changes jobs after qualification, the original state may have been correct at the time. If a customer later provides an older contract proving an Existing Customer relationship already existed, the original billing may have failed the applicable control. Time and evidence provenance decide the case. How to Handle Conflicting, Duplicate, or Stale Signals explains how to preserve raw events while updating current conclusions.

6. Record approval, denial, or more-evidence decisions

Upheld Use when the evidence establishes that the billable record failed the applicable rule or the wrong price or control was applied. Record the failed criterion, evidence, decision reason, and billing instruction. If the fee has not posted, record no charge. If a prior posted charge requires correction, issue a linked account-credit instruction under the applicable rule. Rejected Use when the record passed the rule and the allegation concerns a downstream result or unsupported assertion. Explain the rule boundary, cite the decisive evidence, and post the fee in the month the dispute is cleared or solved. More Evidence Use when the allegation is material but the submitted and original evidence cannot resolve it. State exactly what is needed, who owns the next action, and the decision deadline. Keep the disputed fee pending and do not deduct it while review remains open. Reviewers should not invent a fourth informal outcome such as goodwill invalid that bypasses reporting. If a commercial goodwill adjustment is authorized, store it as its own reason and authority, not as a false qualification failure.

outcomes

A billing-resolution record should contain:

• resolution ID, outcome, and clear or solved time;

• currency and effective billable amount;

• related billable-event, Qualified Lead, and any posted-charge IDs;

• review decision ID;

• posting month, no-charge state, or account-balance effect;

• reason category;

• actor or service identity;

• idempotency key to prevent duplicate charges or corrections. If the outcome requires correction to an already-posted charge, the account-credit record should also identify the credit ID, exact historical amount, related charge, authority, and ledger time. Do not recalculate it from current pricing or from CPC, CPA, or modeled MQL cost. Do not create a credit when the same amount has already been treated as uncharged. Reconcile: net QL charges = resolved posted QL charges - linked corrections to previously posted QL charges Report counts and money separately:

• gross Qualified Leads created;

• disputes filed;

• disputes upheld, rejected, pending, or otherwise resolved;

• rejected charges posted in their clear or solved month;

• upheld no-charge outcomes;

• account credits posted only for corrections to previously posted charges;

• net billable Qualified Leads under the reporting policy;

• gross charge, credit value, and net charge.

8. Recalculate an illustrative ledger

Illustrative scenario - explicitly fictional. Let P be the exact historical Qualified Lead price resolved for a closed cohort. Twelve gross QLs create billable events. Ten are not disputed and post normally. Two disputes are filed on time: one Existing Customer failure is upheld and one complaint based only on no reply is rejected. Ledger line Count or formula Commercial effect Non-disputed posted charges 10 x P 10P Disputes filed 2 USD 0 deducted while review is open Upheld dispute 1 No charge because the item has not posted Rejected dispute 1 P posts in the clear or solved month Account credit No prior posted charge requires correction Net QL charges after resolution 10P + P 11P Gross creation remains 12. Net billable QLs for the chosen commercial view equal 11. The upheld rate is 1 / 2 = 50% of filed disputes, while upheld no-charge incidence is 1 / 12 = 8.33% of gross QLs. The denominators answer different questions. If the upheld charge had already posted under an earlier or exceptional ledger state and the applicable rule required correction, the alternative trail would show 12P posted and a linked P account credit, also producing 11P. It must not also record that item as uncharged. An idempotency key must reject any duplicate charge or credit attempt. Optional follow-up stays separate. If the upheld record had already accrued two eligible follow-up months, the product rule must state whether and how a QL invalidation affects those service charges. Do not silently assume the QL no-charge outcome or conditional credit also reverses unrelated lines.

9. Measure process quality

Monitor:

• disputes per gross QL;

• approval, denial, pending, and withdrawal counts;

• resolution-month posting and conditional-credit completeness and latency;

• reasons by criteria and rule version;

• late-filing incidence;

• repeat disputes on the same unit;

• duplicate-credit prevention failures;

• reviewer turnaround and evidence requests;

• classification drift by cohort;

• concentration by source, market, or implementation version. A rising approval rate may reveal criteria, evidence, identity, customer-match, or processing problems. It does not automatically prove fraud or poor market fit. Investigate root causes and preserve denominator context.

10. Handle corrections and edge cases

• Incorrect price, valid QL: correct the pending amount before posting or append the authorized difference to an already-posted charge; do not label the lead unqualified.

• Valid at event time, later stale: retain original state; update current operational status separately.

• Duplicate created by retry: merge or correct under the event-idempotency rule; prevent an unposted duplicate or issue a linked correction only if a duplicate charge already posted.

• Existing Customer discovered later: decide using evidence of whether the relationship existed within the rule's relevant time and scope.

• Suppressed but otherwise qualified: outreach treatment and billing treatment must be evaluated separately.

• Conflicting evidence: preserve both records, source dates, and the review decision.

• Customer requests cash: route under binding finance and legal policy; do not represent account credit as a guaranteed cash refund. Google Ads' CPA definition reminds readers that a cost metric depends on the configured event. Google Ads Help, "Average CPA: Definition" It does not define the Qualified Lead charge or remedy. FTC guidance supports evidence-based objective claims. U.S. Federal Trade Commission, "Advertising and Marketing Basics" It does not approve this dispute policy or replace jurisdiction-specific requirements.

11. Common mistakes

• Deciding a dispute from sales satisfaction rather than the effective rule.

• Deleting the original charge or QL event.

• Applying the current criteria or price to a historical case.

• Deducting the disputed fee while review is open.

• Posting a rejected dispute in the original event month instead of the clear or solved month.

• Treating a filing as an automatic credit or applying both no-charge and credit treatment.

• Posting a credit without a related decision and previously posted charge.

• Charging or crediting twice after a retry.

• Calling account credit a guaranteed cash refund.

• Inferring price from USD 5.10 CPC or another benchmark.

• Combining QL and follow-up credits without a governing rule.

• Reporting dispute rate without its denominator.

• Publishing the five-day window without a bound version and effective date.

12. Limits

This guide explains SellersGPT product operations. It does not replace an order form, binding terms, legal remedies, payment-network rules, tax or accounting treatment, or jurisdiction-specific advice. Actual eligibility, timing, evidence, credit, and account treatment follow the effective rules. A dispute outcome does not predict the lead's future commercial outcome. Approval corrects a rule or processing failure; denial does not guarantee future value.

13. Frequently asked questions

Is no response a valid dispute reason? Not by itself. A Qualified Lead is not a response guarantee. A dispute must identify a failed applicable criterion, exclusion, price/control error, or processing defect. Does filing a dispute create a charge or credit immediately? No. Filing opens review, and the disputed fee is not deducted while review remains open. Resolution determines whether the fee posts, is not charged, or requires a linked correction to an already-posted charge. Why preserve the original billable event? It maintains an auditable history and allows gross, pending, posted, no-charge, conditional-credit, and net reporting without erasing the evidence or applying an adjustment twice. Is account credit the same as a cash refund? No. In this process, account credit is a ledger correction for an already-posted charge when the applicable rule requires it. Cash, withdrawal, and payment treatment depend on binding finance and legal terms. What if the wrong price was charged but the lead was valid? Correct the pending amount before it posts or apply the authorized linked correction after posting. Do not misclassify the Qualified Lead to solve a pricing error.

Sources and methodology

The Dispute Evidence Packet, Billable-Event-Review-Resolution Audit Trail, decision states, and symbolic ledger are SellersGPT tools. The supplied billing archive provides the latest effective no-deduction and clear/solved-month decision and marks implementation NOT VERIFIED. Public sources support durable-record, metric, and evidence-based-claims principles; they do not create the dispute window, billing rule, remedy, or product price. 1 LE-01-INTERNAL-DEFINITION - SellersGPT Knowledge, "What Counts as a Qualified Lead?". Qualified Lead definition. 2 LE-03-INTERNAL-PRICING - SellersGPT Knowledge, "How Pay-Per-Qualified-Lead Pricing Works". Billable event, dispute resolution, Existing Customer, Suppression, and follow-up boundaries. 3 LE-09-INTERNAL-AGREEMENT - SellersGPT Knowledge, "How to Set Qualification Criteria Before You Pay for a Lead". Effective criteria and evidence agreement. 4 PP-20-INTERNAL-EVIDENCE - SellersGPT Knowledge, "How to Handle Conflicting, Duplicate, or Stale Signals". Evidence correction and history. 5 LE-10-INTERNAL-BILLING-DECISION - SellersGPT archived billing decision summarized in this guide. Archive dated May 8, 2026; states no immediate deduction during dispute and rejected billing in the clear or solved month; implementation status NOT VERIFIED. 6 NIST-SP800-92 - National Institute of Standards and Technology, "Guide to Computer Security Log Management". Accessed August 25, 2026; durable-record context, not a billing standard. 7 GOV-04 - U.S. Federal Trade Commission, "Advertising and Marketing Basics". Accessed August 25, 2026. 8 DEF-03 - Google Ads Help, "Average CPA: Definition". Accessed August 25, 2026.