Fiji VMS Fiscalisation
FRCS Electronic Fiscal Device (EFD / SDC) protocol for Odoo
Seal customer invoices on the taxpayer's own Electronic Fiscal Device for the Fiji Revenue & Customs Service VAT Monitoring System (VMS). This module adds the device layer that the companion Fiji VAT Label G connector relies on: a device registry, deterministic local receipt signing, a tamper-evident fiscal journal, authority reconciliation and signed daily Z-reports.
EFD device registry
Register each Electronic Fiscal Device with its FRCS serial, branch and BYOK signing key. The record owns the live fiscal counters and the hash-chain head. A non-secret key fingerprint lets operators confirm which key is loaded without revealing it.
Local receipt signing
The device computes the receipt signature and internal-data code with an HMAC-SHA256 algorithm keyed by your communication key — the same way an SDC does — so sales fiscalise even when the FRCS gateway is briefly unreachable (store-and-forward), then reconcile when connectivity returns.
Tamper-evident journal
Every sealed receipt is stored append-only with its signature, internal data, the previous-signature hash-chain link and the exact signed content. Re-verify the whole journal on demand; any break is reported.
Authority reconciliation
When the VSDC returns its own signature, the locally computed one is compared and a match / mismatch is recorded — a divergence is surfaced for investigation rather than silently trusted.
Z-reports (daily close)
Aggregate a period's receipts into a signed end-of-day Z-report with the grand totals and the per-label (A–G) VAT breakdown, chained from the last receipt of the period.
BYOK & monotonic counters
Row-locked per-device receipt / total / Z counters keep the sequence gap-free under concurrency. Offline structural checks validate the serial and key encoding and entropy before any network call. Your key stays on your database — never bundled, never sent except to the FRCS VMS endpoint you configure.
What you get
- EFD device registry with BYOK signing key, branch and SDC type (VSDC / ESDC).
- Deterministic HMAC-SHA256 receipt signing + internal-data MAC.
- Append-only fiscal journal with previous-signature hash chain and full re-verification.
- Authority signature reconciliation (match / mismatch flagging).
- Signed Z-reports with per-label VAT breakdown.
- Guided onboarding wizard, optional auto-seal cron, verification QR per receipt.
Requires the companion Fiji VAT Label G module (VMS transport + VAT labels) and the shared e-Invoice Core Engine. Compatible with Odoo 18 and Odoo 19. Disclosure: this is independent software — we are not FRCS, not a VMS accreditor and not your fiscalisation agent. It is bring-your-own-key (BYOK): you supply the EFD serial and signing key issued to you at FRCS registration; the key is held only on your own database, is never bundled with the module, and is never sent anywhere except the FRCS VMS endpoint you configure. Receipts are signed and stored in your own database. Email support is included and the purchase is refundable per the Odoo Apps Store policy if it does not work as described.
Screenshots
Efd Device Counter Chain Hea
Sealed Vms Fiscal Receipts S
Signed Z Report Day Close La
Update date: 2026-07-02
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4546 |
| Technical Name |
l10n_fj_vms_fiscalisation |
| License | OPL-1 |
| Website | https://pokutsoft.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