Fiscal Transaction
Describes the tracking of fiscal transactions and the operations log in the POS Core archive.
In the Archive for Fiscal Transactions, metadata is stored for each transaction so that communication with the respective interface can be traced.
| Field | Description |
|---|---|
| Location | Location code |
| Cash Register | Cash register code |
| Serial No. | Consecutive serial number |
| Provider | Fiscal provider |
| Module | Fiscal module |
| Receipt Location | Receipt location code |
| Receipt Cash Register | Receipt cash register code |
| POS Process | POS process |
| Receipt No. | Receipt number |
| Document Type | Type of receipt |
| Slip Type | Type of slip |
| Transferred | Indicates that the transaction was transferred |
| Processed | Indicates that the transaction was processed |
| Operations Log | Number of operations log entries |
| Result Code | Shows the number of error messages and events |
| Error Message | Shows the error message |
| Contains Warnings | Indicates that the transaction contains warnings |
| Request Date | Date of the request |
| Request Time | Time of the request |
| Response Date | Date of the response |
| Response Time | Time of the response |
| Cash Register Setup Initialized | Indicates whether the cash register setup has already been initialized for fiscalization |
| Request URI | Request address |
| HTTP Status Code | HTTP status code |
| HTTP Status Description | HTTP status code name |
Operations Log
For an entry with a result code, it must be documented what triggered this entry and when and how the error was resolved.
Note: These are events that are not the fault of the module provider, such as hardware failures, loss of internet connection, and similar issues.
The Operations Log is available for documenting these events.
Short explanations of the events can be recorded here and traced during a financial audit.
