A build-to-order Odoo localization for Taiwanese payroll that handles labor and health insurance contributions, income-tax withholding, labor pension, and TWD salary structures. ECOSIRE builds, installs, and supports it after you request a quotation. 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 localization for Taiwanese payroll that handles labor and health insurance contributions, income-tax withholding, labor pension, and TWD salary structures. ECOSIRE builds, installs, and supports it after you request a quotation.
今すぐのお支払いはありません。これはチームへの見積もり依頼を送信します。価格と次のステップをメールでご案内します。
Taiwanese employers running Odoo hit a wall the moment payroll needs to reflect local reality. Odoo Community ships no payroll engine at all, and Odoo Enterprise hr_payroll provides only a generic rule engine with a handful of country localizations — Taiwan is not one of them. That leaves HR teams hand-calculating Labor Insurance (勞保) and National Health Insurance (健保) contributions off the bracketed insured-salary tables, tracking the employer/employee/government split, computing the 6% Labor Pension (勞退) employer contribution, and applying income-tax withholding rules in spreadsheets — then keying results back into Odoo. It is slow, error-prone, and impossible to audit cleanly at month-end.
Labor Insurance (勞保) contribution calculation from the bracketed insured-salary grade table, with the correct employer / employee / government split as `hr.salary.rule` records
National Health Insurance (健保) premium computation including dependent-based supplementary premium logic driven by `@api.depends` computed fields
6% Labor Pension (勞退) employer contribution posted as a distinct payslip line, with optional employee voluntary contribution
Income-tax withholding lines applied per Taiwan withholding rules within the TWD salary structure
TWD-denominated salary structure and structure type seeded as installable data, wired to Taiwan-specific `hr.salary.rule.category` categories
Configurable insured-salary grade tables and contribution rates stored as editable model records — update brackets when the government revises them, no code change
This build-to-order module extends Odoo's native HR and payroll framework with a Taiwan-specific localization layer rather than replacing it. We ship a proper Odoo app: a __manifest__.py declaring dependencies on hr and hr_payroll, new models.Model classes for the insured-salary grade tables, contribution-rate configuration, and pension records, plus computed fields using @api.depends so that changing an employee's insured-salary grade or department instantly recalculates the employer and employee portions. Salary rules are seeded as data records (hr.salary.rule / hr.salary.rule.category) wired into a TWD-denominated salary structure, so a payslip run resolves Labor Insurance, Health Insurance, labor pension, and income-tax withholding lines automatically from Python rule logic — no manual formulas.
Technically, the module adds Taiwan-specific HR fields (national ID / ARC number, insured-salary grade, dependents for NHI supplementary premium, hire and enrolment dates) to hr.employee via inheritance, guarded by ir.model.access.csv and record rules so payroll data stays scoped to HR and payroll roles. Views are delivered as XML (with OWL components where an interactive widget helps), and month-end statutory outputs — insurance schedules and withholding summaries — are produced as QWeb reports you can hand to the Bureau of Labor Insurance, NHI Administration, and tax authority. Contribution-rate and insured-salary tables are configuration data, so when the government revises the brackets you update records instead of editing code. Everything is reachable over Odoo's XML-RPC / JSON-RPC API for integration with attendance, time-off, or an external HR system.
Because this is build-to-order, you are not downloading a fixed listing from apps.odoo.com. After a short scoping call we confirm exact requirements — your entities, pay cadence, allowances, and which Odoo version and edition you run — and then build, test, and install the module for you. Typical delivery is 2–4 weeks from confirmed scope. We support Odoo 17.0, 18.0, and 19.0, on Community or Enterprise, and hand over the full source and git repository at go-live.
Owns monthly payroll accuracy and statutory compliance. Needs Labor Insurance, NHI, labor pension, and withholding computed automatically inside Odoo so month-end runs are auditable instead of spreadsheet-driven.
Cares about correct employer contribution costs, GL posting, and defensible audit trails. Wants payroll statutory lines reconciled and reportable directly from Odoo in TWD.
Maintains the Odoo deployment and integrations. Needs a cleanly packaged module with proper access rules, upgrade-safe inheritance, and XML-RPC/JSON-RPC access rather than core patches.
Runs a growing Taiwanese company on Odoo and wants to stop outsourcing payroll calculations, bringing statutory processing in-house without hiring a specialist.
ecosire.com でライセンスを購入し、アカウント ダッシュボードから Taiwan HR & Payroll モジュールの ZIP をダウンロードします。
ZIP をサーバー上の Odoo カスタム アドオン フォルダーに抽出します (または、[アプリ] > [Odoo.sh / runbot のファイルからインストール] を介してアップロードします)。
開発者モードをアクティブにし、アプリを開き、「アプリリストの更新」をクリックして、「Taiwan HR & Payroll」を検索し、「インストール」を押します。
新しいメニューを開き、ECOSIRE ライセンス キーを貼り付け、外部認証情報 (Shopify、Amazon、Stripe など) を接続して保存します。
組み込みの接続テストを実行し、最初の 10 レコードを同期し、定期的な cron をスケジュールします。何か問題が発生した場合はサポートにお問い合わせください。
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| Taiwan statutory coverage | Labor & health insurance, labor pension, and withholding built to Taiwan rules | Whatever you specify and can validate yourself | Rarely covers Taiwan specifically; often generic | |
| Payroll engine on Community | Scoped and delivered as part of the build | You must build it from scratch | Usually Enterprise-only | |
| Fit to your entities & pay cadence | Confirmed in scoping call, built to match | Full control but full effort | Fixed listing, limited configurability | |
| Statutory reports (insurance/withholding) | QWeb reports for authority submission included | Built only if you spec and pay for them | Varies; often absent or partial | |
| Rate/bracket maintenance | Editable config records you can update yourself | Depends on how it was built | May require vendor update or re-purchase | |
| Support & handover | Post-go-live window plus full git repo handover | Tied to your developer's availability | Ticket queue, no source access | |
| Upgrade safety | Inheritance-based, no core patches | Depends on developer discipline | Varies by vendor quality | |
| Time to value | 2–4 weeks from confirmed scope | Months of build and testing | Instant install but needs heavy local rework |
No. This is a build-to-order localization. ECOSIRE builds, tests, and installs it for your specific Odoo version and requirements after you request a quotation and we confirm scope — there is no instant download.
Typical delivery is 2–4 weeks from confirmed scope. The exact timeline depends on the complexity of your entities, allowances, and any integrations, which we agree on during the scoping call before work begins.
Every engagement includes a post-go-live support window for defect fixes and configuration questions, and we hand over the full git repository. Because the insured-salary and contribution-rate tables are editable configuration data, you can update statutory brackets yourself; for engine or version-upgrade changes we offer ongoing support arrangements.
We support both. Odoo Community has no native payroll engine, so for Community deployments we scope the payroll foundation as part of the build; on Enterprise we extend the existing `hr_payroll` framework. We support Odoo 17.0, 18.0, and 19.0.
The insured-salary grade tables and contribution rates are stored as editable model records, not hard-coded. When the Bureau of Labor Insurance or NHI Administration revises the tables, you update the configuration records and future payslips pick up the new values — no code change required.
No. The module uses standard Odoo inheritance to extend `hr.employee` and adds its own models and salary rules. Core files are never patched, which keeps your deployment upgrade-safe across Odoo versions.
Yes. The new models and fields are exposed over Odoo's XML-RPC / JSON-RPC API and the salary rules can read worked days and leave from Odoo's attendance and time-off modules, so payroll draws from a single source of truth.
A build-to-order Odoo localization for Taiwanese payroll that handles labor and health insurance contributions, income-tax withholding, labor pension, and TWD salary structures. ECOSIRE builds, installs, and supports it after you request a quotation.