Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »

Le but de cette documentation est de définir les modalités de l'archivage fiscal :

Documentation en français

COMMENT LIRE LES ARCHIVES

L'archive fiscale est créée pour les factures et les tickets créés dans la plage de dates sélectionnée avant de créer une archive. Un fichier zip est créé avec plusieurs fichiers Excel qui contiennent les détails des factures et des tickets concernés. En outre, ce fichier explicatif fait partie de l'archive fiscale créée.

L'intégrité du fichier est contrôlée par la signature électronique créée qui est ajoutée séparément dans le fichier. Pour générer la signature électronique, les paramètres d'entrée suivants sont nécessaires :

  • Taxes comprises, montants décomposés par taux de tva

  • Montants TTC de la période

  • Horodatage de l'opération

  • Code terminal/POS

  • Type d'opération

  • Signature précédente O/N

  • Si présente, signature électronique précédente

L'ARCHITECTURE DE L'ARCHIVE

Pour chaque archive générée, un fichier zip est créé. Ce fichier est enregistré dans un Google Cloud Storage Bucket et rendu accessible par le logiciel en tant qu'option de téléchargement.

Avant la création du fichier zip, tous les fichiers requis sont constitués. Principalement en exportant les données de la base de données Oracle dans un fichier csv, combiné avec ce pdf, le tout est rassemblé dans une archive zip. Pour ce fichier zip, nous générons un hash de signature et l'enregistrons dans la base de données.

LE CONTENU DES ARCHIVES

Les fichiers de l'archive sont les suivants :

*Reservation_Tax_Total_Report: Il s'agit du principal fichier des archives fiscales, qui contient presque tous les détails relatifs aux factures, aux tickets et aux totaux de clôture périodiques.

*Reservation_Tax_Report: Ce document contient les spécificités de la TVA au niveau des tickets/factures.

*Eventlog_Report: Ce document contient les données JET pour la gamme sélectionnée, qui sont enregistrées dans la table nf525_eventlog.

*Reservation_Bill_Snapshot_Report: Ce document contient un extrait de la facture, chaque fois qu'une transaction sur la réservation est effectuée. Les données sont enregistrées dans la table reservation_bill_snapshot.

*Payment: Ce document contient les détails des paiements reçus.

*signature_file: Ce document contient la signature électronique de l'archive, ainsi que la signature électronique de l'archive fiscale précédente ( si elle existe).

Pour chaque fichier, une explication plus détaillée des principales colonnes est donnée :

Document Name

Main Columns

Details

Reservation_tax_total_report

GTT, GTF, GTP, GTM, GTA,

This file holds all grand totals for the archive created, which is stored in nf525_reservation_tax_total and the applicable tax values and amounts from reservation_tax_total table

Operation type, electronic signatures, customer details, issueing entity details, operation type, NF version, software name

Furthermore, the following ticket and invoice details are included

Reservation_tax_report

RESERVATION_TAX_TOTAL_ID

ID for corresponding record in Reservation_tax_total_report

TAX_PERCENTAGE

Identifier of VAT rate for the record

TAX_AMOUNT

VAT amount for VAT rate

RESOURCE_AMOUNT_INCL_TAX

Total bill amount including VAT for the VAT rate

RESOURCE_AMOUNT_EXCL_TAX

Total bill amount excluding VAT for the VAT rate

Eventlog_report

EVENTLOG_ID

ID for record in database

EMPLOYEE

Employee executing the event which leads to registration in eventlog

EVENT_TYPE,

NF525 eventcodes

EVENT_TYPE_DESCRIPTION

NF525 naming of event type

EVENT_TIME

Time of event

OLD_VALUE_VARCHAR2

Initial record ID of event in particular table primary key.

OLD_VALUE_DESCRIPTION

Old value, if applicable

NEW_VALUE_VARCHAR2

Record ID of event in particular table primary key.

NEW_VALUE_DESCRIPTION

New value, if applicable

SIGNATURE

Electronic signature of event number

PREVIOUS_SIGNATURE

Electronic signature of previous event number

EVENT_NUMBER

Sequential event number.

Reservation_Bill_Snapshot

RESERVATION_ID

Internal backend reference ID for reservation

CASHFLOWRULE_NAME

Identifyer of bill lines

VALUE

Base amount of resource

QUANTITY

Quantity of resource in bill

TOTAL

Total amount per resource in bill

VIRTUAL_OVERRIDE_VALUE

Updated bill amounts including VAT after price override

VAT_RATE

VAT rate per resource in bill

TOTAL_EXCL_VAT

Bill amounts excluding VAT

Payment details report

MUTATION_ID

Internal backend ID for transaction

RESERVATION_ID

Internal backend reference ID for reservation

RESERVATION_NUMBER

Reservation number

PAYER_TYPE

Payment made by Customer, Paying Customer or Agent

DEBIT

Amount for incoming transaction

CREDIT

Amount for outgoing transaction

MUTATION_DATE

Date of registering transaction in system

DEBIT_PAYER_CURRENCY AMOUNT

Amount for incoming transaction in reservation currency

CREDIT_PAYER_CURRENCY AMOUNT

Amount for outgoing transaction in reservation currency

EMPLOYEE_ID

ID of entity registering the transaction

EMPLOYEE_NAME

Name of entity registering the transaction

ACCOUNT_NAME

Name of payment method

ADMINORGANISATION_NAME

Name of the legal entity the archive is created for

Signature_file

SIGNATURE,

Created electronic signature for the created fiscal archive based on the input parameters as described earlier in this document

PREVIOUS_SIGNATURE

Previously created electronic signature

------ENGLISH TEXT BELOW------

English Documentation

HOW TO READ THE ARCHIVE

The fiscal archive is created for invoices and tickets created within the date range selected before creating an archive. A zipfile is created with multiple Excel files which hold the details of relevant invoices and tickets. Furthermore, this explanatory file is part of the created fiscal archive.

The integrity of the file is controlled via the created electronic signature which is added separately in the file. To generate the electronic signature, there are the following input parameters:

  • Tax incl. amounts broken down per vat rate

  • Tax incl. amounts of the period

  • Operation timestamp

  • Terminal/POS code

  • Operation type

  • Previous signature Y/N

  • If present, previous electronic signature

THE ARCHITECTURE OF THE ARCHIVE

For each generated archive a zip file is created. That file is stored in a Google Cloud Storage Bucket and made accessible through the software as a download option.

Before the zipfile is created, all required files are being build up. Mostly by exporting data from the Oracle database into a csv file, combined with this pdf, it’s packaged together in a zip archive. For this zip file we generate a signature hash and store this in the database.

THE CONTENT OF THE ARCHIVE

The files in the archive are:

*Reservation_Tax_Total_Report: This is the main file in the fiscal archive with almost all details related to invoices, tickets and periodical closing totals.

*Reservation_Tax_Report: This document holds VAT specifics on ticket/invoice level.

*Eventlog_Report: This document holds JET data for selected daterange, which is stored in nf525_eventlog table.

*Reservation_Bill_Snapshot_Report: This document contains a snapshot of the bill, everytime a transaction on the reservation performed. Data is stored in reservation_bill_snapshot table.

*Payment: This file holds received payment details.

*signature_file: This document contains the electronic signature of the archive, as well as electronic signature of previous fiscal archive (if applicable).

Per file, a more detailed explanation of the main columns is given:

*Reservation_tax_total_report
This file holds all grand totals (GTT, GTF, GTP, GTM, GTA) for the archive created, which is stored in nf525_reservation_tax_total and the applicable tax values and amounts from reservation_tax_total table.
Furthermore, the following ticket and invoice details are included: operation type, electronic signatures, customer details, issueing entity details, operation type, NF version, Software name.

*Reservation_tax_report
Main columns are:
RESERVATION_TAX_TOTAL_ID: ID for corresponding record in Reservation_tax_total_report
TAX_PERCENTAGE: Identifier of VAT rate for the record
TAX_AMOUNT: VAT amount for VAT rate
RESOURCE_AMOUNT_INCL_TAX: Total bill amount including VAT for the VAT rate
RESOURCE_AMOUNT_EXCL_TAX: Total bill amount excluding VAT for the VAT rate

*Eventlog_report
Main columns are:
EVENTLOG_ID: ID for record in database
EMPLOYEE: Employee executing the event which leads to registration in eventlog
EVENT_TYPE: NF525 eventcodes
EVENT_TYPE_DESCRIPTION: NF525 naming of event type
EVENT_TIME: Time of event
OLD_VALUE_VARCHAR2: Initial record ID of event in particular table primary key.
OLD_VALUE_DESCRIPTION: Old value, if applicable
NEW_VALUE_VARCHAR2: Record ID of event in particular table primary key.
NEW_VALUE_DESCRIPTION: New value, if applicable
SIGNATURE: Electronic signature of event number
PREVIOUS_SIGNATURE: Electronic signature of previous event number
EVENT_NUMBER: Sequential event number.

*Reservation_Bill_Snapshot
Main columns are:
RESERVATION_ID: Internal backend reference ID for reservation
CASHFLOWRULE_NAME: Identifyer of bill lines
VALUE: Base amount of resource
QUANTITY: Quantity of resource in bill
TOTAL: Total amount per resource in bill
VIRTUAL_OVERRIDE_VALUE: Updated bill amounts including VAT after price override
VAT_RATE: VAT rate per resource in bill
TOTAL_EXCL_VAT: Bill amounts excluding VAT

*Payment details report
MUTATION_ID: Internal backend ID for transaction
RESERVATION_ID: Internal backend reference ID for reservation
RESERVATION_NUMBER: Reservation number
PAYER_TYPE: Payment made by Customer, Paying Customer or Agent
DEBIT: Amount for incoming transaction
CREDIT: Amount for outgoing transaction
MUTATION_DATE: Date of registering transaction in system
DEBIT_PAYER_CURRENCY AMOUNT: Amount for incoming transaction in reservation currency
CREDIT_PAYER_CURRENCY AMOUNT: Amount for outgoing transaction in reservation currency
EMPLOYEE_ID: ID of entity registering the transaction
EMPLOYEE_NAME: Name of entity registering the transaction
ACCOUNT_NAME: Name of payment method
ADMINORGANISATION_NAME: Name of the legal entity the archive is created for

*signature_file
SIGNATURE: Created electronic signature for the created fiscal archive based on the input parameters as described earlier in this document.
PREVIOUS_SIGNATURE: Previously created electronic signature.

  • No labels