The Slovenian 'Act on Tax Invoice Verification by the Tax Office' (ZDavPR) stipulates, amongst other things, that each tax payer is obliged to register his Business Premises in the FURS system.
The registration of each business premises is based on the information entered in the RetailForce portal regarding the individual branches / locations (= stores). In addition to the usual master data for the respective store, further store parameters must be entered in Slovenia, as described in the articles "Configuration for Slovenia" and "Configuring mobile business premises in RetailForce".
When a terminal (a cash register) is initialized, the corresponding store (= business premises) under which the terminal was created is automatically registered in the FURS system.
FURS Registration
The store view has been updated to include the 'FURS registration' element. On the right-hand side, below the Action Items, the current registration status and any previous reports relating to the store are displayed.
Changes
Changes to the store’s master data, such as
- Address
- Store parameters
are automatically reported to FURS.
The report is submitted as soon as the new entry is saved.
Attention: the FURS notification is sent immediately. However, the store information stored in the client is not automatically updated. To do this, the client configuration must be updated using the portal function "Push Configuration" or the client function "UpdateConfiguration".
What triggers a FURS notification?
The following events trigger a report to the FURS system of the Slovenian tax authority.
| Event in Portal | Report to FURS |
| First terminal of the store is initialised | Initial registration of the relevant business premises. |
| Change to store address, cadastral data or type of business premises | Update of the registration. |
| Change to the 'store number' | Closure of the existing registration and re-registration under the new store number. |
| Setting the 'closing date' | The business premises are reported as 'closed' in FURS (only works if no active terminals / clients exist). |
| Replacement or upload of a certificate | Incorrect registrations, due to an invalid or expired certificate, are repeated. |
| The user clicks on 'Register again' | The current registration is resubmitted to FURS. |
| Every 6 hours | Any changes that were overlooked are reported retrospectively. |
What happens after saving?
The following steps are carried out when changes to the store’s master data (e.g. house number) are made and saved.
| Event | Description |
| Upon saving | The change is checked and the FURS change is placed in a queue. Incomplete details (e.g. missing opening hours) are not submitted – missing data is displayed on the store page. |
| Queue processing | Shortly afterwards, the cloud system submits the signed registration to the FURS system. |
| FURS accepts | The shop page displays the change; the data is added to the business premises report. |
| FURS rejects | The shop page displays the status 'Failed' and the reason for the rejection. The data may need to be corrected and resubmitted. |
| FURS unreachable | The system repeats the submission periodically (maximum of 10 attempts; after that, the submission must be sent manually). |
Business Premises Report
Reports on the registration status of business premises are provided for Slovenian organisations and companies.
Below the action items (on the right) for the relevant entity (organisation or company), you will find the 'Business premises (FURS)' element with a 'Download' button.
Here you can download the so-called 'Internal Record of Business Premises'.
Checking registration status
In the new 'FURS registration' element, which is displayed on the right-hand side of the relevant store, below the action items, you can check the current FURS registration status of the corresponding business premises.
This is done by clicking the 'Check FURS' button.
For test terminals / test clients, the FURS notification is sent to the test environment accordingly.
Comments
0 comments
Please sign in to leave a comment.