Skip to main content

๐Ÿ‡ซ๐Ÿ‡ท France

This document describes all necessary configuration for a compliant setup in France (NF525 compliant).

Configurationโ€‹

In order to configure your store in France to be compliant, the following configurations need to take place.

Settingsโ€‹

All settings below should be set on the most convenient level possible. In other words, if your organization structure has a country organization which houses all French stores, then that's where they should go.

SettingValueOrganization unitDescription
Auditing:ProviderNF525 or DEFAULTNF525 on store OU's when go-live is in phases or on country level when big bang go live. DEFAULT on ecom organization units.Triggers the NF525 related logic on orders and invoices
UseInvoiceOutputFacadetrueRoot level or container levelAttaches the Certified Invoice PDF when emailing the Invoice from POS &/or Companion App. This setting enables the use of the CertifiedInvoice stencil with destination Mail
Auditing:UseInvoiceCloningtrueRoot level or container levelUsed to create a duplicate of an original invoice whenever a customer is attached or mutated
Auditing:PublicKeyBlobID-Root level or container levelID of the blob that was uploaded that contains the public key. Note: we can provide a service to generate it for you
Auditing:PrivateKeyBlobID-Root level or container levelPart of the key-pair used in your public key blob setting
Auditing:EnforceTransactionValidationtrueRoot level or container levelTo check if all auditing fields have been filled properly upon conducting any sales transction
note

Once you're done with all configuration steps. Make sure to run the service: AuditingValidateConfiguration which should return any step(s) that you may have missed or possibly undocumented.

Public and private keyโ€‹

To generate the public and private key one of our developers will help you. Or if youโ€™re savvy enough with this command line:

openssl genrsa -out private.pem 2048
openssl rsa -in private.pem -out public.pem -outform PEM -pubout
Private keyโ€‹

To set the private key the service AuditingSetPrivateKey can be used. This will upload the private key file and also increment the version setting automagically. It will also update the setting Auditing:PrivateKeyBlobID. We will have this setup done for you at the start of the project.

Public keyโ€‹

The public key should be uploaded to EVA via the StoreBlob service. Please note that the blob needs to have an "OriginalName" otherwise, it'll expire immediately. We will get this done for you at the start.

The public key should be shared with the authorities whenever they ask for it, so they can verify signatures.

Infrastructureโ€‹

Cosmos DB will be setup by us, as this is required to keep track of the technical event log and the X/Z reports. If this is not set up, you won't be able to see any details in de technical event log section of EVA Admin.

Companyโ€‹

When configuring your French organization unit(s), a company needs to be attached. If there is no French company present yet on EVA, a new one should be created within Admin Suite under the Companies chapter. The following fields need to be filled:

  • Name
  • VatNumber
  • RegistrationNumber
  • Address (VisitorAddress)
    • Street
    • HouseNumber
    • ZipCode
    • City
    • CountryID

Auditing fieldsโ€‹

These inputs need to be set on the company(ies) attached to the French organization unit(s) through the service(s): GetAuditingFieldsForCompany and SetAuditingFieldsForCompany

  • SIREN (example: 538485384)
  • SIRET (example: 53848538400019)
  • Legal form
  • Social capital (starting capital when the company was registered)
  • NAF (special code for the main activity of the company)
  • RCS number (example: 844988105)
  • RCS city (city where the RCS number was given)

Organization unit(s)โ€‹

Once a company is in place, you need to attach it to an organization unit(s).

Make sure the following fields are filled when creating an organization unit:

  • Name
  • BackendID (store number)
  • RegistrationNumber
    • Used as the SIRET in the audit file
  • VatNumber (aka TaxRegistrationNumber)
  • BranchNumber
    • Used as the NAF in the audit file
  • Address
    • Street
    • ZipCode
    • City
    • CountryID
  • CompanyID
note
  • It is crucial that you have the CompanyID field filled when creating the organization unit. You can retrieve this ID from the French company you created/have. This is the legal entity under which this OU/store is operating and will be referred to when filling in the details on the invoices and receipts.
  • Sales will not be permitted on all apps if the SIRET, VAT or NAF numbers are missing.

Further, please make sure to fill all the auditing fields for your respective French OU's.

Ecom organization unitsโ€‹

For web shop/ecom organization units, additional considerations are needed on the OU level as follows:

  • The setting AutoOpenCloseFinancialPeriod must be set to true.
  • The setting Auditing:Provider remains NF525 as earlier advised under settings.
  • The organization unit is set to "Open".
  • The web shop organization unit must be attached to the French company.
  • The financial period of the webshop OU must be set to "Open".
  • The following tasks need to be set up:
    • EVA.Core.Finance.Periods.AutoOpenCloseFinancialPeriod
    • EVA.Auditing.Tasks.CreateFinancialPeriodAuditTask (For this one, please input the French web shop/ecom OU ID in the designated field).

Stationsโ€‹

You can find steps on adding a new station here.

When creating a station, make sure the following fields are filled in:

  • Station name.
  • The checkmark This station is a fiscal station and will be used for transactions needs to be checked.
note

All payment types must have a category, otherwise the payment can't be correctly mapped, and Ship Orders would fail.

Tasksโ€‹

The following two tasks need be set up under Management โ†’ Tasks.

Financial period auditโ€‹

Theย CreateFinancialPeriodAuditTaskย should be configured every second day of the month at 04:00.ย This task will basically do an automated generation of an audit file,ย which you can also trigger manually.

The following fields need to be set:

  • Name - (can be any unique name you want).
  • Cron: 0 4 2 * *
  • Arguments
    • Type - (can be left blank).
    • Organization unit - (the ID of the country of the Japanese OU).
    • Email address - (In case of task failures the email address you mention here will receive a notification. This is an optional field but quite handy).
note

For NF525 implementations, the audit file document output is modified to not include a billing address if (1) the customer attached to an order had no billing address details (2) the invoice template was just a ticket/receipt i.e. the address fields are not part of the receipt.

Financial reporting periodโ€‹

Theย CloseFinancialReportingPeriodsTaskย should be configured every night at 03:00.ย This task will check and close reporting periodsย (months,ย years,ย fiscal years).

The following fields need to be set:

  • Name - (can be any unique name you want).
  • Cron: 0 3 * * *
  • Type - (1 for shops 2 for webshops)
  • Email address - (Again, this is an optional field but quite handy in case the task run fails).
note

Unlike the financial period audit task, this task does not require an organization unit. It will simply look at all the automatically opened reporting periods and make sure to close them.

Auditing provider details on POSโ€‹

In POS under the more options tab a card is available displaying the auditing provider details. Further, the auditor provider logo can be seen to comply with the CF certification rules "to display the logo and reference to the NF525 mark".