Advertising delivery reconciliation records across systems: a map of where each record lives and the keys that join them

Short answer

Reconstructing one reconciliation means joining six places: the order system's insertion order and placement list, the ad server's line item and delivery, third-party verification counts, the finance adjustment log, billing's invoice or credit memo, and the email in which the advertiser accepted the remedy. Each hop needs a shared key: order ID, line item ID, placement or ad unit ID, the remedy line's pointer to the line it repaired, and the invoice line. Where a key was typed by hand or never stored, the chain breaks.

Visual briefFull-size diagram
Six nodes, order system, ad server, verification, makegood line, finance and billing, and mailboxes, joined by order ID, date and time zone, and line item ID, with two weak dashed keys: the original line ID typed on the makegood and the IO number in an email subject.
Illustrative system map. Key names vary by ad server and order system; the company's administrators confirm which ones exist.

This map is part of the advertising delivery reconciliation hub. The worked exception follows one case through its decisions; this page shows the plumbing underneath: which system holds which record and how they connect.

System, record, linking key and owner

SystemRecord it holdsLinking keyUsual owner
Order management systemSigned insertion order, placement list, run dates, rateOrder ID and line referenceSales operations
Ad serverLine items, targeting, delivery reports, remedy linesLine item ID, carrying the order ID; placement or ad unit IDAd operations
Verification and third-party reportsIndependent counts and the removals they justifyCampaign or line name, date range and time zoneAd operations
Finance adjustment logCorrected totals, each removal with a reason, the settled figureLine item ID or order ID plus reason codeBilling or revenue accounting
Billing systemInvoice lines, credit memosInvoice line referencing order IDFinance
Account managers' mailboxesAgency acceptance of a makegood or creditOrder number in the subject or body, if anyone typed itCommercial team

Read the table as a chain from top to bottom. The strong keys (order ID, line item ID) are system-generated. The weak ones (names, email subjects) depend on habit.

One fully joined case

Illustrative and fictional. A 340-person business-to-business trade media company runs a sponsorship campaign for an industrial equipment maker. Here is the chain as it would look if every key held:

HopFromToKey that joins themStatus
1Insertion order IO-2219Ad server orderOrder number pushed by integrationJoined
2Ad server orderLine item for newsletter placementsOrder ID on the line itemJoined
3Line itemPlacement list in the signed orderAd unit ID, unchanged since signingJoined
4Line item deliveryVerification reportSame date range, time zone and line name recorded in the discrepancy logJoined
5DeliveryAdjustment log rowLine item ID plus reason "off-contract placement"Joined
6ShortfallMakegood line itemOriginal line ID in the makegood's notes fieldWeak: typed by hand
7MakegoodAgency acceptance emailIO-2219 in the email subjectWeak: depends on habit
8OrderInvoice lineOrder ID on the invoiceJoined

Six strong joins and two weak ones. That is a realistic, useful result: the weak hops are exactly where SourceX's review would test coverage, and where the company's administrators should check how many years follow the same pattern.

Each hop, and where it breaks

Follow IO-2219 through the systems again, this time asking what would have broken the chain at each hop.

Hop 1, insertion order to ad server order. At the trade media company an integration pushes the IO number into the ad server, so the join holds. Many sales teams instead retype it into a free-text name. Inside the ad server itself the link is solid: in Google Ad Manager's API every line item has a required orderId field naming its parent order. The fragile part is the step before, between the sales system's numbering and the ad server's.

Hops 2 and 3, line item to the newsletter placements that were sold. The ad server records where the sponsorship actually ran; the signed order records where it was allowed to run. The ad unit ID ties the two together, which works only while the unit keeps its ID. If the newsletter section was renamed or split after signing, someone needs a mapping from old unit to new.

Hop 4, delivery to the equipment maker's own counts. The two never agree to the impression. Google's help on investigating discrepancies asks for the same date range, time zone and line items on both sides, and for discrepancy tolerances agreed with the buyer upfront. A discrepancy log that wrote those settings down is what lets someone redo the comparison.

Hop 5, delivery to the adjustment row. The finance row keys the removal to the line item ID and the reason "off-contract placement". Ask also which count the row started from: Google's Open Bidding help prefers Billed impressions for reconciliation because the billing ping fires before invalid-traffic and discrepancy deductions.

Hop 6, shortfall to the makegood line. Here the trade media company is weak: the original line ID sits in a notes field someone typed. A formal Ad Manager makegood would hold it as data, since the makegood proposal line item stores the original line item's ID and a reason such as underdelivery, but formal makegoods exist for Programmatic Guaranteed deals, keep the original CPM and quantity limits, and need the buyer's acceptance. Direct-sold sponsorships rarely use them.

Hops 7 and 8, acceptance and invoice. The invoice line carries the order ID, so finance closes cleanly. The agency's acceptance is found only because an account manager habitually put IO-2219 in the subject line. Without that email the makegood reads as unexplained free inventory.

Coverage questions for the ad operations director

Ask about keys and years, never contents:

  • For how many years of closed campaigns do order IDs appear on ad server line items?
  • Were placements renamed during that period, and was a mapping kept?
  • Does the adjustment log key each removal to a line item and a reason?
  • How were makegoods booked, and do they reference the original line?
  • Which mailboxes hold agency acceptances, and what happens to them when staff leave?
  • Can the current ad server still export closed line items with their IDs intact? Export capability varies by system and contract, so the company confirms this with its administrators.

How diligence teams test revenue adjustments, which uses the same joins, is covered in MCP for quality of earnings and MCP for general ledger reconciliation. The wider data category is described on the reconciliation exceptions data page.

What the map tells a partner about fit

Records: closed campaigns where at least the order-to-line-item and line-item-to-invoice joins hold. Ownership: the publisher's own operating records, subject to rights review of advertiser terms. Authority: a named executive, usually not the ad operations director. The company baseline: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Unknown until SourceX reviews it: buyer interest, the rights result, de-identification and any offer. To hand the answers to a decision-maker, use the referral brief template.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the director confirms that most hops join for several years of closed campaigns, register as a partner, check the company against who qualifies and read the program terms before introducing the executive who can approve.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Which join breaks most often?

Placement terms to delivery, when placements are renamed between the signed order and trafficking. The second most common is a makegood booked as a new line with no reference back to the original.

Do all ad servers store an original line item ID on makegoods?

No. In Google Ad Manager the formal makegood for Programmatic Guaranteed deals carries one, but makegoods booked as ordinary line items may not. The company's administrators should check how their team worked.

Is a partner expected to test these joins?

No. The partner asks whether the keys exist and how many years they cover. Testing is the company's job, and only if it decides to go further.

Sources

  1. developers.google.com/ad-manager/api/reference/v202508/LineItemSer…
  2. developers.google.com/ad-manager/api/reference/v202502/ProposalLin…
  3. support.google.com/admanager/answer/9659935
  4. support.google.com/admanager/answer/6160380
  5. support.google.com/authorizedbuyers/answer/13531755
  6. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment