It is a plan, not a shipped feature. Here is what is known, what isn't, and how finance teams in Austria should treat it.
What the roadmap entry says
The entry describes extending SAF-T audit-file generation to companies operating in Austria. It says the work reuses the existing SAF-T W1 implementation to cover country-specific compliance scenarios. The stated goals are:
- A standardized electronic audit file that can be shared with tax authorities and auditors when required.
- A more consistent audit-reporting approach for multinational organizations across supported countries.
The listed metadata:
| Field | Value |
|---|---|
| Product | Dynamics 365 Business Central |
| Platform | Web |
| Cloud instance | Worldwide (Standard Multi-Tenant) |
| Status | In development |
| Preview estimate | November 2026 |
| General availability estimate | April 2027 |
Microsoft states that roadmap dates are estimates and subject to change. Items are removed once they reach general availability or are cancelled or postponed. Plan around "April 2027" as a target, not a commitment.
What the entry leaves out
The roadmap text does not name any of the following:
- An Austrian tax-authority schema or file specification.
- Data fields, validation rules or the export workflow.
- Licensing or localization requirements.
- A minimum Business Central version.
- Any statement that the output will satisfy a particular Austrian legal obligation.
Its wording about benefits is marketing-level intent. It is not evidence of an Austrian mandate, and it does not promise that every country's SAF-T flavor is interchangeable. SAF-T is an OECD-derived framework, and national implementations differ (general industry knowledge). A shared engine does not mean a shared file.
Why "reuse SAF-T W1" matters
The reuse claim has a documented basis. Microsoft's Update 22.4 notes say SAF-T functionality was extracted to W1 and a generic audit file framework was added, delivered as the Audit File Export extension. That update text, from the 2023 wave 1 cycle, is the origin of the "W1" reference in the roadmap.
Microsoft Learn describes the extension this way:
- The framework is preinstalled but ships with no export format of its own.
- Customers install an app for a specific format, such as SAF-T, SIE (Sweden) or FEC (France), or partners develop a custom format.
- Documented export entries are typically general ledger or VAT entries, though other data is sometimes required.
So adding Austria looks like adding a country-specific layer to an existing extensible framework. It does not look like a new engine. That is a reasonable reading of the evidence, not a confirmed design.
The Austria documentation: a slipping target?
Microsoft's Austria local-functionality page has listed SAF-T under "Future legislation requirements being investigated" rather than among features marked "Available Now". One version of that page, retrieved in a web search, named "SAF-T reporting in Austria 2024 release wave 2" in that category. The briefing for this story says the current page was updated October 8, 2026, and refers to "2026 release wave 2". I could not open the current page directly, so treat the newer wording as unverified.
If both versions are accurate, the target moved from 2024 to 2026 and now sits on a roadmap estimate of April 2027. That is a pattern worth noticing, but it is an inference and not a Microsoft statement. The sensible takeaway is to track the dates and not to assume them.
How the generic export works today
None of the following is Austria-specific. It is the documented generic framework, and the Austrian format may add its own fields and requirements. It still shows what preparation looks like.
- Audit File Export Setup. Pick the default export format code. Only formats enabled through Feature management, plus custom formats, appear in the list.
- Data quality checks. You can turn on checks for company information, customers, vendors, bank accounts, ZIP codes and addresses. A default ZIP code can be set for records that lack one.
- Audit File Export Format Setup. Set the default file name or template. Optionally archive exports as ZIP files.
- G/L Account Mapping. Create a mapping tied to a reporting period and export format. Map G/L accounts to standard account categories and numbers. Optionally include incoming balances for balance-sheet accounts instead of only the period's net change. Microsoft notes that many authority formats require a standard chart of accounts.
- Audit File Export Documents. Create a document, choose the format and mapping, and optionally split by month or day. You can add a header comment and a contact, and create multiple ZIP files if the installed format app supports it.
- Processing. Run in the current session or as parallel background jobs. Microsoft advises against exporting many entries in the current session because of possible performance problems. It recommends parallel processing outside working hours for large exports.
- Download. Use Download as File for the selected line.
Microsoft also notes that installing a format app will likely add fields and functions to the export tool. The Austrian app may therefore change this workflow.
Practical advice for Austrian finance and IT teams
- Don't count on the feature yet. The status is in development, and preview is only estimated for this month.
- Audit your data now. Missing postal codes, bad bank details and inconsistent addresses are the kind of problems the data-quality checks look for. Cleaning them up is useful whatever the final format requires.
- Review your chart of accounts. Check whether your accounts can be mapped to a standard chart. This is a general expectation of authority formats, not a confirmed Austrian rule.
- Test in a sandbox first. When preview arrives, check the output against the specification your tax adviser or auditor expects. The roadmap does not say that Business Central output will be accepted as is.
- Watch for the release notes. Business Central ships major versions in April and October. Version 29.0, the 2026 wave 2 release, is already out. The Austria SAF-T app's requirements, supported versions and documentation will matter more than the roadmap blurb.
- Multinational groups may benefit from a common tool across countries. Check country-specific differences before assuming one setup fits all.
Bottom line
This is a modest but real signal that Microsoft intends to ship a first-party SAF-T path for Austria on top of an existing framework. The estimates are preview in November 2026 and general availability in April 2027. Austria's own documentation has long filed SAF-T as a future requirement under investigation. Until the preview shows a concrete specification, treat it as a plan, and keep your auditors in the loop.