Skip to content
All field notes
Measurement
Published
Oct 28, 2026
Updated
Nov 3, 2026
Reading time
12 min read

Ad Invoice Reconciliation: Match Delivery and Track Credits

Match advertising invoice lines to orders and comparable delivery. Separate count gaps, billing calculations, accepted corrections and applied credits.

AP
AdProof Research
Independent measurement desk
Order, delivery, invoice and credit sheets are connected by matching lines, with one unresolved amber question mark.
A delivery difference, an invoice correction and an applied credit are separate records. Conceptual illustration without customer figures or a refund promise.
In this guide (9 sections)

To reconcile an advertising invoice, match each billed line to the applicable order version and comparable delivery, recalculate its charge under that agreed basis, and track any correction through acceptance and actual application. Keep the delivery difference, proposed monetary correction and completed financial adjustment in separate fields. A smaller measurement total does not automatically determine the amount payable.

For DV360, first map Media Cost, Total Media Cost, Billable Cost and configured Revenue using the applicable fee configuration and export units. A tracked service billed by another vendor, a platform-invoiced fee and a client markup belong to different commercial layers; their difference does not by itself establish a correction.

Start with one invoice and its service period. Build an exception worksheet that another person can reproduce, rather than a campaign-wide percentage with no connection to billed rows.

A public ad-operations discussion about manual invoice reconciliation asks how teams check delivery against invoices. The older August 2026 thread has an October follow-up asking what evidence governs settlement and whether corrections are tracked. That is a practical workflow question, not evidence of a universal discrepancy rate, a particular vendor's accuracy or money recovered.

Keep five decisions separate#

The worksheet should distinguish these stages:

StageQuestion to answerRecord to retain
Counted discrepancyDo comparable delivery sources disagree?Counts, event definitions, interval and export versions
Contractual billing basisWhich units, rate and adjustments apply to this line?Applicable order, amendments and agreed measurement provisions
Invoice calculationDoes the billed amount follow that basis?Quantity, rate, pricing unit, fees, currency and rounding
Accepted correctionWhat correction has the responsible party agreed to?Response, revised invoice or credit-document reference
Applied correctionWhere did that correction actually take effect?Allocation or payment record linked to the affected invoice

A detected count gap can remain technically unresolved. An arithmetically supported request can remain commercially disputed. A credit document can exist before it is allocated to the relevant balance. These are different open tasks.

Use the ad-server discrepancy guide to investigate why event totals differ. This guide begins with the finance team's next task: linking that finding to invoice rows and following the resulting correction.

For your campaign

Make the delivery comparison useful for reconciliation.

Match the billed line to the order and comparable delivery before discussing the difference.

Discuss measurement scope

A short inquiry to scope relevant measurement options; financial adjustments are not promised.

Freeze the order basis before calculating money#

Collect the insertion order or other applicable agreement, relevant amendments, invoice and supporting delivery exports. Record the exact version effective for the service being billed. If terms changed mid-flight, split the analysis at the change boundary rather than applying today's rate to every earlier event.

For each billed line, fill in:

  • Buyer and seller identifiers, order ID and placement or line-item ID.
  • Service start and end, reporting time zone and relevant cutoffs.
  • Pricing model: for example, CPM, CPC, fixed fee or another stated unit.
  • Rate, currency, rounding convention and separately billed fees.
  • Named counting source, billable event and required quality treatment.
  • Any applicable tolerance, cap, adjustment process and required supporting evidence.
  • The person responsible for resolving an ambiguous or missing provision.

Treat these as extraction fields, not instructions to rewrite the agreement. If a provision is unclear, mark the basis unresolved and ask the responsible commercial or legal owner to confirm it. Do not invent a standard tolerance or assume an independent verifier always takes precedence.

Version tracking matters even when people say “IAB terms.” IAB's May 2026 framework overview lists modular General Terms, a Direct Buy Addendum and order-specific terms. The existence of a published framework does not establish which documents the parties adopted, what they amended or which counting rule applies to this invoice.

Match identifiers before joining totals#

Create an explicit mapping between the buyer's order lines, the seller's invoice lines and the delivery system's IDs. Names help a reviewer recognize a row; stable IDs and effective dates should carry the match.

A useful local matching table looks like this:

Invoice keyOrder version and lineDelivery keyCovered intervalMatch result
Invoice ID + revision + rowOrder ID + amendment + placementPlatform + account/network + campaign/line IDStart, end and time zoneExact, approved allocation or unresolved

This is a proposed analytical schema, not an industry API payload. Preserve the original fields alongside your normalized keys so someone can trace the mapping back to the source.

Expect legitimate one-to-many relationships. One invoice row may cover several creatives or delivery line items. Aggregate those records to the invoice's agreed scope before joining the monetary amount. If you join the same invoice row to five creative rows and then sum the invoice amount, you have multiplied the charge rather than reconciled it.

The reverse also occurs: one delivery line can span two invoices or a rate amendment. Allocate events using the documented service boundaries and mapping. Do not copy its full monthly count into both invoices. Keep ambiguous allocations in an exception queue until the owner approves the mapping.

Add validation checks for duplicate invoice keys, missing order IDs, overlapping service periods and unmatched delivery rows. An unmatched row means “mapping incomplete,” not automatically “the placement never ran.”

Normalize the delivery evidence once#

The finance worksheet needs a defined quantity for each line, not every metric available in an export. Preserve gross counts, relevant exclusions and the resulting proposed billing quantity with their definitions. Distinguish invalid-traffic filtration, duplicate records and missing measurement coverage; they may overlap or require different treatment. For podcast inventory, reconcile download and ad-delivery evidence before choosing an invoice quantity; a downloaded episode, delivered ad and confirmed play are different observations.

Google's Data Transfer documentation gives a concrete reporting caution: event timestamps, file names and file arrival times can differ, while later traffic cleanup can make raw files differ from reports. Use the relevant event period and export version. Do not select an invoice month's events solely from similarly named download files.

If an exclusion waterfall is needed, use mutually exclusive buckets or preserve overlap explicitly. Never subtract a count already excluded by the selected net metric. A new “quality adjustment” column should not silently apply the same filter twice.

The anonymized fashion-retail duplicate-counting case illustrates why count-once adjustments and traffic-quality exclusions are separate contributions. It does not establish an invoice correction or financial saving. Its impression records also do not measure unique shoppers or repeated audience exposure.

For failed versus blocked verification fields, use the pre-bid and post-bid investigation. A block counter needs its actual definition and applicable commercial treatment before it enters invoice arithmetic.

Work the invoice line by line#

The following is a hypothetical worksheet, with invented identifiers and amounts. Assume a USD CPM order, a confirmed rate amendment applying throughout the service period, no taxes in this example, and a separate USD100 fee that is not being challenged. The delivery quantities support a review request; the seller has not yet accepted every requested adjustment.

LineInvoiced impressionsInvoice CPMInvoice amountReview quantityApplicable CPMReview amount
A800,000$4.00$3,200760,000$4.00$3,040
B300,000$6.00$1,800280,000$5.50$1,540
Media subtotal$5,000$4,580

For each line, CPM arithmetic is impressions / 1,000 × rate. Line A's proposed difference is $160. Line B's is $260, combining a quantity difference and use of the earlier rate.

Decompose line B in one consistent sequence:

Quantity component at the invoiced rate:
(300,000 - 280,000) / 1,000 × $6.00 = $120

Rate component on the remaining review quantity:
280,000 / 1,000 × ($6.00 - $5.50) = $140

Total proposed line B correction: $120 + $140 = $260

Applying the rate difference to all 300,000 invoiced units as well as the quantity calculation above would double-count part of the difference. Keep the calculation order explicit.

The proposed media correction is $160 + $260 = $420. Including the unchanged fee, the original pre-tax invoice is $5,100 and the review amount is $4,680. These are conditional calculations for the stated assumptions, not a determination of liability, an instruction to pay a particular balance or evidence that $420 has been recovered.

If actual taxes, currency conversion, minimum commitments, tiered prices or fee adjustments apply, give them separate rows with their stated calculation basis. Do not mix currencies into one variance total or assume every charge varies with impression volume.

Follow a partial correction through to application#

Continue the same hypothetical example. Suppose the partner accepts line A's $160 adjustment and line B's $140 rate adjustment, but disputes the $120 quantity component. A credit document for $300 is issued. Finance later verifies that $180 of that credit has been allocated to the relevant invoice balance.

Reconciliation stateAmountEvidence
Proposed correction$420Review worksheet and supporting basis
Accepted and documented correction$300Partner response and credit reference
Still disputed$120Unaccepted quantity component
Applied against the relevant balance$180Verified allocation record
Accepted but not yet applied$120$300 documented minus $180 applied

The two open $120 items are different: one needs a decision on the disputed quantity, the other needs completion of an accepted correction. Do not add the $300 credit document to the $180 application and report $480 recovered. They describe stages of the same correction.

A credit may be applied to a later invoice or another agreed balance. Retain that allocation reference rather than assuming it reduced the original invoice. If it is paid as cash, retain the corresponding payment evidence. A change to a payable balance and cash received should remain distinguishable in the report.

Store original and revised documents with their relationships. IAB's Invoice API specification, sections on invoice fields and line items, provides structured fields for invoice identity, service period, currency and line-item amounts; a credit tied to an existing invoice references that original. Confirm the receiving system's requirements. The worksheet here is a review model, not an implementation of that API.

Keep platform settlement workflows distinct#

First identify who issues the invoice and who processes the adjustment. Google's Ad Manager transaction guide distinguishes traditional deals, where the parties handle billing and reconciliation, from Programmatic Direct's platform-managed process. Do not route every transaction through the same seller-credit workflow.

For Programmatic Direct, Google's payment and reporting documentation also distinguishes reporting metrics and gross revenue from net payments. Choose the correct transaction scope before comparing a delivery export to a payment entry. A net remittance should not be compared directly with a gross line rate without its intervening adjustments.

Preserve platform-specific finalized records alongside the analytical worksheet. The existing discrepancy guide covers the separate Programmatic Guaranteed overdelivery rules and their timing; they should not be reproduced as a blanket deduction from every invoice.

For Amazon Sponsored Ads, reconcile the gross, invalid and remaining click populations before associating a report revision with an invoice correction.

Automate the repeatable checks, preserve human decisions#

Automate reliable identifier mapping, service-period checks, rate calculations, duplicate-invoice detection and required-field validation. Produce a row-level exception report with source references. Keep missing terms, uncertain allocations, conflicting measurement definitions and disputed corrections assigned to a person.

IAB's Digital Advertising Invoice API overview separates structured invoice exchange from supporting-document upload. That standardization can make inputs easier to validate. Successful delivery or structural acceptance of an invoice is not agreement that its commercial calculation is correct, nor proof that a credit was applied.

Before closing an exception, retain:

  1. Invoice row and original document reference.
  2. Order version, applicable rate and counting basis.
  3. Delivery mapping, interval, filters and export timestamp.
  4. Reproducible quantity and monetary calculation.
  5. Requested amount and partner's accepted or disputed portions.
  6. Correction document and actual allocation or payment reference.
  7. Remaining unresolved amount, next action and accountable owner.

Share only the authorized records needed for review. Keep customer identities, contracts, account access and unnecessary event-level identifiers out of public issue descriptions.

For supported campaign delivery, ask AdProof about a scoped reconciliation using campaign-event or aggregate exports with the agreed dates and metric definitions. Bring those records alongside your invoice mapping, then use the delivery-verification workflow. AdProof's measurement evidence can inform the review; the agreement owners and finance systems establish the applicable billing treatment and completed correction.

Frequently asked questions#

Which delivery report should decide the invoice?

Identify the counting source, event definition, quality treatment and dispute process in the applicable agreement. A lower count or an independent provider's label does not automatically take precedence. Mark an unclear basis unresolved for its responsible owner.

Is a discrepancy percentage the same as a credit amount?

No. Match the affected quantity to its pricing unit, rate version, service period and applicable adjustments. A fixed fee or unlike metric cannot be converted to a credit merely by multiplying the headline percentage.

Does an issued credit mean the correction is finished?

It documents a correction at one stage. Verify the amount and where it was actually allocated or paid. Keep accepted-but-unapplied amounts separate from portions that remain disputed.

Can invoice reconciliation be fully automated?

Stable matches, arithmetic and structural checks can be automated. Ambiguous agreements, missing mappings and contested evidence still need accountable review. A successful import is not proof of settlement or financial recovery.

Your next step

Make the delivery comparison useful for reconciliation.

Match the billed line to the order and comparable delivery before discussing the difference.

Discuss measurement scope

A short inquiry to scope relevant measurement options; financial adjustments are not promised.

Back to all field notes