Skip to content

LGW TV, Podcast & Articles

Lead Returns and Credits: Build a Clear Exception Process

Magnifying glass over a blank card beside a stack of cards and a blue folder.

Lead Returns and Credits: Build a Clear Exception Process

November 17, 2026    Comment off


A lead return is a request to review a purchased record against the terms of the purchase. A credit is a commercial adjustment that may follow that review. They are different steps, and neither should be assumed simply because a lead did not become a customer.

The useful question is specific: which agreed requirement did this record fail, what evidence supports that finding, and what remedy does the supplier allow? Build your process around that question before volume starts. This worksheet covers operating controls; the agreement and your company’s review process determine the actual terms.

Agree on the rules before placing the order

Ask the supplier to define eligible reasons, evidence requirements, submission deadlines and how decisions will be communicated. Confirm whether an approved request produces a refund, an account credit or a replacement record. Those outcomes affect purchasing and reporting differently.

A replacement adds another record to handle. An account credit may reduce a later invoice. A refund returns money. Do not treat them as interchangeable in your source report, and do not describe any one of them as a universal buyer entitlement.

Include these questions in your lead vendor review. If a promise is important to the purchase, make the operational meaning clear enough that two people can apply it consistently.

Use specific reasons instead of “bad lead”

A missing required field, an out-of-scope location and a duplicate under the agreed duplicate rule are different issues. Record the precise reason being claimed. A customer declining an offer is also different from a delivery exception; whether any situation qualifies depends on the purchase terms.

Ask reviewers to distinguish a verified fact from an unresolved observation. “Phone number failed our documented check” says more than “fake.” “No response after the approved contact process” does not establish that the person never made an inquiry. Avoid turning an uncertain sales outcome into an unsupported accusation.

Keep one exception log

Field What to capture
Record reference Supplier lead ID, internal ID and purchase batch
Applicable rule Product version, reason code and the relevant agreed requirement
Timing Delivery, discovery and submission timestamps
Evidence Minimum necessary supporting detail in an approved secure location
Request Amount or remedy requested, submitted by whom and where
Decision Pending, approved, partially approved or rejected, with explanation
Settlement Credit, refund or replacement reference and reconciliation date

Keep personal information out of casual email chains and shared presentation slides. Use the approved exchange method for evidence and share only what the review requires. A reporting sheet can usually point to a controlled record instead of copying its full contents.

Separate requested, approved and applied amounts

Consider a hypothetical order of 100 leads at $20 each: $2,000 in gross lead charges. The buyer requests $200 in credits, the supplier approves $120, and $80 has appeared on the invoice so far. The requested amount is not a settled reduction in cost. There is $40 of approved credit still to reconcile, and the remaining $80 of requested credit needs its own decision status.

This is an arithmetic example, not an accounting policy or a normal return rate. Use the appropriate treatment for your own books. For an operating review, clearly label gross charges, approved adjustments and adjustments actually applied so another person can reproduce the report.

Do not count the same remedy twice. If a replacement is provided, track its relationship to the original record and its handling cost. If a credit later appears on an invoice, connect it to the original claim rather than recording an unexplained improvement in a different month’s source performance.

Reconcile the exceptions, not just the total

Match the supplier’s response back to individual IDs. A total credit can look right while the wrong records were approved or one claim was submitted twice. Investigate unmatched IDs, partial decisions and records whose status changed after the report was exported.

Platform workflows differ. For example, LeadsPedia documents approval and rejection steps, while Lead Prosper describes matched and unmatched return handling. Check your actual configuration and agreement rather than assuming software availability establishes a return policy.

Use the pattern to fix the source of the problem

  • Repeated missing fields: review the delivery specification and validation.
  • Duplicate disputes: clarify the matching rule and time window.
  • Late requests: repair the internal review and submission handoff.
  • Approved credits not applied: assign a reconciliation owner.
  • Weak customer outcomes without a qualifying exception: review targeting, handling and economics separately.

Your lead management process should preserve both the commercial exception and the customer outcome. One field should not erase the other. Review the resulting costs alongside customer economics before changing purchase volume.

Bring clearer buying questions to LGW

Use this checklist to discuss how potential partners handle exceptions before you launch. Review eligibility and apply for LGW’s $395 Lead Buyer Pass. Application and approval are required. The pass serves qualifying end buyers purchasing leads for their own use; lead sellers, publishers, agencies and call center providers are ineligible even when they buy leads.