How do programmatic buyers get a verifiable record of what was agreed in a media deal?

Programmatic buyers get a verifiable record of what was agreed in a media deal through bilateral deal governance infrastructure that produces a signed record accessible to both buyer and publisher from a neutral source. Most current programmatic deal infrastructure does not provide this. What buyers have instead is their own platform's log of what it believes was agreed. Getting a genuinely verifiable record requires infrastructure where the record is committed at agreement, held by a neutral party, and accessible to both sides without the other party's cooperation.

Programmatic buyers get a verifiable record of what was agreed in a media deal when the deal is negotiated through infrastructure that commits the terms to a neutral, bilateral record at the moment of agreement. Most programmatic deal infrastructure does not work this way. The verifiable record most buyers actually have is their DSP's record of the deal, which represents what their DSP believes was agreed, as distinct from a record both parties can independently verify.

At a glance

Verifiable record: A deal record that can be confirmed as unchanged since commitment, because it is held by the neutral marketplace and any modification after commitment is logged.

Deal reconciliation: The process of comparing delivery data against the committed deal record at the end of a campaign period to confirm what was delivered matched what was agreed.

Bilateral access: Both the buying agent and publishing agent can query the same deal record from the neutral marketplace, ensuring both sides work from the same source of truth.

Delivery discrepancy: A difference between what the deal record says was committed (price, volume, publisher environment) and what delivery data shows was actually delivered.

What does "verifiable" require?

A verifiable deal record is one that both parties can confirm is accurate by retrieving it from the same source. Verification requires three conditions. The record must be from a neutral source: not the buyer's platform, not the publisher's platform, but an entity with no economic interest in either side of the deal. The record must be identical for both parties: the buyer and publisher retrieve the same document, not parallel versions that may or may not match. And the record must be immutable after both parties commit: it cannot have been modified since the deal was agreed.

A buyer who can retrieve their DSP's record of a deal does not have a verifiable record by this definition. What they have is evidence of what their DSP logged. If that record and the publisher's SSP record differ, neither is authoritative. Both are one party's account of the transaction.

Why is the current state inadequate?

The current state is inadequate because the dispute rate in programmatic deal programmes is significant. Billing discrepancies between what buyers expect to pay and what publishers expect to receive are routine. The IAB Tech Lab's 2024 programmatic audit found that the majority of direct deal campaigns included billing discrepancies that required manual resolution.

Manual resolution is manageable at human deal volumes. It is not manageable at agent deal volumes. A buying agent executing a high deal volume per week will generate discrepancy flags at a rate that cannot be handled by account team negotiation. The resolution mechanism must be automated, and automation requires a verifiable record that both sides agree is authoritative.

What infrastructure produces a genuinely verifiable record?

Genuinely verifiable deal records require a neutral marketplace that functions as a deal governance layer. The marketplace sits between buyer and publisher, receives the agreed terms from both sides, commits them to a record that neither controls, and provides both with access to the same document.

This infrastructure is distinct from deal management modules within DSPs or SSPs, which are useful for tracking deals within a platform but do not provide the neutrality condition for bilateral verifiability.

Alkimi's DealSheet is one live implementation of this infrastructure. Buyer and publisher agents negotiate through the platform. When both commit, the DealSheet is written to the marketplace: accessible to both sides from the same source, structured in a machine-readable format, and immutable after signing. Either party can retrieve the DealSheet independently to verify what was committed, without requiring the other party's cooperation.

What happens when buyer and publisher records differ?

When buyer and publisher records differ under current infrastructure, the resolution process is: each side produces their own documentation, account teams compare records, and a credit or adjustment is agreed through negotiation. The outcome has no relationship to what was actually agreed; it reflects the commercial dynamics of the relationship.

When a bilaterally verifiable record exists, the resolution process is different. The record settles the question of what was committed. What remains is the question of what was delivered. If delivery matched the committed terms, the deal is settled. If delivery diverged from the committed terms, the divergence is the basis for resolution, not competing accounts of what was agreed in the first place.

This shift from "what did we agree" to "what was delivered" is the practical value of verifiable deal records. It removes a category of dispute that is currently unresolvable through objective means.

Frequently asked questions

What is a deal sheet in programmatic advertising?

A deal sheet is a bilateral record of what both a buying agent and publishing agent committed to, held by the neutral marketplace and queryable by both parties throughout the campaign.

What is bilateral deal ownership?

Bilateral deal ownership means neither the buyer nor the publisher holds the authoritative deal record. Both access the same document from the marketplace, preventing unilateral modification and giving both sides the same reference point for disputes.

How does an agentic marketplace handle deal disputes between agents?

When a discrepancy is detected, the buying agent flags it against the deal record. The marketplace surfaces the committed terms and delivery data from both sides. If the data confirms a discrepancy, the dispute terms in the deal record specify the remedy and timeline.