| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 1499 |
| Technical Name |
einvoice_inbound_cii |
| 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 | 1499 |
| Technical Name |
einvoice_inbound_cii |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Inbound UN/CEFACT CII e-Invoice Import
Turn received UN‑CEFACT CII (Cross Industry Invoice) e-invoices — ZUGFeRD 2.x, Factur-X, XRechnung-CII — into vendor bills, automatically, with no country lock-in
CII is the second EN 16931 syntax (the first being UBL) and is the XML carried by ZUGFeRD 2.x, Factur-X and XRechnung-CII. Across the EU, reception of structured e-invoices is mandated before issuance — Germany since 2025, Belgium and France from 2026 under the ViDA package. When your suppliers send CII, this module ingests the XML and creates a draft vendor bill with the lines, allowances, charges, taxes and seller already mapped. Compatible with Odoo 18 and Odoo 19.
Dedicated CII parser
A focused parser for the UN/CEFACT CrossIndustryInvoice D16B schema: ZUGFeRD 2.x, Factur-X (all profiles), XRechnung-CII and EN 16931 CII. Invoice or credit note (UNTDID 1001 type codes), both are handled, with the guideline / profile identifier surfaced.
Factur-X / ZUGFeRD PDFs
Hybrid PDF/A-3 invoices are supported too: the embedded
factur-x.xml / zugferd-invoice.xml is
extracted straight from the PDF — no external PDF library or
cloud service required.
Full allowances & charges
Document-level (BG-20 / BG-21) and line-level (BG-27 / BG-28) trade allowances and charges are parsed, signed and folded into the reconciliation — not silently dropped — and reproduced as their own vendor-bill lines so totals match the supplier exactly.
Reconciled totals
Per-rate ApplicableTradeTax buckets (BG-23) and the
EN 16931 calculation rules are checked against the document's own
stated tax basis, tax and payable amount. Mismatches and dubious
identifiers are surfaced as warnings before a bill is posted.
Seller matching & validators
The SellerTradeParty is matched by VAT then by name, or a
new company partner is created. Real check-digit validators —
ISO 13616 / ISO 7064 MOD-97 IBAN and country-dispatched EU VAT
check digits (DE/AT/NL/IT/ES/FR/BE/PL/LU) — catch corrupt
identifiers before a partner is created.
Inbox, wizard & cron
A one-click import wizard, an inbound-document inbox with status tracking and a per-document import log, plus an optional hourly auto-import cron (off by default). Tax point date, exchange / tax currency and seller tax representative are captured too.
What you get
- UN/CEFACT CII CrossIndustryInvoice parser (D16B): ZUGFeRD, Factur-X, XRechnung-CII, EN 16931 CII.
- Factur-X / ZUGFeRD hybrid PDF embedded-XML extraction with no external tool.
- Document- and line-level allowances & charges parsed, signed and reconciled.
- Automatic vendor-bill mapping: header, dates, currency, lines, net unit prices (basis-quantity aware), tax buckets, total reconciliation with warnings.
- Seller matching by VAT / name with company-partner creation from the party block.
- Real IBAN & EU VAT check-digit validators.
- Import wizard, inbound inbox, audit archive and optional auto-import cron.
- Compatible with Odoo 18 and Odoo 19.
BYOK — your data stays in Odoo
This module only reads the CII files you upload or place in Odoo; it does not transmit any data to external services. Network transport (Peppol / AS4 reception) is out of scope and handled by your own access point. No third-party account, token or subscription is required.
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