Company: Link Technologies
Case No: L13100. Project: 15.90: LinkSOFT Version 15.90
Logged By: Sanjay (Link Technologies) on 29 Jan 2025 10:35AM
Priority: Low
Product: Point of Sale
Group: Enhancement
Time Taken: 61.00 (Weight: 80.00)
Assigned To: Sanjay (Link Technologies)
Circulation: Sanjay, Sitla, Vineet, Vineshwar Prasad
Resolve By: Friday, 29 August 2025 02:28 PM [203 days since logged date]
Status: UAT
Subject: FRCS VMS V3 Implementation
Summary:    

Hi Sanjay, 

There are changes in VMS Version 3, and it requires development work

Please kindly re-register as a developer to gain access to the latest documentation.

There is no highlight on the changes; we are told that the developers will need to go through the documentation to be in compliance with their POS systems.

Areas we will need to consider are

  1. LinkPOS,
  2. VMS Integration to all other ERPs, MYOB, XERO, JIWA.

 I have registered EBS as a developer, but to re-accredit, this will only be possible once we have the technical end sorted with your team.

Below is an email from FRCS to me with links. Let me know if you need the registration to be done ASAP to move things faster.

***********************************************************************************************************************

Robert R. Fonmanu <rfonmanu001@frcs.org.fj>

Apologies for the delay. Please refer to the documentation below.

 

Refer below for new specifications regarding Sandbox VSDC URL:

https://tap.sandbox.vms.frcs.org.fj/help/view/1235385360/Detailed-Specs/en-US

 

Other relevant material can be found on:

https://tap.sandbox.vms.frcs.org.fj/help/view/158851269/Readme/en-US

 

Do let us know if you have any further queries.

 

regards
Robert Fonmanu
IT Support Engineer , Technology Division
Building 2 – Level 1 | Revenue & Customs Services Complex Cnr of Queen Elizabeth Drive & Ratu Sukuna Road
Nasese, Suva

Audit Notes:Edited by sanjay on 31/07/25 11:58. Edited by sanjay on 09/07/25 12:35. Edited by sanjay on 15/05/25 09:32. Edited by sanjay on 15/05/25 09:28. Edited by sanjay on 12/02/25 15:39. 
12 Feb 202503:39PM Comment 1 by Sanjay (Link Technologies) Comment removed by sanjay
18 Feb 202510:35AM Comment 2 by Sanjay (Link Technologies) Comment removed by sanjay
04 Apr 202503:45PM Comment 3 by Sanjay (Link Technologies) Comment removed by sanjay
30 Apr 202511:41AM Comment 4 by Sanjay (Link Technologies) Comment removed by sanjay
09 Jul 202508:19AM Comment 5 by Sitla (Edge Business Solutions) Comment removed by sanjay
09 Jul 202512:35PM Comment 6 by Sanjay (Link Technologies) Case L13100 added to project 16.00
29 Jul 202511:43AM Comment 7 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 08-08-2025 11:41 AM Time Taken: 8.00
After several emails back and forth with FRCS, I have been asked to register as a New Developer. See final email below.

******************************************************************
TaxCore Support 28 Jul 2025, 18:58 (16 hours ago) to me

Dear Sanjay Singh,

Dear Sanjay,

The certificate you were using was created before the upgrade done to the global sandbox.
In order to access it you will need to register again and request a new certificate.

Best regards,
Related to your #TC005744

Your TaxCore Support Team,
TaxCore Support Department

******************************************************************


30 Jul 202512:55PM Comment 8 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 08-08-2025 12:54 PM Time Taken: 2.00

Certificqtes has been received and installed.

VMS Changes in progress. Expected completion 8th August 2025.


31 Jul 202511:57AM Comment 9 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 08-08-2025 11:53 AM Time Taken: 4.00 Notes: ETC extended from: 31/07/2025 to 08/08/2025

Table 1 - New Status Codes

Status and Error Codes
All protocols share the same Info, Error and Warning codes.
Code0-Info 1-Warning 2-ErrorDescriptionApplies to
    
 INFO  
0000All OKCommand is executed without warnings or errorsVSDC, E-SDC
0100Pin OKThis code indicates that the provided PIN code is correctE-SDC
0210Internet AvailableInternet Connection is available (optional)E-SDC
0220Internet UnavailableInternet Connection is not available (optional)E-SDC
    
 WARNINGS  
1100Storage 90% FullStorage used to store audit packages is 90% percent full. It is time to perform the audit.E-SDC
1300Smart Card is not presentSecure element card is not inserted in the E-SDC smart card readerE-SDC
1400Audit RequiredTotal Sale and Refund amount reached 75% of the SE limit. It is time to perform the audit.E-SDC
1500Pin Code RequiredIndicates that POS must provide the PIN codeE-SDC
1999Undefined WarningSomething is wrong but specific warning is not defined for that situation. Manufacturer can use manufacturer-specific codes to describe warning in more detailsE-SDC
    
 ERRORS  
2100Pin Not OKPIN code sent by the POS is invalidE-SDC
2110Card LockedThe number of allowed PIN entries exceeded. The card is locked for useE-SDC
2210SE LockedSecure Element is locked. No additional invoices can be signed before the audit is completedE-SDC
2220SE Communication FailedE-SDC cannot connect to the Secure Element appletE-SDC
2230SE Protocol MismatchSecure Element does not support requested protocol version (reserved for later use)E-SDC
2310Invalid tax labelsTax Labels sent by the POS are not definedV-SDC, E-SDC
2400Not configuredSDC device is not fully configured for invoice signing (i.e. tax rates or verification URL are missing etc.)E-SDC
2800Field RequiredA field is required (a mandatory invoice request field is missing)V-SDC, E-SDC
2801Field Value Too LongThe length of the field value is longer than expectedV-SDC, E-SDC
2802Field Value Too ShortThe length of the field value is shorter than expectedV-SDC, E-SDC
2803Invalid Field LengthThe length of the field value is shorter or longer than expectedVSDC, E-SDC
2804Field Out Of RangeA field value out of expected rangeVSDC, E-SDC
2805Invalid Field ValueA field contains an invalid valueVSDC, E-SDC
2806Invalid Data FormatThe data format is invalidVSDC, E-SDC
2807List Too ShortThe list of items or the list of tax labels in the invoice request does not contain at least one element (item/label).VSDC, E-SDC
2808List Too LongThe list of items or the list of tax labels in the invoice request exceeds the maximum allowed number of elements (items/labels) or byte size. The maximum values depend on an SDC's capacity for processing invoice requests and can be manufacturer-specific.VSDC, E-SDC
2809Secure Element ExpiredThe digital certificate on the smart card secure element has expired.E-SDC
Obsolete error codes
   
CodeErrorDescriptionApplies to
2811Invalid Invoice TypeValue of Invoice Type field is invalid or out of range (replaced with 2805)VSDC, E-SDC
2812Invalid Transaction TypeValue of Transaction Type field is invalid or out of range (replaced with 2805)VSDC, E-SDC
2813Invalid Payment TypeValue of Payment Type field is invalid or out of range (replaced with 2805)VSDC, E-SDC
2814BuyerIdLenghtInBytes Length ExceededBuyerID field maximum length is exceeded (20 chars) (replaced with 2803)VSDC, E-SDC
2815BuyerCostCenterId Length ExceededBuyerCostCenterId field maximum length is exceeded (15 chars) (replaced with 2803)VSDC, E-SDC
2816POSInvoiceNumber Length ExceededPOSInvoiceNumber field maximum length is exceeded (20 chars) (replaced with 2803)VSDC, E-SDC
2817GTIN Length InvalidPOSInvoiceNumber field length is less than 8 or greater than 14 (replaced with 2803)VSDC, E-SDC
2818Name Length ExceededName field maximum length is exceeded (2048 chars) (replaced with 2803)VSDC, E-SDC
2819Name is RequiredAn item name is required (replaced with 2800)VSDC, E-SDC
2820Labels Length ExceededLabel length is exceeded (replaced with 2803)VSDC, E-SDC

31 Jul 202501:21PM Comment 10 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 08-08-2025 12:00 PM Time Taken: 18.00
PART A - Development work for this case has been completed.

1. The change will be available in version: 15.90

2. The following changes were made (Include Database object names, Program classes, and any other relevant information):

  1. Completed development work for VMS changes

3. Affected Areas:

  1. VMS - New API updates

4. The issue was caused by:

  1. FRCS VMS changes

5. Other Relevant Notes
6. Next Step
(Review and System Test (Developer) -> UAT (Quality) -> Documentation):  UAT then Compliance


31 Jul 202505:43PM Comment 11 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 08-08-2025 05:42 PM Time Taken: 6.00
Certification Submitted. See attachment.

06 Aug 202512:05PM Comment 12 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 15-08-2025 12:03 PM Time Taken: 2.00
*** Email Response from EFD Support ***

Kaushal Kumar 08:01 (4 hours ago) to Peni, EFD, Sitla, me

Hi Sanjay

Apologies on the delayed response as your email was blocked due to no SPF record. 

To answer your questions: 
  1. When is the new version of SDC taking effect
    1. If you have the new SDC available for accreditation then proceed with submission so it can be accredited and rolled out for your customers in the market. 
  2. When will the PREVIOUS version stop being supported?
    1. This will take effect when all your customers have been migrated to V3 of POS / SDC. There is no immediate deadline set but if you can get your customers on V3 sooner, then you will just have to maintain one version. 
  3. Do vendors need to maintain both versions of SCD or just the current one?
    1. Until such time your customers are on V3, the vendor will have to maintain both versions to ensure business continuity for customers. 
Also on the same note, Peni has not ben part of FRCS for over 7 years now. You can contact me or any other team members part of the EFDCompliance email group for assistance in the future. 

Do advise if there is anything else we can assist with. 

Kind Regards,


Kaushal Kumar
www.frcs.org.fj

06 Aug 202512:07PM Comment 13 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 15-08-2025 12:05 PM Time Taken: 1.00
Certification Request # 44 was submitted on the 31st of July 2025. Still awaiting confirmation.

06 Aug 202501:11PM Comment 14 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 15-08-2025 01:10 PM Time Taken: 2.00

*** Email Response from Samoa TIMS Support ***

Patrick Ah Kuoi 12:16 (54 minutes ago) to Sitla-Edge, me

Hi Sitla,

 

No worries.

 

Please find my responses below:

 

  1. When is the new version of SDC taking effect?

We are now on v3 starting today and will be finishing migration tonight and anticipating any potential issues this week to be identified and resolved at the earliest.

  1. When will the PREVIOUS version stop being supported?

A grace period will be granted to all EFDs currently accredited for v2 to still operate while re-accrediting to v3, due date will be re-confirmed and notification will be sent out to all as we had to push back the upgrade for a bit, but it was initially set to January 2026.

  1. Do vendors need to maintain both versions of SDC or just the current one?

Backward compatibility with v2 to operate on v3 is in effect once we successfully complete upgrade. Once the grace period finishes, then v2 will be decommissioned and no longer supported. So, all EFDs that have not been accredited for v3 after the grace period will be non-compliant with TIMS.

 

Hope this provides clarity.

 

Kind Regards,



08 Aug 202502:15PM Comment 15 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 15-08-2025 02:14 PM Time Taken: 2.00 Notes: ETC extended from: 08/08/2025 to 15/08/2025
*** FRCS Meeting Notes ***

Q: When does v3 take effect? Will this break the currently working POS VMS commands? (E-SDC).

A: Already deployed – V2 compatibility mode currently switched on. All current POS and ESDC will work. 

Q: Where can we find tech specifications for Invoice cancellation?

A: Special Kind of Reformed – How it's implemented. It will be described in the tech specs published on the website. It's in the sandbox

Q: Please supply transition period details, from V2 to V3?

A: Switch off V2 compatibility. Exact dates by FRCS –

Q: Change of VAT Labels was very hectic.

A: Take into account the timelines

Q: Can vendors test v3 in one POS while using V2
A: Yes, can do that provided you are accredited in V3

Q: Why do the copy receipts and invoices require refiscalization?

A: Track if cashiers are issuing a suspicious number of copies – data collection requirements -

Q: Hello Kaushik here from Cloud Development, are you able to go over the changes required for Online POS?

A: No specific changes except the requirements to comply with the new updated version of the protocol.

Q: Some of our clients were using ESCD. Their old card has expired, and after replacing it with a new one, the VMS stopped working. Based on our investigation, it appears that the new hardware is not compatible with V3. Please advise on the possible solution to resolve this issue.

A: Request for V2 smart card.

Q: There is a tech guide, a downloadable PDF version

A: Help system in the sandbox. Does not download the entire guide. Download with Child 

Q: Is there a specific FONT and SIZE required on the invoice

A: No, there is not, as long as each type of invoice contains the necessary information, the font and size on an invoice are not a concern

INHOUSE - Can we have a better front that is more printer-friendly and darker when printed? The current font is not too visible.


08 Aug 202502:16PM Comment 16 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 15-08-2025 02:15 PM Time Taken: 4.00

# Comment 13 - Accreditation response has been provided with a request for additional documentation.

This was provided and accreditation resubmitted.


19 Aug 202502:30PM Comment 17 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 29-08-2025 02:28 PM Time Taken: 12.00 Notes: ETC extended from: 15/08/2025 to 29/08/2025

FRCS has responded with some additional requirements, such as a demonstration of "Multiple Payments", Documentation References, and some changes to "Advanced Receipts".

The changes have been completed and resubmitted for approval.


Attachments:
- General Documents:CertificationDocuments.zip
If you have any queries regarding this support incident, please email Support@LinkTechnologies.com.au and include the Case No: L13100 in the subject line of all emails regarding this issue.

Document size: 56.4 KB
For call complaints, please contact the Managing Director of the company using this form