A build-to-order Odoo module that adds Swedish SIE 4 accounting interchange, the BAS chart of accounts, and Peppol BIS Billing 3 e-invoicing so your Odoo books speak the same language as your Swedish accountant. ECOSIRE scopes, builds, installs, and supports it for your specific setup. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $299.00 USD; request a quote for a scoped proposal.

A build-to-order Odoo module that adds Swedish SIE 4 accounting interchange, the BAS chart of accounts, and Peppol BIS Billing 3 e-invoicing so your Odoo books speak the same language as your Swedish accountant. ECOSIRE scopes, builds, installs, and supports it for your specific setup.
ابھی کوئی ادائیگی نہیں۔ یہ ہماری ٹیم کو قیمت کی درخواست بھیجتا ہے — ہم قیمت اور اگلے اقدامات کے ساتھ ای میل کے ذریعے رابطہ کریں گے۔
Swedish SMEs hit a wall the moment their Odoo bookkeeping has to meet their accountant's world. The accountant (redovisningskonsult) works in BAS-numbered accounts and exchanges the year's ledgers as SIE files; Swedish trading partners increasingly expect Peppol BIS Billing 3 e-invoices, not a PDF attachment. Odoo core ships l10n_se with a basic Swedish chart, but out of the box it cannot produce or read a valid SIE 4 file, it does not generate a Peppol BIS UBL invoice carrying the correct Swedish party identifiers, and it has no concept of a bankgiro OCR reference or a momsdeklaration box mapping. Teams end up re-keying figures into a separate program or paying for a manual SIE export at every closing — exactly the friction this build removes.
SIE 4 export and import: round-trips `#KONTO`, `#IB`/`#UB` balances, `#RES` results, `#VER`/`#TRANS` verifications, and `#DIM`/`#OBJEKT` dimension records in the correct PC8/CP437 encoding
SIE cost-centre (kostnadsställe) `#DIM`/`#OBJEKT` mapping onto Odoo analytic accounts, bidirectional so dimensions survive the round trip
Peppol BIS Billing 3 sales e-invoice generation as an `account.edi.format` emitting UBL 2.1 with correct Swedish `EndpointID` party identifiers
Inbound Peppol invoice import that parses a received UBL document into a draft `account.move` vendor bill with lines and taxes pre-filled
BAS chart-of-accounts template loaded with Swedish account groups and the tax tags the SIE and VAT-return logic rely on
Swedish VAT rate set: 25% / 12% / 6% / 0% plus reverse-charge taxes, tagged for both SIE export and the VAT return
This is a productized module we build to order on top of account, account_edi, base_vat, and l10n_se. On the interchange side we implement a SIE 4 reader and writer that round-trips the #KONTO accounts, #IB/#UB opening and closing balances, #RES results, #VER/#TRANS verifications, and #DIM/#OBJEKT dimensions — mapping SIE cost centres (kostnadsställe) onto Odoo analytic accounts so your dimension breakdown survives the trip both ways, in the correct PC8/CP437 encoding the standard expects. We load a proper BAS chart-of-accounts template and wire the Swedish VAT rates (25% / 12% / 6%, plus 0% and reverse charge) with the tax tags the SIE export and VAT-return logic depend on.
On the e-invoicing side we add a Peppol BIS Billing 3 format to the account_edi framework: a new account.edi.format record whose _get_move_applicability targets Swedish customer invoices, an XML builder that emits UBL 2.1 with the buyer/seller EndpointID (scheme 0007 for organisationsnummer), momsregistreringsnummer (VAT number), and tax subtotals per rate, plus inbound parsing that turns a received Peppol invoice into a draft vendor bill with lines and taxes pre-filled. We add compute fields for the bankgiro/plusgiro OCR reference (with the Luhn/mod-10 check digit), res.partner and res.company validation for organisationsnummer and momsregistreringsnummer via base_vat constraints, and a momsdeklaration mapping that groups the VAT tax tags into the Skatteverket return boxes. Everything is delivered as a clean module with ir.model.access.csv, record rules for multi-company isolation, OWL/XML views, QWeb templates where a printable artefact is needed, and the whole thing exposed over the standard XML-RPC/JSON-RPC API so an external portal or your accountant's tooling can trigger a SIE export or read invoice status.
Delivery is build-to-order: we start with a short scoping call, confirm the exact scope in writing, then build on staging, run UAT with your data, and install on your Odoo (Community or Enterprise, version 17.0, 18.0, or 19.0). Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $299 (indicative, single-company base scope); multi-company groups, bankgiro/plusgiro payment-file integration, historical SIE data migration, and deeper localization depth increase the quoted scope. You get a fixed quote after the scoping call — never a surprise.
Runs day-to-day accounting in Odoo but has to hand the year's ledgers to an external redovisningskonsult who only accepts SIE files. Needs a clean, valid SIE 4 export at every closing instead of a manual re-key.
Services several Odoo clients and wants ledgers to arrive as standards-compliant SIE with correct BAS accounts and dimensions, so review and VAT-return prep stay in familiar tooling.
Handles invoicing and vendor bills and needs Peppol BIS Billing 3 out to Swedish customers plus inbound Peppol bills parsed automatically, with correct bankgiro OCR references on payments.
Owns the Odoo setup for a multi-entity Swedish group and needs SIE, VAT, and e-invoicing to work per company with clean isolation, API access for reporting, and a maintainable, owned codebase.
Buy the license on ecosire.com and download the Sweden SIE Export + Peppol BIS module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Sweden SIE Export + Peppol BIS, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| SIE 4 export/import | Full round-trip: accounts, balances, verifications, and dimensions, built and tested to your accountant's file | Possible but you specify and QA the SIE standard yourself | Often export-only, fixed feature set, limited dimension handling | |
| Peppol BIS Billing 3 | Send and receive via `account_edi`, with Swedish identifiers wired to your access point | Build from scratch against the UBL spec | Varies; may be send-only or a generic EU format | |
| BAS chart + Swedish VAT | BAS template with 25/12/6% and reverse charge tagged for SIE and the VAT return | You configure and tag every account and tax | Basic chart; VAT-return box mapping often missing | |
| Bankgiro/plusgiro OCR | Compute field with mod-10 check digit, plus optional payment-file export | Implement the reference algorithm and file format yourself | Sometimes included, rarely with payment files | |
| Org.nr / VAT validation | `base_vat` constraints on partners and companies, tested | Add and maintain the constraints yourself | May validate format only | |
| Fit to your setup | Scoped, built on staging with your data, UAT before go-live | Fully yours to design, build, and QA | One-size-fits-all; you adapt to it | |
| Ownership & support | Source + git handover, training, and a support window | You own it and staff the maintenance | Vendor-licensed; support depends on their terms | |
| Delivery model | Build-to-order, 2–4 weeks from confirmed scope, fixed quote | Open-ended internal or contractor timeline | Instant download but no fit guarantee |
No. This is a build-to-order module — a productized service. ECOSIRE scopes it with you, builds it on staging against your Odoo version and data, then installs and supports it. It is not an existing apps.odoo.com download, and we make no instant-download claim.
Typical delivery is 2–4 weeks from confirmed scope. The clock starts once we've agreed the exact scope in writing after the scoping call. Larger multi-company setups, payment-file integration, or historical SIE data migration can extend the timeline, which we state in your quote.
Pricing starts from $299 (indicative, single-company base scope). The exact figure depends on drivers like multi-company groups, bankgiro/plusgiro payment-file work, data migration volume, and localization depth. After a short scoping call we give you a fixed quote — no surprise charges beyond it.
Yes. We build for Odoo 17.0, 18.0, or 19.0 on Community or Enterprise. Some Enterprise editions include broader accounting features; we build the SIE and Peppol capabilities to work on your specific edition and confirm any edition-dependent behaviour during scoping.
Every build includes a post-go-live support window for defect fixes and configuration questions. Because you receive the git repository and own the source, you can maintain it yourself or extend the support arrangement. Version upgrades (e.g. moving from 18.0 to 19.0) are quoted separately as they involve real porting work.
We implement the SIE 4 standard — accounts, opening/closing balances, results, verifications, and dimensions — in the correct encoding, and validate exports against sample imports during UAT. If your accountant uses a specific program with quirks, share a sample file during scoping and we test round-tripping against it before go-live.
Yes. Outbound, we generate Peppol BIS Billing 3 UBL sales invoices with the correct Swedish party identifiers. Inbound, we parse received Peppol documents into draft vendor bills with lines and taxes pre-filled. Connection to a specific Peppol access point is confirmed and wired during scoping.
A build-to-order Odoo module that adds Swedish SIE 4 accounting interchange, the BAS chart of accounts, and Peppol BIS Billing 3 e-invoicing so your Odoo books speak the same language as your Swedish accountant. ECOSIRE scopes, builds, installs, and supports it for your specific setup.