$ 216.83
In-App Purchases| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) • Point of Sale (point_of_sale) • Inventory (stock) |
| Community Apps Dependencies | Show |
| Lines of code | 3934 |
| Technical Name |
l10n_ci_fne_pos |
| 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) • Point of Sale (point_of_sale) • Inventory (stock) |
| Community Apps Dependencies | Show |
| Lines of code | 3934 |
| Technical Name |
l10n_ci_fne_pos |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Cote d'Ivoire FNE — Point of Sale (RNE)
Fiscalise retail POS tickets at the DGI FNE platform: per-ticket fiscal seal, fiscal number & certification QR, BYOK API
Fiscalise retail point-of-sale tickets against the Cote d'Ivoire Direction Generale des Impots (DGI) Facture Normalisee Electronique (FNE) platform. This is the B2C counterpart of the invoice connector: the Recu Normalise Electronique (RNE). Each paid POS order is transmitted to the DGI, which applies an electronic fiscal seal and a unique fiscal number (numero de sticker), and returns a certification QR code printed on the customer ticket. Full mandate for all tax regimes from 1 January 2026 (platform launched 21 July 2025). Built on the shared e-Invoice Core Engine and the companion l10n_ci_fne_einvoice connector.
Per-Ticket DGI Fiscalisation
A single low-latency sign round-trip at the till — the customer is waiting — with a short timeout, sandbox / production endpoints and full transport logging. Auto-fiscalise on payment, or run a back-office batch for intermittently-connected tills.
Fiscal Seal, Number & QR
The DGI fiscal number, electronic seal and a reproducible verification QR (or a compact offline JSON QR) are stored on the POS order and rendered to a PNG for the ticket, with a compact fiscal reference for the ticket footer.
Retail-Shaped RNE Document
A POS-shaped envelope: no mandatory buyer party, cash / mobile-money (Wave, Orange, MTN, Moov) / card / bank tender, and per-line VAT bucketing into the S / D / Z / E / O categories at 18% / 9% / 0% / exempt / out-of-scope. A deterministic canonical signing string and a whole-franc XOF total.
Real NCC / IDU Validation
The merchant NCC is validated with the real Ivorian taxpayer-account structure (7-11 digit NCC with an optional activity letter, or 9-13 digit IDU). A B2C ticket needs no buyer; an identified business buyer's NCC is checked when present.
Bring Your Own Key (BYOK)
The DGI API token is supplied by you and held on your own database. The official endpoints ship as editable defaults; the token is transmitted only to the DGI FNE endpoint you configure. No data is sent anywhere else.
Per-Till Identification
Point-of-sale and register (caisse) codes are sent so the DGI can sequence each till's tickets. Each till can override the company connection with its own BYOK connection (e.g. a separate shop with a separate token).
What You Get
- RNE ticket generation with canonical signing string and XOF rounding.
- Per-ticket DGI fiscalisation over a BYOK REST transport with retry/backoff.
- Certification QR (verification URL or offline JSON) rendered to a PNG.
- ci_fne_pos validation profile layered on the EN 16931-style engine core.
- pos.order Validate / Fiscalise / Check-Status buttons, status column & filters.
- Auto-fiscalise on payment plus back-office batch and status-poll crons.
- Product tax-category override for exempt vs out-of-scope vs zero-rated lines.
- One-step onboarding wizard: company NCC, DGI connection and a till.
Compatibility & Disclosure
Compatible with Odoo 18 and Odoo 19 (Community & Enterprise). Requires the e-Invoice Core Engine and the l10n_ci_fne_einvoice connector. This module transmits POS ticket data only to the DGI FNE endpoint you configure; your API token stays on your database.
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