Enable Certified POS system for France in Microsoft Dynamics AX 2012 R3 for Retail (X++)

This update is an application part of the combined update that enables Microsoft Dynamics AX 2012 R3 for Retail localization functionality for France. With this combined update, Microsoft Dynamics AX 2012 R3 for Retail is certified per the NF 525 certification requirements. See KB 4058330 for the binary part of the update.

The article provides an overview of the cash register functionality that is available for France in Microsoft Dynamics AX 2012 R3 for Retail. It also provides guidelines for setting the functionality.

The article applies to both Microsoft Dynamics AX 2012 R3 Enterprise POS and Modern POS. Both applications are commonly referred as point-of-sale (POS).

To learn about POS features that are available to customers in all countries or regions, see Microsoft Dynamics AX 2012 R3 for Retail documentation.

The following POS localization features that are available to customers in all countries or regions can now be used specifically for France:

• Register additional events in the POS audit event log. If the Audit option in the POS functionality profile is set to Yes, the following events are registered in the POS audit event log:
  • Sign-in
  • Sign-out
  • Printing a copy of a receipt
  • Starting offline mode
  • Ending offline mode
  • Starting training mode
  • Ending training mode
  • Cleanup of transactions from the channel database

The following France-specific POS features are enabled when the ISO code field in the POS functionality profile is set to FR.

Digital signing overview

The following types of data (transactions and events) are digitally signed in POS:

• Sales transactions
• Copies of receipts
• Closed shifts/Z reports
• Audit events

The signature is created and recorded in the channel database at the same time that the transaction is finalized or the event is registered. The data that is signed is a text string that consists of several data fields. These fields vary, depending on the type of data. The general signing process consists of the following steps:

1. Based on the type of data, select the next sequential number for signing purposes.
2. Extract the data fields that must be signed from the record that is being signed.
3. Build a string that consists of a comma-separated list of the data fields.
4. Add the previous signature for the same type of data.
5. Calculate a hash code of the string by using the SHA-x algorithm.
6. Encrypt the resulting string by using a digital certificate.
7. Do the base64url transformation for the resulting string.
8. Store the string that is used for signing, the sequential number, the signature, and the thumbprint of the certificate in a fiscal response record that is linked to the transaction or event.
9. Transfer the fiscal response to the enterprise resource planning (ERP) system in Retail headquarters, together with the transaction or event.

Digital signing of sales transactions

Only transactions for cash sales are signed. Here are some examples of transactions that are excluded from the signing process:

• Prepayments (customer account deposits)
• Quotations
• Prepayments for sales orders (customer order deposits)
• Issuing a gift card and adding funds to a gift card
• Non-sales transactions (float entry, tender removal, and so on)

The data that is signed for a sales transaction is a text string that consists of the following data fields:

1. The total amount of sales lines. The amount includes tax per tax rate.
2. The total amount of sales. The amount includes tax.
3. The date and time of the transaction, in the format of YYYYMMDDHHMMSS.
4. The register number.
5. The sequential number of the signed sales transaction.
6. The type of sales transaction.
7. A value (Y/N) that indicates whether the transaction is the first signed sales transaction for the register.
8. The previous signature for the same register. A blank value is used for the first signed sales transaction.

You can view the transaction signature, together with the transaction data that was used to generate it, on the Fiscal transactions fast tab of the Retail store transactions form in Retail headquarters.

Digital signing of receipt copies

When a copy of a receipt is printed, the event is registered in the POS audit event log. Only copies of receipts for signed sales transactions are signed. The data that is signed for a receipt copy event is a text string that consists of the following data fields:

1. The receipt number of the original sales transaction.
2. The type of retail transaction for the original sales transaction.
3. The number of the receipt copy for this sales transaction.
4. The staff ID of the operator who is printing the receipt copy.
5. The date and time of the receipt copy event, in the format of YYYYMMDDHHMMSS.
6. The sequential number of the signed receipt copy event.
7. A value (Y/N) that indicates whether the transaction is the first signed receipt copy event for the register.
8. The previous signature for the same register. A blank value is used for the first signed receipt copy event.

You can view the signature of the receipt copy, together with the event data that was used to generate it, on the Audit events form in Retail headquarters.

Digital signing of closed shifts

When a shift is closed, the event is registered in the POS audit event log. The data that is signed for a shift closing event is a text string that consists of the following data fields:

1. The total amount of sales. The amount includes tax per tax rate.
2. The total amount of sales. The amount includes tax.
3. The date and time of the shift closing event, in the format of YYYYMMDDHHMMSS.
4. The sequential number of the shift closing event.
5. A value (Y/N) that indicates whether the transaction is the first signed shift closing event for the register.
6. The previous signature for the same register. A blank value is used for the first signed shift closing event.

You can view the signature of a closed shift, together with the shift data that was used to generate it, on the Signature tab of the Shifts form in Retail headquarters.

Digital signing of events

The data that is signed for an event other than a receipt copy or shift closing event is a text string that consists of the following data fields:

1. The sequential number of the signed event.
2. A predefined event code.
3. A description of the event.
4. The date and time of the event.
5. The staff ID of the operator who raised the event.
6. The register number.
7. A value (Y/N) that indicates whether the transaction is the first signed event for the register.
8. The previous signature for the same register. A blank value is used for the first signed event.

You can view the event signature, together with the event data that was used to generate it, on the Audit events form in Retail headquarters.

Receipts

Receipts for France can include additional information that was implemented by using custom fields:

• Transaction type – You can add a field to a receipt format layout to identify the type of transaction. For example, a sales receipt will include the text "Sales".
• Sequential number of signed sales transaction – A receipt can include the sequential number of a signed sales transaction. This number is used to associate the printed receipt with a digital signature in the database.
• Extract from digital signature – A receipt can include an extract from the digital signature. This extract is used to confirm that the transaction is signed. It consists of a concatenation of the third, seventh, thirteenth, and nineteenth symbols of the signature.
• Reprint number – An original receipt or a receipt copy can include the number of the receipt copy. For an original receipt, the value is 0 (zero).
• Line count – A receipt can include the number of printed item lines on the receipt.
• Sales totals – Custom fields for receipt totals exclude non-sales amounts from the total transaction amounts. Non-sales amounts include amounts for the following operations:
  • Prepayments (customer account deposits)
  • Prepayments for sales orders (customer order deposits)
  • Issuing a gift card
  • Adding funds to a gift card
• Certification data – A receipt can include the category and number of the certificate of compliance that an authorized body issued per the NF 525 certification requirements.
• Build number – A receipt can include the POS build number.

Restricting duration of shifts

There is an option to enforce daily shift closing in POS. A shift can't last longer than the time that is specified in the Shift closing time field. Several minutes before that time, the operator will start to receive warnings that the shift must be closed. The number of minutes is determined by the value of the Shift closing interval (minutes) field.

X and Z reports

The information that is included on the X and Z reports is based on French requirements:

• Total sales for the shift. This information includes amounts only for cash sales transactions. Prepayments and operations for issuing a gift card are excluded.
• Total returns for the shift.
• Cumulative grand total. This amount is calculated as the cumulative grand total amount of the previous shift plus the total sales amount of this shift minus the absolute value of the total returns amount of this shift.
• Cumulative perpetual grand total. This amount is calculated as the cumulative perpetual grand total amount of the previous shift plus the total sales amount of this shift plus the absolute value of the total returns amount of this shift.
• Value-added tax (VAT) amounts per tax rate.

The totals are also stored in the closed shift record and transferred to Retail headquarters.

Period grand total journal

Period grand total journals summarize sales totals per store and fiscal period.

Period grand total journals are maintained in the Period grand total journal form. To create a new journal, you must specify a store. If previous journals exist for the store, the next fiscal period after the last closed journal for the store is automatically used as the new journal period. If the previous journals do not exist, you can specify the end date of the journal. In this case, the fiscal period that includes the specified date is used as the journal period.

The journal can then be calculated. Shifts that were closed during the journal period are selected, and totals are calculated for those shifts. You can view the journal's tax totals per sales tax code. You can also view the shifts that are included in the journal.

After the journal is calculated, it can be closed. A closed journal can't be modified, and another journal can't be created for a previous period, the same period, or an intersecting period. However, the last closed journal for a store can be canceled. In that case, another journal can be created for the same store and period.

A closed journal is digitally signed. You can view the journal signature, together with the journal data that was used to generate it, on the Signature details tab of the Period grand total journal form in Retail headquarters.

Archive

An archive is an XML file that can be exported from a Period grand total journal that has been closed. It includes the totals for the closed period, and also includes detailed data about sales transactions and events. The exported file is digitally signed, and the signature is contained in a separate file.

This section describes the Retail settings that are specific to and recommended for France. For more information about how to set up Retail, see Microsoft Dynamics AX 2012 R3 for Retail documentation.

To use the France-specific functionality for Retail, you must complete these tasks:

• Set the Country/region field to FRA (France) in the primary address of the legal entity.
• Set the ISO code field to FR (France) in the POS functionality profile of every store that is located in France.

You must also specify the following settings for France. Note that you must run appropriate distribution jobs after you complete the setup.

Set up the legal entity

You must make the following changes in the Legal entities form. These settings are used in the archive format.

• On the Bank account information FastTab, in the Routing number field, specify the VAT identifier of the organization.
• On the Statutory reporting FastTab, in the NAF code field, specify the Nomenclature des Activités Françaises (NAF) code of the organization.
• On the Tax registration FastTab, in the Tax registration number field, specify the Système d'identification du répertoire des établissements (SIRET) number of the organization.

Set up VAT per French requirements

You must create sales tax codes, sales tax groups and item sales tax groups. You must also setup sales tax information for products and services. For more information about how to set up and use sales tax in Microsoft Dynamics AX 2012, see Setting up sales tax codes [AX 2012], Setting up sales tax groups and item sales tax groups [AX 2012].

You must also specify sales tax groups and enable the Prices include sales tax option for stores that are located in France.

Set up functionality profiles

You must enable auditing by setting the Audit option to Yes.

To enforce daily shift closing, you must make the following changes:

• Set the Enforce daily shift closing option to Yes.
• Set the Shift closing time and Shift closing interval (minutes) fields.

Configure receipt formats

For every required receipt format, change the value of the Print behavior field to Always print.

In the Receipt format designer, add the following fields to the appropriate receipt sections.

• Header: Add the following field:
  • Transaction type – This field identifies the type of receipt.
• Lines: We recommend that you add the following standard fields:
  • Unit price with tax
  • Total price with tax
  • Tax ID
• Footer: Add the following fields:
  • Total (sales) – This field prints the receipt's total cash sale amount. The amount excludes tax. Prepayments and gift card operations are excluded.
  • Total tax (sales) – This field prints the receipt's total tax amount for cash sales. Prepayments and gift card operations are excluded.
  • Total with tax (sales) – This field prints the receipt's total cash sale amount. The amount includes tax. Prepayments and gift card operations are excluded.
  • Tax ID – This standard field enables a sales tax summary to be printed per sales tax code. The field must be added to a new line.
  • Tax amount (sales) – This field prints the receipt's tax amount for cash sales per sales tax code. Prepayments and gift card operations are excluded. The field must be added to the same line as the Tax ID field.
  • Sequential number – This field prints the sequential number of a signed sales transaction.
  • Digital signature – This field prints the extract from the digital signature.
  • Reprint number – This field prints the number of a receipt copy.
  • Build number – This field prints the POS build number.
  • Certification category – This field prints the category of the certificate of compliance that an authorized body issued per the NF 525 certification requirements.
  • Certificate number – This field prints the number of the certificate of compliance that an authorized body issued per the NF 525 certification requirements.
  • Line count – This field prints the number of printed item lines on a receipt.
  • Text – Add a text field and specify the VAT identifier of the organization.
  • Text – Add a text field and specify the NAF code of the organization.
  • Text – Add a text field and specify the SIRET number of the organization.
  • Store name – This standard field prints the name of the store.
  • Store address – This standard field prints the address of the store.

For more information about how to work with receipt formats, see Set up receipt formats [AX 2012].

Configure the digital signature parameters for Retail headquarters

To digitally sign Period grand total journals and archives, you must setup digital signature parameters. The signing is done by using a digital certificate that is stored in the local certificate storage of the Application Object Server (AOS).

In the Retail parameters form, you must specify the parameters for digital signatures:

• Certificate - Select a certificate that is available in the local certificate storage of AOS.
• Hash function - Specify one of the cryptographic hash algorithms that are supported by Microsoft .NET, such as SHA1.
• Encoding - Specify the encoding of the signed data, such as UTF-8.

Configure archive export

Archive export is implemented using Application Integration Framework (AIF). To enable archive export, you must configure an outbound integration port for it:

1. Export the XSLT file from the Application Object Tree (AOT)
   1. Open AOT > Resources, and select the resource AifOutboundPortReportRetailArchive_FR;
   2. Right-click the resource and select the Export option from the context menu;
   3. Specify the file name and click OK.
2. Configure an outbound port:
   1. Open System administration > Services and Application Integration Framework > Outbound ports for electronic audit reports;
   2. Click Create / Update ports. This will populate the list of default formats;
   3. Select the Retail data archive (France) format;
   4. Specify the path to the earlier exported XSLT file in the Import XSLT field;
   5. Specify the Default export path;
   6. Click Create / Update ports once more. This will import the XSLT file and create the RetaildataarchiveFrance outbound port;
   7. Right-click the Outbound port field and select View details;
   8. In the Outbound ports form, select the RetaildataarchiveFrance port and click Activate.

Reinitialize Retail components

Note: You only need to complete the steps of this section if you are updating an existing environment.

To enable audit events, you must reinitialize the Retail Extensible enumerations. To enable transmitting France-specific data from POS to Retail headquarters, you must reinitialize the Retail Scheduler.

On the Retail parameters form, click Initialize.

Configure POS

See KB 4058330 for the configuration procedure for POS.

How to obtain the Microsoft Dynamics AX updates files

This update is available for manual download and installation from the Microsoft Download Center.

• Download update for Microsoft Dynamics AX 2012 R3

Prerequisites

You must have one of the following products installed to apply this hotfix:

• Microsoft Dynamics AX 2012 R3

Restart requirement

You must restart the Application Object Server (AOS) service after you apply the hotfix.

If you are encountering an issue downloading, installing this hotfix, or have other technical support questions, contact your partner or, if enrolled in a support plan directly with Microsoft, you can contact technical support for Microsoft Dynamics and create a new support request. To do this, visit the following Microsoft website:

https://mbs.microsoft.com/support/newstart.aspx

You can also contact technical support for Microsoft Dynamics by phone using these links for country specific phone numbers. To do this, visit one of the following Microsoft websites:

Partners

https://mbs.microsoft.com/partnersource/resources/support/supportinformation/Global+Support+Contacts

Customers

https://mbs.microsoft.com/customersource/northamerica/help/help/contactus

In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained here in is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.