Fiji, through FRCS VMS, and Samoa, through TIMS, are moving to Version 3 (v3) fiscal compliance. For POS vendors, this is not only a technical update. It affects invoice creation, PIN verification, environment handling, status checks, accreditation preparation, and production rollout.
- Fiji FRCS VMS and Samoa TIMS v3 introduce stricter fiscalization rules for POS systems.
- POS vendors should not treat v3 as a minor endpoint change or simple API upgrade.
- Invoice creation, PIN verification, status checks, and environment parameters must be implemented correctly.
- Accreditation testing requires a working POS setup, not only isolated API calls.
- FiscoBridge SDC helps POS vendors reduce development risk and migrate faster to v3 compliance.
Who is this guide for?
This guide is written for POS software vendors, system integrators, accounting software providers, ERP developers, and IT companies that need to support fiscalization in Fiji or Samoa.
It is especially useful if your software needs to create fiscal invoices, connect with an SDC, support smart card-based signing, or pass accreditation under the latest v3 requirements.
Why does v3 compliance matter?
v3 compliance matters because older POS fiscalization logic may no longer be accepted under the latest Fiji FRCS VMS and Samoa TIMS requirements. POS systems that do not migrate correctly may fail accreditation, be rejected in production, or face delays during customer rollout.
Compared with earlier versions, v3 requires more precise implementation and better alignment with official fiscalization workflows.
- Stricter validation rules for invoice requests and responses
- Clearer separation between POS software and SDC responsibilities
- More precise endpoint usage for invoice creation, PIN verification, and status checks
- Less tolerance for legacy behavior or undocumented shortcuts
What changed in v3 fiscal compliance?
v3 changed the way POS systems interact with fiscalization components. Migration is not just replacing one URL with another. POS vendors must review request formats, endpoint mapping, validation rules, and the full invoice workflow.
| Area | What changed in v3 | Why it matters |
|---|---|---|
| Invoice creation | Legacy invoice creation logic must be mapped to the correct v3 invoice workflow. | Incorrect invoice structure can block accreditation or production usage. |
| PIN verification | PIN verification must follow the required v3 flow. | Incorrect PIN handling can prevent secure fiscalization. |
| Status checks | Status and environment parameters are handled more explicitly. | POS software must understand whether the SDC is ready, configured, and available. |
| Validation | Request and response validation is stricter. | Behavior that worked in previous versions may fail in v3. |
Which v3 migration guides should POS vendors read?
POS vendors should review the core migration guides before changing production code. These guides explain endpoint mapping, common mistakes, and the correct v3 implementation approach.
- Invoice creation: Read the v3 create invoice migration guide
- PIN verification: Read the verify PIN migration guide
- Status and environment parameters: Read the status and environment parameters migration guide
What are the most common migration challenges?
The most common v3 migration problems happen when POS vendors underestimate the scope of the change. v3 should be treated as a compliance migration, not only a small technical update.
Is v3 just a minor update?
No. v3 endpoints are not simple drop-in replacements. Request structures, validation rules, and workflows can be different from previous versions.
Can old and new endpoints be mixed?
POS vendors should avoid mixing legacy invoice signing or status calls with v3 endpoints. A mixed implementation can create inconsistent behavior and may fail accreditation testing.
Can accreditation be prepared later?
Accreditation should be planned early. In most real-world cases, the POS software must already be installed, configured, and functional before testing can be completed properly.
What must POS vendors prepare for accreditation?
Accreditation usually evaluates the complete POS workflow, not only individual API calls. POS vendors should be ready to demonstrate that their system can create, fiscalize, print, and recover invoices correctly.
- A fully installed and operational POS system
- Correct invoice creation behavior
- Proper PIN verification handling
- Correct use of status and environment parameters
- Clear error handling when fiscalization fails or connectivity is unavailable
- Correct receipt, journal, or invoice output after fiscalization
- A tested rollout process for customers in Fiji or Samoa
How can FiscoBridge SDC help with v3 migration?
FiscoBridge SDC helps POS vendors connect their existing POS software to a v3-aligned fiscalization layer. Instead of building and maintaining a custom compliance engine from scratch, vendors can integrate their POS with FiscoBridge and reduce the risk of implementation mistakes.
- Faster time to market in Fiji and Samoa
- Lower development and accreditation risk
- Clear integration surface for POS software
- Support for v3 migration planning and endpoint mapping
- Ongoing alignment with fiscalization updates
POS vendors that need a direct integration can also review the FiscoBridge POS to SDC integration protocol .
How does FiscoBridge support POS vendors?
FiscoBridge supports POS vendors through practical migration guidance, technical integration support, and accreditation preparation assistance.
- v3 endpoint mapping and migration guidance
- Implementation review and validation
- SDC integration assistance
- Accreditation preparation support
- Rollout guidance for customers in Fiji and Samoa
- Consultation for complex POS, ERP, or enterprise setups
FAQ: Fiji VMS and Samoa TIMS v3 migration
Do POS vendors need to update their software for v3?
Yes. POS vendors that support Fiji FRCS VMS or Samoa TIMS should review their fiscalization workflow and update their implementation for v3 requirements.
Is v3 migration only about changing API URLs?
No. v3 migration may require changes to request structures, endpoint usage, status handling, PIN verification, validation, and accreditation preparation.
Can a POS vendor use FiscoBridge instead of building its own compliance engine?
Yes. A POS vendor can integrate with FiscoBridge SDC and use it as the fiscalization layer, instead of building and maintaining the full compliance engine internally.
What should POS vendors prepare before accreditation?
POS vendors should prepare a working POS setup, correct invoice creation, PIN verification, status checks, error handling, and fiscalized invoice or receipt output.
Who should read the FiscoBridge v3 migration guides?
The guides are useful for POS vendors, ERP developers, accounting software providers, IT service companies, and system integrators preparing for Fiji or Samoa fiscalization.
Final takeaway
Fiji FRCS VMS and Samoa TIMS v3 compliance require careful planning, correct implementation, and real-world testing. POS vendors that migrate early, follow v3 requirements, and use a proven fiscalization solution can reduce risk and reach production faster.