| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 3213 |
| Technical Name |
l10n_es_facturae_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 |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 3213 |
| Technical Name |
l10n_es_facturae_gb |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Facturae 3.2.2 for Spain — FACe & Crea y Crece
Native Facturae XML + XAdES signing for B2G public administrations and B2B e-invoicing — bring your own certificate
Generate legally structured Facturae 3.2.2 invoices and credit notes straight from Odoo, seal them with an enveloped XAdES-EPES signature using your own certificate, and route them to FACe (the General Point of Entry for public administrations) or the Crea y Crece B2B platform. Built for the 2026–2028 Spanish e-invoicing rollout (Law 18/2022 & Royal Decree 238/2026).
Native Facturae 3.2.2 XML
FileHeader, Parties, Invoices, TaxesOutputs, InvoiceTotals and Items built directly to the Ministerio de Hacienda schema — per-rate IVA breakdown (21% / 10% / 4% / 0%), legal vs natural person handling and the Spanish decimal & rounding policy.
XAdES-EPES signature (BYOK)
The document is sealed locally with an enveloped XAdES-EPES signature (signing time, signing-certificate digest, Facturae signature policy) using your certificate and private key. Keys are pasted into company settings, stored only on your database, never bundled or sent.
FACe (B2G) with DIR3
Address public administrations with the three mandatory DIR3 administrative centres — Oficina Contable (01), Organo Gestor (02) and Unidad Tramitadora (03) — managed on the partner. Submission and lifecycle status against editable FACe endpoints.
Crea y Crece (B2B)
Route business-to-business invoices to the Crea y Crece public platform with a configurable base URL and BYOK token, ready for the phased B2B obligation under Royal Decree 238/2026 once its implementing Ministerial Order enters into force.
NIF / CIF / NIE validation
Seller and buyer tax identifiers are validated with the official control algorithms: the DNI/NIE control-letter table and the CIF check character. Invalid identifiers are blocked before the document is generated.
Validate before you send
A pre-submission validation wizard runs the Facturae and channel business rules (EN 16931 core + Spanish layer) and lists every error and warning, so invoices are clean before they reach the authority.
How it works
- Enable Spain Facturae on the company and set your NIF/CIF.
- Paste your signing certificate & private key (BYOK), and configure a FACe or Crea y Crece connection.
- On a customer invoice: Generate Facturae builds and signs the XML, Validate checks the business rules, Submit delivers it to the chosen channel.
- Registry number and tracking code are captured back onto the invoice; an optional cron drains posted invoices in bulk.
Compatibility & disclosure
Odoo 18 & 19 Community. Requires the E-Invoice Core Engine. Python dependencies: lxml, cryptography, requests. This module signs locally with the certificate you configure and transmits invoice data only to the FACe / Crea y Crece endpoint you set — no data is sent anywhere else.
Screenshots
Facturae Face B2G Invoice Wi
Facturae 3 2 2 Xml Payload F
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