SAP release: 15–16 August 2026 production rollout window for D/P tenants
SAP Cloud ERP Public Edition 2608 brings Hungary’s eVAT machine-to-machine reporting workflow into the production release. SAP documents a Hungary-specific statutory report that generates VAT analytics and a VAT Return XML, supports verification, and submits the return electronically to the Hungarian National Tax and Customs Administration, NAV, through the Run Statutory Reports app.
The release changes the implementation baseline for Public Edition customers, but availability is not the same as readiness. SAP’s schedule identifies 15–16 August 2026 as the D/P tenant rollout window with HFC03+. Each customer should still record the actual software level and hotfix collection in its own tenant before treating the capability as available.
NAV production already requires XSD 2.0
SAP’s 2608 feature became available after the authority cutover had already occurred. NAV production has accepted only eÁFA M2M XSD 2.0 since 3 August 2026; the test environment has been 2.0-only since 1 July, and NAV does not provide version 1.0 coexistence.
Implementation evidence: capture a real XML generated by the customer tenant, record its namespace and payload fingerprint, validate it against NAV’s official 2.0 package, submit through the intended environment and reconcile the accepted values to the source statutory-report run.
The feature name or successful tenant upgrade does not establish payload compatibility. A 1.0 payload is not a rollback path. Official NAV production notice · Regression procedure
What SAP delivered in release 2608
SAP’s official 2608 feature record identifies the following technical objects:
| Technical element | SAP-documented value |
|---|---|
| Product edition | SAP S/4HANA Cloud Public Edition 2608 |
| Feature type | New, localized for Hungary, action/review required |
| Application | Run Statutory Reports |
| Application ID | F1515_HU |
| Report category | HU_VAT_DCL |
| Report definition | HU_EVAT_DCL_V0 |
| Scope item | 1J2, Compliance Formats – Support Preparation |
| Feature toggle | S4HC_GLO_TAX_HU_EVAT |
| Application component | FI-LOC-FI-HU |
| SAP Help valid as of | 15 July 2026 |
| Production rollout window | 15–16 August 2026 for D/P tenants |
The report is named VAT Analytics and Declaration with Machine to Machine Communication (eVAT M2M). The important architectural change is that generation, verification, and electronic submission sit within the statutory reporting process rather than being treated only as an outbound XML export.
Configuration is still required
SAP’s feature record marks both “Preparation Required” and “Feature Requires Latest Reference Content Version” as No. That metadata should not be read as “no implementation work.” SAP’s setup documentation still requires a defined reporting structure and tax configuration.
- Map SAP processes, tax codes, document types, and special G/L indicators to the authority’s standard tax boxes in configuration activity
107328. - Configure the reporting entity
HU_EVAT_EN, report categoryHU_VAT_DCL, and reporting activityHU_EVAT_DCL_V0_S. - Assign the relevant company code and maintain due dates, VAT identifiers, sender information, taxpayer status, and other reporting parameters.
- Complete the electronic communication setup for submission through SAP Document and Reporting Compliance, cloud edition.
- Verify the productive and test submission modes. SAP states that manual submission is not supported for this electronic report activity.
This distinction matters in project governance. The feature can be present in the release while the customer tenant remains unable to produce an accurate, traceable, and accepted return because mapping, authorizations, communication, or source data are incomplete.
Product-edition boundaries
The 2608 feature record is specifically for SAP Cloud ERP Public Edition. It must not be used as evidence that the same delivery is available in SAP ECC 6.0.
SAP separately documents eVAT electronic submission for SAP S/4HANA and SAP S/4HANA Cloud Private Edition at listed maintenance levels, including 2025 FPS01, 2023 SPS06, 2022 SPS08, and 2021 SPS10, with SAP Note 3697544. That is a separate product and delivery path. Neither SAP record establishes standard eVAT M2M availability for ECC 6.0.
Hungary eVAT M2M must also remain separate from Real-Time Invoice Reporting. RTIR and VAT return submission use related business data, but they have different reporting purposes, messages, lifecycle states, and evidence requirements.
Implementation and regression checklist
- Confirm the tenant baseline. Record the 2608 software level, hotfix collection, feature availability, and activated scope.
- Trace every reported field. Map the eVAT XML elements to the originating SAP documents, tax codes, tax bases, amounts, and master data.
- Control the schema. Retain the exact NAV XSD version and checksum used for every test cycle. Treat any schema update as a regression event.
- Separate validation layers. Preserve transport, authentication, XSD, and business-rule results independently. A successful connection does not prove that the return content is acceptable.
- Test corrections and repeat runs. Prove how rejected submissions, corrected source data, regeneration, and duplicate-prevention controls behave.
- Retain submission evidence. Store the payload fingerprint, timestamps, request or correlation identifiers, authority response, and final status available to the process.
- Reconcile the result. Trace the submitted population and authority outcome back to SAP. Assign owners to exclusions, unexplained differences, and unresolved errors.
S4FN analysis: the evidence standard for DRC Sprint
DRC Sprint should turn the release into a verified implementation baseline. The baseline should record the product edition, release and hotfix level, available report objects, configuration prerequisites, source-to-XML mapping, schema-controlled test results, communication evidence, and open blockers.
This separates three statements that are often confused: SAP has delivered the capability, the capability is configured in the customer tenant, and the customer’s end-to-end process has been proven against the applicable NAV requirements. Only the third statement demonstrates implementation readiness.