Skip to content

Commit

Permalink
Merge pull request #175 from fiskaltrust/user/tsc/utc
Browse files Browse the repository at this point in the history 
Clarify that moments should be UTC
  • Loading branch information
@TSchmiedlechner
TSchmiedlechner committed Mar 23, 2021
2 parents 132a827 + 7f1fcf7 commit 4f582ee
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions doc/general/data-structures/data-structures.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ The information necessary for processing of a receipt is provided through the co
| `ftPosSystemId` | `guid/string` | null<br />optional | This field identifies and documents the type and software version of the PosSystem sending the request. It is used for audits and as a base for commission calculation. The PosSystem itself has to be created in the portal and its ID can be implemented as a constant value by the PosCreator. | 0- |
| `cbTerminalID` | `String`<br />Max 1k | empty-string<br />mandatory | The unique identification of the input station/ cash register within a ftCashBoxID | 0- |
| `cbReceiptReference` | `String`<br />Max 1k | empty-string<br />mandatory | Reference number returned by the cash register. Ideally, this value would be a unique receipt number for the cash register, to allow saving of the return value to the cash register data set. | 0- |
| `cbReceiptMoment` | `DateTime` | null<br />mandatory | The time of receipt creation. Must be provided in UTC. | 0- |
| `cbReceiptMoment` | `DateTime` | null<br />mandatory | The time of receipt creation. Must be provided in UTC, e.g. `2020-06-29T17:45:40.505Z`. | 0- |
| `cbChargeItems` | `ChargeItem[]` | null<br />mandatory | List of services or items sold. | 0- |
| `cbPayItems` | `PayItem[]` | null<br />mandatory | List of payment received. | 0- |
| `ftReceiptCase` | `Int64` | 0<br />mandatory | Type of business transaction ac-cording to the [reference table](../reference-tables/reference-tables.md#t-service-status-ftstate-22) in the appendix. It is used to choose the right processing logic. | 0- |
Expand Down Expand Up @@ -148,7 +148,7 @@ The details of fields supported by this data structure are outlined in the table
| `Unit` | `String`<br />Max 1k | empty-string<br />optional | Unit of measurement | 0- |
| `UnitQuantity` | `Decimal`? | null<br />optional | Quantity of the service(s) of receipt entry, displayed in indicated units. | 0- |
| `UnitPrice` | `Decimal`? | null<br />optional | Gross price per indicated unit. | 0- |
| `Moment` | `DateTime` | null<br />optional | Time of service (year, month, day, hour, minute, second) | 0- |
| `Moment` | `DateTime` | null<br />optional | Time of service (year, month, day, hour, minute, second). Must be provided in UTC, e.g. `2020-06-29T17:45:40.505Z`. | 0- |

<span id="_Ref527915365" class="anchor"></span>*Table 5. Charge Items Entry (ftChargeItems)*

Expand Down Expand Up @@ -199,7 +199,7 @@ The ftPayItemCase field is particularly important for the correct processing of
| `CostCenter` | `String`<br />Max 1k | empty-string<br />optional | Indicator for transfer into cost accounting (type, centre and payer) | 0- |
| `MoneyGroup` | `String`<br />Max 1k | empty-string<br />optional | This value allows the logical grouping of payment types | 0- |
| `MoneyNumber` | `String`<br />Max 1k | empty-string<br />optional | This value identifies the payment type | 0- |
| `Moment` | `DateTime`? | now<br />optional | Time of payment | 0- |
| `Moment` | `DateTime`? | now<br />optional | Time of payment. Must be provided in UTC, e.g. `2020-06-29T17:45:40.505Z`. | 0- |

<span id="_Toc510009094" class="anchor"></span>*Table 6. Pay Items Entry*

Expand Down

0 comments on commit 4f582ee

Please sign in to comment.