Frequently Asked Question

How can we use available APIs to avoid duplicates when issuing fiscal invoices?
Last Updated 9 months ago

For each request sent to an SDC, the POS needs to get a response before sending another request.

In other words, the POS should wait for a response before being able to issue another invoice.

Note that in production environment(s), the infrastructure is capable of supporting almost instantaneous response from a V-SDC. In the Sandbox environment, the delay could happen because the V-SDC server is located in Europe and hence the delay. That delay should not happen in production unless there are unrelated issues, such as poor internet connection or something similar.

In addition to that, you can find the differences between offline and online POS integration here:

Jurisdictions

Entry

Samoa
Choosing an Appropriate Model
Fiji
Choosing an Appropriate Model
Serbia
Choosing an Appropriate Model
Republika Srpska (RS)Choosing an Appropriate Model

In case a POS is connected to a V-SDC only (provided such scenario is allowed by law), there is a way to instruct cashier to rectify these incidents in the following manner:

1. POS sends invoice request for fiscalization to V-SDC service
2. POS receives time-out
3. Prior to sending the next invoice request, inform the cashier that such action can cause the invoice to be duplicated
4. Cashier (authorized person) can access TAP to check if any double invoices are issued and perform corrective measures (refund)

You can read more about issuing refunds in the articles below:

Jurisdictions

Entry

Samoa
Invoice Actions Buttons
Fiji
Invoice Actions Buttons
Serbia

Fiscal Invoice


Please Wait!

Please wait... it will take a second!