| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 461 |
| Technical Name |
l10n_ph_einvoice_gb |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 461 |
| Technical Name |
l10n_ph_einvoice_gb |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Philippines e-Invoice
Philippines BIR EIS for Odoo: document number, VAT 12% with VATable/zero-rated/exempt split, EIS JSON payload and BIR QR
Build BIR sales documents for the Electronic Invoicing/Receipting System — VAT 12% breakdown, EIS JSON & XML and the BIR QR — directly from Odoo.
Key Features
Document types
Sales Invoice, Official Receipt, Credit and Debit notes, each with a running document number from a configurable prefix.
VAT 12% breakdown
The BIR VATable / zero-rated / VAT-exempt split at 12%, centavo-accurate in pesos, with the amount in words.
EIS JSON & XML payload
documentInfo, seller (TIN + RDO), buyer and item lines serialised to the EIS JSON submission format, plus a BIR-style XML.
JWS signing input (BYOK)
The deterministic Base64url(header).Base64url(payload) string the EIS expects you to sign (RS256) with your own private key.
BIR QR
A base64-encoded JSON QR with the key document fields (seller/buyer TIN, doc number, date, total, VAT).
TIN format validation
9-digit and branch-suffixed TINs on the company and partners, with RDO code and the ATP / EIS permit number.
Screenshots
Philippines Eis
Why Choose This Module
Prepares Philippine sales documents for the BIR EIS: Sales Invoice, Official Receipt, Credit and Debit notes with a running document number, the BIR VATable / zero-rated / VAT-exempt split at 12%, the amount in words required on invoices, an EIS JSON & XML payload, the JWS signing input and the BIR QR. Credit/debit notes reference the original document.
Format generator + bring-your-own-key. The current BIR EIS (RR 11-2025) requires each JSON invoice to carry a JSON Web Signature — signed with the taxpayer's own private key and verified by the BIR. This module builds the EIS JSON, the XML and the deterministic JWS signing input; you sign with your own key and transmit with your own credentials. It does not hold any signing key and is not a BIR-accredited e-invoicing integrator. Phased mandatory rollout is in progress (RR 11-2025 / extended by RR 26-2025); confirm your covered date with the BIR.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: 35+
- Author: Baris Genc
- Dependencies: account, base, mail
- Support: odoo@gencbaris.com
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module