Enhance Electronic Reporting with new capabilities

Business value

You’ll see ongoing improvements to Electronic Reporting in the current and upcoming releases. These updates make it easier for you to adapt to changing regulations by boosting flexibility, simplifying maintenance, and enabling greater reuse across configurations. This means less time spent on manual adjustments and more confidence in staying compliant as requirements evolve.

Feature details

Electronic Reporting (ER) is the configurable engine you use to author and run business documents—invoices, statutory reports, VAT declarations and payment files, and more. In 10.0.48 and 10.0.49 Microsoft delivered a set of general enhancements that respond directly to the most highly voted ideas on the Microsoft Idea portal and to recurring partner/customer requests. The enhancements remove long-standing workarounds, expand what ER formats can express out of the box, and modernize commonly used destinations.

You can now:

• Send generated documents to silent (BCC) recipients straight from ER.
• Produce industry-standard GS1 barcodes directly in your ER labels.
• Write cleaner ER formulas using new integer-arithmetic functions.
• Print the exact number of copies you configured for ER-based documents.
• Run validation for multiple ER configurations at scale, with background execution and full traceability of validation results across configuration versions.
• Run ER with improved memory efficiency, enabling more reliable processing of large-volume reports and complex datasets.

New capabilities

Send blind copies (BCC) from ER Email destinations

With this release wave, the ER Email destination is extended with support for blind carbon copy (BCC) recipients. In previous versions, only To and Cc recipients could be configured, which limited the ability to distribute generated documents to compliance, audit, or archival mailboxes without disclosing those addresses to the primary recipients.

ER's Email destination now includes a Bcc field next to To and Cc.

• To enable, select Electronic reporting > Electronic reporting destination > File destination > Settings > Email.
• The Bcc field accepts the same kinds of values as To and Cc: static addresses, ER expressions, or values bound to the data model.

Business outcome: Confidential distribution of ER-generated documents to compliance, audit, and archival mailboxes is achieved entirely through configuration, eliminating the need for customization or post-processing.

Generate GS1 barcodes directly from ER

GS1 is the global standard for barcodes used in retail, warehousing, supply chain, transportation, and healthcare.

ER now generates GS1 barcodes natively, with three new formats available in the barcode data source:

• GS1-128
• GS1 DataMatrix
• GS1 QR Code

When you choose one of these formats, ER applies the correct GS1 encoding rules automatically. ER also warns you at design time when the configured barcode width is too small to scan reliably, so you catch problems before they reach the shop floor.

Business outcome: You can design GS1-compliant labels (warehouse, shipping, retail, healthcare) entirely inside ER, with no third-party barcode tools.

New ER formula functions: DIV and MOD

Integer division and remainder are common in reporting—for pagination, packaging quantities, currency splits, period bucketing, and check-digit calculations. Previously, ER report authors had to express these with combinations of ROUND, subtraction, and multiplication, which is verbose and easy to get wrong.

Two new functions are now part of the ER formula language:

• DIV(a, b) — integer division. Returns the integer (or Int64) quotient.
• MOD(a, b) — the remainder of integer division. Returns the integer (or Int64) remainder.

Business outcome: Cleaner, faster, and more readable ER formulas wherever whole-number arithmetic is needed.

ER destinations now apply the configured number of copies in Print management

When an ER-based document—for example, Container content—was configured in Print management with a number of copies greater than one, the printer still produced only a single copy. Warehouse, manufacturing, and logistics teams had to duplicate documents manually, slowing down pick, pack, and ship operations.

ER destinations now correctly print the Number of copies configured in Print management, as well as the number requested in ad-hoc print dialogs. This applies across the standard entry points for ER documents driven by Print management.

Business outcome: The number of copies you configure is the number of copies you get—faster throughput, and fewer process errors.

Optimize memory consumption for large Electronic Reporting (ER) executions

This feature enhances memory efficiency during Electronic Reporting execution by introducing targeted optimizations in the reporting engine. These improvements reduce peak memory consumption by minimizing unnecessary object creation, avoiding redundant data duplication in memory, and reusing existing data structures more effectively.

The optimization is broadly applicable across Electronic Reporting scenarios and is particularly beneficial for reports that process large volumes of data. Because the improvements are built into the engine, you benefit from them automatically, no configuration changes or report redesign are required.

Business outcome: Large ER reports run more reliably with reduced peak memory usage, lowering the risk of out-of-memory failures and helping high-volume reporting workloads complete consistently.

Enhanced validation management for Electronic Reporting configurations

This feature enables validation of multiple Electronic Reporting (ER) configuration versions in a single operation. When the feature is enabled, the Configuration repository page introduces a Validation experience that lets you:

• Select and validate multiple completed ER configurations at once, instead of validating one version at a time.
• Run validation as a batch job, so large validation workloads no longer block interactive sessions.
• Review validation results through a persistent Validation history, where results are retained for later review by configuration and version.

This feature also introduces version-level validation tracking. Both users and system processes can identify which configuration versions have already been validated in the current environment, which helps you avoid redundant validation runs and focus on versions that still need attention.

Business outcome: Configuration quality can be governed at scale—teams validate many configuration versions in a single batch operation and rely on a persistent history and version-level tracking to confirm what has already been validated, reducing manual effort and rework.

Availability

Geographic areas

Visit the Explore Feature Geography report for Microsoft Azure areas where this feature is planned or available.

Language availability

Visit the Explore Feature Language report for information on this feature's availability.