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.

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 one working week from confirmed scope. Pricing starts from $999 (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.