NETWORK BROADCAST FUNDAMENTALS

From feed handoff to invoice & payment

A readable map of who accepts the output and who approves the bill.

What the network delivers, and what the affiliate transmits

For this fictional Eastern feed, 8 p.m. America/New_York on November 2, 2026 is 01:00 UTC on November 3. The network sends the approved program feed to authorized affiliates. Local master control confirms reception, handles local avails and transmits its station output. Different regional feeds and time zones need separate schedules and tune-in checks.

The receiving-system checklist includes batch/revision, primary and secondary record counts, media IDs, durations, feed identity, local-avail cues, rights, fallback instructions and rejection recovery. A sent file is not an accepted import; a network as-run is not evidence of every affiliate’s transmission.

Secondary events are attached to a primary event

Record the parent reconciliation key, offset, duration, asset/command and target feed. The example uses a logo at +5 seconds into segment 1 and a tune-in graphic at +10 seconds into segment 5, each lasting ten seconds. Both fit inside their parents and add no primary clock frames. The teaching sidecar is not an executable automation file.

Two failures need separate decisions

Issue	Evidence to review	Example remedy
Wrong or missed commercial	Automation output, copy mapping, aircheck, relevant carriage evidence	Buyer-approved replacement or agreed credit
Audience below guarantee	Accepted posting report on the agreed basis	Approved audience-deficiency inventory or other agreed settlement

The commercial could air correctly but deliver too little audience. Or the clock could balance while the wrong creative plays. Preserve both the transmission decision and the audience decision.

Billing, invoicing and cash application

Billing review: match eligible units, accepted rate, buyer, billing party and documented amendments.
Invoice: issue the itemized amount under the agreement and retain its supporting delivery records.
Dispute or credit: hold or adjust the affected amount according to the approved remedy. Preserve the audit trail.
Receivable: track the invoice balance and due date.
Payment: apply the remittance to the correct invoice; investigate short payments instead of marking an unpaid balance settled.

Example state	Eligible amount	Treatment
All four original units accepted	$40,000 net	Audience ADU adds $0
One wrong-copy unit unresolved	$30,000 eligible + $10,000 held	Draft review; unresolved delivery
Linked replacement accepted	$40,000 total	Original unit billed once; no fifth paid unit
Simulated payment	$40,000 received and applied	Invoice receivable becomes zero

The exercise assumes net-30 payment and an eventual full remittance. It does not perform accounting or invoice a real client. An audience makegood need not delay invoicing in every contract; follow the accepted terms.

A canceled show still leaves records to finish

In this scenario management cancels the series after reviewing audience, economics and cost. Teams must revise future promos, graphics, schedules, orders and feed notices. Outstanding delivery remedies and payment obligations continue through their agreed resolution.

Return to the billing chapter →

Sources & scope

Sources checked October 22, 2026. Vendor materials describe their own systems. Published contract examples are illustrative, dated and not universal terms. All Harbor Street records and policies are fictional.