This article describes a typical process at a cash register, from the opening of the day to the closing of the day. The Fiskal middleware offers various functions to support the individual process steps. The transmission of so-called audit log entries (events of the "Technical Event Protocol") are not shown for the sake of simplicity.
Variant 1
In this variant, the cash register is the leading system. All receipts are generated exclusively by the cash register and transmitted to the corresponding client.
The following table shows the individual calls of the cash register to the middleware.
Function | DocumentType | Notes |
PUT /.../createDocument | [90] = OpeningBalance |
Opens a transaction and indicates that the expected document is a daily opening (OpeningBalance).
Note: createDocument currently only required for the implementations Germany and Québec
|
POST /.../storeDocument | [90] = OpeningBalance |
The cash register autonomously generates a document of the type OpeningBalance and transmits it to the middleware. |
PUT /.../createDocument | [0] = Receipt |
Opens a transaction and indicates that the document to be expected is a sales document (receipt).
Note: createDocument currently only required for the implementations Germany and Québec
|
POST /.../storeDocument | [0] = Receipt |
The cash register generates a sales receipt and transmits it to the corresponding client in the middleware. |
... | divers |
Cash register transmits documents according to the respective transactions. |
PUT /.../createDocument | [99] = EndOfDay |
Opens a transaction and specifies that the document to be expected is a Z-report / end-of-day document (EndOfDay).
Note: createDocument currently only required for the implementations Germany and Québec
|
POST /.../storeDocument | [99] = EndOfDay |
Cash register autonomously generates a document of the type EndOfDay for the daily closing of the cash register and transmits this to the middleware. |
Variant 2
In this variant, although the POS system generates the opening document (OpeningBalance) independently, the Z-report / end-of-day document is generated by the middleware based on the totals of the documents transmitted during the day. The document generated by the middleware is then saved with POST /api/v1/transactions/storeDocument.
The following table shows the individual calls of the cash register to the middleware.
Function | DocumentType | Notes |
PUT /.../createDocument | [90] = OpeningBalance |
Opens a transaction and indicates that the expected document is a daily opening (OpeningBalance).
Note: createDocument currently only required for the implementations Germany and Québec
|
POST /.../storeDocument | [90] = OpeningBalance |
The cash register autonomously generates a document of the type OpeningBalance and transmits it to the middleware. |
PUT /.../createDocument | [0] = Receipt |
Opens a transaction and indicates that the document to be expected is a sales document (receipt).
Note: createDocument currently only required for the implementations Germany and Québec
|
POST /.../storeDocument | [0] = Receipt |
The cash register generates a sales receipt and transmits it to the corresponding client in the middleware. |
... | divers |
Cash register transmits documents according to the respective transactions. |
GET /.../{clientId} /endofdayDocument | [99] = EndOfDay |
The cash register requests the daily closing document / Z-report generated by the middleware. Middleware returns this.
Attention: No booking is made, only an EndOfDay document is returned!
|
PUT /.../createDocument | [99] = EndOfDay |
Opens a transaction and specifies that the document to be expected is a Z-report / end-of-day document (EndOfDay).
Note: createDocument currently only required for the implementations Germany and Québec
|
POST /.../storeDocument | [99] = EndOfDay |
Cash register transmits the EndOfDay closing document generated by the middleware back to the middleware. |
Variant 3
In contrast to the previous variants 1 and 2, the cash register here uses middleware functions to generate the daily opening (OpeningBalance) and daily closing without having to transmit the corresponding documents.
The following table shows the individual calls of the cash register to the middleware.
Function | DocumentType | Notes |
POST /.../openingSt |
[11] = PayIn |
By calling this function, the middleware generates a day opening for the closing statement of the corresponding day. Only a deposit (PayIn) is posted, but the cash balance is not reset. |
PUT /.../createDocument | [0] = Receipt |
Opens a transaction and indicates that the document to be expected is a sales document (receipt).
Note: createDocument currently only required for the implementations Germany and Québec
|
POST /.../storeDocument | [0] = Receipt |
The cash register generates a sales receipt and transmits it to the corresponding client in the middleware. |
... | divers |
Cash register transmits documents according to the respective transactions. |
POST /.../cashpointClose |
Äquivalent zu: [99] = EndOfDay |
By calling this function, the middleware automatically posts a daily closing with a closing document / Z-report
Attention: Only a daily closing is posted, but no document is returned.
Note: To be able to use cashpointClose, the option "Simple cashpoint closing" must be activated in the configuration.
|
Related Articles
Daily closing of the cash register
Implementation End of day (Cashpoint closing)
Comments
0 comments
Please sign in to leave a comment.