示意预览Egypt-localized Odoo payroll:
social insurance, progressive income-tax brackets, EGP salary rules and Arabic + English payslips.
什么是 Egypt Payroll & Social Insurance？
Egypt-localized Odoo payroll: social insurance, progressive income-tax brackets, EGP salary rules and Arabic + English payslips. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
核心功能
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Odoo 上构建、配置并安装。
- 3
上线 + 支持
约一个工作周内上线，并包含两周上线支持。我们交付的代码中的缺陷免费修复。
技术规格
- Odoo 兼容性
- Odoo 17, Odoo 18, Odoo 19
- 版本
- 企业版和社区版
- 许可证
- 许可证需要确认
- Python 要求
- Python 3.10+
- 数据库
- PostgreSQL 12+
关于此产品
Running Egyptian payroll inside Odoo means wrestling core HR Payroll into shape for local rules that Odoo does not ship out of the box: the tiered social insurance base with its capped contribution ceiling, the progressive annual income-tax brackets with the personal exemption, and payslips your employees can actually read in Arabic. Most teams end up maintaining a fragile spreadsheet alongside Odoo, or paying to re-derive the same salary rules on every version upgrade.
Egypt Payroll & Social Insurance is a build-to-order localization that ECOSIRE designs, develops and installs for your company. This is not an instant download from apps.odoo.com — our team builds the module against your actual salary structures, allowance policy and legal entity, tests it on a copy of your database, and hands it to you production-ready in one working week.
Under the hood it is a proper Odoo addon. We ship a clean __manifest__.py declaring dependencies on hr and hr_payroll (Enterprise) or a Community-payroll base, versioned for Odoo 17.0, 18.0 or 19.0. Egyptian salary rules live as hr.salary.rule records computing gross, the social-insurance contributory base, employer and employee shares, taxable income and net — driven by Python code and localization parameters rather than hard-coded numbers, so brackets and ceilings can be updated when the law changes. New models (models.Model) extend hr.contract and hr.payslip with Egypt-specific fields; computed totals use @api.depends so they recalculate correctly. Access is locked down with ir.model.access.csv plus record rules so HR officers, payroll managers and employees each see only what they should. Payslips render through a bilingual QWeb report with full Arabic RTL layout, and month-end runs can be triggered by scheduled automated actions. Everything is reachable over Odoo's XML-RPC / JSON-RPC API if you integrate with a bank file or attendance system.
You keep full ownership of the source. Because it is real Odoo — salary rules, structures, views (XML/OWL) and reports — your team or ours can extend it later without vendor lock-in, and it upgrades cleanly across Odoo 17, 18 and 19.
你得到什么
- The complete, installable Odoo module source (addon folder with __manifest__.py, models, salary rules, views, security and QWeb reports) — you own the code
- Configured Egyptian salary structures, structure types and the social-insurance + income-tax salary rules mapped to your actual pay components
- Security configuration: ir.model.access.csv and record rules for payroll manager, HR officer and employee/portal roles
- Bilingual Arabic + English payslip QWeb report templates styled to your company letterhead
- Installation and deployment on your Odoo 17, 18 or 19 instance, validated first on a copy of your production database
- Administrator and HR-user documentation covering payroll runs, updating tax brackets/insurance ceilings, and end-of-service settlement
- A live training session for your HR/payroll team, with a recording and a quick-reference guide
- A post-go-live support window for bug fixes and adjustments, plus a defined channel for change requests
这是给谁的
HR & Payroll Manager at an Egyptian SME
Runs monthly payroll for staff paid in EGP and needs social insurance and income tax calculated correctly and defensibly, without maintaining a parallel spreadsheet or re-checking every figure by hand against the law.
Finance Controller at a multi-entity group operating in Egypt
Wants payroll journal entries to post cleanly into Odoo Accounting with the right salary-rule-to-account mapping, and needs the numbers to reconcile with statutory insurance and tax filings each month.
Odoo administrator / IT lead
Owns the Odoo instance and cares about a clean, upgradeable addon — proper __manifest__.py, salary rules instead of hard-coded values, sane security rules — that survives version upgrades across Odoo 17, 18 and 19 without a rebuild.
HR officer processing new hires and leavers
Onboards employees with the correct insured salary and tax data, and needs end-of-service and leave-settlement figures generated automatically and consistently when someone leaves.
Egypt Payroll & Social Insurance 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Odoo 原生 |
|---|---|---|---|---|
| Egyptian social insurance base & capped ceiling | Built in as a configurable salary rule with employer/employee split | Possible, but you specify and pay for every edge case | Rare; most generic payroll apps aren't Egypt-localized | 不包括在内 |
| Progressive income-tax brackets + personal exemption | Implemented as annualized salary rules, brackets held as parameters | Buildable but re-derived from scratch each time | Sometimes partial or hard-coded to one tax year | 不包括在内 |
| Bilingual Arabic (RTL) + English payslip | QWeb report with true RTL layout, both languages | Extra scope you brief and fund separately | Usually English-only or LTR-only | 部分支持 |
| End-of-service & leave settlement | Computed automatically on termination from accrued balances | Depends on how thoroughly it was specified | Varies widely; often not Egypt-specific | 不包括在内 |
| Odoo 17 / 18 / 19 version parity | Built and tested for your target version, upgradeable | One-off; re-work likely on each upgrade | Depends on the publisher keeping it current | 包含 |
| Source-code ownership & no lock-in | You receive and own the full addon source | You own it, at full bespoke cost | Often obfuscated or license-restricted | 包含 |
| Role-based access (ir.model.access.csv + record rules) | Configured for manager/HR/employee/portal roles | Only if scoped and built | Generic, rarely tuned to payroll sensitivity | 部分支持 |
| Legal-change updates (ceiling / brackets) | Config edit, not a rebuild; maintenance available | Developer engagement each time | Wait on the publisher's release cycle | 不包括在内 |
关于Egypt Payroll & Social Insurance的常见问题
How long until the module is delivered, and how does the build process work?
This is a build-to-order module, not an instant apps.odoo.com download. Typical delivery is one working week from the point we confirm your salary structures, allowance policy and target Odoo version. The process is: discovery and requirements sign-off, development of the salary rules and models against your data, testing on a copy of your production database, then installation, training and go-live. If you have an unusual allowance or settlement policy the timeline can shift, and we'll tell you up front.
What support and updates do I get after go-live?
Every build includes a defined post-go-live support window for bug fixes and adjustments, plus a clear channel for change requests. Because the social-insurance ceiling and income-tax brackets are stored as configurable parameters (not hard-coded), routine legal changes are a config update rather than a paid rebuild. When Egyptian rules change materially, or you upgrade to a newer Odoo version, we can quote a maintenance update — you keep the source either way, so you're never locked in.
Does it work on Odoo Community or only Enterprise?
Both are supported. Odoo's full HR Payroll app is an Enterprise feature, so on Enterprise we extend hr_payroll directly. For Community deployments we build on a Community payroll base and confirm the exact dependency and scope with you during discovery. We target Odoo 17.0, 18.0 or 19.0 — tell us your edition and version and we build the __manifest__.py to match.
How are the Egyptian social insurance and income tax actually calculated?
Both are implemented as proper Odoo salary rules (hr.salary.rule) with Python computation. Social insurance uses the statutory contributory base within the minimum/maximum insured-wage bracket and splits employer and employee shares. Income tax applies the personal exemption then the progressive annual brackets, annualized and pro-rated to the monthly payslip. Rates, the exemption and the ceiling are configurable localization parameters, so you can update them when the law changes without a developer.
Are the payslips really in Arabic, and can employees download their own?
Yes. Payslips render through a bilingual QWeb report with a full Arabic right-to-left layout plus an English version, styled to your letterhead. Employees can access their own payslips through the Odoo Portal, gated by record rules so each person only sees their own — HR doesn't have to email PDFs around.
Can it integrate with our bank file or existing HR/attendance systems?
Yes. Everything is standard Odoo data reachable over the XML-RPC / JSON-RPC API, so bank-transfer file exports, attendance imports or third-party HR tools can read and write payroll records. If you need a specific bank format or integration, we scope it during discovery and build it as part of the module.
相关模块
Egypt Payroll & Social Insurance
Egypt-localized Odoo payroll: social insurance, progressive income-tax brackets, EGP salary rules and Arabic + English payslips.
- Egyptian social insurance engine computing the contributory (insurance) base within the statutory minimum/maximum wage bracket, with separate employer and employee contribution shares posted per payslip line
- Configurable social-insurance rates and the contribution ceiling stored as localization parameters (not hard-coded), so updates when the ceiling changes are a config edit, not a code rewrite
- Progressive income-tax calculation across the Egyptian annual tax brackets, applied on an annualized basis and pro-rated back to the monthly payslip
- Personal exemption / tax-free threshold applied before the progressive brackets, with the higher-income phase-out logic handled in the salary rule