Before You Pay: The Minimum B2B Lead Evidence Pack

Definition

The minimum proof pack is the evidence attached to one invoice, deposit release or delivered batch. It answers a narrow question: does the amount requested match units that the buyer received and accepted under the signed contract? The supplier has already been selected and the contract already exists. This is not vendor shortlisting and it is not a new legal or security due-diligence exercise.

The pack joins four records: the commercial authorization, the delivered batch, the buyer's replay and the payment decision. A valid pack lets a second reviewer reproduce why each charged unit was accepted, corrected, disputed or excluded. A dashboard screenshot, a total row count or a promise of future replacements is not enough because none proves which contractual unit was received.

The U.S. Federal Acquisition Regulation states that invoice payment is based on a proper invoice and satisfactory contract performance, and that authorization is supported by a receiving report or equivalent record naming the contract, work, accepted quantity, delivery date, acceptance date and responsible official source.

That rule governs U.S. federal procurement, not every private contract. Its useful operating principle is the separation of invoice, receipt, acceptance and named approval. The method below adapts that auditable chain to a small B2B founder buying leads.

Prerequisites

Start only when the following items already exist:

• a signed order, contract or approved purchase authorization;
• a contractual schedule defining the billable lead or meeting;
• an invoice tied to a named delivery period or batch;
• the actual transfer file, not only a dashboard total;
• a buyer reviewer who did not prepare the supplier's proof;
• an acceptance window and a route for disputes or corrections.

If the parties have not defined the billable unit, stop. Do not invent a definition after seeing the delivery. Return to the contract stage and resolve the gap in writing. The lead-supplier contract guide belongs before commitment. This article begins when those terms are available and a payment request must be checked.

Separate commercial acceptance from lawful use. A record may match the ideal customer profile and still lack adequate provenance, permitted use or objection handling. A clean invoice also does not prove that a list can be used safely.

Steps

First, freeze the payment perimeter. Give the pack one identifier. Record the invoice, contract version, order reference, delivery period, batch identifier, unit price, submitted quantity and amount. Save the exact file received and a checksum so later corrections do not overwrite the original delivery. Mark any deposit, retainer or milestone separately from units already delivered.

Second, copy the contractual lead definition into the review sheet. Do not paraphrase it. For each billable unit, list required account fit, role, source, freshness, contact fields, qualification evidence, duplicate rule, exclusion rule, permitted use and acceptance window. Define accepted, rejected, duplicate, unknown, corrected and replaced as separate states. A replacement may satisfy a remedy, but it must not erase the original defect from the batch result.

Match the invoice to the contract and transfer file. The sum of accepted units multiplied by the applicable price should reconcile to the undisputed charge. Retainers and milestones require their own delivered-work evidence. Do not convert an activity measure, such as research attempts or messages sent, into a billable lead unless the contract expressly defines that unit.

Third, replay a buyer-selected sample. The buyer chooses the records after freezing the delivered file. Include all disputed units, high-risk edge cases and a random slice that the team can inspect carefully. Store the selection method or seed. Do not let the supplier present only its strongest examples.

For every selected record, repeat the promised checks from the underlying evidence:

1. open the stated source and confirm what it supported on the recorded date;
2. reproduce account and role qualification using the contract rules;
3. verify required fields, timestamps and duplicate matching;
4. check exclusions, known objections and permitted use;
5. confirm that notes, evidence and status survived the transfer;
6. assign accepted, rejected or unknown with a reason code;
7. have the reviewer sign and date the replay.

There is no universal sample size. The sample is large enough only when the buyer can inspect it fully and when it represents the risks that affect payment. A replay validates the batch evidence and control process. It does not promise replies, meetings or revenue.

Use the defensible qualification framework to keep account fit, role, problem, timing and unknown states explicit.

Fourth, verify provenance and rights at record level. The pack should connect each sampled record to a source category, exact source where available, collection or observation date, entity that supplied it, permitted purpose, role of each party, notice or objection route and any onward recipient. A generic privacy policy does not prove the chain for the delivered record.

The CNIL says organisations reusing public online data for commercial prospecting must inform people about the data source and their rights, respect objections, and notify partners of correction, erasure or restriction requests when the data was shared source.

European Commission guidance says a processor must provide sufficient guarantees, act under a contract or other legal act, and obtain prior written authorization before appointing another processor source.

Those requirements depend on the actual countries, purposes and roles. The founder should obtain qualified legal advice where needed. The payment reviewer is not asked to reperform all legal diligence. The reviewer checks that the delivery carries the provenance and rights evidence the signed contract required, then escalates any mismatch.

If the supplier executed commercial email in the United States, the proof pack should also include the approved sender identity, message version, suppression check and opt-out handling log.

The FTC says CAN-SPAM covers business-to-business commercial email and that hiring another company to send marketing messages does not remove the promoted company's legal responsibility source.

Fifth, preserve correction history. A correction record should name the original unit, defect code, person who reported it, evidence used, change made, date, reviewer and final status. Keep the original value visible. Re-run the same acceptance rule after correction. If a unit is replaced, connect the replacement to the original without changing the original denominator.

Correction and payment are separate decisions. A correctable defect may justify a hold until the remedy passes. A repeated defect may trigger the contract's suspension or root-cause clause. The buyer should not promise to pay simply because the supplier says a cleaner file will arrive later.

Sixth, verify transfer and exit evidence. The delivered export should include the fields the buyer needs to continue safely: accepted-unit identifiers, source and date, qualification evidence, decision history, objections, suppression status, corrections and ownership of any notes or assets. Test that the buyer can read and reuse the export under the contract.

For a first or final payment, run the exit check now. Confirm how accounts and credentials are revoked, how open work is handed over, which data is returned or deleted, how backups and subprocessors are handled and who provides confirmation. For recurring invoices, repeat the full exit test when the process or supplier changes, and verify the critical export fields on every batch.

Seventh, issue one control record. The reviewer signs a payment release sheet containing the pack identifier, invoice, contract version, original batch checksum, sample method, findings, accepted and disputed amounts, corrections, open rights issues, decision, owner and date.

Use four possible decisions:

• pay the supported amount;
• pay the undisputed amount and hold the disputed part if the contract allows it;
• hold the invoice pending named evidence or correction;
• reject the invoice with contractual reasons and the required next step.

European Commission procurement guidance says progress reports may accompany invoices and describe completed work, delivered items, issues and delays to justify payment source.

The Commission guidance concerns its own procurement contracts, but it supports the same distinction: a progress narrative should identify what was delivered and what went wrong, not merely accompany an invoice with marketing metrics.

Worked example

An early-stage software founder receives an invoice for a batch of one hundred leads. The signed schedule says that a billable lead must match the target account criteria, hold a relevant role, show a reproducible current source, contain the required handoff fields, fall outside the duplicate window and carry no known objection. The supplier transfers a spreadsheet and a dashboard image.

The buyer freezes the spreadsheet, records its checksum and selects every disputed record plus a random slice. During replay, several records match the account but not the role, some source links no longer support the stated function and one known objection is absent from the transfer. The supplier's dashboard counted all delivered rows. The buyer's receiving record counts only units that pass the signed definition.

The supplier corrects missing notes and replaces two rejected records. The review keeps the original defects and links the replacements. The buyer also tests the export and finds that source dates and suppression status are present, while correction history is missing. The disputed amount remains on hold until the corrected export passes.

The founder does not infer future pipeline or revenue from the accepted units. The decision is simply that the supported portion of this invoice matches the contract. The sample result remains a quality observation for this batch, not a performance guarantee.

Common mistakes

Paying from the row count. Delivered rows are not automatically accepted leads. Reconcile each charged category with the contractual definition.

Letting the supplier curate the replay. A polished demonstration tests presentation skill. The buyer must freeze the batch and choose the records.

Changing the denominator after review. Duplicates, unknowns and corrected records remain visible. Excluding them can make the batch look better without changing what was delivered.

Allowing replacement to erase defects. A replacement may repair inventory, but the original defect still informs quality, remedies and repeated-failure clauses.

Accepting a source name without a chain. The reviewer needs the record, source, date, permitted purpose and transfer path required by the contract.

Treating payment as a revenue verdict. A lead can meet the definition and never convert. Invoice acceptance proves contractual receipt, not commercial success.

Reopening the whole supplier decision. If a new critical risk appears, escalate it. Otherwise, keep this control focused on the current invoice instead of duplicating preselection or final contract diligence.

Use the weekly outbound review after accepted units enter the sales workflow. Do not use downstream activity to retroactively change the invoice definition.

Tools

A small founder needs a controlled folder and a review sheet, not a large procurement platform. The folder holds the contract schedule, invoice, original delivery, checksum, supplier evidence, replay log, correction log, export test and signed payment decision. The sheet calculates submitted, accepted, rejected, duplicate, unknown, corrected, replaced and disputed units without deleting any state.

Use read-only source capture for the replay and keep access limited to the people who need it. Separate supplier evidence from buyer findings. Name each version and record who changed it. If the pack contains personal data, apply the agreed access, retention and deletion rules.

Lead Intelligence prioritises opportunities from the available context source.

Lead Intelligence monitors signals about people and companies to keep context current source.

Lead Intelligence proposes the next action and channel that fit the lead situation source.

These capabilities can support the sales workflow after accepted data enters the buyer's context. They do not approve an invoice. The payment decision remains a human reconciliation of contract, delivery, evidence and control.

When to use this method

Use the proof pack before releasing a first batch payment, a recurring invoice based on delivered leads, a milestone tied to a transferred dataset or a final payment that closes the relationship. It is most useful when quality, provenance and transfer determine whether a unit is billable.

Run the replay more deeply on the first invoice and after a change in source, method, subprocessor, definition, export or pricing. On stable recurring batches, preserve the same fields and decision trail while adapting sample depth to known risk and review capacity.

The method is also useful when the founder expects to dispute only part of an invoice. A record-level pack lets both parties isolate supported and unsupported amounts without turning every defect into a dispute over the whole relationship.

When not to use it

Do not use this method to shortlist suppliers. The buyer has not yet reached an invoice at that stage. Do not use it to replace final contract due diligence, negotiate data roles or invent a lead definition after delivery.

It is not a revenue attribution model. If the contract bills advisory time, campaign capacity or a fixed milestone rather than leads, adapt the receiving evidence to that unit instead of forcing a per-lead calculation.

Do not use a sample replay as authority to contact people. Any live outreach must follow the buyer's approved purpose, channel rules, notices, objections and limits. Stop and seek specialist advice when the contract, jurisdiction or rights evidence is unclear.

Action plan

Before the due date: request the invoice pack using a fixed checklist. Reject missing batch identifiers, contract references or transfer files early enough for correction.

After receipt: freeze the original delivery, record the checksum and copy the signed lead definition into the review sheet.

During review: reconcile invoice lines, select the sample, replay the evidence and record every verdict. Escalate provenance, objection or rights failures immediately.

Before approval: verify corrections, test required export fields, check the exit evidence when applicable and calculate the supported and disputed amounts.

At decision: sign one release record with pay, partial payment if contractually permitted, hold or reject. State the evidence and next step. Do not write a vague approval email.

After decision: archive the pack under the invoice identifier. Move accepted units into the sales workflow and retain rejected or disputed units only as the contract and applicable rules permit. Feed recurring defects into the next supplier review without changing the historical batch.

If accepted leads require prioritisation, use the lead-scoring guide after payment acceptance. Qualification for billing and commercial priority are separate decisions.

Ember data

Observation: this repair retained 10 source pages across 8 domains on 3 August 2026 source source source source source source source source source source.

Sample: the URLs attached to this repaired article.

Period: source review completed on the date stated in the observation.

Method: deterministic count of retained pages and unique host names after removing the www prefix.

Limitation: this measures source diversity. It does not measure supplier performance, batch accuracy, conversion or revenue.

Sources and methodology

The invoice and receiving-record analogy comes from the current U.S. Federal Acquisition Regulation source and European Commission procurement guidance source. These public-sector rules do not govern every private purchase. They are cited as auditable examples of separating authorization, delivery, acceptance and payment.

Data provenance and processor responsibilities use current CNIL and European Commission guidance source source. U.S. commercial-email responsibility uses the FTC guide source. Legal application depends on the real parties, countries, sources and channels.

The historical research dossier is preserved: ZoomInfo maps current lead-provider categories source; Bessemer discusses founder-led demand development source; Danish Lead Co. provides a startup outbound field guide source. They supply market context, not proof that any vendor will produce revenue.

The three descriptions in the Tools section are quoted from the attached official product context. The minimum pack, replay procedure, worked example and payment decisions are editorial recommendations. Sources were reviewed on 3 August 2026.