| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 1455 |
| Technical Name |
l10n_no_saft_140 |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 1455 |
| Technical Name |
l10n_no_saft_140 |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Norway SAF-T Financial 1.30 / 1.40
Standard Audit File for Tax export for Norway — Altinn-ready XML straight from your posted accounting
Generate the Norwegian SAF-T Financial audit file (Standard Audit
File for Tax) required by Skatteetaten. The export covers the full
government schema in the namespace
urn:StandardAuditFile-Taxation-Financial:NO, built straight
from your posted Odoo accounting — mapped, balanced and ready to
upload to Altinn yourself.
Compatible with Odoo 18 and Odoo 19.
What the file contains
Header
Software identity, the audited company (organisasjonsnummer, address, contact, bank, VAT registration) and the selected accounting period — with the SAF-T part-numbering (NumberOfParts / PartNumber) when the transaction count requires splitting.
MasterFiles
General-ledger accounts mapped onto the Norwegian standard chart of accounts (NS 4102 derived), customers and suppliers, the standard VAT code TaxTable and the analysis (dimension) table.
GeneralLedgerEntries
Every posted journal entry, grouped by journal, with one Transaction per move and one Line per move line carrying per-line debit / credit amounts and, on each taxed line, the standard VAT code, base and amount.
Balanced & cross-checked
File totals are computed and cross-checked, so an unbalanced ledger is caught before upload. The element order follows the published XSD sequence exactly, because SAF-T validators reject out-of-order children.
Versions 1.30 and 1.40
Both SAF-T Financial 1.30 and 1.40 are produced. Version 1.40 is mandatory from 1 January 2027 and is backward compatible; 1.30 stays valid for earlier periods. Pick the version per export or set a company default.
Pre-export validation
A built-in validator reproduces the most common Skatteetaten rejection reasons — an invalid MOD11 organisation number, a missing standard-account mapping, a non-standard VAT code, an unbalanced transaction or ledger — and blocks generation with a readable report.
Screenshots
Privacy & data handling
This module produces a file for you to upload to Altinn yourself. It does not transmit any data to any third party. Everything runs inside your own Odoo instance — bring-your-own-credentials, no external service.
Support
Questions or a tailored chart-of-accounts mapping? Write to odoo@gencbaris.com. More Odoo apps at gencbaris.com/odoo_plugins.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module