Skip to content
Open
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,12 @@ The results will be shown, and the content will be available for download on a d

The procedure archives the requested period. An archive can contain a maximum of 12 months from the start of the queue or from the last archive date, up to the receipt's date. If the archiving period is longer than 12 months, multiple archive receipts have to be sent with the start date of each consecutive receipt beginning right after the end date of the previous one.

Every time an archive receipt is sent to the middleware, a hash recalculation is performed. If any discrepancies are found in the hashes, an error message will be displayed in the portal, under (Configuration-\> Queues\>ActionJournal)
Every time an archive receipt is sent to the middleware, a hash recalculation is performed. If any discrepancies are found in the hashes, an error message starting by `Code 90` will be displayed in the portal, under (Configuration-\> Queues\>ActionJournal)
Comment thread
LGuichet marked this conversation as resolved.
Outdated


For NF525 compliant cash registers, this error message must be checked after each archive request by calling the journal endpoint.

The action journal request call is type 1, and will respond with a list of entries. If one or more entries's message starts by "Code 90" : `"Message": "Code 90 , \\NF525\\ Detection of an integrity flaw in secured data or a tax archive"`, the cash register must send a Technical Event Log receipt request to the middleware including : `"ftReceiptCaseData" : "{\"Code\": \"90\", \"Message\": \"Detection of an integrity flaw in secured data or a tax archive\"}"`
Comment thread
LGuichet marked this conversation as resolved.
Outdated

## Receipt Structure

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -135,6 +135,11 @@ There are no special requirements or laws for the French market.
A Signature Entry can include an electronic signature for printing on the receipt and further information regarding the operational state of the fiskaltrust.SecurityMechanism. Furthermore, but only when receipts with special functions are used, the previous state of the totalizers (in case of a temporal closure), can also be sent back in this block.
**All SignatureItems send back to the POS-System must be printed on the receipt, therefore it's mandatory to print the content of the fields _Caption_ and _Data_.**
Comment thread
LGuichet marked this conversation as resolved.
Outdated

The signature excerpt (ftSignatureType 0x4652000000000008) is only mandatory for NF525 compliance and the caption "-----" must not be printed. It is 4 characters extracted from the JWT signature part and following NF525 specification (characters 3, 7, 13 and 19).
Comment thread
LGuichet marked this conversation as resolved.
Outdated
NF525 requires that the signature excerpt must to be printed after the product number shown on the NF525 certificate.

Exemple with signature excerpt "Wxi2" and product number "1234" : `(NF525) B 1234 Wxi2 HAPPYPOS v1.1`
Comment thread
LGuichet marked this conversation as resolved.
Outdated

This table describes additional fields of the Signature Entry applicable to the French market.

| **Field Name** | **Data Type** | **Default Value**<br />**Mandatory Field** | **Description** | **Version** |
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -166,6 +166,7 @@ The `ftSignatureType` indicates the type and origin of the signature.
| `0x4652000000000005` | Year Closing Sum | 1.2 |
| `0x4652000000000006` | Archive Totals Sum | 1.2 |
| `0x4652000000000007` | Perpetual Total Sum | 1.2 |
| `0x4652000000000008` | Signature Excerpt | 1.2 |

<span id="_Toc527986689" class="anchor"></span>

Expand Down
Loading