AEM Forms brings regulated correspondence into the cloud – and the account statement becomes a CX channel

Unpopular opinion: your bank’s best marketing channel isn’t email. It’s not the website either. It’s the account statement. Marketing emails get opened by maybe one in five customers – statements, policy letters and benefit notices are read by nearly everyone, line by line. These documents shape how trustworthy a company feels. And in most banks and insurers they are built far away from the marketing team: on a Windows-only desktop tool, owned by IT or operations, last redesigned years ago. That just changed.

What shipped, exactly

• June 2026 release (2026.6.0, June 25), now GA: Adobe moved Interactive Communications into AEM Forms as a Cloud Service. Customer correspondence – statements, bills, policy documents, welcome kits – is now authored in the browser, on the same cloud platform as website and campaigns.
• Previously: Interactive Communications existed in AEM 6.5 Forms, but authoring required the Windows-only Desktop Designer. The Cloud Service editor runs fully in the browser, including XDP file editing.

The architecture behind it

Data binding runs via Form Data Models (FDM): a visual mapping of document components to the data source, so statements render per customer. Template locking is the governance control – layout and fragments like headers, footers and legal disclaimers are locked at template level, and authors can only edit what governance allows. That is MRM/compliance control built into the authoring layer rather than bolted on as a review step.

Around it: versioning, annotation-based review and side-by-side PDF version compare give correspondence changes an audit trail. And the Associate UI provides a runtime interface on publish instances where front-line staff enter data and generate personalized documents in real time – no developer needed.

Why this matters for the operating model

When a CMO maps customer touchpoints, correspondence is usually missing from the slide. When a COO budgets document operations, marketing is never in the room. This release puts both at the same table: the most-read documents a company sends become part of the customer experience stack – with the same personalization data, the same content governance and the same cloud platform as every other channel.

Questions to settle

1. Who owns the account statement in your company – marketing, operations, or IT?
2. Which correspondence templates carry compliance-approved fragments that must be locked – and who approves changes to them?
3. Where does correspondence data come from today, and can the Form Data Model bind to it directly?
4. Does the front line need real-time document generation (Associate UI), or is batch enough?

The channel everyone reads was the channel nobody designed. That excuse is gone.

Frequently asked questions

What changed with Interactive Communications in AEM Forms?

With the June 2026 release (2026.6.0, 25 June), now generally available, Adobe moved Interactive Communications into AEM Forms as a Cloud Service. Customer correspondence – statements, bills, policy documents and welcome kits – is now authored in the browser, on the same cloud platform as website and campaigns. Previously, authoring required the Windows-only Desktop Designer.

How is compliance controlled when correspondence is authored in the cloud?

Through template locking. Layout and fragments such as headers, footers and legal disclaimers are locked at template level, and authors can only edit what governance allows. Versioning, annotation-based review and side-by-side PDF version compare give every correspondence change an audit trail, so the control sits in the authoring layer rather than being bolted on as a review step.

What is a Form Data Model in AEM Forms?

A Form Data Model is a visual mapping of document components to the data source, so that a statement renders per customer. It decides whether correspondence can bind directly to the data you already hold – which is the first question to settle before moving a template into the cloud.

Sources: AEM as a Cloud Service release notes (2026.6.0) and Interactive Communications documentation on Adobe Experience League. Adobe and Adobe Experience Manager are trademarks of Adobe Inc. This is an independent analysis; no partnership with or endorsement by Adobe. First published as part of my LinkedIn series, August 2026.