Finnish SMEs increasingly run day-to-day operations — sales, purchasing, inventory, contacts — in Odoo, while the books stay in the accountant's Finnish accounting platform. That split creates a recurring reconciliation tax: customer invoices are re-keyed into the sales ledger, purchase invoices are exported to spreadsheets and imported by hand, payments land in one system days before the other knows about them, and VAT codes drift apart until month-end close turns into detective work. Odoo core has no native bridge to the Finnish ledger. Out of the box you get account, sale and purchase models, but no connector, no external-ID matching, and no field mapping to another accounting system's REST API — so the gap is filled with manual data entry and CSV round-trips that quietly introduce duplicates and errors.

The Netvisor Connector for Finland is a made-to-order Odoo module that ECOSIRE builds for your specific chart of accounts, VAT setup and dimension structure. Technically it is a proper Odoo addon: a __manifest__.py depending on account, sale, purchase, stock and contacts; new models.Model classes that persist an external-ID map (netvisor_id, netvisor_identifier) alongside every synced res.partner, account.move, product.product and payment record; and a transport layer that authenticates to the Netvisor REST API using the HMAC/MAC private-key signature scheme with your partner and customer IDs. Sync runs on ir.cron scheduled jobs (with an on-demand manual trigger), and every push or pull is idempotent — records are matched on the stored external ID so re-running a job never creates duplicates. VAT codes and general-ledger accounts are translated through configurable mapping tables, and cost-centre / dimension (kustannuspaikka) values map to Odoo analytic accounts, so a posted account.move carries the correct ledger and dimension coding in both systems.

The connector moves data in both directions. Odoo customer invoices and credit notes are pushed to the sales ledger; vendor invoices from the accounting side are imported as Odoo account.move vendor bills; customers and vendors sync as contacts; products and price lists stay aligned; and payments and vouchers are imported so bank reconciliation happens where your accountant works. Reliability is first-class: a persistent error queue captures any record the remote API rejects, with per-record logging, automatic retry with backoff, and a dry-run mode that shows exactly what would be created or updated before you commit real data. Access is controlled through ir.model.access.csv and record rules so only the finance and integration roles can see credentials or replay the queue, and OWL/XML views give you a mapping console and a sync-monitor dashboard inside Odoo. The build targets Odoo 17.0, 18.0 or 19.0 (Community or Enterprise — we confirm the edition-specific accounting behaviour during scoping).

Because this is build-to-order, nothing is downloaded and switched on. After you request a quotation we run a short scoping call, confirm your Odoo version and edition, your VAT and GL mapping, which document flows you need, and your Netvisor credentials model, then build and test against a staging copy of your data before go-live. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); additional legal entities, extra document flows or custom dimension logic, and larger historical data-migration volumes increase the quoted scope. You receive a fixed quote after the scoping call — no surprises mid-build.