vendor bill
Google Cloud partnership for AI data and agentic capabilities (vendor bill)
Not sized
The Q2 call, release and 10-Q do not mention the Google Cloud partnership or AI. The partnership was announced in April 2026 and may have been in force for part or all of the quarter, but no start date, amount, price or scope has been given and the IT investments the 10-Q names have no amount, so no decomposition rests on anything Merck has said.
inscrutabledisclosure: not mentioned· motive: exploratory· before LLMs: expanded
Q2 is silent on the partnership and on AI. Selling, general and administrative expenses rose by , or , to ; the 10-Q names investments in IT within higher administrative costs for the first time in coverage (claim c1), without saying AI. That is consistent with spending on the partnership and equally with any other IT work, so it is recorded as a metric and not as a bridge.
Evidence: 0 quotes, 3 figures, 2 confounds, 2 from before coverage
What the company pays Google Cloud under the multi-year partnership the CEO announced in the week before the Q1 2026 call, to scale advanced AI data and agentic capabilities across the company; the Q1 release lists it as a partnership to accelerate agentic AI enterprise transformation. No amount, price, scope or start date is given, and no filing names Google Cloud or any AI vendor bill. The CEO names it beside an expanded collaboration with Tempus AI and an agreement with Mayo Clinic for clinical insights and genomic data; those two are not registered as channels, because no source states a flow for either (who pays whom, or whether it is a data licence, a research collaboration or cost-sharing) and the stated aim (greater speed and a higher likelihood of reaching patients in the pipeline) has no measure. Research and development spend is not AI spend, and nothing in this channel is taken from the research and development line. Google Cloud is Alphabet's (GOOGL on this ledger); what Merck pays may be part of GOOGL's Google Cloud AI solutions revenue, which is compute layer there and end-use here. The ledger records each company's own flows and does not net them.
Why this motive
Exploratory, carried from Q1; silence is not evidence about motive.
Before LLMs: expanded
At the anchor the FY2024 10-K already said the company was increasing its use of AI systems to automate processes, analyze data and support decision-making (claim mrk-anchor-c1) and depended on cloud service providers among its IT systems (claim mrk-anchor-c2), with no amount and no AI vendor named; no IT line is reported, and selling, general and administrative expenses, the line the Q2 2026 10-Q names for investments in IT, were for FY2024. The Q1 2024 call carried no AI passage. No earlier AI vendor spend is traced, so the level has no baseline. The size is the whole of an activity that existed before.
“The Company’s growing use of artificial intelligence (AI) systems to automate processes, analyze data, and support decision-making poses inherent risks.”
“The Company is increasingly dependent on sophisticated software applications, complex information technology systems, computing infrastructure, and cloud service providers (collectively, IT systems) to conduct critical operations and financial reporting.”
Figures
- Selling, general and administrative · 2026-CQ2
- Change in selling, general and administrative on the prior-year quarter · 2026-CQ2
- Selling, general and administrative growth on the prior-year quarter · 2026-CQ2
What else could explain it
- line composition: The 10-Q names investments in IT among higher administrative costs in SG&A, beside launch promotion, selling costs and foreign exchange (claim c1), with no amount and no AI or Google Cloud named; IT spending of any kind would sit there, so the line movement of cannot be read as this channel.
- transformation program: The multi-year optimization effort, credited by the CFO with offsetting operating expense growth (claim c2), and the 2025 Restructuring Program, expected to save a year, are not attributed to AI.
By quarter
- Q1 2026described · described, no size · exploratory
- Q2 2026not mentioned · inscrutable · exploratory