Is your Dynamics 365 Finance build ready for Norway's SAF-T 1.40 and French e-reporting?
Norway won't accept old SAF-T files for 2027, and the Finance release that fixes it everywhere doesn't arrive until March. Here's the build you need now, what to import, and who should hold the keys.
part 12 of 12 · Running enterprise platforms wellthe ideaThe right build has to be in place before January. 10.0.51 doesn't arrive until March.
after reading, you can- Work out whether your Finance build can make a 1.40 file, and what to do if it can't
- Import the new configurations without losing the VAT mappings you already built
- Get Finance sending French e-reporting files itself, and keep the token out of shared documents
If you run Dynamics 365 Finance for a Norwegian or French company, your build number now matters to the tax office. Norway won't take anything but SAF-T FinancialdefinitionNorway's standard audit file. Finance exports your books in this layout, and you hand it over when the Tax Administration audits you. 1.40 for periods from January 2027, and France's e-reportingdefinitionFrance's rule for the sales e-invoicing doesn't cover, like sales to consumers and cross-border sales, plus some payments. You report them through an approved platform, period by period. is already running. Check the build and the ER configurations this month, while you've still got an update window before year end.
Your finance system has to speak the tax office's new dialect, and the old one stops counting in January
Dynamics 365 Finance keeps your company's books, and tax offices want copies in their own electronic formats. Norway's audit file is moving to a new version, SAF-T Financial 1.40, and from January 1, 2027 it's the only one they'll accept for new periods. France wants sales to consumers, cross-border sales and some payments reported through an approved platform, on a calendar that started last September. Microsoft has built both into Finance. You only get them if your system's on the right build and somebody imports the new report definitions, and that second part is easy to forget.
Think of a customs form that gets a new edition. The goods are the same and your records are the same, but the border post will only take the new form for anything shipped after a set date. Somebody in your office has to get the new forms and learn the boxes that changed before the first shipment goes out.
- Finance teams with a Norwegian legal entity
- Anyone selling into France from Finance
- Dynamics 365 Finance admins and partners
- Tax and audit leads
- Identity and security teams who own Key Vault
A file format nobody reads until an auditor asks for it
Norway doesn't ask you to file SAF-T every month. The Tax Administration says a company only has to hand the file over during an audit. That's exactly why it gets missed. Nobody runs the report until an auditor asks for 2027 data, and then the team finds out the format on the system is a version behind.
France is different because the reporting is routine. Each regular period gets its own transmission through an approved platformdefinitionA company the French tax authority has registered to carry e-invoices and e-reporting. Microsoft's integration talks to EDICOM, but you sign the contract yourself., and corrections go in as rectifying files. If Finance can't produce the right file, someone ends up assembling the data by hand for every period, and that's where errors creep in.
Neither deadline needs a big project, and both depend on a build number and a few configuration imports. The risk is calendar math. Microsoft's release schedule puts 10.0.50 at general availability on December 22, 2026, and 10.0.51 doesn't open for self-update until March. If you plan to pick up the Norwegian change with the next major release, you'll be late.
-
01 You post as usual
Your team posts invoices, payments and journals to the ledger exactly as before. Nobody on the finance floor sees a difference.
-
02 ER formats shape the data
Microsoft publishes Electronic reporting configurations that reshape ledger data into each country's layout. When the rules change, somebody has to import the new version, or nothing changes.
-
03 The build has to support it
Sometimes a new format needs new application code as well. For SAF-T 1.40 you need at least a listed build of 10.0.48, 10.0.49 or 10.0.50, or any build of 10.0.51.
-
04 The file goes out
Norway only sees your SAF-T file when an auditor asks for it, through Altinn. France gets e-reporting files every period, through an approved platform like EDICOM.
-
05 Wrong version, wrong answer
An old format or a missing build gives you a file the authority won't accept, usually at the worst moment.
For engineers: both changes run through the Electronic reportingdefinitionThe part of Finance that rearranges your ledger data into a government's layout. When the rules change, someone imports Microsoft's new version, or you keep sending the old one. framework. Norway uses the SAF-T Format (NO) export format. France uses Electronic messagesdefinitionWhere Finance builds tax files, sends them and keeps track of them. Each report is one message, so you can see which one failed. processing actions, with an optional web service channel to EDICOM. In both cases the version of the ER configuration matters as much as the application build, and importing one without the other gets you nowhere.
Norway: what changes in SAF-T Financial 1.40
Got a Norwegian legal entity in Finance? Here's what changes
SAF-T Format (NO) 221.208 with model mapping 221.176 produces 1.40 files. Import the model, mapping and format together from the Global repository.
The Report tax information in sales tax currency checkbox disappears for 1.40. Amounts go out in accounting currency, and Finance adds NOK amounts when that currency isn't NOK.
If you want 1.40 to show where imported goods shipped from, turn on Vendor ship-from address support on invoices. It's optional, so nobody will remind you.
Microsoft names a minimum build for 10.0.48, 10.0.49 and 10.0.50, and any 10.0.51 build works. 10.0.47 isn't there at all, so it can't make 1.40 files.
Skatteetaten still takes 1.20 and 1.30 for financial year 2026 and earlier. If an auditor asks for an old year, you'd run format 190.180 or earlier to get 1.30.
Moving from 1.30 to 1.40 doesn't need a new Feature management switch, only the optional ship-from feature.
The checkbox change is the one that'll surprise people. Companies that keep their books in euros or dollars and ticked Report tax information in sales tax currency got tax lines in the tax code's currency. With 1.40 that option is gone. Run a 1.40 file against a test period and compare the TaxInformation amounts with what your tax advisor expects before an auditor sees it.
The application-specific parameters catch people too. If you mapped your sales tax codes to Norwegian standard VAT codes through the ER format's lookup, that mapping sits on the old format version. Microsoft's instructions are to export it from the previous version, import it into the new one and set its state to Completed. Skip that and the report warns about missing mappings, which is easy to wave through on a busy day.
| Finance version | Minimum build for 1.40 | End of service | What we'd do |
|---|---|---|---|
| 10.0.47 | Not listed | Nov 20, 2026 | Move to a supported version now. It leaves service on November 20 |
| 10.0.48 | 10.0.2645.170 | Feb 16, 2027 | Take the quality update, but plan the next version too |
| 10.0.49 (major) | 10.0.2790.101 | May 21, 2027 | Check the build and import the configurations |
| 10.0.50 | 10.0.2919.15 | Aug 20, 2027 | Self-update opens Dec 22, 2026. Confirm the build you land on |
| 10.0.51 (major) | Any build | Nov 19, 2027 | Self-update opens Mar 12, 2027, which is after the deadline |
France: e-reporting, and whether to let Finance send it for you
France split its reform in two. E-invoicing covers domestic sales between VAT-registered companies, which go through an approved platform as structured invoices. E-reporting picks up whatever's left, like sales to consumers and cross-border sales, plus payment data where VAT is due on payment. Microsoft's feature pulls that out of Finance documents and builds the French files, so nobody has to rebuild them in a spreadsheet.
| Obligation | Large companies and ETI | SMEs and micro-businesses |
|---|---|---|
| Receive e-invoices | Sep 1, 2026 | Sep 1, 2026 |
| Issue e-invoices | Sep 1, 2026 | Sep 1, 2027 |
| E-reporting | Same calendar as issuing | Same calendar as issuing |
| New invoice mentions (customer SIREN, delivery address, type of operation, VAT on debits) | Sep 1, 2026 | Sep 1, 2027 |
Microsoft added e-reporting in 10.0.49, with builds for 10.0.47 and 10.0.48. The direct EDICOM channel arrived in builds of 10.0.47 to 10.0.49 and is described in the 10.0.50 notes. With it, you submit files from Finance through Electronic messages and pull the status back, so nobody downloads XML and uploads it to a portal. Microsoft lists it as available in the commercial cloud, and it's optional. You can still generate the file in Finance and send it some other way.
What you'll actually notice in French e-reporting today
Finance can send the file to EDICOM itself and ask how it went. You'll see five new Electronic messages actions for submitting and checking status, and three web service settings that hold EDICOM's addresses.
Pick your VAT regime in the parameter and Finance splits the periods itself. Standard monthly filers get ten-day periods for transactions and a monthly one for payments.
Incoming invoices and their payments now go in a file of their own, with issuer role code BY. Expect one more file per period to keep track of.
Document numbers now carry a date-time stamp. If a transaction changes after the file was accepted, you can report it again and the numbers won't collide.
Regenerate report adds new and pending items to a message you've already built. If that period's already gone out, the file has to go back as a rectifying transmission, coded RE. The EDICOM channel sets that for you, and if you send files yourself, you set it before you regenerate.
You won't see any of this until someone imports the newest e-Reporting configurations. Check the versions before you assume it's there.
The ten-day split is where finance teams feel it. A standard monthly filer produces at least three transaction files a month plus a payment file, and more if you report incoming invoices, and each one is its own electronic message with its own status. Someone has to watch those statuses. If a rejected file sits unnoticed for a month, your tax team has a problem to explain.
EDICOM shows up in Microsoft's e-invoicing documentation as well, where the setup assumes EDICOM is the approved platform you picked. It's a sensible default if you want one connection for both halves of the reform, but it's still a contract you sign with EDICOM. Check that the platform you choose appears on the tax authority's list of approved platforms before you build anything around it.
Line the deadlines up against Microsoft's update calendar
Dates to plan around
- Sep 1, 2026French reform starts
Every company now has to accept e-invoices. The big ones and ETI had to start sending them, and reporting the rest, on the same day.
- Nov 20, 202610.0.47 end of service
No more cumulative updates. It also isn't on the SAF-T 1.40 build list.
- Dec 22, 202610.0.50 self-update
It's the last service update to open for self-update before Norway's date.
- Jan 1, 2027SAF-T 1.40 only
From here on, Norway only takes 1.40 for any period that starts on or after this date. Older files only count for old years.
- Jan 31, 202710.0.50 first autoupdate
If you haven't moved to 10.0.50 yourself by now, Microsoft starts updating production on its first schedule.
- Mar 12, 202710.0.51 self-update
The major release that carries 1.40 in any build.
- Sep 1, 2027French SMEs join
Smaller French firms start sending e-invoices and e-reporting. If that's you, you've got until then to pick a platform and test it.
Microsoft makes every customer take at least two service updates a year, and you can only pause one at a time. Sandboxes update a week before production. If you're still on 10.0.47 and paused the next one, you don't have much room left under that policy. You'd rather pick the moment yourself than have Microsoft pick it for you.
- Production still sits on 10.0.47 and stops getting cumulative updates after November 20
- SAF-T Format (NO) still on a 1.30 version, with tax code mappings on that version
- Every ten days, somebody exports the French file and uploads it by hand
- The EDICOM token pasted into a config note nobody owns
- Nobody makes a 1.40 file until an auditor asks for one
- You're on a supported version, and the build is one Microsoft actually lists
- Model 221, mapping 221.176 and format 221.208 are in, and the VAT mappings came with them
- Finance sends each French file to EDICOM itself, and someone checks the status every week
- The token's in Azure Key Vault, someone owns it, and there's a date to rotate it
- Someone in tax has already opened a 1.40 test file and checked it by December
What to do now, by role
Who does what before year end
- Ask IT which Finance version and build production is on today, and get the answer in writing.
- Pick one person to sign off the Norwegian SAF-T test file before January. If everyone owns it, nobody checks it.
- Trading in France? Ask which approved platform you've signed with, and check the contract covers e-reporting as well as invoices before you build on it.
- Compare your build with Microsoft's 1.40 list. Anything on 10.0.47 has to move.
- Import Standard Audit File (SAF-T) model 221, mapping 221.176 and SAF-T Format (NO) 221.208 in a sandbox first.
- Set Default for model mapping to Yes, then carry the VAT code parameters across and mark them Completed. People skip this one.
- For France, import the latest e-Reporting configurations and the Electronic messages package from the Lifecycle Services shared asset library.
- Run a 1.40 file for a recent period in a sandbox. Check its tax amounts against what you actually filed.
- If your financial year doesn't start in January, ask your advisor which version the straddling year needs.
- For French entities, tell IT which VAT regime you're on. It decides how the periods get split, and a wrong one means wrong files.
- Put the EDICOM token in Azure Key Vault and switch on Use advanced certificate store. Microsoft's setup expects both.
- Give the Electronic messages processing to a named security role. Without one, only system admins can see it.
- Track down the ID-porten client ID and secret your Norwegian VAT returns use. Write down who owns them, because someone will need to rotate them.
The order we'd do it in
- 01Read the build number
Check the application build on production and every sandbox. Write the versions down. A sandbox doesn't always match production, and you'll test on the sandbox.
- 02Get onto a listed build
Take the quality update or the next service update that lands you on a build from Microsoft's 1.40 list. Do it in a sandbox first and let it sit for a test cycle.
- 03Import the Norwegian configurations
Import the model, mapping and format together, set the mapping as default and carry the application-specific parameters across. Check General ledger parameters still points at SAF-T Format (NO).
- 04Run a test file
Generate 1.40 for a closed period in batch, check the Electronic reporting jobs log, and hand the file to whoever signs it off. Large years split into files under 2 GB, so check you got all of them.
- 05Wire up France
Import the base e-Reporting package, or the EDICOM one if Finance will send the files. Set the VAT regime, put the token in Key Vault and give consent on each executable class. Then push a test period through and import its status.
- 06Put it on a calendar
Schedule the French status checks so nobody has to remember them. Put a December reminder in for next year's Norwegian changes, and have someone read Microsoft's regulatory page once a quarter.
Somebody has to own the credentials that file your taxes
Once Finance submits on its own, it needs its own credentials. France uses a token from EDICOM. Norway's VAT returns go through an ID-porten integration point, with a client ID and secret that call Altinn. Microsoft tells you to store those safely and puts the EDICOM token in Azure Key Vault. Anyone who gets hold of them can file tax data in your company's name.
Treat them like any other privileged secret. Someone should own each one, it should have a rotation date, and access to the Key Vault should be limited to the people who run the integration. Norway's VAT return scopes changed from September 2026, and Microsoft shipped that update in 10.0.50 and earlier builds, so check that the integration point in ID-porten carries the scopes Microsoft now lists.
There's also a data question. Microsoft's privacy notice says turning on the EDICOM channel shares sales, purchase and payment information with EDICOM. Your data protection lead will want to know that before go-live, and Microsoft says a system administrator can switch the interoperation off under Tax, Setup, Electronic messages.
Before: files leave by hand
Someone exports XML, saves it locally and uploads it. The file sits on a laptop and nobody can say which version went out.
After: Finance sends the files and nobody pastes a secret anywhere
The current ER versions build the file, Electronic messages sends it and keeps track of the answer, and the credentials sit in one vault somebody owns.
When a file's rejected or the wrong version went out, start here
If a tax file fails, work through it in this order
Start with the configuration version and the build. Check both before anyone touches a posting in the ledger.
- 01Find out what failedfirst hour
- Open Electronic reporting jobs and select Show log for the run. For France, read the status imported back from EDICOM.
- Note the build number and the ER format version that produced the file. Support will ask for both.
- Look for warnings about unmapped sales tax codes or main accounts. They're easy to click past.
- 02Fix the format, not the datasame day
- If the configuration's out of date, re-import the latest one. Then set the model mapping as default again, because Microsoft's steps have you do that by hand.
- Carry the application-specific parameters to the new format version and mark them Completed. Skip it and the warnings come back.
- If the build is below Microsoft's minimum, plan the quality update before you regenerate anything.
- 03Send it again properlyfirst days
- Already sent that French period? Regenerate it as a rectifying RE transmission instead of a fresh initial one.
- For Norway, regenerate the 1.40 file for the period the auditor asked for and keep the run log.
- Keep every file you sent, including the bad one, so you can show what changed.
- 04Tell the right peoplewithin the week
- Tell your tax advisor what went out and when. If the authority gets in touch, they'll want to have heard it from you first.
- If a credential leaked or was pasted somewhere it shouldn't be, rotate it and check the logs for submissions you didn't make.
- Write down what caused it. Then add a check for it to the next update cycle so it doesn't come back.
Three illustrative situations
- the setup
- A group runs its Norwegian subsidiary on Finance 10.0.47. It paused the last update during a busy quarter, and nobody's imported the SAF-T format since 1.30.
- what happens
- 10.0.47 leaves service on November 20, and Microsoft's 1.40 list doesn't include it. In spring an auditor asks for January to March 2027, and the file comes out in the old version.
- what to do
- Move to a listed build of a supported version in the next window, import the 1.40 configurations and run a test file before the year closes.
- the setup
- A large retailer sells to French consumers and runs Finance in the cloud. Every period, a finance analyst exports the e-reporting files and uploads them to the platform's portal by hand.
- what happens
- Ten-day periods mean three uploads a month plus payments. A holiday week goes by, one period isn't sent, and nobody notices because there's no status in Finance.
- what to do
- Switch on direct submission through Electronic messages and schedule the status check. Give the processing to a security role with at least two people in it, so a holiday doesn't stop it.
- the setup
- A mid-size company hooked Finance up to EDICOM in a rush before September. The token ended up in a shared document while someone worked out Key Vault.
- what happens
- Then the contractor who did the setup leaves. Nobody knows where the token's used, or who can file in the company's name.
- what to do
- Move the token into Key Vault, rotate it with EDICOM, record an owner and limit vault access to the people who run the integration.
How Cohash helps
Most of this is careful admin work, and it's easy to get wrong under a deadline. We'll read the build on every environment, take a sandbox through the update and the new ER configurations, and run test files your tax team can check. For France, we can set up Electronic messages with the token in Key Vault and the roles cleaned up. See our Finance and Operations page, engineers for this work, or start with an assessment.
What to take from this
- 01
Norway takes only SAF-T Financial 1.40 for periods from January 1, 2027. Nobody asks for it until an audit, so run a test file before anyone does.
- 02
10.0.51 arrives in March, too late. Get onto a listed build of 10.0.48, 10.0.49 or 10.0.50 instead.
- 03
10.0.47 leaves service on November 20 and isn't on the 1.40 list. Move now.
- 04
Carry your VAT code mappings to the new format version, or the report warns and someone ignores it.
- 05
France's e-reporting runs on the e-invoicing calendar. Smaller French companies start both next September, so don't leave it until August.
- 06
Anyone holding the EDICOM token or the ID-porten secret can file in your name. Put both in a vault and give each one an owner who'll rotate it.
01Do we have to send SAF-T to Norway every month?
No. You only hand the file over during an audit, the Tax Administration says. But you need to be able to produce 1.40 for periods from January 2027, so test it before an auditor asks.
02Can we keep producing SAF-T 1.30 files?
For financial year 2026 and earlier, yes. Skatteetaten says 1.20 and 1.30 still work for those years. In Finance you'd need format version 190.180 or earlier to produce a 1.30 file.
03Which Dynamics 365 Finance build do we need for SAF-T 1.40?
You need 10.0.2645.170 on 10.0.48, 10.0.2790.101 on 10.0.49 or 10.0.2919.15 on 10.0.50. Any 10.0.51 build works, but that doesn't arrive until March. 10.0.47 isn't on the list, and it leaves service on November 20, 2026.
04Do we have to use EDICOM for French e-reporting?
No. Microsoft's direct channel only goes to EDICOM, but you don't have to use it. You can generate the file in Finance and send it through another approved platform, as long as that platform's on the tax authority's list.
05When do small French companies have to start?
SMEs (PME) and micro-businesses start issuing e-invoices on September 1, 2027, and e-reporting starts for them at the same time. Receiving is different. Every company has had to accept e-invoices since September 2026, so if you buy from French suppliers you're already in it.
06Does French e-reporting work on-premises?
Microsoft says direct EDICOM submission works in the commercial cloud, and its France e-invoicing service is cloud-only too. If you're on-premises, ask Microsoft what's supported before you plan around either.
Three questions, about a minute
Pick an answer and we'll tell you if it's right, and why it is or isn't. The score stays in this browser.
-
Q1Your Norwegian entity is on 10.0.49 and the team wants to wait for 10.0.51 to get SAF-T 1.40. What's the problem?
show the answer
B. It won't open for self-update until March, so you'd miss January 10.0.51 doesn't open for self-update until March 12, 2027. If you're on 10.0.49 with build 10.0.2790.101 or later, you can make 1.40 files today.
-
Q2The new SAF-T format is in, but the report now warns about unmapped sales tax codes. What got missed?
show the answer
B. You didn't carry the VAT code mappings over to the new format version The VAT code lookup sits on the old format version, so it doesn't come across by itself. Export it, import it into the new version and set it to Completed.
-
Q3A transaction changes in a French period you've already sent. What do you do with the file?
show the answer
B. As a rectifying transmission Send it as a rectifying transmission, coded RE. Microsoft's guide says that's how a period that's already gone out gets corrected, so don't send a second initial file.