In addition to securing the cash register journal, which contains data on sales transactions of the electronic recording system ("cash register"), in some countries a so-called event log must be kept and in some cases also secured via a digital signature or other means. In the RetailForce infrastructure, this log method is called AuditLog.
Currently, the technical event log is used in the following countries (as of 04/2022). However, in terms of a complete implementation, we recommend integrating the event log in all countries that you map via the RetailForce Fiscal Middleware. The middleware decides independently 1) how and whether the event log must be processed in the respective country and 2) which events must be recorded for this:
| Country | Label | must/can | Notes |
| Denmark | EventLog | must | part of the SAF-T export |
| France | Journal des Evènements Techniques (JET) / Technical Event Log | must | part of NF525-certification (Infocert) |
| Austria | Stammdatenprotokoll / Master Data Protocol |
can |
Acc. to the Cash Register Directive 2012 |
| Sweden | Log Memory / Audit Log | can |
Logging of other transactions |
Event entries (audit log entries) are transmitted to the RetailForce fiscalisation service via the function:
The following is a list of all audit log events that can be managed by the RetailForce system.
The following information is provided:
Headline ... Event designation in the RetailForce system
Code ... RetailForce Event-Code
Description ... Description of the event
Method ... Transmission method - Events are set automatically by the Fiscal Middleware, or must be transmitted by the recording system. Automatic recording only takes place if DocumentTypes etc. are used correctly.
Denmark ... SAF-T EventCode (more information on the danisch EventCodes)
France ... NF525 JET Code (Inforcert)
Note in "[ ]":
- [M] ... must field - mandatory information to meet the requirements of NF525.
- [C] ... can field - are mandatory as soon as this function is provided by the electronic recording system ("cash register") or the data is available / recorded.
- [O] ... optional - optional data, mainly for information purposes.
DocumentReprintOther
| Code | 1 |
| Description | Used to record the reprinting / duplicating of a document |
| Method | |
| Denmark | 13014 |
DocumentSuspend
| Code | 2 |
| Description |
Used to track suspended / parked documents (recording in progess but not yet validated / issued). "Parked" in this case means that the final status of the document is not yet defined, i.e. whether the recording will be cancelled or completed. |
| Method | |
| Denmark | 13010 |
| France | 320 [C] |
DocumentResume
| Code | 3 |
| Description | Used when a previously suspended transaction is resumed |
| Method | |
| Denmark | 13011 |
DocumentTrainingModeOn
| Code | 10 |
| Description | When starting a training, demo or education mode of the recording system (in many countries, receipts issued when using this mode need to be specially marked) |
| Method | automatic |
| Denmark | 13023 |
| France |
100 [C] |
DocumentTrainingModeOff
| Code | 11 |
| Description | End of use of the training, demo or education mode of the recording system |
| Method | |
| Denmark | 13024 |
| France | 105 [C] |
DocumentTypeSales
| Code | 100 |
| Description | Sales document, cash receipt; mapped to DocumentType [0] = Receipt in RetailForce DocumentObjectModel v 1.1.0 |
| Method | automatic |
| Denmark | 13012 |
DocumentTypeReturn
| Code | 101 |
| Description | Return receipt (issued when previously provided goods or services are returned by the customer) |
| Method | automatic |
| Denmark | 13013 |
| France | 326 [C] |
DocumentTypeProforma
| Code | 102 |
| Description | Proforma invoice - preliminary bill or estimated invoice, can be used to propose the details of the upcoming transaction. Often used to show the value of a consignment of goods |
| Method | automatic |
| Denmark | 13015 |
DocumentTypeDelivery
| Code | 103 |
| Description | Delivery note - document that lists all the goods included in a delivery, often also referred to as dispatch note, or goods receipt |
| Method | automatic |
| Denmark | 13016 |
DocumentTypeTraining
| Code | 104 |
| Description | Training receipt - a document created using a training, demo or education mode of the recording system. |
| Method | automatic |
| Denmark | 13017 |
| Sweden | [M] |
DocumentTypeWithDrawal
| Code | 105 |
| Description | Skimming - special type of withdrawal (DocumentTypePayOut = 106); With a skimming, money is withdrawn from the cash register, e.g. to take it to the bank during the day. The cash balance of the cash register is reduced in the process. |
| Method | automatic |
| Denmark | 13019 |
DocumentTypePayOut
| Code | 106 |
| Description | Record a pay-out form the cash register - e.g. when taking money out of the cash drawer |
| Method | automatic |
DocumentTypePayIn
| Code | 107 |
| Description | Record a pay-in to the cash register - e.g. when change is deposited in the cash drawer |
| Method | automatic |
DocumentTypeOpeningBalance
| Code | 108 |
| Description | Opening balance (opening stock) of the cash register |
| Method | automatic |
DocumentTypeNullReceipt
| Code | 109 |
| Description | Zero receipt - receipt with sum = 0; used, for example, within the framework of the Austrian Cash Register Security Ordinance (RKSV) |
| Method | automatic |
DocumentTypeInvoice
| Code | 110 |
| Description | Invoice - regular sales document |
| Method | automatic |
DocumentTypeOther
| Code | 120 |
| Description | Other / own document types not covered by codes 100 - 119 and 121 - 139 (DocumentTypeMiscellenousNonFiscal) |
| Method | automatic |
| Denmark | 13018 |
DocumentTypeVoid
| Code | 121 |
| Description | Used to void a previously issued document |
| Method | automatic |
| Denmark | 13028 |
| France | 190 [C] |
DocumentTypeLongTermOrder
| Code | 122 |
| Description | Use for supporting document: Long Term Order in Germany, "note (bill)" in France, mostly in gastronomy - e.g. kitchen slip, table order |
| Method | automatic |
DocumentTypePaymentConfirmation
| Code | 123 |
| Description | Payment confirmation - used to confirm receiving a payment for certain service or goods |
| Method | automatic |
DocumentTypeCustomerOrder
| Code | 124 |
| Beschreibung | Customer Order |
| Art | automatic |
DocumentTypeInventory
| Code | 125 |
| Beschreibung | Cash balance booking |
| Art | automatic |
DocumentTypePurchase
| Code | 126 |
| Beschreibung | Purchases which are recorded via the POS-system |
| Art | automatic |
DocumentReprintLongTermOrder
| Code | 140 |
| Description | Used when duplicating / reprinting supporting documents (see code: 122) |
| Method | |
| France | 155 [C] |
DocumentReprintPaymentConfirmation
| Code | 141 |
| Description | Used when payment confirmations (see code: 123) are duplicated / reprinted |
| Method | |
| France | 156 [C] |
DocumentAbandonLongTermOrder
| Code | 150 |
| Description |
Used to track recorded supporting documents (long term order, note,...) that have been previously recorded / validated but for which no receipt has been issued. So an order was "placed", but no settlement was made later. |
| Method | |
| France | 324 [C] |
DocumentTraceUnprintLongTermOrder
| Code | 151 |
| Description |
this event is used to trace order document ("long term oder" in Germany, “note” in France) which have been successfully signed but have not been printed, but electronically issued. Infocert introduced this event for the law of Feb. 10th 2020, on the fight against waste and the circular economy. Example: An order was successfully placed in the restaurant and the document was signed. However, there is no printout but the order is only displayed digitally, e.g. on a kitchen monitor. |
| Method | |
| France | 329 [C] |
DocumentCancelLine
| Code | 160 |
| Description | Cancellation of an article line - applies to supporting documents prior to the transaction |
| Method | |
| France | 323 [C] |
DocumentVoidLine
| Code | 161 |
| Description | Cancellation(s) of article(s) after order |
| Method | |
| France | 325 [C] |
DocumentUpdatePayment
| Code | 170 |
| Description | Used to track changing the method of payment after issuing the receipt |
| Method | |
| France | 420 [C] |
DocumentUpdateLongTermOrder
| Code | 171 |
| Description | Used to track updates to already issued (signed) supporting documents (long term order, note,...) |
| Method | |
| France | 327 [C] |
DocumentUpdateLine
| Code | 172 |
| Description | Used to track updates / changes to offered articles (lines) |
| Method | |
| France | 328 [C] |
DocumentUpdateTable
| Code | 173 |
| Description | Used to track change of table (in gastronomy / catering industry) already assigned to a supporting document (long term oder, note,...) |
| Method | |
| France | 430 [C] |
DrawerOpen
| Code | 200 |
| Description | Used to record opening of the cash drawer |
| Method | |
| Denmark | 13005 |
DrawerClose
| Code | 201 |
| Description | Used to record closing of the cash drawer |
| Method | |
| Denmark | 13006 |
PrinterUnavailable
| Code | 210 |
| Description | Used to track unavailability of printer |
| Method | |
| France | 150 [C] |
PrinterAvailable
| Code | 211 |
| Description | Restore communication with the printer |
| Method |
UserLogin
| Code | 400 |
| Description | Used to track login of a user |
| Method | |
| Denmark | 13003 |
UserLogout
| Code | 401 |
| Description | Used to track when a user logges out |
| Method | |
| Denmark | 13004 |
UserRightsChange
| Code | 410 |
| Description | Used to track when user rights changed (FR: Any change in user rights, profiles, types impacting certified features must be traced by this event) |
| Method | |
| France | 130 [C] |
ApplicationStMethod
| Code | 500 |
| Description | Start of the application |
| Method | |
| Denmark | 13001 |
| France | 80 [C] |
ApplicationShutDown
| Code | 501 |
| Description | Shutdown / stopping of the terminal / application |
| Method | |
| Denmark | 13002 |
| France | 40 [C] |
ApplicationUpdate
| Code | 502 |
| Description | Used to document updates to the (cash register) application. In France, major updates are recorded via this event. |
| Method | |
| Denmark | 13007 |
| France | 250 [M] |
ApplicationUpdateMinor
| Code | 503 |
| Description | Used to document minor updates of the (cash register) application. |
| Method | |
| France | 255 [C] |
ApplicationFiscalMiddlewareUpdate
| Code | 504 |
| Description | Used to document updates to RetailForce Fiscal Middleware. |
| Method |
ApplicationEmergencyModeOn
| Code | 505 |
| Description | Used to record the activation of a possible autonomous mode / emergency mode of the recording system (FR: autonomous mode corresponds to an interruption of the connection of a terminal to the central system so that it works offline). |
| Method | |
| Denmark | 13026 |
| France | 70 [C] |
ApplicationEmergencyModeOff
| Code | 506 |
| Description | Used to record the deactivation of autonomous mode / emergency mode and the return to normal operation (FR: The end of emergency mode corresponds to a reconnection of the terminal, which causes the end of autonomous mode and the restart of centralised/connected mode). |
| Method | |
| Denmark | 13027 |
| France | 120 [C] |
ApplicationInitialize
| Code | 510 |
| Description | Data initialization - may occure the first time the application / software is used |
| Method | automatic |
| France | 260 [C] |
ApplicationAddWorkstation
| Code | 511 |
| Description | Used when a new workstation / input device is added or commissioned. |
| Method | |
| France | 126 [O] |
ApplicationDeleteWorkstation
| Code | 512 |
| Description | Used when a new workstation (workstation) / input device is taken out of service / decommissioned |
| Method | |
| France | 127 [O] |
MasterDataItemPriceChange
| Code | 700 |
| Description | Used to track price changes |
| Method | |
| Denmark | 13021 |
MasterDataItemPriceLookup
| Code | 701 |
| Description | Used to track look-up of prices |
| Method | |
| Denmark | 13022 |
MasterDataItemUpdateCompany
| Code | 702 |
| Description | Used to track any changes in the data related to the taxable company identification (e.g. changes in: address, company ID, company name, FR: SIRET-No.,...) |
| Method | automatic |
| France | 410 [C] |
TransferOwnership
| Code | 899 |
| Description | Used in case of changes of entity owning and using the application (e.g. modification of the company ID, FR: SIREN) |
| Method | |
| France | 128 [C] |
DataIntegrityBackupDatabase
| Code | 900 |
| Description | Used when a backup of the database is made |
| Method | |
| France | 230 [C] |
DataIntegrityRestoreDatabase
| Code | 901 |
| Description | Used when the database is restored with a previously made backup; attention: differs from DataIntegrityDataRecovery = 905! |
| Method | |
| France | 220 [C] |
DataIntegrityPurgeDatabase
| Code | 903 |
| Description | Used when the database of the application is purged (e.g. due to insufficiant memory), FR: attention - periodical closing and archiving of fiscal data MUST precede purge |
| Method | |
| France | 200 [C] |
DataIntegrityPurgeEventLog
| Code | 904 |
| Description | Used when the Event Log (FR: Technical Event Log) is purged, FR: attention - only "purgeable" events of the JET may be deleted and only after archiving of the old JET. |
| Method | |
| France | 205 [C] |
DataIntegrityDataRecovery
| Code | 905 |
| Description | Only used to record data recovery when switching to a new system (e.g. in the event of a hardware failure, or planed due to exchange of hardware); attention - differs from DataIntegrityRestoreDatabase = 901! |
| Method | |
| France | 210 [C] |
DataIntegrityForwardData
| Code | 910 |
| Description | Used when data is forcedly forwarded to a central system (from an input device) |
| Method | |
| France | 123 [C] |
DataIntegrityConsolitationComplete
| Code | 911 |
| Description | Used when data are consolidated at a central system after the end of an emergency mode (after ApplicationEmergencyModeOff = 506) |
| Method | |
| France | 125 [C] |
DataIntegrityFailure
| Code | 949 |
| Description | Used when detecting an integrity failure in secured data (integrity is broken when secured data have been altered subsequentially) |
| Method | |
| France | 90 [M] |
DataSequenceChange
| Code | 950 |
| Description | Used when changing the continuous sequence management mode (change in numbering methods due to temporal or organisational changes) |
| Method | |
| France | 10 [C] |
DataSequenceFailure
| Code | 951 |
| Description | Used when a break in the continuous sequence (document numbers) has been detected (concerns the detection of a break in the continuous document numbering, except when changing the numbering mode, which is managed by the event DataSequenceChange = 950). |
| Method | |
| France | 95 [C] |
DataImportExternal
| Code | 960 |
| Description | Used when importing data from a third party / external software |
| Method | |
| France | 140 [C] |
DataIExportAccounting
| Code | 970 |
| Description | Used when the application generates an export file for import into an accounting software |
| Method | |
| France | 180 [C] |
DataExportGeneric
| Code | 971 |
| Description | Used when exporting generic data (except: DataExportAccounting = 970), e.g. to stock managment systems, or other third party applications/systems |
| Method | |
| France | 110 [C] |
FiscalPeriodClosingDay
| Code | 1000 |
| Description | Used when creating a daily closing / Z report |
| Method | automatic |
| Denmark | 13009 |
| France | 50 [M] |
FiscalPeriodClosingMonth
| Code | 1001 |
| Description | Used when creating a monthly closing |
| Method | automatic |
| France | 50 [M] |
FiscalPeriodClosingYear
| Code | 1002 |
| Description | Used when creating an annual closing of closing of the fiscal year |
| Method | automatic |
| France | 60 [M] |
FiscalReportClosingDay
| Code | 1010 |
| Description | Used when creating an intermediary closing / X report |
| Method | |
| Denmark | 13008 |
FiscalArchiveYear
| Code | 1100 |
| Description | Used when end of year / end of fiscal year is sent to archive |
| Method | |
| France | 30 [M] |
FiscalArchiveIntermediate
| Code | 1101 |
| Description | Used when moving files to archive |
| Method | |
| France | 20 [C] |
FiscalJournalExport
| Code | 1200 |
| Description | Used when exporting the archived journal data to an external medium |
| Method | |
| France | 440 [O] |
FiscalSignatureUpdateKey
| Code | 1300 |
| Description | Used to track changes in the key pair of the electronic signature |
| Method | |
| France | 450 [C] |
FiscalAudit
| Code | 1400 |
| Description | Used in case that the application allows the creation of a "Tax-Auditor" user profile; FR: Start/end of tax audit, This event is used to track the first login of this user |
| Method | |
| France | 280 [C] |
FiscalAuditFileTransfer
| Code | 1401 |
| Description | Used to document file transfer at the request of the tax administration |
| Method | |
| France | 295 [C] |
FiscalUpdateAffiliation
| Code | 1401 |
| Description | |
| Method | |
| France | 270 [C] |
Other
| Code | 10000 |
| Description | Used to document any other / own events |
| Method | |
| Denmark | 13999 |
Comments
0 comments
Please sign in to leave a comment.