From 52b633282fa49361f3ef22c1c2eef02f9aae4373 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=20Rivi=C3=A8re?= Date: Mon, 8 May 2023 08:14:02 +0200 Subject: [PATCH 01/20] ref-tables FR-AT reworked --- .../reference-tables/1- ftState.md | 31 +++ .../reference-tables/2 - ftReceiptCase.md | 34 +++ .../reference-tables/3- ftReceiptCaseFlag.md | 23 ++ .../reference-tables/4 - ftChargeItemCase.md | 51 ++++ .../reference-tables/5 - ftPayItemCase.md | 35 +++ .../reference-tables/6 - ftSignatureFormat.md | 30 +++ .../reference-tables/7 - ftSignatureType.md | 19 ++ .../reference-tables/8 - ftJournalType.md | 247 ++++++++++++++++++ .../reference-tables/1 - ftState.md | 18 ++ .../reference-tables/2 - ftReceiptCase.md | 41 +++ .../reference-tables/3 - ftReceiptCaseFlag.md | 24 ++ .../reference-tables/4 - ftChargeItemCase.md | 55 ++++ .../reference-tables/5 - ftPayItemCase.md | 37 +++ .../reference-tables/6 - ftSignatureType.md | 25 ++ .../reference-tables/7 - ftJournalType.md | 34 +++ .../reference-tables/8 - ftJournalTypeFlag.md | 14 + 16 files changed, 718 insertions(+) create mode 100644 doc/middleware-at-rksv/reference-tables/1- ftState.md create mode 100644 doc/middleware-at-rksv/reference-tables/2 - ftReceiptCase.md create mode 100644 doc/middleware-at-rksv/reference-tables/3- ftReceiptCaseFlag.md create mode 100644 doc/middleware-at-rksv/reference-tables/4 - ftChargeItemCase.md create mode 100644 doc/middleware-at-rksv/reference-tables/5 - ftPayItemCase.md create mode 100644 doc/middleware-at-rksv/reference-tables/6 - ftSignatureFormat.md create mode 100644 doc/middleware-at-rksv/reference-tables/7 - ftSignatureType.md create mode 100644 doc/middleware-at-rksv/reference-tables/8 - ftJournalType.md create mode 100644 doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/1 - ftState.md create mode 100644 doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/2 - ftReceiptCase.md create mode 100644 doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/3 - ftReceiptCaseFlag.md create mode 100644 doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/4 - ftChargeItemCase.md create mode 100644 doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/5 - ftPayItemCase.md create mode 100644 doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/6 - ftSignatureType.md create mode 100644 doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/7 - ftJournalType.md create mode 100644 doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/8 - ftJournalTypeFlag.md diff --git a/doc/middleware-at-rksv/reference-tables/1- ftState.md b/doc/middleware-at-rksv/reference-tables/1- ftState.md new file mode 100644 index 00000000..cd4a04dd --- /dev/null +++ b/doc/middleware-at-rksv/reference-tables/1- ftState.md @@ -0,0 +1,31 @@ +--- +slug: /poscreators/middleware-doc/austria/reference-tables +title: Service Status: ftState +--- + +## Reference tables + +This chapter expands on the reference tables covered in the Chapter ["Reference tables"](../../general/reference-tables/reference-tables.md) of the General Part, with country-specific information applicable to the Austrian market. + +### Service Status: ftState + +The table below describes it supported statuses for the ftState field following the Austrian law. The ftState from this reference table and the general part of this documentation can be combined through the logic operator "OR". For example `0x4154000000000010` (monthly report due) and `0x4154000000000008` combined through `OR` results in `0x4154000000000018`. + +The country-specific code is made of the country's code value following the ISO-3166-1-ALPHA-2 standard, converted from ASCII into hex. For Austria (AT) this is `0x4154`, which results in `0x4154000000000000` as the value for the "ready" status. + +| **Value** | **Description** | **Middleware-Version** | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------| +| `0x4154000000000001` | "out of service"
No RKSV signatures are generated or sent back. No RKSV-DEP is written, as nothing is being signed. The E131-DEP records requests and responses. | 1.0 | +| `0x4154000000000002` | "SSCD temporary out of service"
For at least one receipt, it was not possible to receive the signature from an allocated SSCD. Thus, the security mechanism has been put into "signature creation device out of service" mode. Regardless of whether an allocated SSCD is available again or not, the mode remains in place until, via zero receipt, all previous receipts can be signed. If this mode is activated, an out of service signature, in accordance with the RKSV, is generated and sent back. | 1.0 | +| `0x4154000000000004` | "SSCD permanently out of service"
The status "SSCD temporary out of service" was activated more than 48h ago. Thus a FinanzOnline notification has been generated.
For conduct and termination of this mode, see "SSCD temporary out of service". | 1.0 | +| `0x4154000000000008` | "subsequent entry activated"
At least one receipt has been transferred with a subsequent entry flag. In order to finalize the subsequent entry and leave the mode, it is necessary to generate a zero receipt. This zero receipt signs and secures the preliminary receipts accordingly to the RKSV. | 1.0 | +| `0x4154000000000010` | "monthly report due"
If the latest monthly or annual report are is in the current month, the service will signal this. This status does not impact the signature conduct of the service; it is merely an indicative notification. | 1.0 | +| `0x4154000000000020` | "annual report due"
Same conduct as for "monthly report due" | 1.0 | +| `0x4154000000000040` | "message / notification pending"
A status message and/or FinanzOnline notification is ready for collection.
Using a zero receipt, the messages can be retrieved and archived or processed in bookkeeping. | 1.0 | +| `0x4154000000000080` | "backup SSCD in use"
The receipt was signed by a signature creation unit configured for backup use. | 1.1.17248 | + + + +*Table 21. Service status: ftState for AT - RKSVO* + + diff --git a/doc/middleware-at-rksv/reference-tables/2 - ftReceiptCase.md b/doc/middleware-at-rksv/reference-tables/2 - ftReceiptCase.md new file mode 100644 index 00000000..4a8e937b --- /dev/null +++ b/doc/middleware-at-rksv/reference-tables/2 - ftReceiptCase.md @@ -0,0 +1,34 @@ +--- +slug: /poscreators/middleware-doc/austria/reference-tables +title: Type of Receipt: ftReceiptCase +--- + +### Type of Receipt: ftReceiptCase + +The ftReceiptCase indicates the receipt type and defines how it should be processed by the fiskaltrust.SecurityMechanism in accordance with the Austrian law. + +For Austria (AT) the country code is `0x4154`. Thus, the value for an unknown ftReceiptCase in Austria is `0x4154000000000000`. + +| **Value** | **Description** | **Middleware- Version** | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| `0x4154000000000000` | "unknown type of receipt for AT"
This receipt is processed like a cash transaction with RKSV requirement. | 1.0 | +| `0x4154000000000001` | "Cash transaction with RKSV requirement for AT"
The fiskaltrust decision tree is being run through, and, if needed, the signature process is started and the cumulative counter adjusted respectively.
An example of a signature being needed is an "other service" paid for with a "credit card".
An example of a case where no signature is needed is a receipt with only "no own sales" on it which has been paid for by "credit card". | 1.0 | +| `0x4154000000000002` | "zero receipt"
Charge items block (ftChargeItems) as well as pay items block (ftPayItems) are empty.
The "zero receipt" can be used to test operability by collecting a service status notification, such as an out-of-service notification for FinanzOnline. | 1.0 | +| `0x4154000000000003` | "initial operation receipt"
The request is only valid as a zero receipt. The initial operation procedure is started. When using fiskaltrust.SecuritymMechansimsPlus, the receipt will also be checked for correctness. | 1.0 | +| `0x4154000000000004` | "out of operation receipt"
The procedure to take the service out of operation is started.
The request is only valid as a zero receipt. When using the fiskaltrust.Carefree package, the receipt will also be checked for correctness, and the notification to the "FinanzOnline" will be performed automatically in the background. | 1.0 | +| `0x4154000000000005` | "monthly receipt"
The procedure for the creation of the monthly receipt is started. The request is only valid as a zero receipt. | 1.0 | +| `0x4154000000000006` | "annual receipt"
The procedure for the creation of the annual receipt is started.
The request is only valid as a zero receipt. When using the fiskaltrust.Carefree package, the receipt will also be checked for correctness, and the notification to the "FinanzOnline" will be performed automatically in the background. | 1.0 | +| `0x4154000000000007` | "cash transaction RKSV relief or cash revenue law"
This is used to process cash transactions which do not have an RKSV requirement (e.g. emptying a vending machine). | 1.0 | +| `0x4154000000000008` | "target business"
An outgoing invoice which does not necessarily have to be issued by a cash register but can also be issued by an invoicing system. | 1.0 | +| `0x4154000000000009` | "delivery note"
Information about an internal or external delivery or also a transfer into a different IT system. The sales tax statement is issued through the outgoing invoice or in the other system. | 1.0 | +| `0x415400000000000A` | "cash deposit"
For example the payment of a target calculation, or deposit on the customer card.
Usually, the receipt data only includes pay items while the charge items block remains empty. Since the total amount must always be zero, you must use a negative pay item to balance the sum of pay items to zero. | 1.0 | +| `0x415400000000000B` | "cash pay-out"
For example to pay for deliveries . | 1.0 | +| `0x415400000000000C` | "means of payment transfer"
For example the switching between "cash", "credit card", "ATM", etc. This function is also used to issue vouchers. | 1.0 | +| `0x415400000000000D` | "protocol"
Simple protocol function. The data sets that need to be logged can be transferred in the field ftReceiptCaseData in manufacturer-specific JSON format. For example, opening the cash drawer or changing master data. | 1.0 | +| `0x415400000000000E` | "Internal / material consumption"
For example recording breakages or own consumption. | 1.0 | +| `0x415400000000000F` | "sales in an online shop, telephone-/fax orders"
Through the cash revenue law, sales from online shops and similar are exempted, even if these have been paid by credit card or comparable means of payments with RKSV requirement but not paid on business premises. As a cash transaction, the issued receipt comes with a recording requirement in accordance with §131 BAO and needs to be processed in bookkeeping. | 1.0 | +| `0x4154000000000010` | "foreign sales"
Foreign sales do not have an RKSV-requirement. As a cash transaction, the issued receipt comes with a recording requirement in accordance with §131 BAO and need to be processed in bookkeeping. Foreign requirements, for example in connection with receipt generation or cash register requirements, have to be taken into account. | 1.0 | + + + +*Table 22. Type of Receipt: ftReceiptCase (AT - RKSVO)* diff --git a/doc/middleware-at-rksv/reference-tables/3- ftReceiptCaseFlag.md b/doc/middleware-at-rksv/reference-tables/3- ftReceiptCaseFlag.md new file mode 100644 index 00000000..a8d0207f --- /dev/null +++ b/doc/middleware-at-rksv/reference-tables/3- ftReceiptCaseFlag.md @@ -0,0 +1,23 @@ +--- +slug: /poscreators/middleware-doc/austria/reference-tables +title: Reference tables +--- + +#### ftReceiptCaseFlag + +This table expands on the values provided in the table ["Type of Receipt: ftReceiptCaseFlag"](../../general/reference-tables/reference-tables.md#t-type-of-receipt-ftreceiptcaseflag-64) of with values applicable to the Austrian market. + +| Value | Description | Middleware-Version | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| `0x0000000000010000` | "out of service"
The transferred receipt contains data which has been created during an outage of the security mechanism. The original receipts are available in handwritten or digital format and must now be transferred and subsequently consolidated and signed via zero receipt. In order to decide whether it is a temporary or permanent (more than 48 hours) outage of the security mechanism (for example in case of theft), the "oldest" or the receipt with the earliest date/time value of all retrieved receipts is used. This can be necessary, for example, after a power or server outage. | 1.0 | +| `0x0000000000020000` | "training receipt"
Requests with this type of receipt are annotated with the reference "TRA" in the signature block. Instead of the encrypted cumulative sales counter, the BASE64 encrypted value of the TRA string is entered. The sales counter is, in accordance with the RKSV, not adjusted. | 1.0 | +| `0x0000000000040000` | "reverse receipt"
Requests with this type of receipt are annotated with the reference "STO" in the signature block. Instead of the encrypted cumulative sales counter, a BASE64 encrypted value of the STO string is entered. Further processing depends on the underlying type of receipt. | 1.0 | +| `0x0000000000080000` | "handwritten receipt" or "subsequent entry"
The transferred receipt contains data which has been collected in a handwritten receipt. Although there is no requirement for a time annotation on a handwritten receipt we recommend using 12:00 for this purpose.
Further processing depends on the underlying type of receipt. For example, this can be conducted after §7 cash revenue law for sales made outside business premises. | 1.0 | +| `0x0000000000100000` | "small business, sales tax relief in accordance with §6 Abs 1 Z 27 UStG (sales tax law)"
The transferred receipt contains data which have been generated by a small business. A special note "sales tax relief in accordance with §6 Abs 1 Z 27" is possible. The RKSV requirement is handled according to the basic business transaction.
The transferred receipt data should contain the correct VAT rate and the correct ftChargeItemCase, even if the identified sales tax is 0%. | 1.0 | +| `0x0000000000200000` | "receiver is a company"
The transferred receipt contains a sales receipt, and the receiver is a trader.
Note regarding the characteristics of §11 UStG: for receipts with up to €400 gross amount, an invoice for small amounts can be issued. From €400 onwards, there are additional features to be displayed on the invoice, to enable the pre-tax deduction for the receiver of the invoice.
For receipts with a gross amount of €10.000 or more, in addition, the service receiver’s UID number has to be indicated.
We suggest transferring the data about the receiver in the field ftReceiptCaseData, in manufacturer-specific JSON format. | 1.0 | +| `0x0000000000400000` | "contains characteristics in accordance with §11 UStG"
On the receipt, the characteristics are issued in accordance with §11 UStG, and the transferred receipt contains receiver data in manufacturer-specific JSON format within the field ftReceiptCaseData. | 1.0 | +| `0x0000800000000000` | Receipt request. Common behaviour. | | + + + +*Table 23. Type of Receipt: ftReceiptCase Flags(AT - RKSVO)* diff --git a/doc/middleware-at-rksv/reference-tables/4 - ftChargeItemCase.md b/doc/middleware-at-rksv/reference-tables/4 - ftChargeItemCase.md new file mode 100644 index 00000000..dd0df8a3 --- /dev/null +++ b/doc/middleware-at-rksv/reference-tables/4 - ftChargeItemCase.md @@ -0,0 +1,51 @@ +--- +slug: /poscreators/middleware-doc/austria/reference-tables +title: Type of Service: ftChargeItemCase +--- + +### Type of Service: ftChargeItemCase + +This table expands on the values provided in the table ["Type of Service: ftChargeItemCase"](../../general/reference-tables/reference-tables.md#t-type-of-service-ftchargeitemcase) with values applicable to the Austrian market. + +| **Value** | **Description** | **Middleware-Version** | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------| +| `0x4154000000000000` | "unknown type of service for AT"
With help of the VAT-rates table saved within fiskaltrust.SecurityMechanisms, an allocation to normal /discounted-1 /discounted-2/zero is attempted. | 1.0 | +| `0x4154000000000001` | "undefined type of service for AT discounted-1"
(as of 1.7.2016, this is calculated with 10%). | 1.0 | +| `0x4154000000000002` | "undefined type of service for AT discounted-2"
(as of 1.7.2016, this is calculated with 13%). | 1.0 | +| `0x4154000000000003` | "undefined type of service for AT normal"
(as of 1.7.2016, this is 20%). | 1.0 | +| `0x4154000000000004` | "undefined type of service for AT special"
Includes all rates which are not contained in the previous ones (as of1.7.2016, this can be for example 12% or 19%). | 1.0 | +| `0x4154000000000005` | "undefined type of service for AT zero"
Includes data which is indicated with 0% sales tax and also data where the sales tax is unknown, for example in a reference to an outgoing invoice. Also in cases where the sales tax should not be apparent, for example in the case of differential taxation, the data can be issued with this code. | 1.0 | +| `0x4154000000000006` | "reverse charge"
Reversal of tax liability.
These can e.g. include construction works, mobile phones from € 5.000,-, services abroad, etc. | 1.0 | +| `0x4154000000000007` | "not own sales"
In the data, a VAT-rate can be indicated, whereby the gross amount according to the RKSV always has to be recorded in the signature field, set zero. | 1.0 | +| `0x4154000000000008` | "delivery discounted-1"
For processing, see (0x4154000000000001) | 1.0 | +| `0x4154000000000009` | "delivery discounted-2"
For processing, see (0x4154000000000002) | 1.0 | +| `0x415400000000000A` | "delivery normal"
For processing, see (0x4154000000000003) | 1.0 | +| `0x415400000000000B` | "delivery special"
For processing, see (0x4154000000000004) | 1.0 | +| `0x415400000000000C` | "delivery zero"
For processing, see (0x4154000000000005) | 1.0 | +| `0x415400000000000D` | "other services discounted-1"
For processing, see (0x4154000000000001) | 1.0 | +| `0x415400000000000E` | "other services discounted-2"
For processing, see (0x4154000000000002) | 1.0 | +| `0x415400000000000F` | "other services normal"
For processing, see (0x4154000000000003) | 1.0 | +| `0x4154000000000010` | "other services special"
For processing, see (0x4154000000000004) | 1.0 | +| `0x4154000000000011` | "other services zero"
For processing, see (0x4154000000000005) | 1.0 | +| `0x4154000000000012` | "catalogue services discounted-1"
For processing, see (0x4154000000000001) | 1.0 | +| `0x4154000000000013` | "catalogue services discounted-2"
For processing, see (0x4154000000000002) | 1.0 | +| `0x4154000000000014` | "catalogue services normal"
For processing, see (0x4154000000000003) | 1.0 | +| `0x4154000000000015` | "catalogue services special"
For processing, see (0x4154000000000004) | 1.0 | +| `0x4154000000000016` | "catalogue services zero"
For processing, see (0x4154000000000005) | 1.0 | +| `0x4154000000000017` | "own consumption discounted-1"
For processing, see (0x4154000000000001) | 1.0 | +| `0x4154000000000018` | "own consumption discounted-2"
For processing, see (0x4154000000000002) | 1.0 | +| `0x4154000000000019` | "own consumption normal"
For processing, see (0x4154000000000003) | 1.0 | +| `0x415400000000001A` | "own consumption special"
For processing, see (0x4154000000000004) | 1.0 | +| `0x415400000000001B` | "own consumption zero"
For processing, see (0x4154000000000005) | 1.0 | +| `0x415400000000001C` | "down payment discounted-1"
For processing, see (0x4154000000000001) | 1.0 | +| `0x415400000000001D` | "down payment discounted-2"
For processing, see (0x4154000000000002) | 1.0 | +| `0x415400000000001E` | "down payment normal"
For processing, see (0x4154000000000003) | 1.0 | +| `0x415400000000001F` | "down payment special"
For processing, see (0x4154000000000004) | 1.0 | +| `0x4154000000000020` | "down payment zero"
For processing, see (0x4154000000000005) | 1.0 | +| `0x4154000000000021` | "account of a third party/ third party name/ collection"
For processing, see (0x4154000000000007) | 1.0 | +| `0x4154000000000022` | "obligation with RKSV requirement"
Obligations are to be equalized with pay items. If however, it is for technical reasons necessary to transfer obligations in the charge items block, then this code should be used for obligations with RKSV requirement. The gross amount due is recorded in the signature field, set zero, according to the RKSV.
For example, a receipt for a voucher issuance, for which the voucher is indicated as item in the charge items block and the corresponding cash amount is indicated in the pay items block.
An example for this would be a voucher intake via charge items block, or a payment of an outgoing invoice. | 1.0 | +| `0x4154000000000023` | "obligation without RKSV requirement"
Obligations are to be equalized with pay items. If however, it is systematically necessary to transfer obligations in the charge items block, then this code should be used for obligations without RKSV requirement. The gross amount due is recorded in the signature field, set zero, according to the RKSV. For processing, also see (0x4154000000000007). | 1.0 | + + + +*Table 24. Type of Service: ftChargeItemCase (AT - RKSVO)* diff --git a/doc/middleware-at-rksv/reference-tables/5 - ftPayItemCase.md b/doc/middleware-at-rksv/reference-tables/5 - ftPayItemCase.md new file mode 100644 index 00000000..34ea5d63 --- /dev/null +++ b/doc/middleware-at-rksv/reference-tables/5 - ftPayItemCase.md @@ -0,0 +1,35 @@ +--- +slug: /poscreators/middleware-doc/austria/reference-tables +title: Type of Payment: ftPayItemCase +--- + +### Type of Payment: ftPayItemCase + +This table expands on the values provided in the table ["Type of Payment: ftPayItemCase"](../../general/reference-tables/reference-tables.md#t-type-of-payment-ftpayitemcase-90) with values applicable to the Austrian market. + +| **Value** | **Description** | **Middleware-Version** | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------|---------------------| +| `0x4154000000000000` | "default value"
unknown payment type: automatic processing through the fiskaltrust.SecurityMechanisms settings is attempted. | 1.0 | +| `0x4154000000000000` | "unknown payment type for AT"
This is handled like a cash payment in national currency. | 1.0 | +| `0x4154000000000001` | "cash payment in national currency" | 1.0 | +| `0x4154000000000002` | "cash payment in foreign currency" | 1.0 | +| `0x4154000000000003` | "crossed cheque" | 1.0 | +| `0x4154000000000004` | "debit card payment" | 1.0 | +| `0x4154000000000005` | "credit card payment" | 1.0 | +| `0x4154000000000006` | "voucher payment (coupon)" | 1.0 | +| `0x4154000000000007` | "online payment" | 1.0 | +| `0x4154000000000008` | "customer card payment" | 1.0 | +| `0x4154000000000009` | "other debit card" | 1.0 | +| `0x415400000000000A` | "other credit card" | 1.0 | +| `0x415400000000000B` | "account receivable"
delivery note/ settlement in foreign currency | 1.0 | +| `0x415400000000000C` | "SEPA transfer" | 1.0 | +| `0x415400000000000D` | "other transfer" | 1.0 | +| `0x415400000000000E` | "cash book expense" | 1.0 | +| `0x415400000000000F` | "cash book contribution" | 1.0 | +| `0x4154000000000010` | "levy"
AT: Anzahlung | 1.0 | +| `0x4154000000000011` | "internal/ material consumption" | 1.0 | +| `0x4154000000000012` | "change"
tip | 1.0 | + + + +*Table 25. Type of Payment: ftPayItemCase (AT - RKSVO)* diff --git a/doc/middleware-at-rksv/reference-tables/6 - ftSignatureFormat.md b/doc/middleware-at-rksv/reference-tables/6 - ftSignatureFormat.md new file mode 100644 index 00000000..37dfa79f --- /dev/null +++ b/doc/middleware-at-rksv/reference-tables/6 - ftSignatureFormat.md @@ -0,0 +1,30 @@ +--- +slug: /poscreators/middleware-doc/austria/reference-tables +title: Type of Signature: ftSignatureFormat +--- + +### Type of Signature: ftSignatureFormat + +This table expands on the values provided in the table ["Format of Signature: ftSignatureFormat"](../../general/reference-tables/reference-tables.md#t-type-of-signature-ftsignatureformat-112) with values applicable to the Austrian market. + +According to the RKSV, there is one exception: if the fiskaltrust.SecurityMechanism responds with a QR code but the printer, through which the receipt is supposed to be printed (or electronically issued), cannot display QR codes, it is allowed to convert the signature value and display it as bar code, link, or in OCR typeface on the receipt. This requirement and a sample code can be found in the Chapter ["Printing of QR-Code not supported"](#printing-of-qr-code-not-supported). + +| **Value** | **Description** | +|-----------|---------------------------------------------| +| `0x00` | unknown / without | +| `0x01` | Text | +| `0x02` | Link | +| `0x03` | QR code (2D code) | +| `0x04` | Code128 (bar code) | +| `0x05` | OCR-A (text recognition, Base32 compatible) | +| `0x06` | PDF417-(2D code) | +| `0x07` | DATAMATRIX-(2D code) | +| `0x08` | AZTEC-(2D Code) | +| `0x09` | EAN-8 (bar code) | +| `0x0A` | EAN-13 (bar code) | +| `0x0B` | UPC-A (bar code) | +| `0x0C` | Code39 (bar code, Base32 compatible) | + + + +*Table 26. Type of Signature: ftSignatureFormat (AT - RKSVO)* diff --git a/doc/middleware-at-rksv/reference-tables/7 - ftSignatureType.md b/doc/middleware-at-rksv/reference-tables/7 - ftSignatureType.md new file mode 100644 index 00000000..b77955be --- /dev/null +++ b/doc/middleware-at-rksv/reference-tables/7 - ftSignatureType.md @@ -0,0 +1,19 @@ +--- +slug: /poscreators/middleware-doc/austria/reference-tables +title: Type of Signature: ftSignatureType +--- + +### Type of Signature: ftSignatureType + +This table expands on the values provided in the table ["Type of Signature: ftSignatureType"](../../general/reference-tables/reference-tables.md#t-type-of-signature-ftsignaturetype-127) with values applicable to the Austrian market. + +| **Value** | **Description** | **Version** | +| -------------------- | ------------------------------------------------------------ | ----------- | +| `0x4154000000000000` | unknown | 1.0 | +| `0x4154000000000001` | signature according to RKSV | 1.0 | +| `0x4154000000000002` | Archiving required according to RKSV or BAO §132.
E.g. notification of collective receipt after failure, initial receipt, monthly receipt, etc.. | 1.0 | +| `0x4154000000000003` | FinanzOnline notification | 1.0 | + + + +*Table 27. Type of Signature: ftSignatureType (AT - RKSVO)* \ No newline at end of file diff --git a/doc/middleware-at-rksv/reference-tables/8 - ftJournalType.md b/doc/middleware-at-rksv/reference-tables/8 - ftJournalType.md new file mode 100644 index 00000000..8a92ec9f --- /dev/null +++ b/doc/middleware-at-rksv/reference-tables/8 - ftJournalType.md @@ -0,0 +1,247 @@ +--- +slug: /poscreators/middleware-doc/austria/reference-tables +title: Reference tables +--- + +## Reference tables + +This chapter expands on the reference tables covered in the Chapter ["Reference tables"](../../general/reference-tables/reference-tables.md) of the General Part, with country-specific information applicable to the Austrian market. + +### Service Status: ftState + +The table below describes it supported statuses for the ftState field following the Austrian law. The ftState from this reference table and the general part of this documentation can be combined through the logic operator "OR". For example `0x4154000000000010` (monthly report due) and `0x4154000000000008` combined through `OR` results in `0x4154000000000018`. + +The country-specific code is made of the country's code value following the ISO-3166-1-ALPHA-2 standard, converted from ASCII into hex. For Austria (AT) this is `0x4154`, which results in `0x4154000000000000` as the value for the "ready" status. + +| **Value** | **Description** | **Middleware-Version** | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------| +| `0x4154000000000001` | "out of service"
No RKSV signatures are generated or sent back. No RKSV-DEP is written, as nothing is being signed. The E131-DEP records requests and responses. | 1.0 | +| `0x4154000000000002` | "SSCD temporary out of service"
For at least one receipt, it was not possible to receive the signature from an allocated SSCD. Thus, the security mechanism has been put into "signature creation device out of service" mode. Regardless of whether an allocated SSCD is available again or not, the mode remains in place until, via zero receipt, all previous receipts can be signed. If this mode is activated, an out of service signature, in accordance with the RKSV, is generated and sent back. | 1.0 | +| `0x4154000000000004` | "SSCD permanently out of service"
The status "SSCD temporary out of service" was activated more than 48h ago. Thus a FinanzOnline notification has been generated.
For conduct and termination of this mode, see "SSCD temporary out of service". | 1.0 | +| `0x4154000000000008` | "subsequent entry activated"
At least one receipt has been transferred with a subsequent entry flag. In order to finalize the subsequent entry and leave the mode, it is necessary to generate a zero receipt. This zero receipt signs and secures the preliminary receipts accordingly to the RKSV. | 1.0 | +| `0x4154000000000010` | "monthly report due"
If the latest monthly or annual report are is in the current month, the service will signal this. This status does not impact the signature conduct of the service; it is merely an indicative notification. | 1.0 | +| `0x4154000000000020` | "annual report due"
Same conduct as for "monthly report due" | 1.0 | +| `0x4154000000000040` | "message / notification pending"
A status message and/or FinanzOnline notification is ready for collection.
Using a zero receipt, the messages can be retrieved and archived or processed in bookkeeping. | 1.0 | +| `0x4154000000000080` | "backup SSCD in use"
The receipt was signed by a signature creation unit configured for backup use. | 1.1.17248 | + + + +*Table 21. Service status: ftState for AT - RKSVO* + + + +### Type of Receipt: ftReceiptCase + +The ftReceiptCase indicates the receipt type and defines how it should be processed by the fiskaltrust.SecurityMechanism in accordance with the Austrian law. + +For Austria (AT) the country code is `0x4154`. Thus, the value for an unknown ftReceiptCase in Austria is `0x4154000000000000`. + +| **Value** | **Description** | **Middleware- Version** | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| `0x4154000000000000` | "unknown type of receipt for AT"
This receipt is processed like a cash transaction with RKSV requirement. | 1.0 | +| `0x4154000000000001` | "Cash transaction with RKSV requirement for AT"
The fiskaltrust decision tree is being run through, and, if needed, the signature process is started and the cumulative counter adjusted respectively.
An example of a signature being needed is an "other service" paid for with a "credit card".
An example of a case where no signature is needed is a receipt with only "no own sales" on it which has been paid for by "credit card". | 1.0 | +| `0x4154000000000002` | "zero receipt"
Charge items block (ftChargeItems) as well as pay items block (ftPayItems) are empty.
The "zero receipt" can be used to test operability by collecting a service status notification, such as an out-of-service notification for FinanzOnline. | 1.0 | +| `0x4154000000000003` | "initial operation receipt"
The request is only valid as a zero receipt. The initial operation procedure is started. When using fiskaltrust.SecuritymMechansimsPlus, the receipt will also be checked for correctness. | 1.0 | +| `0x4154000000000004` | "out of operation receipt"
The procedure to take the service out of operation is started.
The request is only valid as a zero receipt. When using the fiskaltrust.Carefree package, the receipt will also be checked for correctness, and the notification to the "FinanzOnline" will be performed automatically in the background. | 1.0 | +| `0x4154000000000005` | "monthly receipt"
The procedure for the creation of the monthly receipt is started. The request is only valid as a zero receipt. | 1.0 | +| `0x4154000000000006` | "annual receipt"
The procedure for the creation of the annual receipt is started.
The request is only valid as a zero receipt. When using the fiskaltrust.Carefree package, the receipt will also be checked for correctness, and the notification to the "FinanzOnline" will be performed automatically in the background. | 1.0 | +| `0x4154000000000007` | "cash transaction RKSV relief or cash revenue law"
This is used to process cash transactions which do not have an RKSV requirement (e.g. emptying a vending machine). | 1.0 | +| `0x4154000000000008` | "target business"
An outgoing invoice which does not necessarily have to be issued by a cash register but can also be issued by an invoicing system. | 1.0 | +| `0x4154000000000009` | "delivery note"
Information about an internal or external delivery or also a transfer into a different IT system. The sales tax statement is issued through the outgoing invoice or in the other system. | 1.0 | +| `0x415400000000000A` | "cash deposit"
For example the payment of a target calculation, or deposit on the customer card.
Usually, the receipt data only includes pay items while the charge items block remains empty. Since the total amount must always be zero, you must use a negative pay item to balance the sum of pay items to zero. | 1.0 | +| `0x415400000000000B` | "cash pay-out"
For example to pay for deliveries . | 1.0 | +| `0x415400000000000C` | "means of payment transfer"
For example the switching between "cash", "credit card", "ATM", etc. This function is also used to issue vouchers. | 1.0 | +| `0x415400000000000D` | "protocol"
Simple protocol function. The data sets that need to be logged can be transferred in the field ftReceiptCaseData in manufacturer-specific JSON format. For example, opening the cash drawer or changing master data. | 1.0 | +| `0x415400000000000E` | "Internal / material consumption"
For example recording breakages or own consumption. | 1.0 | +| `0x415400000000000F` | "sales in an online shop, telephone-/fax orders"
Through the cash revenue law, sales from online shops and similar are exempted, even if these have been paid by credit card or comparable means of payments with RKSV requirement but not paid on business premises. As a cash transaction, the issued receipt comes with a recording requirement in accordance with §131 BAO and needs to be processed in bookkeeping. | 1.0 | +| `0x4154000000000010` | "foreign sales"
Foreign sales do not have an RKSV-requirement. As a cash transaction, the issued receipt comes with a recording requirement in accordance with §131 BAO and need to be processed in bookkeeping. Foreign requirements, for example in connection with receipt generation or cash register requirements, have to be taken into account. | 1.0 | + + + +*Table 22. Type of Receipt: ftReceiptCase (AT - RKSVO)* + +#### ftReceiptCaseFlag + +This table expands on the values provided in the table ["Type of Receipt: ftReceiptCaseFlag"](../../general/reference-tables/reference-tables.md#t-type-of-receipt-ftreceiptcaseflag-64) of with values applicable to the Austrian market. + +| Value | Description | Middleware-Version | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| `0x0000000000010000` | "out of service"
The transferred receipt contains data which has been created during an outage of the security mechanism. The original receipts are available in handwritten or digital format and must now be transferred and subsequently consolidated and signed via zero receipt. In order to decide whether it is a temporary or permanent (more than 48 hours) outage of the security mechanism (for example in case of theft), the "oldest" or the receipt with the earliest date/time value of all retrieved receipts is used. This can be necessary, for example, after a power or server outage. | 1.0 | +| `0x0000000000020000` | "training receipt"
Requests with this type of receipt are annotated with the reference "TRA" in the signature block. Instead of the encrypted cumulative sales counter, the BASE64 encrypted value of the TRA string is entered. The sales counter is, in accordance with the RKSV, not adjusted. | 1.0 | +| `0x0000000000040000` | "reverse receipt"
Requests with this type of receipt are annotated with the reference "STO" in the signature block. Instead of the encrypted cumulative sales counter, a BASE64 encrypted value of the STO string is entered. Further processing depends on the underlying type of receipt. | 1.0 | +| `0x0000000000080000` | "handwritten receipt" or "subsequent entry"
The transferred receipt contains data which has been collected in a handwritten receipt. Although there is no requirement for a time annotation on a handwritten receipt we recommend using 12:00 for this purpose.
Further processing depends on the underlying type of receipt. For example, this can be conducted after §7 cash revenue law for sales made outside business premises. | 1.0 | +| `0x0000000000100000` | "small business, sales tax relief in accordance with §6 Abs 1 Z 27 UStG (sales tax law)"
The transferred receipt contains data which have been generated by a small business. A special note "sales tax relief in accordance with §6 Abs 1 Z 27" is possible. The RKSV requirement is handled according to the basic business transaction.
The transferred receipt data should contain the correct VAT rate and the correct ftChargeItemCase, even if the identified sales tax is 0%. | 1.0 | +| `0x0000000000200000` | "receiver is a company"
The transferred receipt contains a sales receipt, and the receiver is a trader.
Note regarding the characteristics of §11 UStG: for receipts with up to €400 gross amount, an invoice for small amounts can be issued. From €400 onwards, there are additional features to be displayed on the invoice, to enable the pre-tax deduction for the receiver of the invoice.
For receipts with a gross amount of €10.000 or more, in addition, the service receiver’s UID number has to be indicated.
We suggest transferring the data about the receiver in the field ftReceiptCaseData, in manufacturer-specific JSON format. | 1.0 | +| `0x0000000000400000` | "contains characteristics in accordance with §11 UStG"
On the receipt, the characteristics are issued in accordance with §11 UStG, and the transferred receipt contains receiver data in manufacturer-specific JSON format within the field ftReceiptCaseData. | 1.0 | +| `0x0000800000000000` | Receipt request. Common behaviour. | | + + + +*Table 23. Type of Receipt: ftReceiptCase Flags(AT - RKSVO)* + +### Type of Service: ftChargeItemCase + +This table expands on the values provided in the table ["Type of Service: ftChargeItemCase"](../../general/reference-tables/reference-tables.md#t-type-of-service-ftchargeitemcase) with values applicable to the Austrian market. + +| **Value** | **Description** | **Middleware-Version** | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------| +| `0x4154000000000000` | "unknown type of service for AT"
With help of the VAT-rates table saved within fiskaltrust.SecurityMechanisms, an allocation to normal /discounted-1 /discounted-2/zero is attempted. | 1.0 | +| `0x4154000000000001` | "undefined type of service for AT discounted-1"
(as of 1.7.2016, this is calculated with 10%). | 1.0 | +| `0x4154000000000002` | "undefined type of service for AT discounted-2"
(as of 1.7.2016, this is calculated with 13%). | 1.0 | +| `0x4154000000000003` | "undefined type of service for AT normal"
(as of 1.7.2016, this is 20%). | 1.0 | +| `0x4154000000000004` | "undefined type of service for AT special"
Includes all rates which are not contained in the previous ones (as of1.7.2016, this can be for example 12% or 19%). | 1.0 | +| `0x4154000000000005` | "undefined type of service for AT zero"
Includes data which is indicated with 0% sales tax and also data where the sales tax is unknown, for example in a reference to an outgoing invoice. Also in cases where the sales tax should not be apparent, for example in the case of differential taxation, the data can be issued with this code. | 1.0 | +| `0x4154000000000006` | "reverse charge"
Reversal of tax liability.
These can e.g. include construction works, mobile phones from € 5.000,-, services abroad, etc. | 1.0 | +| `0x4154000000000007` | "not own sales"
In the data, a VAT-rate can be indicated, whereby the gross amount according to the RKSV always has to be recorded in the signature field, set zero. | 1.0 | +| `0x4154000000000008` | "delivery discounted-1"
For processing, see (0x4154000000000001) | 1.0 | +| `0x4154000000000009` | "delivery discounted-2"
For processing, see (0x4154000000000002) | 1.0 | +| `0x415400000000000A` | "delivery normal"
For processing, see (0x4154000000000003) | 1.0 | +| `0x415400000000000B` | "delivery special"
For processing, see (0x4154000000000004) | 1.0 | +| `0x415400000000000C` | "delivery zero"
For processing, see (0x4154000000000005) | 1.0 | +| `0x415400000000000D` | "other services discounted-1"
For processing, see (0x4154000000000001) | 1.0 | +| `0x415400000000000E` | "other services discounted-2"
For processing, see (0x4154000000000002) | 1.0 | +| `0x415400000000000F` | "other services normal"
For processing, see (0x4154000000000003) | 1.0 | +| `0x4154000000000010` | "other services special"
For processing, see (0x4154000000000004) | 1.0 | +| `0x4154000000000011` | "other services zero"
For processing, see (0x4154000000000005) | 1.0 | +| `0x4154000000000012` | "catalogue services discounted-1"
For processing, see (0x4154000000000001) | 1.0 | +| `0x4154000000000013` | "catalogue services discounted-2"
For processing, see (0x4154000000000002) | 1.0 | +| `0x4154000000000014` | "catalogue services normal"
For processing, see (0x4154000000000003) | 1.0 | +| `0x4154000000000015` | "catalogue services special"
For processing, see (0x4154000000000004) | 1.0 | +| `0x4154000000000016` | "catalogue services zero"
For processing, see (0x4154000000000005) | 1.0 | +| `0x4154000000000017` | "own consumption discounted-1"
For processing, see (0x4154000000000001) | 1.0 | +| `0x4154000000000018` | "own consumption discounted-2"
For processing, see (0x4154000000000002) | 1.0 | +| `0x4154000000000019` | "own consumption normal"
For processing, see (0x4154000000000003) | 1.0 | +| `0x415400000000001A` | "own consumption special"
For processing, see (0x4154000000000004) | 1.0 | +| `0x415400000000001B` | "own consumption zero"
For processing, see (0x4154000000000005) | 1.0 | +| `0x415400000000001C` | "down payment discounted-1"
For processing, see (0x4154000000000001) | 1.0 | +| `0x415400000000001D` | "down payment discounted-2"
For processing, see (0x4154000000000002) | 1.0 | +| `0x415400000000001E` | "down payment normal"
For processing, see (0x4154000000000003) | 1.0 | +| `0x415400000000001F` | "down payment special"
For processing, see (0x4154000000000004) | 1.0 | +| `0x4154000000000020` | "down payment zero"
For processing, see (0x4154000000000005) | 1.0 | +| `0x4154000000000021` | "account of a third party/ third party name/ collection"
For processing, see (0x4154000000000007) | 1.0 | +| `0x4154000000000022` | "obligation with RKSV requirement"
Obligations are to be equalized with pay items. If however, it is for technical reasons necessary to transfer obligations in the charge items block, then this code should be used for obligations with RKSV requirement. The gross amount due is recorded in the signature field, set zero, according to the RKSV.
For example, a receipt for a voucher issuance, for which the voucher is indicated as item in the charge items block and the corresponding cash amount is indicated in the pay items block.
An example for this would be a voucher intake via charge items block, or a payment of an outgoing invoice. | 1.0 | +| `0x4154000000000023` | "obligation without RKSV requirement"
Obligations are to be equalized with pay items. If however, it is systematically necessary to transfer obligations in the charge items block, then this code should be used for obligations without RKSV requirement. The gross amount due is recorded in the signature field, set zero, according to the RKSV. For processing, also see (0x4154000000000007). | 1.0 | + + + +*Table 24. Type of Service: ftChargeItemCase (AT - RKSVO)* + +### Type of Payment: ftPayItemCase + +This table expands on the values provided in the table ["Type of Payment: ftPayItemCase"](../../general/reference-tables/reference-tables.md#t-type-of-payment-ftpayitemcase-90) with values applicable to the Austrian market. + +| **Value** | **Description** | **Middleware-Version** | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------|---------------------| +| `0x4154000000000000` | "default value"
unknown payment type: automatic processing through the fiskaltrust.SecurityMechanisms settings is attempted. | 1.0 | +| `0x4154000000000000` | "unknown payment type for AT"
This is handled like a cash payment in national currency. | 1.0 | +| `0x4154000000000001` | "cash payment in national currency" | 1.0 | +| `0x4154000000000002` | "cash payment in foreign currency" | 1.0 | +| `0x4154000000000003` | "crossed cheque" | 1.0 | +| `0x4154000000000004` | "debit card payment" | 1.0 | +| `0x4154000000000005` | "credit card payment" | 1.0 | +| `0x4154000000000006` | "voucher payment (coupon)" | 1.0 | +| `0x4154000000000007` | "online payment" | 1.0 | +| `0x4154000000000008` | "customer card payment" | 1.0 | +| `0x4154000000000009` | "other debit card" | 1.0 | +| `0x415400000000000A` | "other credit card" | 1.0 | +| `0x415400000000000B` | "account receivable"
delivery note/ settlement in foreign currency | 1.0 | +| `0x415400000000000C` | "SEPA transfer" | 1.0 | +| `0x415400000000000D` | "other transfer" | 1.0 | +| `0x415400000000000E` | "cash book expense" | 1.0 | +| `0x415400000000000F` | "cash book contribution" | 1.0 | +| `0x4154000000000010` | "levy"
AT: Anzahlung | 1.0 | +| `0x4154000000000011` | "internal/ material consumption" | 1.0 | +| `0x4154000000000012` | "change"
tip | 1.0 | + + + +*Table 25. Type of Payment: ftPayItemCase (AT - RKSVO)* + +### Type of Signature: ftSignatureFormat + +This table expands on the values provided in the table ["Format of Signature: ftSignatureFormat"](../../general/reference-tables/reference-tables.md#t-type-of-signature-ftsignatureformat-112) with values applicable to the Austrian market. + +According to the RKSV, there is one exception: if the fiskaltrust.SecurityMechanism responds with a QR code but the printer, through which the receipt is supposed to be printed (or electronically issued), cannot display QR codes, it is allowed to convert the signature value and display it as bar code, link, or in OCR typeface on the receipt. This requirement and a sample code can be found in the Chapter ["Printing of QR-Code not supported"](#printing-of-qr-code-not-supported). + +| **Value** | **Description** | +|-----------|---------------------------------------------| +| `0x00` | unknown / without | +| `0x01` | Text | +| `0x02` | Link | +| `0x03` | QR code (2D code) | +| `0x04` | Code128 (bar code) | +| `0x05` | OCR-A (text recognition, Base32 compatible) | +| `0x06` | PDF417-(2D code) | +| `0x07` | DATAMATRIX-(2D code) | +| `0x08` | AZTEC-(2D Code) | +| `0x09` | EAN-8 (bar code) | +| `0x0A` | EAN-13 (bar code) | +| `0x0B` | UPC-A (bar code) | +| `0x0C` | Code39 (bar code, Base32 compatible) | + + + +*Table 26. Type of Signature: ftSignatureFormat (AT - RKSVO)* + +### Type of Signature: ftSignatureType + +This table expands on the values provided in the table ["Type of Signature: ftSignatureType"](../../general/reference-tables/reference-tables.md#t-type-of-signature-ftsignaturetype-127) with values applicable to the Austrian market. + +| **Value** | **Description** | **Version** | +| -------------------- | ------------------------------------------------------------ | ----------- | +| `0x4154000000000000` | unknown | 1.0 | +| `0x4154000000000001` | signature according to RKSV | 1.0 | +| `0x4154000000000002` | Archiving required according to RKSV or BAO §132.
E.g. notification of collective receipt after failure, initial receipt, monthly receipt, etc.. | 1.0 | +| `0x4154000000000003` | FinanzOnline notification | 1.0 | + + + +*Table 27. Type of Signature: ftSignatureType (AT - RKSVO)* + +### Type of Journal: ftJournalType + +This table expands on the values provided in the table of Chapter ["Type of Journal: ftJournalType"](../../general/reference-tables/reference-tables.md#c-type-of-journal-ftjournaltype-129) of the General part with values applicable to the Austrian market. + +| **Value** | **Description** | **Version** | +| -------------------- | ------------------------------ | ----------- | +| `0x4154000000000000` | status information for QueueAT | 1.0 | +| `0x4154000000000001` | RKSV-DEP-Export | 1.0 | + +*Table 28. Type of Journal: ftJournalType (AT - RKSVO)* + +### Printing of QR-Code not supported + +If no QR code can be issued, it is allowed to place text using OCR typeface onto the receipt. For this procedure, BASE64-coded data fields are displayed in BASE32 according to §11 para. 2 RKSV. This is because the capital "i" and lowercase "L" are not distinguishable from each other in many typefaces. + +For example, the following signature value is converted in the way described above. Whereby the following output BASE64 (bold) is: + +```nohighlight +_R1-AT0_DEMO-CASH-BOX426_776730_2015-10-14T18:20:23_0,00_0,00_0,00_0,00_0,00_0gJTFI8/zqc=_968935007593160625_fP7/PMP-SnQ0=_Xh5wNe0akaTOVvMgLVrCcRh2xmIyP91ogbxc5xv4Rrw64lpQsqLm+1GZxuCz4D1sZl9WCv3wMMoE0p+gyLaufg== +``` + + + +*Code 15. Example of OCR output in Base64* + +The BASE32 display in accordance with the RKSV for this OCR text output in BASE32 (bold) looks as follows: + +```nohighlight +_R1-AT0_DEMO-CASH-BOX426_776730_2015-10-14T18:20:23_0,00_0,00_0,00_0,00_0,00_2IBFGFEPH7HKO===_968935007593160625_PT7P6PGD2KOQ2===_LYPHANPNDKI2JTSW6MQC2WWCOEMHNRTCGI7522EBXROOOG7YI26DVYS2KCZKFZX3KGM4NYFT4A6WYZS7KYFP34BQZICNFH5AZC3K47Q= +``` + + + +*Code 16. Example of OCR output in Base32* + +This procedure has to be carried out by the cash register or input station itself because the service does not know whether a QR code can be printed or not, and because the data format for DEP storage requires a BASE64 display anyway. + +A conversion tool is provided in the class fiskaltrust.ifPOS.Utility. + +**C# code example Converting to OCR:** +```cs +string ocr = fiskaltrust.ifPOS.Utilities.AT_RKSV_Signature_ToBase32(qr_data); +``` + + + +*Code 17. Example for converting the QR-Code to OCR* diff --git a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/1 - ftState.md b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/1 - ftState.md new file mode 100644 index 00000000..57d0031e --- /dev/null +++ b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/1 - ftState.md @@ -0,0 +1,18 @@ +--- +slug: /poscreators/middleware-doc/france/reference-tables +title: Service Status: ftState +--- + +# Reference tables + +### Service Status: ftState + +The ftState is returned with every receipt response. Through this status, fiskaltrust.Middleware can signal its operability or request processing logic. + +The country-specific code is made of the country's code value following the ISO-3166-1-ALPHA-2 standard, converted from ASCII into hex. For France (FR), the country code is `0x4652`, which results in `0x4652000000000000` as the value for the "ready" status. + +The table below describes supported statuses for the ftState field. Those codes can be combined by using the logic operator `OR`. + +| **Value** | **Description** | **Middleware Version** | +|----------------------|-----------------------------------------------------------------------------------------------------|------------------------| +| `0x4652000000000040` | Message Pending
Use Zero-Receipt to show Message on Receipt | 1.0 | diff --git a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/2 - ftReceiptCase.md b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/2 - ftReceiptCase.md new file mode 100644 index 00000000..8c8ba3f2 --- /dev/null +++ b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/2 - ftReceiptCase.md @@ -0,0 +1,41 @@ +--- +slug: /poscreators/middleware-doc/france/reference-tables/receiptcase +title: Type of receipt: ftReceiptCase +--- + +# Reference tables + +## Type of Receipt: ftReceiptCase + +The `ftReceiptCase` defines the type of receipt and hence how fiskaltrust.SecurityMechanisms should process receipts according to French law. + +The country-specific code is made of the country's code value following the ISO-3166-1-ALPHA-2 standard, converted from ASCII into hex. For France (FR), the country code is `0x4652`. Thus, the value for an unknown `ftReceiptCase` in France is `0x4652000000000000`. + +| **Value** | **Description** | **Middleware-Version** | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| `0x4652000000000000` | **Unknown receipt for FR**
Processed like a ticket | 1.2 | +| `0x4652000000000001` | **Ticket**
Legal document; has to be signed.
Sign: Yes
Chain and national numbering: T
Details: GT counters are raised | 1.2 | +| `0x4652000000000002` | **Payment Prove**
Payment without knowing what was paid.
Legal document; has to be signed.
Sign: Yes
Chain and national numbering: P
No ChargeItems on payment-prove, the total amount is always zero, a negative payitem of type `0x4652000000000011` is used to get the sum of PayItems to zero.
Details: GT counters are not raised | | +| `0x4652000000000003` | **Invoice**
Legal document; has to be signed.
Sign: Yes
Chain and national numbering: I
A reference to the ticket can be created by using `cbPreviousReceiptNumber` in the request.
Detail: GT counters are raised | | +| `0x4652000000000004` | **Shift Receipt / Grand Total Ticket / Grand Total Invoice: Shift**
Sign: Yes
Chain and national numbering: G
Details: Resets the shift-counter, keeps all other counters | 1.2 | +| `0x4652000000000005` | **Daily Receipt / Grand Total Ticket / Grand Total Invoice: Daily**
Sign: Yes
Chain and national numbering: G
Details:
- Adds a daily-counter to the monthly-counter and then resets the daily-counter
- keeps the shift-counter | 1.2 | +| `0x4652000000000006` | **Monthly Receipt / Grand Total Ticket / Grand Total Invoice: Month**
Sign: Yes
Chain and national numbering: G
Details:
- Adds a daily-counter to the monthly-counter and then resets the daily-counter
- Adds a monthly-counter to the yearly-counter and then resets the monthly-counter
- keeps the shift-counter | 1.2 | +| `0x4652000000000007` | **Yearly Receipt / Grand Total Ticket / Grand Total Invoice: Year**
Sign: Yes
Chain and national numbering: G
Details:
- Adds a daily-counter to the monthly-counter and then resets the daily-counter
- Adds a monthly-counter to the yearly-counter and then resets the monthly-counter
- Resets the yearly-counter
- keeps the shift-counter | 1.2 | +| `0x4652000000000008` | **Bill**
List of ChargeItems to be paid. Used to inform customers about their open ChargeItems. PayItemType `0x4652000000000011` is used
Sign: Yes
Chain and national numbering: B
Details: GT counters are not raised. When the bill is used, the phrase "document provisoire" is returned with the fiskaltrust signature and must be printed on the bill. If bill and payment prove are created, this does not replace a ticket creation. A ticket or an invoice has to be issued to raise turnover and raise the GT counters as well | | +| `0x4652000000000009` | **Delivery Note**
Sign: no
Chain and national numbering: no | | +| `0x465200000000000A` | **Cash pay-in / Cash Deposit**
Same handling as payment prove
Chain and national numbering: P | | +| `0x465200000000000B` | **Cash pay-out**
Same handling as payment prove
Chain and national numbering: P | | +| `0x465200000000000C` | **Payment transfer**
Switch between payment method, e.g. from cash to credit card
Sign: Yes
Chain and national numbering: P | | +| `0x465200000000000D` | **Internal / Material**
Sign: No
Chain and national numbering: no | | +| `0x465200000000000E` | **Foreign sales**
Same handling as bill
Sign: Yes
Chain und national numbering: B | | +| `0x465200000000000F` | **Zero-Receipt**
Sign: Yes
Chain and national numbering: G
Details: A receipt with empty charge items block `ftChargeItem` and empty payment block `ftPayItem` which amounts to a total of "0". | | +| `0x4652000000000010` | **Start-Receipt**
Sign: Yes
Chain and national numbering: G | | +| `0x4652000000000011` | **Stop-Receipt**
Sign: Yes
Chain and national numbering: G | | +| `0x4652000000000012` | **Protocol / Technical Event Log**
Has to be signed
Sign: Yes
Chain and national numbering: L
Details: Can be used by the POS-System to log custom data. | 1.2 | +| `0x4652000000000013` | **Protocol / Accounting / Audit**
Has to be signed
Sign: Yes
Chain and national numbering: L
Details: Can be used by the POS-System to log custom data. | 1.2 | +| `0x4652000000000014` | **Protocol / Custom**
Does not need to be signed
Sign: No
Chain and national numbering: No
Details: Can be used by the POS-System to log custom data. | 1.2 | +| `0x4652000000000015` | **Archive**
Has to be Signed
Sign: Yes
Chain and national numbering: A
Details: Will trigger a daily closing automatically.
Creates an archive starting with the first receipt of the queue (or the last archive receipt) until the last receipt before this request. It must not contain more than 365 days.
To retrieve the export as a zip-file (containing the certificate, ReceiptJournals and QueueItems), a normal `/journal`request has to be sent to the `ftJournalType`: `0x4652000000010010`. The value of `ftQueueRow` in the response of this ReceiptCase has to be sent in the `from`-parameter.
The content of the retrieved zip-file can be verified with the _ExportTool_ for France. It can be downloaded [here](https://github.com/fiskaltrust/interface-doc/files/10928504/fiskaltrust.TaxAuditorTool.zip) | 1.2 | +| `0x4652000000000016` | **Copy**
Has to be Signed
Sign: Yes
Chain and national numbering: C
Details: in a request the `cbPreviousReceiptReference` is mandatory. It contains the receipt number which was handed out as a copy, issued by the original cash register. When a copy of a receipt is requested, the phrase "duplicata" is returned with the fiskaltrust signature and must be printed on the receipt. Every time the receipt is reprinted, an up-counting number denoting how many times the receipt has been printed, is returned. It must be printed on the receipt and is then recorded in the journal.The layout and the information contained shall be the same as in the original document. | 1.2 | + +*Table 33. Type of Receipt: ftReceiptCase (FR – BOI-TVA-DECL 30-10-30)* + diff --git a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/3 - ftReceiptCaseFlag.md b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/3 - ftReceiptCaseFlag.md new file mode 100644 index 00000000..283df60e --- /dev/null +++ b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/3 - ftReceiptCaseFlag.md @@ -0,0 +1,24 @@ +--- +slug: /poscreators/middleware-doc/france/reference-tables +title: Type of receipt: ftReceiptCaseFlag +--- + +# Reference tables + +### ftReceiptCaseFlag + +According to French law and regulations, various business transactions can result in specific combinations of types of receipts. For this, bytes 6, 5, 4 and 3 are used as combinable codes. These codes can be added with the logic operator "OR". + +| **Value** | **Description** | **Version** | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| `0x0000000000010000` | **Failed receipt**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). | 1.2 | +| `0x0000000000020000` | **Training receipt**
All requests issued with this flag are chained and signed in a separate chain. The phrase "mode école" is printed on any artefact that is printed while the flag is being used. For national numbering "X" is used.
GT counters are not raised. | 1.2 | +| `0x0000000000030000` | **Failed training receipt**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). | 1.2 | +| `0x0000000000040000` | **Reverse/voided receipt**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). |1.2|| +| `0x0000000000050000` | **Failed reverse/voided receipt**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). | 1.2 | | | +| `0x0000000000060000` | **Failed reverse/voided training receipt**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). | 1.2 | +| `0x0000800000000000` | **Receipt request**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). | 1.2 | + + + +*Table 34. Type of Receipt: ftReceiptCase Flags (FR – BOI-TVA-DECL 30-10-30)* diff --git a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/4 - ftChargeItemCase.md b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/4 - ftChargeItemCase.md new file mode 100644 index 00000000..23166986 --- /dev/null +++ b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/4 - ftChargeItemCase.md @@ -0,0 +1,55 @@ +--- +slug: /poscreators/middleware-doc/france/reference-tables +title: Type of sevices: ftChargeItemCase +--- + +# Reference tables + + +## Type of Service: ftChargeItemCase + +The `ftChargeItemCase` defines the type of service in charge item blocks and how fiskaltrust.SecurityMechanism processes individual receipts following French law. + +For France (FR), the country code is 0x4652. Thus, the value for an unknown `ftChargeItemCase` in France is `0x4652000000000000`. + +| **Value** | **Description** | **Middleware Version** | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| `0x4652000000000000` | **Unknown type of service for FR**
With the help of the VAT-rates table saved within fiskaltrust.SecurityMechanisms, an allocation to standard /reduced-1 /reduced-2 / super-reduced/zero is attempted. | 1.2 | +| `0x4652000000000001` | **Undefined type of service for FR reduced-1**
(as of 1.1.2017, this is calculated with 5,5%). | 1.2 | +| `0x4652000000000002` | **Undefined type of service for FR reduced-2**
(as of 1.1.2016, this is calculated with 10%,
Loi n° 2015-1786 du 29 décembre 2015, art. 79). | 1.2 | +| `0x4652000000000003` | **Undefined type of service for FR normal**
(as of 1.1.2014, this is 20%,
Loi n° 2012-1510 du 29 décembre 2012, art. 68-III-B). | 1.2 | +| `0x4652000000000004` | **Undefined type of service for FR special (super-reduced)**
Includes all rates that are not contained in the previous ones (as of 1.1.2017, this can be, for example, 2,1%). | 1.2 | +| `0x4652000000000005` | **Undefined type of service for FR zero**
Includes data indicated with 0% sales tax and data where the sales tax is unknown, for example, about an outgoing invoice. Also, in cases where the sales tax should not be apparent, for example, in differential taxation, the data can be issued with this code. | 1.2 | +| `0x4652000000000006` | **Reverse charge**
Reversal of tax liability. | 1.2 | +| `0x4652000000000007` | **Not own sales**
In the data, a VAT-rate can be indicated. | 1.2 | +| `0x4652000000000008` | **Delivery reduced-1**
For processing, see (`0x4652000000000001`) | 1.2 | +| `0x4652000000000009` | **Delivery reduced-2**
For processing, see (`0x4652000000000002`) | 1.2 | +| `0x465200000000000A` | **Delivery normal**
For processing, see (`0x4652000000000003`) | 1.2 | +| `0x465200000000000B` | **Delivery special**
For processing, see (`0x4652000000000004`) | 1.2 | +| `0x465200000000000C` | **Delivery zero**
For processing, see (`0x4652000000000005`) | 1.2 | +| `0x465200000000000D` | **Other services reduced-1**
For processing, see (`0x4652000000000001`) | 1.2 | +| `0x465200000000000E` | **Other services reduced-2**
For processing, see (`0x4652000000000002`) | 1.2 | +| `0x465200000000000F` | **Other services normal**
For processing, see (`0x4652000000000003`) | 1.2 | +| `0x4652000000000010` | **Other services special**
For processing, see (`0x4652000000000004`) | 1.2 | +| `0x4652000000000011` | **Other services zero**
For processing, see (`0x4652000000000005`) | 1.2 | +| `0x4652000000000012` | **Catalogue services reduced-1**
For processing, see (`0x4652000000000001`) | 1.2 | +| `0x4652000000000013` | **Catalogue services reduced-2**
For processing, see (`0x4652000000000002`) | 1.2 | +| `0x4652000000000014` | **Catalogue services normal**
For processing, see (`0x4652000000000003`) | 1.2 | +| `0x4652000000000015` | **Catalogue services special**
For processing, see (`0x4652000000000004`) | 1.2 | +| `0x4652000000000016` | **Catalogue services zero**
For processing, see (`0x4652000000000005`) | 1.2 | +| `0x4652000000000017` | **Own consumption reduced-1**
For processing, see (`0x4652000000000001`) | 1.2 | +| `0x4652000000000018` | **Own consumption reduced-2**
For processing, see (`0x4652000000000002`) | 1.2 | +| `0x4652000000000019` | **Own consumption normal**
For processing, see (`0x4652000000000003`) | 1.2 | +| `0x465200000000001A` | **Own consumption special**
For processing, see (`0x4652000000000004`) | 1.2 | +| `0x465200000000001B` | **Own consumption zero**
For processing, see (`0x4652000000000005`) | 1.2 | +| `0x465200000000001C` | **Prepayment reduced-1**
For processing, see (`0x4652000000000001`) | 1.2 | +| `0x465200000000001D` | **Prepayment reduced-2**
For processing, see (`0x4652000000000002`) | 1.2 | +| `0x465200000000001E` | **Prepayment normal**
For processing, see (`0x4652000000000003`) | 1.2 | +| `0x465200000000001F` | **Prepayment special**
For processing, see (`0x4652000000000004`) | 1.2 | +| `0x4652000000000020` | **Prepayment zero**
For processing, see (`0x4652000000000005`) | 1.2 | +| `0x4652000000000021` | **Account of a third party/ third party name/ collection**
For processing, see (`0x4652000000000007`) | 1.2 | +| `0x4652000000000022` | **Obligation** | 1.2 | + + + +*Table 35. Type of Service: ftChargeItemCase (FR – BOI-TVA-DECL 30-10-30)* diff --git a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/5 - ftPayItemCase.md b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/5 - ftPayItemCase.md new file mode 100644 index 00000000..f990e65e --- /dev/null +++ b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/5 - ftPayItemCase.md @@ -0,0 +1,37 @@ +--- +slug: /poscreators/middleware-doc/france/reference-tables +title: Type of Payment: ftPayItemCase +--- + +# Reference tables + +## Type of Payment: ftPayItemCase + +The `ftPayItemCase` defines the type of payment within the pay items block and how the fiskaltrust.SecurityMechanism processes individual payment of the receipt. + +| **Value** | **Description** | **Middleware Version** | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| `0x4652000000000000` | **Default value**
Unknown payment type: Automatic processing through the fiskaltrust.SecurityMechanism settings is attempted. | 1.2 | +| `0x4652000000000000` | **Unknown payment type for FR**
This is handled like a cash payment in national currency. | 1.2 | +| `0x4652000000000001` | **Cash payment in national currency**
cash | 1.2 | +| `0x4652000000000002` | **Cash payment in foreign currency**
cash | 1.2 | +| `0x4652000000000003` | **Crossed cheque**
cash | 1.2 | +| `0x4652000000000004` | **Debit card payment**
noncash | 1.2 | +| `0x4652000000000005` | **Credit card payment**
cash | 1.2 | +| `0x4652000000000006` | **Voucher payment (coupon) - voucher by money value**
cash | 1.2 | +| `0x4652000000000007` | **Online payment**
noncash | 1.2 | +| `0x4652000000000008` | **Customer card payment**
noncash | 1.2 | +| `0x4652000000000009` | **Other debit card**
noncash | 1.2 | +| `0x465200000000000A` | **Other credit card**
cash | 1.2 | +| `0x465200000000000B` | **Account receivable**
Delivery note/ settlement in foreign currency
internal | 1.2 | +| `0x465200000000000C` | **SEPA transfer**
noncash | 1.2 | +| `0x465200000000000D` | **Other transfer**
noncash | 1.2 | +| `0x465200000000000E` | **Cash book expense**
internal | 1.2 | +| `0x465200000000000F` | **Cash book contribution**
internal | 1.2 | +| `0x4652000000000010` | **Levy**
internal | 1.2 | +| `0x4652000000000011` | **Internal/ material consumption**
Can be used for bill
internal | 1.2 | +| `0x4652000000000012` | **Change**
tip
cash | 1.2 | + + + +*Table 36. Type of Payment: ftPayItemCase (FR - BOI-TVA-DECL 30-10-30)* \ No newline at end of file diff --git a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/6 - ftSignatureType.md b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/6 - ftSignatureType.md new file mode 100644 index 00000000..57d062e5 --- /dev/null +++ b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/6 - ftSignatureType.md @@ -0,0 +1,25 @@ +--- +slug: /poscreators/middleware-doc/france/reference-tables +title: Type of Signature: ftSignatureType +--- + +# Reference tables + +## Type of Signature: ftSignatureType + +The `ftSignatureType` indicates the type and origin of the signature. + +| **Value** | **Description** | **Version** | +|----------------------|---------------------|-------------| +| `0x4652000000000000` | unknown FR | | +| `0x4652000000000001` | JWT | 1.2 | +| `0x4652000000000002` | Shift Closing Sum | 1.2 | +| `0x4652000000000003` | Day Closing Sum | 1.2 | +| `0x4652000000000004` | Month Closing Sum | 1.2 | +| `0x4652000000000005` | Year Closing Sum | 1.2 | +| `0x4652000000000006` | Archive Totals Sum | 1.2 | +| `0x4652000000000007` | Perpetual Total Sum | 1.2 | + + + +*Table 37. Type of Signature: ftSignatureType (FR - BOI-TVA-DECL 30-10-30)* \ No newline at end of file diff --git a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/7 - ftJournalType.md b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/7 - ftJournalType.md new file mode 100644 index 00000000..41846562 --- /dev/null +++ b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/7 - ftJournalType.md @@ -0,0 +1,34 @@ +--- +slug: /poscreators/middleware-doc/france/reference-tables +title: Type of Journal: ftJournalType +--- + +# Reference tables + +## Type of Journal: ftJournalType + +The `ftJournalType` is used in connection with the journal function and defines the journal stream given back according to the French law. In the `ftJournalType`, the ISO-3166-1-ALPHA-2 from ASCII value is converted into hex and used as byte 8 and 7. For France (FR) this is 0x4652. + +| **Value** | **Description** | **Version** | +|----------------------|-------------------------------------|-------------| +| `0x4652000000000000` | Status information for queue FR | 1.2 | +| `0x4652000000000001` | Ticket ("T" group) export | 1.2 | +| `0x4652000000000002` | Payment Prove ("P" group) export | 1.2 | +| `0x4652000000000003` | Invoice ("I" group) export | 1.2 | +| `0x4652000000000004` | Grand Total ("G" group) export | 1.2 | +| `0x4652000000000007` | Bill ("B" group) export | 1.2 | +| `0x4652000000000008` | Archive ("A" group) export | 1.2 | +| `0x4652000000000009` | Log ("L" group) export | 1.2 | +| `0x465200000000000A` | Copy ("C" group) export | 1.2 | +| `0x465200000000000B` | Training ("X" group) export | 1.2 | +| `0x4652000000000010` | Export (in conjunction with Archiv) | 1.2 | + +*Table 38. Type of Journal: ftJournalType (FR - BOI-TVA-DECL 30-10-30)* + +### ftJournalTypeFlag + +Journals can be extracted in combination with these flags, indicated using codes in byte 5. These codes can be combined using the logic operator `OR`. + +| **Value** | **Description** | **Version** | +|----------------------|---------------------------------------------------------------------------|-------------| +| `0x0000000000010000` | Receive Archive as zip-file created with ReceiptCase `0x4652000000000015` | 1.2 | diff --git a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/8 - ftJournalTypeFlag.md b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/8 - ftJournalTypeFlag.md new file mode 100644 index 00000000..e6f3bba0 --- /dev/null +++ b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/8 - ftJournalTypeFlag.md @@ -0,0 +1,14 @@ +--- +slug: /poscreators/middleware-doc/france/reference-tables +title: Type of Journal: ftJournalTypeFlag +--- + +# Reference tables + +### ftJournalTypeFlag + +Journals can be extracted in combination with these flags, indicated using codes in byte 5. These codes can be combined using the logic operator `OR`. + +| **Value** | **Description** | **Version** | +|----------------------|---------------------------------------------------------------------------|-------------| +| `0x0000000000010000` | Receive Archive as zip-file created with ReceiptCase `0x4652000000000015` | 1.2 | \ No newline at end of file From ecfa0674316878030fc047b600dfd24d717b2d2f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 07:16:55 +0200 Subject: [PATCH 02/20] Update and rename 1- ftState.md to service-status-ftstate --- .../reference-tables/{1- ftState.md => service-status-ftstate} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename doc/middleware-at-rksv/reference-tables/{1- ftState.md => service-status-ftstate} (99%) diff --git a/doc/middleware-at-rksv/reference-tables/1- ftState.md b/doc/middleware-at-rksv/reference-tables/service-status-ftstate similarity index 99% rename from doc/middleware-at-rksv/reference-tables/1- ftState.md rename to doc/middleware-at-rksv/reference-tables/service-status-ftstate index cd4a04dd..7e7d57ee 100644 --- a/doc/middleware-at-rksv/reference-tables/1- ftState.md +++ b/doc/middleware-at-rksv/reference-tables/service-status-ftstate @@ -1,6 +1,6 @@ --- slug: /poscreators/middleware-doc/austria/reference-tables -title: Service Status: ftState +title: 'Service Status: ftState' --- ## Reference tables From cd8d0a8ce0a58c95a8f57f8699a7e37292208f5b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 07:43:34 +0200 Subject: [PATCH 03/20] Update and rename 2 - ftReceiptCase.md to type-of-receipt-ftreceiptcase --- .../{2 - ftReceiptCase.md => type-of-receipt-ftreceiptcase} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename doc/middleware-at-rksv/reference-tables/{2 - ftReceiptCase.md => type-of-receipt-ftreceiptcase} (99%) diff --git a/doc/middleware-at-rksv/reference-tables/2 - ftReceiptCase.md b/doc/middleware-at-rksv/reference-tables/type-of-receipt-ftreceiptcase similarity index 99% rename from doc/middleware-at-rksv/reference-tables/2 - ftReceiptCase.md rename to doc/middleware-at-rksv/reference-tables/type-of-receipt-ftreceiptcase index 4a8e937b..4244b767 100644 --- a/doc/middleware-at-rksv/reference-tables/2 - ftReceiptCase.md +++ b/doc/middleware-at-rksv/reference-tables/type-of-receipt-ftreceiptcase @@ -1,6 +1,6 @@ --- slug: /poscreators/middleware-doc/austria/reference-tables -title: Type of Receipt: ftReceiptCase +title: 'Type of receipt: ftReceiptCase' --- ### Type of Receipt: ftReceiptCase From 90ee738fedcfc39e2a3bfb3d6954952927547f03 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 07:46:01 +0200 Subject: [PATCH 04/20] Update type-of-receipt-ftreceiptcase --- .../type-of-receipt-ftreceiptcase | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/doc/middleware-at-rksv/reference-tables/type-of-receipt-ftreceiptcase b/doc/middleware-at-rksv/reference-tables/type-of-receipt-ftreceiptcase index 4244b767..5454f3b3 100644 --- a/doc/middleware-at-rksv/reference-tables/type-of-receipt-ftreceiptcase +++ b/doc/middleware-at-rksv/reference-tables/type-of-receipt-ftreceiptcase @@ -32,3 +32,23 @@ For Austria (AT) the country code is `0x4154`. Thus, the value for an unknown ft *Table 22. Type of Receipt: ftReceiptCase (AT - RKSVO)* + +## ftReceiptCaseFlag + +This table expands on the values provided in the table ["Type of Receipt: ftReceiptCaseFlag"](../../general/reference-tables/reference-tables.md#t-type-of-receipt-ftreceiptcaseflag-64) of with values applicable to the Austrian market. + +| Value | Description | Middleware-Version | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| `0x0000000000010000` | "out of service"
The transferred receipt contains data which has been created during an outage of the security mechanism. The original receipts are available in handwritten or digital format and must now be transferred and subsequently consolidated and signed via zero receipt. In order to decide whether it is a temporary or permanent (more than 48 hours) outage of the security mechanism (for example in case of theft), the "oldest" or the receipt with the earliest date/time value of all retrieved receipts is used. This can be necessary, for example, after a power or server outage. | 1.0 | +| `0x0000000000020000` | "training receipt"
Requests with this type of receipt are annotated with the reference "TRA" in the signature block. Instead of the encrypted cumulative sales counter, the BASE64 encrypted value of the TRA string is entered. The sales counter is, in accordance with the RKSV, not adjusted. | 1.0 | +| `0x0000000000040000` | "reverse receipt"
Requests with this type of receipt are annotated with the reference "STO" in the signature block. Instead of the encrypted cumulative sales counter, a BASE64 encrypted value of the STO string is entered. Further processing depends on the underlying type of receipt. | 1.0 | +| `0x0000000000080000` | "handwritten receipt" or "subsequent entry"
The transferred receipt contains data which has been collected in a handwritten receipt. Although there is no requirement for a time annotation on a handwritten receipt we recommend using 12:00 for this purpose.
Further processing depends on the underlying type of receipt. For example, this can be conducted after §7 cash revenue law for sales made outside business premises. | 1.0 | +| `0x0000000000100000` | "small business, sales tax relief in accordance with §6 Abs 1 Z 27 UStG (sales tax law)"
The transferred receipt contains data which have been generated by a small business. A special note "sales tax relief in accordance with §6 Abs 1 Z 27" is possible. The RKSV requirement is handled according to the basic business transaction.
The transferred receipt data should contain the correct VAT rate and the correct ftChargeItemCase, even if the identified sales tax is 0%. | 1.0 | +| `0x0000000000200000` | "receiver is a company"
The transferred receipt contains a sales receipt, and the receiver is a trader.
Note regarding the characteristics of §11 UStG: for receipts with up to €400 gross amount, an invoice for small amounts can be issued. From €400 onwards, there are additional features to be displayed on the invoice, to enable the pre-tax deduction for the receiver of the invoice.
For receipts with a gross amount of €10.000 or more, in addition, the service receiver’s UID number has to be indicated.
We suggest transferring the data about the receiver in the field ftReceiptCaseData, in manufacturer-specific JSON format. | 1.0 | +| `0x0000000000400000` | "contains characteristics in accordance with §11 UStG"
On the receipt, the characteristics are issued in accordance with §11 UStG, and the transferred receipt contains receiver data in manufacturer-specific JSON format within the field ftReceiptCaseData. | 1.0 | +| `0x0000800000000000` | Receipt request. Common behaviour. | | + + + +*Table 23. Type of Receipt: ftReceiptCase Flags(AT - RKSVO)* + From 7cbaea801ea07bf33a226885e6ac62fb5055ade2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 07:47:43 +0200 Subject: [PATCH 05/20] Delete 3- ftReceiptCaseFlag.md --- .../reference-tables/3- ftReceiptCaseFlag.md | 23 ------------------- 1 file changed, 23 deletions(-) delete mode 100644 doc/middleware-at-rksv/reference-tables/3- ftReceiptCaseFlag.md diff --git a/doc/middleware-at-rksv/reference-tables/3- ftReceiptCaseFlag.md b/doc/middleware-at-rksv/reference-tables/3- ftReceiptCaseFlag.md deleted file mode 100644 index a8d0207f..00000000 --- a/doc/middleware-at-rksv/reference-tables/3- ftReceiptCaseFlag.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -slug: /poscreators/middleware-doc/austria/reference-tables -title: Reference tables ---- - -#### ftReceiptCaseFlag - -This table expands on the values provided in the table ["Type of Receipt: ftReceiptCaseFlag"](../../general/reference-tables/reference-tables.md#t-type-of-receipt-ftreceiptcaseflag-64) of with values applicable to the Austrian market. - -| Value | Description | Middleware-Version | -|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| -| `0x0000000000010000` | "out of service"
The transferred receipt contains data which has been created during an outage of the security mechanism. The original receipts are available in handwritten or digital format and must now be transferred and subsequently consolidated and signed via zero receipt. In order to decide whether it is a temporary or permanent (more than 48 hours) outage of the security mechanism (for example in case of theft), the "oldest" or the receipt with the earliest date/time value of all retrieved receipts is used. This can be necessary, for example, after a power or server outage. | 1.0 | -| `0x0000000000020000` | "training receipt"
Requests with this type of receipt are annotated with the reference "TRA" in the signature block. Instead of the encrypted cumulative sales counter, the BASE64 encrypted value of the TRA string is entered. The sales counter is, in accordance with the RKSV, not adjusted. | 1.0 | -| `0x0000000000040000` | "reverse receipt"
Requests with this type of receipt are annotated with the reference "STO" in the signature block. Instead of the encrypted cumulative sales counter, a BASE64 encrypted value of the STO string is entered. Further processing depends on the underlying type of receipt. | 1.0 | -| `0x0000000000080000` | "handwritten receipt" or "subsequent entry"
The transferred receipt contains data which has been collected in a handwritten receipt. Although there is no requirement for a time annotation on a handwritten receipt we recommend using 12:00 for this purpose.
Further processing depends on the underlying type of receipt. For example, this can be conducted after §7 cash revenue law for sales made outside business premises. | 1.0 | -| `0x0000000000100000` | "small business, sales tax relief in accordance with §6 Abs 1 Z 27 UStG (sales tax law)"
The transferred receipt contains data which have been generated by a small business. A special note "sales tax relief in accordance with §6 Abs 1 Z 27" is possible. The RKSV requirement is handled according to the basic business transaction.
The transferred receipt data should contain the correct VAT rate and the correct ftChargeItemCase, even if the identified sales tax is 0%. | 1.0 | -| `0x0000000000200000` | "receiver is a company"
The transferred receipt contains a sales receipt, and the receiver is a trader.
Note regarding the characteristics of §11 UStG: for receipts with up to €400 gross amount, an invoice for small amounts can be issued. From €400 onwards, there are additional features to be displayed on the invoice, to enable the pre-tax deduction for the receiver of the invoice.
For receipts with a gross amount of €10.000 or more, in addition, the service receiver’s UID number has to be indicated.
We suggest transferring the data about the receiver in the field ftReceiptCaseData, in manufacturer-specific JSON format. | 1.0 | -| `0x0000000000400000` | "contains characteristics in accordance with §11 UStG"
On the receipt, the characteristics are issued in accordance with §11 UStG, and the transferred receipt contains receiver data in manufacturer-specific JSON format within the field ftReceiptCaseData. | 1.0 | -| `0x0000800000000000` | Receipt request. Common behaviour. | | - - - -*Table 23. Type of Receipt: ftReceiptCase Flags(AT - RKSVO)* From 1f87895c89e36fa7a3acd51edc1a0bd82d4332e0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 07:53:36 +0200 Subject: [PATCH 06/20] Update and rename 4 - ftChargeItemCase.md to type-of-service-ftchargeitemcase --- ...4 - ftChargeItemCase.md => type-of-service-ftchargeitemcase} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename doc/middleware-at-rksv/reference-tables/{4 - ftChargeItemCase.md => type-of-service-ftchargeitemcase} (99%) diff --git a/doc/middleware-at-rksv/reference-tables/4 - ftChargeItemCase.md b/doc/middleware-at-rksv/reference-tables/type-of-service-ftchargeitemcase similarity index 99% rename from doc/middleware-at-rksv/reference-tables/4 - ftChargeItemCase.md rename to doc/middleware-at-rksv/reference-tables/type-of-service-ftchargeitemcase index dd0df8a3..098241ba 100644 --- a/doc/middleware-at-rksv/reference-tables/4 - ftChargeItemCase.md +++ b/doc/middleware-at-rksv/reference-tables/type-of-service-ftchargeitemcase @@ -1,6 +1,6 @@ --- slug: /poscreators/middleware-doc/austria/reference-tables -title: Type of Service: ftChargeItemCase +title: 'Type of service: ftChargeItemCase' --- ### Type of Service: ftChargeItemCase From 2879fc00834cc95ff814726cef0b1326978dc4f7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 08:00:27 +0200 Subject: [PATCH 07/20] Update and rename 5 - ftPayItemCase.md to type-of-payment-ftpayitemcase --- .../{5 - ftPayItemCase.md => type-of-payment-ftpayitemcase} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename doc/middleware-at-rksv/reference-tables/{5 - ftPayItemCase.md => type-of-payment-ftpayitemcase} (99%) diff --git a/doc/middleware-at-rksv/reference-tables/5 - ftPayItemCase.md b/doc/middleware-at-rksv/reference-tables/type-of-payment-ftpayitemcase similarity index 99% rename from doc/middleware-at-rksv/reference-tables/5 - ftPayItemCase.md rename to doc/middleware-at-rksv/reference-tables/type-of-payment-ftpayitemcase index 34ea5d63..135a0809 100644 --- a/doc/middleware-at-rksv/reference-tables/5 - ftPayItemCase.md +++ b/doc/middleware-at-rksv/reference-tables/type-of-payment-ftpayitemcase @@ -1,6 +1,6 @@ --- slug: /poscreators/middleware-doc/austria/reference-tables -title: Type of Payment: ftPayItemCase +title: 'Type of Payment: ftPayItemCase' --- ### Type of Payment: ftPayItemCase From cebf6697fe1688714ded950c8a125d3bb21329d4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 08:04:37 +0200 Subject: [PATCH 08/20] Update and rename 6 - ftSignatureFormat.md to 'Type of Payment: ftPayItemCase' --- ...at.md => 'Type of Payment: ftPayItemCase'} | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) rename doc/middleware-at-rksv/reference-tables/{6 - ftSignatureFormat.md => 'Type of Payment: ftPayItemCase'} (60%) diff --git a/doc/middleware-at-rksv/reference-tables/6 - ftSignatureFormat.md b/doc/middleware-at-rksv/reference-tables/'Type of Payment: ftPayItemCase' similarity index 60% rename from doc/middleware-at-rksv/reference-tables/6 - ftSignatureFormat.md rename to doc/middleware-at-rksv/reference-tables/'Type of Payment: ftPayItemCase' index 37dfa79f..648b2ad9 100644 --- a/doc/middleware-at-rksv/reference-tables/6 - ftSignatureFormat.md +++ b/doc/middleware-at-rksv/reference-tables/'Type of Payment: ftPayItemCase' @@ -1,9 +1,9 @@ --- slug: /poscreators/middleware-doc/austria/reference-tables -title: Type of Signature: ftSignatureFormat +title: 'Format of signature: ftSignatureFormat' --- -### Type of Signature: ftSignatureFormat +# Type of Signature: ftSignatureFormat This table expands on the values provided in the table ["Format of Signature: ftSignatureFormat"](../../general/reference-tables/reference-tables.md#t-type-of-signature-ftsignatureformat-112) with values applicable to the Austrian market. @@ -28,3 +28,18 @@ According to the RKSV, there is one exception: if the fiskaltrust.SecurityMechan *Table 26. Type of Signature: ftSignatureFormat (AT - RKSVO)* + +## Type of Signature: ftSignatureType + +This table expands on the values provided in the table ["Type of Signature: ftSignatureType"](../../general/reference-tables/reference-tables.md#t-type-of-signature-ftsignaturetype-127) with values applicable to the Austrian market. + +| **Value** | **Description** | **Version** | +| -------------------- | ------------------------------------------------------------ | ----------- | +| `0x4154000000000000` | unknown | 1.0 | +| `0x4154000000000001` | signature according to RKSV | 1.0 | +| `0x4154000000000002` | Archiving required according to RKSV or BAO §132.
E.g. notification of collective receipt after failure, initial receipt, monthly receipt, etc.. | 1.0 | +| `0x4154000000000003` | FinanzOnline notification | 1.0 | + + + +*Table 27. Type of Signature: ftSignatureType (AT - RKSVO)* From 3f293a992e72148242894e3454da559e9e27a011 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 08:04:50 +0200 Subject: [PATCH 09/20] Delete 7 - ftSignatureType.md --- .../reference-tables/7 - ftSignatureType.md | 19 ------------------- 1 file changed, 19 deletions(-) delete mode 100644 doc/middleware-at-rksv/reference-tables/7 - ftSignatureType.md diff --git a/doc/middleware-at-rksv/reference-tables/7 - ftSignatureType.md b/doc/middleware-at-rksv/reference-tables/7 - ftSignatureType.md deleted file mode 100644 index b77955be..00000000 --- a/doc/middleware-at-rksv/reference-tables/7 - ftSignatureType.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -slug: /poscreators/middleware-doc/austria/reference-tables -title: Type of Signature: ftSignatureType ---- - -### Type of Signature: ftSignatureType - -This table expands on the values provided in the table ["Type of Signature: ftSignatureType"](../../general/reference-tables/reference-tables.md#t-type-of-signature-ftsignaturetype-127) with values applicable to the Austrian market. - -| **Value** | **Description** | **Version** | -| -------------------- | ------------------------------------------------------------ | ----------- | -| `0x4154000000000000` | unknown | 1.0 | -| `0x4154000000000001` | signature according to RKSV | 1.0 | -| `0x4154000000000002` | Archiving required according to RKSV or BAO §132.
E.g. notification of collective receipt after failure, initial receipt, monthly receipt, etc.. | 1.0 | -| `0x4154000000000003` | FinanzOnline notification | 1.0 | - - - -*Table 27. Type of Signature: ftSignatureType (AT - RKSVO)* \ No newline at end of file From f60e76e070c5f1ae1804173ed05bb7b30e1e3134 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 08:05:15 +0200 Subject: [PATCH 10/20] Rename 'Type of Payment: ftPayItemCase' to type-of-payment-ftpayitemcase' --- ... of Payment: ftPayItemCase' => type-of-payment-ftpayitemcase'} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename doc/middleware-at-rksv/reference-tables/{'Type of Payment: ftPayItemCase' => type-of-payment-ftpayitemcase'} (100%) diff --git a/doc/middleware-at-rksv/reference-tables/'Type of Payment: ftPayItemCase' b/doc/middleware-at-rksv/reference-tables/type-of-payment-ftpayitemcase' similarity index 100% rename from doc/middleware-at-rksv/reference-tables/'Type of Payment: ftPayItemCase' rename to doc/middleware-at-rksv/reference-tables/type-of-payment-ftpayitemcase' From 3de9801b55cc5a099bf6628e5f58fa60381b9e7c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 08:06:28 +0200 Subject: [PATCH 11/20] Update and rename 8 - ftJournalType.md to type-of-journal-ftjournaltype --- .../{8 - ftJournalType.md => type-of-journal-ftjournaltype} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename doc/middleware-at-rksv/reference-tables/{8 - ftJournalType.md => type-of-journal-ftjournaltype} (99%) diff --git a/doc/middleware-at-rksv/reference-tables/8 - ftJournalType.md b/doc/middleware-at-rksv/reference-tables/type-of-journal-ftjournaltype similarity index 99% rename from doc/middleware-at-rksv/reference-tables/8 - ftJournalType.md rename to doc/middleware-at-rksv/reference-tables/type-of-journal-ftjournaltype index 8a92ec9f..8b24f6e3 100644 --- a/doc/middleware-at-rksv/reference-tables/8 - ftJournalType.md +++ b/doc/middleware-at-rksv/reference-tables/type-of-journal-ftjournaltype @@ -1,6 +1,6 @@ --- slug: /poscreators/middleware-doc/austria/reference-tables -title: Reference tables +title: 'Type of Journal: ftJournalType' --- ## Reference tables From e43a46b85d3a4c3c651799da5cbe84f2333f01a9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 08:07:33 +0200 Subject: [PATCH 12/20] Update and rename 8 - ftJournalTypeFlag.md to type-of-journal-ftjournaltype --- ...8 - ftJournalTypeFlag.md => type-of-journal-ftjournaltype} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/{8 - ftJournalTypeFlag.md => type-of-journal-ftjournaltype} (85%) diff --git a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/8 - ftJournalTypeFlag.md b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-journal-ftjournaltype similarity index 85% rename from doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/8 - ftJournalTypeFlag.md rename to doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-journal-ftjournaltype index e6f3bba0..7fa4f1c3 100644 --- a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/8 - ftJournalTypeFlag.md +++ b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-journal-ftjournaltype @@ -1,6 +1,6 @@ --- slug: /poscreators/middleware-doc/france/reference-tables -title: Type of Journal: ftJournalTypeFlag +title: 'Type of Journal: ftJournalType' --- # Reference tables @@ -11,4 +11,4 @@ Journals can be extracted in combination with these flags, indicated using codes | **Value** | **Description** | **Version** | |----------------------|---------------------------------------------------------------------------|-------------| -| `0x0000000000010000` | Receive Archive as zip-file created with ReceiptCase `0x4652000000000015` | 1.2 | \ No newline at end of file +| `0x0000000000010000` | Receive Archive as zip-file created with ReceiptCase `0x4652000000000015` | 1.2 | From 9f2492a6266288cbe15309b08daf2ef06be2be6f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 08:10:31 +0200 Subject: [PATCH 13/20] Update and rename 1 - ftState.md to service-status-ftstate --- .../reference-tables/{1 - ftState.md => service-status-ftstate} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/{1 - ftState.md => service-status-ftstate} (97%) diff --git a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/1 - ftState.md b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/service-status-ftstate similarity index 97% rename from doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/1 - ftState.md rename to doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/service-status-ftstate index 57d0031e..dc2631cd 100644 --- a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/1 - ftState.md +++ b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/service-status-ftstate @@ -1,6 +1,6 @@ --- slug: /poscreators/middleware-doc/france/reference-tables -title: Service Status: ftState +title: 'Service Status: ftState' --- # Reference tables From bc9ed660287d776681b145fdb41f3d45cfa9897d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 08:12:04 +0200 Subject: [PATCH 14/20] Update and rename 2 - ftReceiptCase.md to type-of-receipt-ftreceiptcase --- ...tCase.md => type-of-receipt-ftreceiptcase} | 20 ++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) rename doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/{2 - ftReceiptCase.md => type-of-receipt-ftreceiptcase} (86%) diff --git a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/2 - ftReceiptCase.md b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-receipt-ftreceiptcase similarity index 86% rename from doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/2 - ftReceiptCase.md rename to doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-receipt-ftreceiptcase index 8c8ba3f2..0af8d403 100644 --- a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/2 - ftReceiptCase.md +++ b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-receipt-ftreceiptcase @@ -1,6 +1,6 @@ --- slug: /poscreators/middleware-doc/france/reference-tables/receiptcase -title: Type of receipt: ftReceiptCase +title: 'Type of receipt: ftReceiptCase' --- # Reference tables @@ -39,3 +39,21 @@ The country-specific code is made of the country's code value following the ISO- *Table 33. Type of Receipt: ftReceiptCase (FR – BOI-TVA-DECL 30-10-30)* +# ftReceiptCaseFlag + +According to French law and regulations, various business transactions can result in specific combinations of types of receipts. For this, bytes 6, 5, 4 and 3 are used as combinable codes. These codes can be added with the logic operator "OR". + +| **Value** | **Description** | **Version** | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| `0x0000000000010000` | **Failed receipt**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). | 1.2 | +| `0x0000000000020000` | **Training receipt**
All requests issued with this flag are chained and signed in a separate chain. The phrase "mode école" is printed on any artefact that is printed while the flag is being used. For national numbering "X" is used.
GT counters are not raised. | 1.2 | +| `0x0000000000030000` | **Failed training receipt**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). | 1.2 | +| `0x0000000000040000` | **Reverse/voided receipt**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). |1.2|| +| `0x0000000000050000` | **Failed reverse/voided receipt**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). | 1.2 | | | +| `0x0000000000060000` | **Failed reverse/voided training receipt**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). | 1.2 | +| `0x0000800000000000` | **Receipt request**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). | 1.2 | + + + +*Table 34. Type of Receipt: ftReceiptCase Flags (FR – BOI-TVA-DECL 30-10-30)* + From 34b74da1edfe56498ad00e3afda764db36918ce8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 08:12:20 +0200 Subject: [PATCH 15/20] Delete 3 - ftReceiptCaseFlag.md --- .../reference-tables/3 - ftReceiptCaseFlag.md | 24 ------------------- 1 file changed, 24 deletions(-) delete mode 100644 doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/3 - ftReceiptCaseFlag.md diff --git a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/3 - ftReceiptCaseFlag.md b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/3 - ftReceiptCaseFlag.md deleted file mode 100644 index 283df60e..00000000 --- a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/3 - ftReceiptCaseFlag.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -slug: /poscreators/middleware-doc/france/reference-tables -title: Type of receipt: ftReceiptCaseFlag ---- - -# Reference tables - -### ftReceiptCaseFlag - -According to French law and regulations, various business transactions can result in specific combinations of types of receipts. For this, bytes 6, 5, 4 and 3 are used as combinable codes. These codes can be added with the logic operator "OR". - -| **Value** | **Description** | **Version** | -|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| `0x0000000000010000` | **Failed receipt**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). | 1.2 | -| `0x0000000000020000` | **Training receipt**
All requests issued with this flag are chained and signed in a separate chain. The phrase "mode école" is printed on any artefact that is printed while the flag is being used. For national numbering "X" is used.
GT counters are not raised. | 1.2 | -| `0x0000000000030000` | **Failed training receipt**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). | 1.2 | -| `0x0000000000040000` | **Reverse/voided receipt**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). |1.2|| -| `0x0000000000050000` | **Failed reverse/voided receipt**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). | 1.2 | | | -| `0x0000000000060000` | **Failed reverse/voided training receipt**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). | 1.2 | -| `0x0000800000000000` | **Receipt request**
Common behaviour, see [general part](https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/general/reference-tables#ftreceiptcaseflag). | 1.2 | - - - -*Table 34. Type of Receipt: ftReceiptCase Flags (FR – BOI-TVA-DECL 30-10-30)* From 8053464d610cd9fb25c4e81416f961bb81914233 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 08:13:59 +0200 Subject: [PATCH 16/20] Update and rename 4 - ftChargeItemCase.md to type-of-service-ftchargeitemcase --- ...4 - ftChargeItemCase.md => type-of-service-ftchargeitemcase} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/{4 - ftChargeItemCase.md => type-of-service-ftchargeitemcase} (99%) diff --git a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/4 - ftChargeItemCase.md b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-service-ftchargeitemcase similarity index 99% rename from doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/4 - ftChargeItemCase.md rename to doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-service-ftchargeitemcase index 23166986..35ebef50 100644 --- a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/4 - ftChargeItemCase.md +++ b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-service-ftchargeitemcase @@ -1,6 +1,6 @@ --- slug: /poscreators/middleware-doc/france/reference-tables -title: Type of sevices: ftChargeItemCase +title: 'Type of service: ftChargeItemCase' --- # Reference tables From ad545f685e727d20843e1dd1afc03a97a2c2e402 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 08:14:35 +0200 Subject: [PATCH 17/20] Update and rename 5 - ftPayItemCase.md to type-of-payment-ftpayitemcase --- .../{5 - ftPayItemCase.md => type-of-payment-ftpayitemcase} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/{5 - ftPayItemCase.md => type-of-payment-ftpayitemcase} (98%) diff --git a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/5 - ftPayItemCase.md b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-payment-ftpayitemcase similarity index 98% rename from doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/5 - ftPayItemCase.md rename to doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-payment-ftpayitemcase index f990e65e..be9bfc0b 100644 --- a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/5 - ftPayItemCase.md +++ b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-payment-ftpayitemcase @@ -1,6 +1,6 @@ --- slug: /poscreators/middleware-doc/france/reference-tables -title: Type of Payment: ftPayItemCase +title: 'Type of Payment: ftPayItemCase' --- # Reference tables @@ -34,4 +34,4 @@ The `ftPayItemCase` defines the type of payment within the pay items block and h -*Table 36. Type of Payment: ftPayItemCase (FR - BOI-TVA-DECL 30-10-30)* \ No newline at end of file +*Table 36. Type of Payment: ftPayItemCase (FR - BOI-TVA-DECL 30-10-30)* From 43099086e41cc10f5bbe4a5732d7dd0617e9a010 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 08:15:53 +0200 Subject: [PATCH 18/20] Update and rename 6 - ftSignatureType.md to type-of-signature-ftsignaturetype --- ...- ftSignatureType.md => type-of-signature-ftsignaturetype} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/{6 - ftSignatureType.md => type-of-signature-ftsignaturetype} (93%) diff --git a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/6 - ftSignatureType.md b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-signature-ftsignaturetype similarity index 93% rename from doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/6 - ftSignatureType.md rename to doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-signature-ftsignaturetype index 57d062e5..c355e367 100644 --- a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/6 - ftSignatureType.md +++ b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-signature-ftsignaturetype @@ -1,6 +1,6 @@ --- slug: /poscreators/middleware-doc/france/reference-tables -title: Type of Signature: ftSignatureType +title: 'Type of signature: ftSignatureType' --- # Reference tables @@ -22,4 +22,4 @@ The `ftSignatureType` indicates the type and origin of the signature. -*Table 37. Type of Signature: ftSignatureType (FR - BOI-TVA-DECL 30-10-30)* \ No newline at end of file +*Table 37. Type of Signature: ftSignatureType (FR - BOI-TVA-DECL 30-10-30)* From 8623d0ce5afe676ac5ad5dceed2f0dbd0c49dc94 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 08:18:15 +0200 Subject: [PATCH 19/20] Delete type-of-journal-ftjournaltype --- .../reference-tables/type-of-journal-ftjournaltype | 14 -------------- 1 file changed, 14 deletions(-) delete mode 100644 doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-journal-ftjournaltype diff --git a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-journal-ftjournaltype b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-journal-ftjournaltype deleted file mode 100644 index 7fa4f1c3..00000000 --- a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-journal-ftjournaltype +++ /dev/null @@ -1,14 +0,0 @@ ---- -slug: /poscreators/middleware-doc/france/reference-tables -title: 'Type of Journal: ftJournalType' ---- - -# Reference tables - -### ftJournalTypeFlag - -Journals can be extracted in combination with these flags, indicated using codes in byte 5. These codes can be combined using the logic operator `OR`. - -| **Value** | **Description** | **Version** | -|----------------------|---------------------------------------------------------------------------|-------------| -| `0x0000000000010000` | Receive Archive as zip-file created with ReceiptCase `0x4652000000000015` | 1.2 | From 28b7c5341dedae3982f29f0247ab52823e6d9ce5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bluette=5FC=2ERivi=C3=A8re?= <93588444+Bluette-C-Riviere@users.noreply.github.com> Date: Thu, 25 May 2023 08:18:52 +0200 Subject: [PATCH 20/20] Update and rename 7 - ftJournalType.md to type-of-journal-ftjournaltype --- .../{7 - ftJournalType.md => type-of-journal-ftjournaltype} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/{7 - ftJournalType.md => type-of-journal-ftjournaltype} (98%) diff --git a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/7 - ftJournalType.md b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-journal-ftjournaltype similarity index 98% rename from doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/7 - ftJournalType.md rename to doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-journal-ftjournaltype index 41846562..cf00407e 100644 --- a/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/7 - ftJournalType.md +++ b/doc/middleware-fr-boi-tva-decl-30-10-30/reference-tables/type-of-journal-ftjournaltype @@ -1,6 +1,6 @@ --- slug: /poscreators/middleware-doc/france/reference-tables -title: Type of Journal: ftJournalType +title: Type of Journal: ftJournalType' --- # Reference tables