Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2026-03-13
Setup Considerations: SAF-T

Setup Considerations: SAF-T

You can use this topic to help make decisions when planning your configuration and use of the Standard Audit File for Tax (SAF-T) functionality. It explains:
  • Why to set it up.
  • How it fits into the rest of Workday.
  • Downstream impacts and cross-product interactions.
  • Security requirements and business process configurations.
  • Questions and limitations to consider before implementation.
Refer to detailed task instructions for full configuration details.

What It Is

Workday enables you to create an integration that generates a SAF-T XML file to submit to auditors or tax authorities.

Business Benefits

The Workday SAF-T functionality helps you to:
  • Create SAF-T quickly without manually processing the data.
  • Comply with tax auditing requirements.

Use Cases

Security administrators can:
  • Configure integrations to create SAF-T for Norway.
  • Assign security to enable users to launch SAF-T integrations.
Integration consultants can:
  • Configure integrations to create SAF-T using the OECD SAF-T v2.0 schema.
  • Add or disable fields within the structure of OECD SAF-T v2.0, override field mappings, and set maximum lengths for fields.
  • Configure custom integrations to transform the output for schemas that have a different structure than OECD SAF-T v2.0.
Tax managers or accounting managers can:
  • Create tax master records to populate the
    TaxTable
     element in SAF-T.
  • Map ledger accounts to the standard account IDs required for Norway.
  • Create SAF-T to submit to tax authorities.

Questions to Consider

Questions
Considerations
Which users do you want to create SAF-T?
Consider that users who can create SAF-T can view sensitive information about:
  • Bank accounts.
  • Customers.
  • Ledger accounts.
  • Payments.
  • Suppliers.
  • Transaction taxes.
Users can view this information even when they don't have access to the relevant domains.
Which SAF-T schema do you plan to use?
These integration templates for Norway produce output files:
  • SAF-T Norway 1.1
    , based on the Norwegian SAF-T financial schema v1.10.
  • SAF-T Norway 1.3
    , based on the Norwegian SAF-T financial schema v1.30.
You can configure a document retrieval step to use a newer version of the schema.
The
SAF-T Core
 integration template produces an output file based on the OECD SAF-T v2.0 schema, including a subset of the optional fields. You can configure field overrides to include optional fields that Workday doesn't populate by default.
When your country uses a schema that:
  • Uses the OECD SAF-T v2.0 structure but changes fields, you can use the
    SAF-T Core
     integration template and configure a document retrieval step to provide your schema.
  • Changes the OECD SAF-T v2.0 structure, you can use the
    SAF-T Core
     integration template and then use the output file as a data source for a custom integration to transform the structure and add fields as required.
What transaction data does the tax authority require you to include in SAF-T?
With the
SAF-T Core
 integration template, you can include approved accounts payable or accounts receivable transactions in the output.
Before you enable these integration services, consider how your schema differs from OECD SAF-T v2.0, as you might need to configure your integration to support those differences. Example: To include canceled invoices in the output, as Workday doesn't include these by default.
How do the fields and structure of your schema differ from the OECD SAF-T v2.0 schema?
When your schema:
  • Adds fields to the
    TaxTable
     element, you can configure the fields on the tax master template for a country. Workday populates this element using tax master records that you create when you set up the SAF-T functionality.
  • Changes fields in other elements but follows the same structure as OECD SAF-T v2.0, you can configure field overrides and extensions on your integration.
  • Adds fields outside the designated extension points, you can configure a custom integration to transform the output file as required.
(Norway only)
Which set of standard account IDs do you plan to use?
Your choice determines the number of ledger account summaries required to map your ledger accounts to the Norwegian standard account IDs. The 2-digit set requires less setup but the 4-digit set enables more granular reporting.

Recommendations

When you:
  • Create ledger account summaries for Norway, include the corresponding standard account ID in the name to make each summary easy to identify.
  • Set up a tax master template, enter default values to save time when you populate the tax master records.
  • Configure field overrides or extensions, use calculated fields to populate static values or enumerations. Calculated fields are the easiest way to populate these values.

Requirements

When you plan to provide your own schema, ensure that the schema is available for integration document retrieval using a supported transport protocol.

Limitations

On the
SAF-T Core
 integration template, Workday supports a subset of the optional fields in the OECD SAF-T v2.0 schema.

Tenant Setup

No impact.

Security

The SAF-T output contains sensitive financial data and is unencrypted, as required by tax authorities.
Domains
Considerations
In the Integration functional area:
  • Integration Build
  • Integration Configure
  • Integration Event
Enable users to configure and run integrations using SAF-T templates.
Manage: SAF-T Norway 1.3 Integration Event Document Security
 subdomain to the
Process: Financials Integration Event Document Security domain
 in the Common Financial Management functional area
Enables users to view attached documents generated by the SAF-T Norway 3 integration.
Process: Audits and Corrections
 in the Financial Accounting functional area
Enables users to assign journal line numbers to posted journals.
Process: Tax Master
 in the Common Financial Management functional area
Enables users to maintain tax master data and view related reporting.
Set Up: Accounts
 in the Common Financial Management functional area
Enables users to configure ledger account summaries. Required to configure SAF-T for Norway only.
Set Up: Company Accounting
 in the Common Financial Management functional area
Set Up: Payroll - Company Specific (Accounting)
 in the Core Payroll functional area
Enable users to configure company accounting settings to meet SAF-T requirements. Ensure that users who set up the SAF-T functionality have access to 1 of these domains.
Set Up: Tax
 in the Common Financial Management functional area
Enables users to view and modify information relevant to tax auditing.

Business Processes

No impact.

Reporting

You can use the
Tax Masters
 report data source to create custom reports.

Integrations

Integration Templates
Considerations
SAF-T Core
Enables you to create SAF-T using the OECD SAF-T v2.0 schema.
SAF-T Norway 1.1
Enables you to create SAF-T using the Norwegian SAF-T v1.10 schema.
SAF-T Norway 1.3
Enables you to create SAF-T using the Norwegian SAF-T v1.30 schema.

Connections and Touchpoints

Features
Considerations
Banking and Settlement
Customer Accounts
Person
Supplier Accounts
Transaction Taxes
Worktags
You can use the SAF-T functionality to extract tax-relevant data from these areas to submit to tax authorities.
Financial Accounting
You can use the SAF-T functionality to extract data relating to:
  • Companies.
  • Journals.
  • Ledger accounts.
Workday offers a Touchpoints Kit with resources to help you understand configuration relationships in your tenant. Learn more about the Workday Touchpoints Kit on Workday Community.