Simphony Fiscal Italy

Oracle® Food & Beverage
Installation Guide for

Simphony Fiscal Italy
Simphony Fiscal Italy

Version 21.2.0.0
July 2021
Oracle Hospitality Simphony Fiscal Italy Installation Guide for Simphony Fiscal Italy Version 21.2.0.0
Copyright © 2013, 2021, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify,
license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.
Reverse engineering, disassembly, or decompilation of this software, unless required by law for
interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free.
If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users
are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-
specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the
programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous applications, including
applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other
measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages
caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks
of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks
are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,
Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced
Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content,
products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and
expressly disclaim all warranties of any kind with respect to third-party content, products, and services
unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its
affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of
third-party content, products, or services, except as set forth in an applicable agreement between you and
Oracle.
Contents
Contents iii
Preface v
1 Fiscal Implementation for Simphony 1

Implementation Model Examples 1
2 Requirements 3
Installer Rights and Privileges 3
System Requirements 3
3 Limitations 4
TRANSACTION SERVICES LIMITATIONS 5
Sanity Checks 5
4 Installation 6
Setting Up Data Extensions at Enterprise 6
ADDING A DATA EXTENSION (ON PREMISES) 9
Configuring the Extensibility Application 10
CREATING AN EXTENSION APPLICATION 10
5 Configuration 12
Fiscal Printer Serial Port Number 12
Payment Types 13
Departments Configuration 15
Tax Classes and Departments (Reparti) 17
Menu Item Class Configuration 19
Customer List (Customer Master Data) 21
Printing Documents with Copies 22
Configuring Courtesy Invoice Counter 23
Functional Configuration 24
CONFIGURING THE EXTENSIBILITY FUNCTION BUTTON 27
Non-Fiscal Receipt on Fiscal Printer 28
6 Conversion Invoice Electronic Format 30
7 Transaction Services Fiscal Plugin 31

TRANSACTION SERVICES ERROR CODES 34
Appendix A Uncollected Payments 36
iii
Appendix B Troubleshooting 37
Solution Architecture 37
Logging 37
Appendix C Courtesy Invoices and Customer Data 39

Customer Data Validation 41
Data Dictionary 42
FCR_CUSTOMER_DATA TABLE 42
FCR_INVOICE_DATA TABLE 44
FCR_TTL_DATA TABLE 46
Appendix D Invoices Export (CSV) 51
Appendix E Courtesy Invoices Export 57
Appendix F Additional Functions for RT Printer 60

RT Printer Status 60
Reso Merce Procedure (ex Nota di credito) 61
Void Check (Annullo conto e scontrino) 62
Appendix G Interfaces to Third-Party Systems 64

Mandatory Simphony Configuration 64
Courtesy Invoices Interface 64
INVOICES DATA DICTIONARY 65
Custom Header and Trailer Rows Interface 67
EMC CONFIGURATION 67
Appendix H How to Report an Issue 69
Appendix I XML 7.0/RT2.0 Changes 70
iv
Preface
Preface
Purpose
This document describes the features and installation steps included in Oracle Fiscal
solution for Oracle MICROS Simphony for Italy.
This document does not describe the installation nor configuration process for third
party fiscal devices. Refer to the manufacturer documentation for this information.
Audience
This document is intended for consultants installing Oracle MICROS Simphony in
Italy and employees providing software support for Simphony.
Customer Support
To contact Oracle Customer Support, access My Oracle Support at the following
URL:
https://support.oracle.com
When contacting Customer Support, please provide the following:
 Product version and program/module name
 Functional and technical description of the problem (include business impact)
 Detailed step-by-step instructions to re-create
 Exact error message received and any associated log files
 Screenshots of each step you take
Documentation
Oracle MICROS product documentation is available on the Oracle Help Center at
https://docs.oracle.com/en/industries/food-beverage/index.html.
Revision History
Date Description of Change

July 2021  Initial next generation version of the fiscal solution for Italy
v
1 Fiscal Implementation for Simphony
Oracle MICROS Simphony Fiscal Italy solution enhances standard product
functionalities with an Epson fiscal printer model Registratore Telematico (RT). The
following units were introduced as a “parts of the whole” solution:
1. Workstation – POS Workstation running fiscal Extension Application
Micros.FiscalLayerClient.
2. Transaction Services Workstation – POSAPI client configured on a
physical POS workstation running the fiscal transaction services client
FiscalItalyTSPlugin.dll.
3. Network Services – The solution makes use of the built-in network
communication to connect to the local fiscal device handling and to remote
workstations.
4. Fiscal Printer type RT – Physical external thermal printer compliant with
local regulations and from type Registratore Telematico (RT) with a required
firmware version. Connected to the workstation through a serial connection
type RS232.
Implementation Model Examples

The fiscal printer RT can be accessed from remote workstations, providing the ability
to have multiple workstations printing on one fiscal printer RT. If the fiscal printer RT
is not reachable, the transaction cannot be finalized with a payment. In such cases
the user can only store the check using a service total.
This approach requires a stable network connection between the remote and the
workstation attached to the fiscal printer RT. If the network connection is unstable, the
solution may encounter unexpected failures and drive to operational issues.
It is important to note that for online operation workstations running Oracle MICROS
Simphony, a minimum of one fiscal printer is required per installation. However, if
Oracle MICROS Simphony is expected to cater to any offline functionality (SAR),
each workstation will require a separate fiscal printer attached.
It is strongly recommended to verify prior the installation, the transactions load by
workstation and related fiscal printer, with the target to avoid possible timeout issues
using one fiscal printer for multiple workstations. The printout of the fiscal receipt
requires time (in some cases several seconds); the fiscalization procedures are
sequential and can only work methodically using a first in first out principle. We highly
recommend evaluating the transactions volume of a single workstation compared to
the time needed to print the fiscal check, in case of high volume environment
distribution of the load to different fiscal printers among the available workstations.
1
CAUTION
This is a new solution for Fiscal Italy. Completely rewritten and not based
on previous solutions, it replaces the legacy solution currently released
with version 21.1.x.x.
We recommend overriding the legacy solution with this application in case
it is necessary to create a new record in the extension application. Keep in
mind that the legacy solution must be disabled in case the legacy
extension application in EMC is deleted. The local files on the workstation
will not be deleted.
 Removed Fiscal Layer Windows Service dependencies.
 Removed fiscal common client the FiscalLayerClient.Common.dll
dependencies.
 Removed Micros.FiscalClient.Properties.xml dependencies.
 Removed Micros.FiscalService.Properties.xml dependencies.
Some legacy functions have been deprecated and are not part of this
solution. See the functional configuration chapter for the list of available
functions.
2
2 Requirements
Installer Rights and Privileges
Before starting the installation process, ensure that the following rights and privileges
are granted. In hosted environments, request assistance from Cloud Operations if
modifications are required at the Enterprise or zone levels.
 Access to EMC login
 Setting up Data Extensions (requires Enterprise configuration rights)
 Adding and editing Extensibility Application on property or zone levels
 Adding and editing the value of data extensions for Workstation and Tax Classes
 Configuring a page
System Requirements
The use of other hardware or software versions requires a separate quality assurance
process.
 Simphony Fiscal Italy version 21.2 and higher supports Oracle MICROS
Simphony, version 19.2 and higher, Transaction Services, and Linux for Oracle
MICROS.
 Oracle MICROS Workstation with Windows or Linux for Oracle MICROS
operating system listed in the related section of the supported devices.
 Solution supports Registratori Telematici (RT) EPSON fiscal printers, with
appropriate firmware version installed and enabled for XML7.0/RT2.0 version.
 Solution supports fiscal printers only with serial communication.
 EPSON Italian Fiscal Printer:
- Minimal Firmware versions with XML 7.0/RT2.0 support
 Fiscal printer type “MEY” or “MEX” (modified) version 11.00 or higher.
 Fiscal printer type “IEB” or “IEC” (native) version 7.00 or higher.
WARNING
Lower firmware versions are not supported.
Legacy Fiscal Printers are not supported.
3
3 Limitations
The Oracle MICROS Fiscal Solution supports features, server technologies,
databases, operating systems, and POS hardware according to the Oracle MICROS
Compatibility Matrix, with the following exceptions:
 Functionalities
o Headless or CAPS on IIS
o Reopen closed check
o Adjust Closed Check
o Invoices export for electronic invoicing runs only on Windows OS
o Automatic cover charge
 Operating Systems
o WS5A on Oracle Linux for MICROS
o Android
 Negative transactions are only permitted with the use of the refund function.
 The Extension Application Name must be Micros.FiscalLayerClient. The DLL
File Name must be Micros.FiscalLayerClient.dll. (This setting is case-
sensitive.) Extensibility option 3 - Write DLL into handlers directory rather
than isolated directory must be disabled.
 The fiscal data is stored in the CAPS database. If that database will be
dropped, the entire historical data will be lost—including the courtesy invoices
counter settings (based on where the counter has been configured) and all
invoices transactions. This solution does not transfer fiscal data to Reporting
and Analytics.
4
Transaction Services Limitations
Transaction Services supports only and solely normal positive fiscal transaction.
Other features or functionalities available in the user front end are not present and
are not supported in Transaction Services.
Note the following limitations:
 Transaction Services (Gen2) is not supported.
 Transaction Services client must be configured on a workstation running POS
Operations through a Service Host.
 Item discounts are not permitted.
 Positive discounts are not permitted.
 Negative items are not permitted.
 Mixing fiscal and non-fiscal payments on the same check is not permitted.
 Automatic Service Charges and automatic cover charges not permitted.
 Tender Media/Currency rounding support for Transaction Service is not
permitted.
 Negative transactions are not permitted.
 Courtesy Invoices feature is not permitted.
 Charged Tips is not permitted.
 Service Totals are not processed and ignored.
 Partial Payments are not permitted.
Sanity Checks
Several mechanisms have been implemented to avoid illegal operations. These
verifications are valid for normal workstations and Transaction Services clients.
 Printer fiscal departments (Reparti) must be configured using the dedicated tax
report group under Tax Rates, or using the dedicated data extension as
outlined in Tax Classes and Departments.
 None or multiple tax rates for any items, after an order type declaration, are not
permitted.
 Fiscal and non-Fiscal Tenders are not permitted on the same check.
 Discounts must be configured to use all taxes.
 Positive and negative tax totals are not permitted on same check.
 None or Multiple Taxes are not permitted for service charges.
 Fiscal printer must be present to finalize transactions. In other cases the
transactions can be stored using service totals with printing enabled to provide
a copy of the receipt to the customer. The checks may be finalized when the
printer is replaced, transferring the data to the tax authorities.
 Several transactional sanity checks are in place. The user is informed through
a prompt if the check contents does not comply with the required local fiscal
rules.
5
4 Installation
Setting Up Data Extensions at Enterprise
The following data extensions are required to be set up at the Enterprise level. Before
proceeding, verify that all extensions exist in the Enterprise configuration; otherwise,
contact the Cloud Operations team to add them.
Table 4-1 - Data Extensions
Table Extra Column Type Data Translatable Translatable Help

Name Constraints Name
Workstations FLC_FisPortID Number 0-99 Fiscal Printer Fiscal printer serial port
Serial Port number
Number
Tender/Media FLC_PaymentType Number 0-999 Payment Fiscal Fiscal type for payment
Type
Tax Class FLC_FiscalLinkID Text Max Fiscal Printer Tax Fiscal device reparto id link
Chars:255 Link
Service Charge FLC_FiscalLinkID Text Max Chars: Fiscal Printer Tax Fiscal device reparto id link
255 Link
Tender/Media FLC_RecCopyCount Number 0-9 Number of Non Number of extra copies

Fiscal Rec. Copies automatically printed after
printed after original receipt
original receipt
Revenue FLC_InvoiceCounterLevel Big Text Invoice Counter Invoice Counter Level

Values:
Center List Level
Property
Workstation
Workstation FLC_FisPortUSB Boolean Linux USB COM Use a USB to Serial adapter
Port on Linux workstations
Workstation FLC_BaudRate Lookup Fiscal Printer Serial connection baud rate.

List Serial Baud Rate
Workstation FLC_HandShake Lookup Fiscal Printer Serial connection hand

List Serial Handshake shake type
Workstation FLC_RemoteDeviceIP Text Max Chars: Fiscal Printer Network address of remote
255 Workstation workstation with RT
address attached
Workstation FLC_UseLocalDevice Boolean Fiscal Printer local RT printer attached to

workstation
Property FLC_VirtualPrinterEnabled Boolean Enable Virtual Enable network printer

Thermal Printer emulator to fiscal printer
Property FLC_VirtualPrinterPort Number Virtual Printer Network printer emulator

network port network port default 9100
Property FLC_VirtualPrinterCodePage Text Virtual printer Network printer emulator

code page codepage, default 1250
6
Table Extra Column Type Data Translatable Translatable Help
Name Constraints Name
Workstation FLC_TmedOpenCashDrawer Boolean FL Open Cash Open cash drawer before
drawer print completion
Workstation FLC_TrnTimeOut Text FL Transactions Change default timeout for

time out transactions
Workstation FLC_RptTimeOut Text FL Reports time Change default timeout for

out reports
All data extensions must be editable, downloadable, and viewable.

NOTE
Legacy data extensions not listed in the previous table are deprecated and
not required.
7
Data Extensions Description
 FLC_FisPortID: Serial com port number.
 FLC_PaymentType: Type of fiscal payment (see payment types under
configuration).
 FLC_FiscalLinkID: Mapping field for tax rate to fiscal device department (reparto)
number.
 FLC_RecCopyCount: Number of reprints for fiscal payments.
 FLC_InvoiceCounterLevel: Defines the invoice counter level: workstation one for
each workstation, or property one counter for the entire property. In this case, the
workstation must be online to complete the courtesy invoice.
 FLC_FisPortUSB: Valid only for Oracle Linux for MICROS workstations.
Checked/unchecked to use either Com/USB Port type.
 FLC_BaudRate: Serial port baud rate for fiscal printer (the sorting is mandatory).
It this entry is not present, the baud rate is set by default to 57600.
1. 9600 Bit per seconds
 FLC_HandShake: Serial port handshake for fiscal printer.
If this entry is not present, the handshake is set by default to None.
1. None
2. RTS Request to Send
3. RTS XOn-XOff RTS XOn XOff
4. XOn XOff
 FLC_RemoteDeviceIP: In case of remote fiscal device, IP address of the

workstation attached to the fiscal device.
 FLC_UseLocalDevice: Enable it if the workstation has attached a fiscal printer.
 FLC_VirtualPrinterEnabled: Enable the emulation for network printer. The fiscal
printer prints the receipts as non-fiscal documents.
 FLC_VirtualPrinterPort: (Optional) Change the default network port, by default
9100.
 FLC_VirtualPrinterCodePage: (Optional) Change the code page, by default 1250.
 FLC_TmedOpenCashDrawer: (Optional) If this option is set, the cash drawer
opens immediately when the printer starts printing.
8
 FLC_TrnTimeOut: (Optional) Change the timeout for a transaction, which may
help for slower connections or receipts having an extraordinary amount of items.
 FLC_RptTimeOut: (Optional) Change the timeout for reports printing, which may
help to print reports with several pages without incurring timeout errors.
Adding a Data Extension (On Premises)

If the installation is on premises, the responsibility for adding a Data Extension lies
with the implementation consultant. The following instructions explain how to add a
new Data Extension at the Enterprise level. For more information, refer to the Oracle
MICROS Simphony documentation.
1. Select the Enterprise, click Configuration, and then click Data Extensions.
2. On the toolbar menu, click the green plus icon to insert a record.
3. Enter the record number, and then click OK.
4. Select the Table to which the data extension will be added.
5. Enter the unique name for the data extension (case sensitive) (see the Extra
Column Name in Table 4-1).
6. Select the data type from the Type drop-down list.
7. Enter the Data Constraints.
8. Enter the Display Width.
9. Enter the Translatable Name and Translatable Help.
10. Select Is Editable, Is Viewable, and Is Downloadable unless indicated
otherwise.
11. Save the changes.
9
Configuring the Extensibility Application
The Extensibility Application files are included in the Fiscal Layer setup archive in the
Extension Application folder.
Complete the following instructions to install the Oracle MICROS Simphony Fiscal
Italy extensibility application within EMC.
Creating an Extension Application

1. Unzip the installation package folder.
2. Open EMC and sign in with your credentials.
3. Select the Enterprise, property, revenue center, or zone, click Setup, and then
click Extension Application.
4. On the toolbar menu, click the green plus icon to insert a record.
5. In the Record Name(s) field, enter Micros.FiscalLayerClient, and then click
OK.
The name is case sensitive and must be entered as it appears.
6. In the extension application record row, enter the same name
Micros.FiscalLayerClient in the Description field.
7. In the Type field, enter 2.
8. Double-click the record that you created (Micros.FiscalLayerClient), and then

click Insert Application Content to add the first file.
a. Enter Micros.FiscalLayerClient in the ZoneableKey field, enter Fiscal For
Win32 in the Description field, and then click OK.
b. Click the Designer:[extension application name] subtab, and select 3 -
DLL from the Content Type drop-down list.
c. Click the Import from a file link.
d. Locate the file Micros.FiscalLayerClient.dll on the server or on the local
hard drive, and then click Open.
e. Click the General tab.
f. In the column Disk File Name, enter the exact name of the file with the
extension Micros.FiscalLayerClient.dll.
Repeat steps 8a through 8f to add the Newtonsoft.Json.dll file.
9. Enter Micros.FiscalLayerClient extension application and add the settings
content, which includes the translation text (if required). If the content is not
10
present, default messages are used. Set Content Type as 23 - Text and set the
name and description to settings. This entry is case-sensitive.
Display Welcome Messages

It is possible to configure two lines as a welcome message for the customer display.
The text can be max. 20 characters each. The message appears when the operator
signs in. These lines can be configured in the settings content file under extension
applications.
Sample:
[translation]
display_welcome_message_row1 = Welcome!
display_welcome_message_row2 = Dear guest
If one of the lines is not configured, the welcome message does not appear.
NOTE
The extension application is initialized when Service Host starts. To ensure
that the extension application is loaded properly, fully reload the database
on each workstation and restart each terminal. This ensures that the
extension application has been correctly loaded and enabled. Verify the
version of the application using the built-in function (see the Page
Designer section).
11
5 Configuration
This chapter describes the basic configuration process that is performed through
EMC.
Fiscal Printer Serial Port Number

To set up the fiscal printer port number for each workstation:
1. Select the property, click Setup, and then click Workstations.
2. Double-click the workstation record, and click the Data Extensions tab.
3. Configure the serial port number as a Fiscal Printer Serial Port Number
(usually 1).
5. Repeat steps 1 through 4 for each workstation with a fiscal printer attached.
NOTE
Set the COM port with the values 0, 99, or 999.
 Use 0 for Windows devices or 999 for Linux devices in case the
workstation is operating as non-fiscal. The workstation is not
enabled for closing a check (Receipts-Invoices).
 The value 99 means that the Fiscal Interface is disabled. Use 99
when the workstation is in Lab Mode or when there is a non-fiscal
printer connected to the workstation (for example, Room Posting).
12
Payment Types
To ensure that Simphony payments are properly mapped to payment types used by
the fiscal printer and properly printed on documents, follow the steps below to set the
correct type for each payment to trigger the fiscal or non-fiscal printing.
WARNING
Each payment with no fiscal type selected (a type) is treated as non-fiscal.
The transaction closed by this payment does not print a fiscal receipt.
1. Select the property, click Configuration, and then click Tender/Media.

2. Double-click the tender media record, and then click the Data Extensions tab.
3. Select types from b to f as a Fiscal Payment Type:
 Empty value - For non fiscal tender
 0 - Cash
 1 - Credit Card or Cheque
 2 - Credit Card
 50 - Account receivable payment (NON RISCOSSO)
Type 50 is not permitted as overtender; the payment amount must be the
same as the check value.
 81 - VOUCHER/COUPONS (BUONO MULTIUSO)
 701-710 (min 701 max 710. Used for Ticket Restaurant1)
5. Repeat steps 1 through 4 for each payment that executes fiscal printing when
used.
WARNING
Tender media rounding is supported only and solely for the default cash
payment (Type 0)—not supported for other payments. Enable rounding to
five in the EMC Tender Media module, select the Options tab, select the
Ops Behavior subtab, and then select 87 - Round Payments and
Change. Only full rounding to 5 cents is supported. When this option is
enabled, it is necessary to enable the rounding option in the fiscal printer
manually in case balance issues arise.
NOTE
Ticket restaurants can be linked to one from 10 available Fiscal Printer
payment groups (Tipo di pagamento). The default group is 1. If specific
Ticket tender media should be linked to another group, Payment Fiscal
Type needs to be filled with a number 7xx, where xx is a group number
(01-10).
1
Payment is registered on the fiscal printer as Non Collected - CORRISPETTIVO NON
RISCOSSO. Refer to Appendix A for description.
13
For example, 709 will be translated as payment type 7 (Ticket), group (09).
Payment groups must be configured as a part of the Fiscal Printer configuration.
14
Departments Configuration
The tax authorities require differentiation of items between goods and services. This
configuration is placed in the departments (Reparti) of the fiscal printer, where each
department can only be set as Goods or Services. The tax class and tax rate are
configured in the department. This requirement causes duplication of the
departments.
For example, a property uses menu items as goods and services. The menu items
defined as goods must be linked to a tax class which maps the 10% tax rate to a
department (reparto) of the printer configured with 10% tax rate and defined as
goods. The menu items acting as services must be linked to a tax class using the
10% tax rate but linked to the fiscal printer department (reparto) configured with 105
tax rate and defined as services.
The department can be set from 1 to 10 (up to 50) for the GOODS, and can be set
from 51 (up to 99) for the SERVICES. The departments (that is, 1 and 51) are
configured identical except for the SALES TYPE/Tipo vend. (0 for the depart.1 – 1 for
depart. 51).
GOODS
SERVICES
See additional information under chapter Tax Classes and Departments (Reparti).
15
One ATECO code is supported by the tax configuration. As such, it is not possible to
switch between multiple ATECO programmatically.
16
Tax Classes and Departments (Reparti)
Fiscal printer tax groups (Departments) must be mapped to Simphony tax rates.
A basic mapping can be configured using the report group under tax rates in EMC.
The number entered in that column reflects the department (reparto) number, which
must match the tax percentage on both systems.
Another approach is to link the department number that contains the tax rate using
the data extension Fiscal Tax ID.
1. Select the Enterprise, property, or zone, click Setup, and then click Tax Classes.
2. Enter the Department number as Fiscal Printer Link.
If the system is configured to use multiple taxes for one tax class (tax dependent of
Order Type), configure the Department number at least for each enabled tax rate.
For example, if tax 1, 2, and 3 are enabled for Tax Class, the Fiscal Printer Link looks
like 1=x;2=y;3=z where x, y, and z are the Department number for specific tax rates.
If the property uses items for goods and services, duplicate the department (reparto)
configuration in the fiscal printer—one for goods and one for services.
See example configuration above. Additional details are available in Departments

Configuration.
17
Tar Rates and Report Groups
In addition to the previous tax to department configuration, the solution provides
the ability to use Report Groups as fiscal printer departments. The solution first
verifies whether the previous configuration is present; if this is not the case, the
solution collects the report group column from the tax rates, where the number
inserted in that column reflects the department number of the fiscal printer.
For Transaction Services clients, the only valid department configuration is the
report group column. The solution does not collect the Tax Class settings, but
requires to define the departments within the tax rates in the report group column.
In the sample configuration above, tax 10% is linked to department 1, tax 22% is
linked to department 2, tax 4% is linked to department 3, and tax exemption with
0% is linked to department 0.
The tax configuration with report groups is the only valid configuration for
Transaction Services clients.
NOTE
Typically in Italy the taxes on fiscal printer are set as: 1-10%; 2-22%; 3-4%; 4-
0% (EXEMPT).
WARNING
 It is required to have a proper tax configuration in place. If the tax
configuration is inaccurate, the taxable totals may affect fiscal operations
and cause possible fiscal issues. This applies to Menu Items, Service
Charges, and Discounts.
 Remember to check the TAX RATE configuration in the Fiscal Printer
every time a Firmware Update is done.
 This configuration approach is not supported for Transaction Services
clients.
18
Menu Item Class Configuration
Menu Items by default shall be handled as goods (Beni). This can be achieved by
assigning the proper tax class linked to a department (Reparto) designed as GOODS
department. If one or more menu items need to be configured as Services (Servizi)
(for example Cover charge, Room Service, and so on), the menu item must use a tax
class linked to a department designed as Services.
The same approach can be applied to service charges, which based on the
designation should be designed as services but in specific cases it may be necessary
to be handled as Goods. For service charges it is necessary to use a tax class which
is linked to a department designed as required.
The following image shows an example of the Menu Item Classes configuration.
Then link the Menu Item to the appropriate Menu Item Class.
19
Tax Configuration Requirements
Any tax relevant details (Menu Item, Service Charge) part of a transaction must have
one tax rate assigned. There are four possible tax rates allowed:
10%
22%
4%
0% (exempt)
Discounts must be configured with a tax class with all tax rates listed above enabled.
The Tax Parameter international option #1 must be disabled.
The Tax Parameter options 4, 6, and 8 must be enabled.
All the tax rates must be printed.

Other Tax Parameters options may be enabled or disabled as needed.
The solution verifies the taxes applied during each transaction. If tax rate amounts
are mismatched, an error shows the amount difference and the transaction cannot be
finalized.
20
Customer List (Customer Master Data)
You can add customer data to any transaction by using a key with the extensibility
function fiscal-invoice. This configuration is described in the Configuring Extensibility
Function Button section.
To print a courtesy invoice, use the dedicated function to print an invoice from the last
receipt or to print a direct invoice. You can add a special function at any moment of
the transaction.
1. Open a transaction and add menu items.
2. In the transaction, add a function that will enable a special screen while using
Tender Media.
3. Press any Tender Media to show the multiple choice contest menu with 5 options.
4. Select an option from 0 to 4.
5. Enter the company or personal information (depending on the selection made in
the previous step). Mandatory fields are indicated in white.
 Ricerca (FIND): Look up a customer profile record saved in the local database.
 Salva come nuovo (Save new record): Save a new customer profile for later.
 Salva (Save): Save a customer profile if it was updated.
The above buttons are enabled when the option Autorizzo il trattamento dei
miei dati personali per riferimenti future (Consent agreement) is checked. If
the option is disabled, customer details are used only to issue an invoice
document as part of the fiscal requirements.
 Azzera (CLEAR): Clears search criteria.
21
 X Button (CANCEL): Closes the customer data window and returns to the
transaction screen.
 Green Tick (CONFIRM): Closes the transaction and prints an invoice document.
After a press to the CAP field, the form shows a list of available postal codes. Enter
the number of the postal code required. The application shows the list of available
postal codes. Press the desired code to select it. The data will be entered into the
main form and the related data is populated.
Printing Documents with Copies

The system prints fiscal documents with a configurable number of copies, depending
on the tender media.
1. Select the Enterprise or property, click Configuration, and then click
Tender/Media.
2. Double-click the tender media record to open it, and then click the Data
Extensions tab.
3. Enter the number of copies in the Number of Fiscal Rec. Copies field. This
value is the number of copies printed in addition to the first copy.
If you do not enter a value, no extra copy is printed.
22
Configuring Courtesy Invoice Counter
You can select courtesy invoice numbers to be unique at each workstation (fiscal
printer), property level, or revenue center level.
1. Select the property, click Setup, and then click RVC Configuration.
2. Double-click the revenue center, and then click the Data Extensions tab.
3. Select the counter level.
The default counter level is Workstation.
WARNING
If the Check and Posting Service (CAPS) is offline, and the counter is set
to property, courtesy invoices cannot be processed.
WARNING
If the invoice counter level (for example, Property, Workstation) has been
configured and used at a certain level, any level change will affect the
number increment. After such a level change, validate the next available
invoice number to avoid possible invoice numbering issues.
The solution retains fiscal data in the Check and Posting (CAPS) databases, and the
courtesy invoice counter for fiscal purposes in the CAPS or in the workstation
database, based on the counter level configuration. If one or both of the databases
are deleted (dropped) the fiscal data may be lost. Before removing the database(s),
export all available courtesy invoices from the CAPS database and save the file in a
secure location.
For the courtesy invoice counter, use the function to read the current courtesy invoice
number (get-inv-cnt). This value should be set when the database has been
regenerated and no fiscal data is present in the database. After restarting the system
with an initial database, set the courtesy invoice counter using the feature to set the
courtesy invoice counter (set-inv-cnt).
23
Functional Configuration
This section describes the functionality provided by the Simphony Fiscal Italy Solution
that can be executed by pressing a button visible on Simphony POS client pages.
Table 5-1 - Functions Available Inside a Transaction
Function Name Description
fiscal-invoice The receipt will be printed as Invoice, so the

(see warning box below) customer search flow is executed before
printing Fiscal Receipt followed by a courtesy
invoice.
fiscal-transaction-return Sets transaction as RESO MERCE (ex Nota di

Credito) (Transaction Return). Possible args
are: none or empty for classic REFUND
(default), POS if the customer has a purchase
POS receipt instead of the purchase fiscal
receipt (all args are case insensitive). When
this option is set, only negative items are
permitted; it is not permitted to mix positive with
negative items apart of discounts.
ask-customer-piva Ask for customer Partita Iva to print on Fiscal

check.
ask-customer-codfisc Ask for customer Codice Fiscale to print on

Fiscal check.
courtesy-receipt After the fiscal receipt is printed, a non-fiscal

document like the fiscal receipt printed, but
without prices. (no Args needed)
group-menu-items Group all menu items in one row by tax rate.

Possible Args: A menu name, such as Lunch
Menu. Also known as “Pasto Concordato”
ask-customer-lotterycode Ask for customer Lottery Code to print on Fiscal

check, or to scan a barcode with the integrated
barcode scanner.
print-check-as-non-fiscal Mark and print a check as non fiscal check.
direct-invoice A courtesy invoice is generated, prompting the

(see warning box below) user to insert the customer data. No fiscal
receipt is printed.
WARNING
The two buttons direct-invoice and fiscal-invoice cannot be configured
together. Only one of them can be present at a time.
24
Table 5-2 - Functions Available Outside of a Transaction
version Show working Fiscal Client version number.
z-report Close a day on fiscal printer and print Z

Report.
x-report Prints fiscal printer X Report.
fiscal-sum-report Prints fiscal summarized report by date.

Button must be restricted to selected
personnel.
fiscal-memory-report Prints fiscal detailed reports. Button must be
restricted to selected personnel.
set-inv-cnt Allow to set next invoice number to be printed
by fiscal printer.
get-inv-cnt Retrieve configured invoice parameters.

disableifc Temporarily disables fiscal interface.
enableifc Enables previously disabled fiscal interface.
reprint-last-receipt Reprints last printed fiscal receipt.
customer-management Shows customer management dialog, restrict
access to dedicated employees, using
Simphony page features.
fiscal-dgfebydates-report Prints DGFE by Dates. Button must be
fiscal-dgfebydatenumbers-report Prints DGFE by Date and Numbers. Button
must be restricted to selected personnel.
reprint-invoice-from-dgfe Reprints a single Invoice from DGFE. Button
must be restricted to selected personnel.
reset-printer Resets Fiscal Printer unit.
invoices-export Exports invoices to CSV flat file.
rt-status Shows detailed RT printer status.
rt-lottery-status Shows detailed Lottery status.
rt-single-lottery-status Shows the Lottery status of a single receipt.
rt-lottery-set-company-name Set Company Name for Lottery XML Files

(This procedure must be performed every time the
customer header (Company Name) is updated in the
fiscal printer)
rt-lottery-move-rej-files Move rejected files to history folder.
rt-lottery-read-message Read and Show on screen the Lottery

Courtesy message stored inside the Fiscal
Printer.
set-automatic-z-report
25
get-automatic-z-report Automatic Daily Closure (set and get

parameter about automatic z-report), must be
done immediately after an end of day.
dgfe-security
Functions to handle the RT security (to access
the fiscal memory). Possible args are: login,
logout and setTimeOut (all args are case
insensitive). Add the buttons in a protected
area, giving access only to specific users.
view-ateco-codes Button must be restricted to selected

personnel.
Shows the ATECO codes set into the RT
printer
disable-rounding This function disables full rounding in the

fiscal printer. Rounding must be disabled in
the printer and in Simphony. Button must be
enable-rounding This function enables full rounding in the fiscal
printer. Only full rounding is supported. When
enabled, it is necessary to enable rounding to
5 cents for the tender media defined as cash.
Button must be restricted to selected
personnel.
customer-management Shall be used outside of a transaction to

display customer administration form.
get-department-bulk Displays department configuration, including

tax percentages and related information.
get-department-parameters Displays the selected department

configuration.
get-tax-rates Displays the configured tax rates from 1 to 9.
26
WARNING
 We strongly suggest making the function dgfe-security available
only to selected personnel with a higher security privilege to
remain compliant with the GDPR requirements.
 You can change the default access code as needed (from a
minimum of 5 to a maximum of 40 characters). The solution
encrypts the access code and this is not visible to the user. Retain
the changed access code in a secure place. If the access code is
not available, a reset of the printer by a professional technician is
required and causes additional costs.
 To change the access code of a printer configured by default, it is
necessary to use the dgfe-security function with the argument
setpassword. If the printer has an access code mismatch with the
workstation attached, it is necessary to use the dgfe-security
function with the argument savepassword. This function saves the
entered access code locally and will be used to contact the printer
to run the reports.
It is possible to reset the workstation to default, deleting the file
gdpr.dat in the extension application directory of the workstation.
This file is newly generated with default values after restarting the
workstation.
Configuring the Extensibility Function Button

To add a button and associate it with the fiscal extensibility function:
1. Select the Enterprise, property, or revenue center, click Configuration, and then
click Page Design.
2. Open the page on which to add the function key.
3. Click Button, and configure it as follows:
 Type: Function
 Function#: Run Extensibility App
 Arguments:
Type=DLL;AppName=Micros.FiscalLayerClient;FileName=Micros.FiscalLayer
Client.dll;Script=[function name];Arg=
 Replace [function name] with one of the functions listed in the previous table
(without [ ] square parenthesis)
Here is an example for setting the access code for GDPR requirements:
type=dll;appname=Micros.FiscalLayerClient;filename=Micros.FiscalLayerClient.dll;scr
ipt=dgfe-security;arg=setpassword
27
Non-Fiscal Receipt on Fiscal Printer
With the Simphony Fiscal Italy solution, you can use a fiscal printer as a regular POS
non-fiscal 40 columns thermal roll printer to allow printing documents such as:
 Guest Checks
 Reports
 Time Chits
 Custom printouts (generated by SIM or other Extensibility)
The printout is formatted and configured on the standard Simphony (or custom SIM or
Extensibility) level, while the application itself acts as an emulator of the EPSON
TM88 Express Thermal printer with TCP/IP interface.
To configure a fiscal printer as a POS printer:
1. Select the property, click Setup, and then click Printers.
2. Add a printer, and set the following values:
 Workstation: Select a workstation with Fiscal Service and a connected fiscal
printer
 Type: Ethernet Roll Printer
 Address: Set the workstation with Fiscal Service and a connected fiscal
printer IP address
 Port: By default, enter 9100
NOTE
The user can print non-fiscal receipts if the receipts are finalized (tax paid) in a
third party system, such as a Property Management System, or if the receipt
taxes are declared in a subsequent receipt. See handling gift cards with loaded
amount.
In addition to the default capabilities to enable non-fiscal receipt printing for non-
fiscal tender medias, you can print on demand a “Documento Gestionale” (Non
fiscal receipt).
To do so, you need to configure a touchscreen button (see Page Design

Functions).The workstation operator presses the preconfigured button to flag the
transaction as non-fiscal and consequently to print a non-fiscal receipt.
28
29
6 Conversion Invoice Electronic Format
Starting with version 3.6.3, you can convert the exported invoices from the CSV files
into an XML file, compliant with the Italian electronic invoices regulation.
This application requires .NET Framework 4.5 or higher.
The application is part of the software solution as “InvoiceExportXML”.
Before trying to process any conversion of the CSV file, you must configure all
required settings in the form “Impostazioni”. If any of the required fields is missing, the
application will prompt with an error.
To convert a previously exported CSV file, open the application, select File | Apri
Export File CSV or press the Converti Fatture button, select the exported CSV file
and confirm the file dialog.
The generated invoices will be exported in the folder “fatture”. For each invoice part of
the CSV file, the application generates an electronic invoice file.
The required naming convention is COUNTRY, FISCAL CODE (Partita IVA) an
underscore sign and the INVOICENUMBER (for example,
IT12345678903_00069.xml).
The application processes all required fields and validates all mandatory formatting
requirements. If any of those required fields is not in the expected format, the
application shows an error and the invoice will not be converted. If errors appear, you
can change the value affected in the CSV file and retry.
Please see Appendix E for additional information about the function to export invoices
to a CSV flat file.
30
7 Transaction Services Fiscal Plugin
To run fiscal transactions in Italy, you must use the Fiscal transaction services plugin.
The file named “FiscalItalyTSPlugin.dll” is contained in the extensibility application.
During the initialization procedure of the workstation, the solution verifies whether the
workstation has been configured to act as an API Workstation. If this is the case, the
solution first extracts the plugin DLL to the Handlers folder, renaming the actual file if
available. Then it verifies whether the web.config file contains the required
configuration entries. If not, it adds the required entries. If changes are applied to the
system, updates or initial installation, the solution prompts the user to restart the
workstation, which must be completed before using this extension.
The DLL, which controls the Transaction Services Interface for Fiscal Italy and is
named: FiscalItalyTSPlugin.dll, must be located in the
“Micros\Simphony\WebServer\wwwroot\EGateway\Handlers” folder.
The following lines must be present in the “web.config.txt”
<add key="TenderMediaClassFile" value="FiscalItalyTSPlugin.dll,
FiscalItalyTSPlugin.TenderMediaPlugin" />
The only permitted tax configuration to map fiscal printer departments to the
Simphony tax rates for transaction services is the use of the report groups available
in the tax rate configuration. Refer to the Tax Classes and Departments (Reparti)
configuration section for additional details.
31
The solution supports up to four checkExtensibilityDetails passed from the
Transaction Services application. The additional data can be used to submit fiscal
information to the authority and to provide the ability to the third party system to
process invoices, without the risk to submit double fiscal figures to the authorities.
Providing Additional Fiscal Data
 Note that you can only provide additional fiscal data with calls to
PostTransactionEx2 or AddToExistingCheckEx2 once. Ideally this should be
provided with the final payment information (that is, the one that will cause
the check to be closed). Calls to PostTransactionEx or
AddToExistingCheckEx will not support that Customer Data is provided.
 Customer Data needs to be provided as an object checkExtensibilityDetails,
which is part of the pGuestCheck object:
 Properties of SimphonyPosApi_Extensibility need to be set as following:

Lottery Code
This feature allows the third party system to send the lottery code to the related
receipt. The value is not validated.
Property Name Value Description
DisplayName "Micros.FiscalLayerClient" Hard-Coded
value
ExtensibilityAppName "Micros.FiscalLayerClient" Hard-Coded
value
ExtensibilityDataName “LOTTERY_CODE” Hard-Coded
value
ExtensibilityDataType "System.String" Hard-Coded
value
PrintOptionBits "000000000000000000000" Hard-Coded
value
StringData “1234567” Lottery Code
as text
32
Fiscal Code
This feature allows the third party system to send the fiscal code (codice fiscal) to the
related receipt. The value is not validated.
value
value
ExtensibilityDataName “FISCAL_CODE” Hard-Coded
value
value
value
StringData “XXXXXX00X00X000X” Fiscal code as
text
Tax Code
This feature allows the third party system to send the fiscal code (partita IVA) to the
related receipt. The value is not validated.
value
value
ExtensibilityDataName “TAX_CODE” Hard-Coded
value
value
value
StringData “01234567890” Tax code as
text
Only one of the above checkExtensibilityDetails can be submitted to the printer. If
there are multiple checkExtensibilityDetails, the solution may report an error or ignore
the submitted checkExtensibilityDetails.
33
No Fiscal Check
This provides the ability to store the check as non-fiscal. As an example, this
approach is required when the third party system generates an electronic invoice.
When this text is submitted, the receipts will not be submitted to the fiscal printer but
only processed internally in Simphony.
value
value
ExtensibilityDataName “NO_FISCAL_CHECK” Hard-Coded
value
value
value
StringData “01234567890” Tax code as
text
Transaction Services Error Codes

The Transaction Services Plugin contains error codes that allow the user to quickly
identify possible issues and react with proper actions.
Table 7-1 - Transaction Services Error Codes
Error Code Description Possible Solutions

FISCALITALY01 In case the tax calculation of all Verify the correct tax
of the check details fails, the configuration of the items, in
system answers with an error relation to tax rated reporting
and with this error code. groups, order types and tax
settings in general of all of the
items present in the check
body.
Verify the egateway.log for a
comprehensive error
description.
FISCALITALY02 Returned in case of network Verify the network connection
errors or fiscal printer related between the workstation
errors. defined as API workstation
and the workstation where the
fiscal printer is attached. Verify
the serial connection to the
printer and the network
connectivity.
Verify the egateway.log for a
comprehensive error
description.
34
Error Code Description Possible Solutions
FISCALITALY03 This error code is returned Verify the egateway.log for a
when the solution has an comprehensive error
unexpected exemption. description.
FISCALITALY04 In case the fiscal code (codice Send a fiscal code (codice
fiscal) is set in the message, fiscale) compliant with the
and the fiscal code format is Italian fiscal requirements.
invalid.
FISCALITALY05 In case the vat code (partita Send a vat code (partita IVA)
IVA) is set in the message, and compliant with the Italian fiscal
the vat code format is invalid. requirements.
35
Appendix A
Uncollected Payments
(CORRISPETTIVO NON RISCOSSO)
In Italy, it is common practice to use specific vouchers called Ticket Restaurant to pay
for the restaurant services. Ticket Restaurant vouchers are issued by third-party
companies.
When the customer pays for the services with Ticket Restaurant vouchers, the
physical payment is not collected at the time of payment. The restaurant typically
issues a Tax Invoice for Ticket Restaurant issuer by the end of the month to collect
the physical payment.
However, there is still an obligation to register a single transaction on the fiscal printer
by printing a standard fiscal receipt.
To avoid a double tax pay obligation, first based on fiscal cash register records and
second on the Tax Invoice issued for the Ticket Restaurant operator, it is required to
use a specific payment method configured as “Corrispettivo Non Riscosso” for the
fiscal receipt.
To configure a specific Tender Media, refer to the Payment Fiscal Types section.
Example (may differ based on version)
Fiscal Receipt Z-Report

90003 RAPPORTO FISCALE
---------------------------------------- EURO
CHK 94 TBL 2 GST 1 TOTALE GIORNO 3,82
614 dev-mwreczycki 02/11/2016 14:21 GRAN TOTALE 140.806,04
---------------------------------------- TOTALE SCONTI 0,00
Dine In TOTALE RETTIFICHE 0,00
EURO TOTALE RESI 0,00
Evian 0,33l 3,82 CORRISPETTIVI NON RISCOSSI 3,82
TOTALE EURO 3,82 SCONTRINI FISCALI 2
Ticket Restaurant 3,82 SCONTRINI MEMORIA FISCALE 0
NON RISCOSSO SCONTRINI NON FISCALI 1
RESTO 0,00 NUMERO AZZERAMENTI 65
02-11-16 15:28 SF. 1 NUMERO SCONTRINI NOTE di CREDITO 0
EX 99250041 TOTALE GIORNO NOTE di CREDITO 0,00
GRAN TOTALE NOTE di CREDITO 353,21
---------------------------------------- NUMERO FATTURE 0
Grazie per averci visitato! TOTALE GIORNO FATTURE 0,00
---------------------------------------- NUMERO RIC. FISC. 0
TOTALE GIORNO RIC. FISC. 0,00
NUMERO DOC. CLASSE II 0
TOTALE GIORNO DOC. CLASSE II 0,00
GRAN TOTALE DOC. CLASSE II 797,86
TOTALE SCONTRINI 3,82
TOTALE FATTURE (DA SCONTRINO) 0,00
TOTALE FATTURE (DIRETTE) 0,00
02-11-16 15:28 SF. 2
NUMERO RIPRISTINI 1
DISPOSITIVO GIORNALE FONDO ELETTRONICO
N. 1 M.F.EX99250041 01-01-2011 00:00
36
Appendix B
Troubleshooting
This appendix describes how application layers cooperate, how to effectively
troubleshoot solutions, and how to report potential issues to make them reproducible
in a lab environment.
Solution Architecture
The fiscal solution for Simphony is built from one extension application, which
contains the Transaction Services client and all libraries required for functional
purposes.
The application has three functional layers:
1. Operational layer handles the transaction logic and prepares the envelope
including fiscal printer commands to the network layer.
2. Network layer coordinates the fiscal printer communication, passing the
information from the operational layer to the device layer. Also if the fiscal
printer is attached to the local workstation.
3. Device layer communicates with the fiscal printer physically and handles the
serial communication.
All three layers are part of the extension application.
Logging
You can use the Simphony EGateway log for troubleshooting:
EGateway Log
Simphony EGateway log files are generated by standard Simphony logging utilities.
The information logged depends on the Log Verbosity level set in the EMC at the
workstation level. If there are issues, you need to increase the log verbosity.
1. Go the folder
C:\Micros\Simphony\WebServer\wwwroot\EGateway\EGatewayLog.
2. Open the file LogZone_LoadHandlers.txt in a text editor.
3. Search for the line with “ExtApps,0” (this is set by default).
4. Change the line, increasing the verbosity to 2 (for example “ExtApps,2”).
All log lines related to the fiscal solution start with “FiscalItaly”. For example, the serial
port initialization results in:
FiscalItaly.DeviceCommunication.Open(): portname set to COM7,
FiscalItaly.DeviceCommunication.Open(): port baudrate set to 57600,
FiscalItaly.DeviceCommunication.Open(): port handshake set to None,
Log files are located in the EGatewayLog folder (usually
C:\Micros\Simphony\WebServer\wwwroot\EGateway\EGatewayLog\Log_[workstation
name].txt).
37
The EGatewayLog folder contains entries about the Simphony ServiceHost
application, and information about the Simphony Fiscal Italy solution, which is
identifiable by the word “FiscalItaly”.
While troubleshooting incidents in the EGatewayLog, ensure that the log verbosity for
the specific workstation is set at a high enough level.
Maximum Communication Log Size
The application automatically overwrites log files after the maximum size is exceeded.
This operation prevents the workstation from running out of disk space. The default
maximum log size is 16 MB. You can modify this value in the <MaxLogSizeMiB> tag.
Example:
<MaxLogSizeMiB>2</MaxLogSizeMiB>
Log file will be overwritten after exceeding 2MB.
Check Item Display Mode
When menu items are added to a check, corresponding information is presented on
the customer display that is connected to the fiscal printer. In default mode, when
applying a menu item, discount, or service charge, the information presented to the
customer shows the item quantity, item name, and item total.
Example:
1 2 3 4 5 6 7 8 9 0 11 12 13 14 15 16 17 18 19 20
Line 1 € 2 2 , 9 2
Line 2 6 x S a n P e l l e g r i n o
When a check is tendered, subtotal information is presented.

Example:
1 2 3 4 5 6 7 8 9 0 11 12 13 14 15 16 17 18 19 20
Line 1 € 3 1 , 3 9
Line 2 S u b t o t a l e
You can change the information presented when adding a menu item, discount, or
service charge to a check by adding information about the current check subtotal.
However, due to the limitations of display space (maximum 20 characters per line)
the article name is truncated, depending on the quantity and total values.
Example:
1 2 3 4 5 6 7 8 9 0 11 12 13 14 15 16 17 18 19 20
Line 1 1 E v i a n 0 , 3 3 € 3 , 8 2
Line 2 S u b t o t a l e € 1 0 , 2 4
38
Appendix C
Courtesy Invoices and Customer Data
There is an obligation for business entities to collect specific customer details for the
transactions closed with Fiscal Invoice. You can add customer data to any transaction
using a key with the extensibility function “fiscal-invoice”. The configuration is
described in Configuring the Extensibility Function Button.
To print the Fiscal Invoice for a transaction, add a fiscal invoice marker during the
transaction. The check details display the entered marker:
The invoice marker can be easily voided like other menu items on the check.
When closing a check with an invoice marker, the system collects customer details.
Complete the relevant customer information.
 Customer information is stored in the database as customer profile only if the

consent agreement checkbox, highlighted in red in the figure above, is checked. If
the consent agreement is unchecked, the customer information is stored only for
fiscal purposes, and is then deleted
 The Customer Type selection appears at the top of the form and can be changed
using the drop-down list.
39
 You can search for a customer in the database. Enter one or more values, and
then click the Search button. If multiple customers match the search criteria, the
system shows all customer profiles returned.
 You can edit a customer already stored in the database. Search for the customer,
edit the information, and then click the Save button. To save the modified record
as a new record, press the Save as new button.
 You can select some fields from the list. To display the list, click the required field.
 Some fields become inactive or active depending on the selected Customer
Type.
 You can clear all fields by clicking the Clear button.
 To print the fiscal invoice with the selected customer, click the Confirm button.
The system validates all mandatory fields before editing or saving customer
information in the database, and before processing invoice printing.
A new customer is not automatically stored in the customer database. You must click
the Save as new button to make customer information available for the future invoice
to be issued. Otherwise, customer information is stored only as a part of the invoice
legally required details.
Example of a customer information printed on a

courtesy invoices:
Company
Name Surname
Street Nr. 11
12345 ZZ IT
P.IVA/C.F TAX ID
00000000000/ABCDEFGHIJKLMNO
40
Customer Data Validation
Italian fiscal regulation requires you to collect specific mandatory information when
printing any kind of invoice. The following data validation rules are implemented:
 Fiscal Code: Conditionally Mandatory if Tax ID is not provided
 Tax ID: Conditionally Mandatory if Fiscal Code is not provided
 Tax Country: Mandatory (rules for Country and Tax Country may be different)
 Company: Conditionally Mandatory if First Name and Surname are not provided
 First Name: Conditionally Mandatory if Company is not provided
 Surname: Conditionally Mandatory if Company is not provided
 Address: Mandatory
 Postal code: Mandatory
 City: Mandatory
 Province: Non-mandatory if country is Italy, province can be selected from list
 Municipality: Mandatory
 Country: Mandatory (can be selected from the list)
 Representative: Non-mandatory
 Representative Tax Country: Conditionally Mandatory if Representative is
present
 Representative Tax ID: Conditionally Mandatory if Representative Fiscal Code is
not provided
 Representative Fiscal Code: Conditionally Mandatory if Representative Tax ID
is not provided
The validation rules implemented are not dependent on the customer type selected,
and are always based on the above criteria.
41
Data Dictionary
Data required is stored in CheckPostingDB on the CAPS workstation, and can be
accessed from there to generate specific exports.
FCR_CUSTOMER_DATA Table
This table stores customer profiles that can be used for invoices issued in the future.
This table cannot be used for issued tax invoice reporting, because data can be
modified or purged.
Table C-2 - FCR_CUSTOMER_DATA Table
Column Description Value Example
[CustomerID] Unique customer ID 12345
[CustomerType] Customer Type IP
IP: Italian Private

IC: Italian Company
NIP: Non-Italian Private
NICL: Non-Italian
Company + Legal
Representative
NIC: Non-Italian
Company
[CustInfo1] Fiscal Code (Codice XXXXXXXXXXXXXXXX
Fiscale)
[CustInfo2] Tax ID / Consent 12345678901^Datetime
datetime
[CustInfo3] Name ^ Surname John^Doe
[CustInfo4] Company Name Company Name
[CustInfo5] Tax Country^Codice ITALY^1234567

Destinatario
[CustInfo6] Address including house Via Garibaldi 55
number
[CustInfo7] ZIP ^ City 12345^City Name
[CustInfo8] Municipality ^Province ^ MI^Milan^ITALY

Country
[PropertyID] Property Number 1
[CustInfo9] Representative Sarah Smith
[CustInfo10] Representative Tax ITALY

Country
[CustInfo11] Representative Fiscal XXXXXXXXXXXXXXXX^
Code^PEC Destinatario pec@xxx.it
42
[CustInfo12] Representative Tax ID 12345678901
[PurgeStatus] 0 not transferred to 0

CAPS, 1 transferred to
CAPS
43
FCR_INVOICE_DATA Table
This table stores issued invoice data. One record represents one invoice. The data
reflects the original invoice; the system cannot modify this data. This table is used for
export creation.
Table C-3 - FCR_INVOICE_DATA Table
[PCWSID] 0 (Always) 1
[FCRInvNumber] Invoice Number/Fiscal 14

Number (Scontrino)
[MicrosChkNum]
[InvoiceType] 1 (Invoice), 2 (Scontrino), 1 only

3 (Nota di Credito)
[InSARMode] 0 - Not in SAR, 1 - closed 0/1
in SAR mode
[CustomerID] CustomerID from 12345
FCR_CUSTOMER_DATA
from Customer Profile
table.
[InvoiceStatus]
[MicrosBsnzDate] Check Closed Business 2016-11-23 12:00:00.000

Date
[FCRBsnzDate] Check Closed DateTime 2016-11-23 14:11:00.000
[RTC]
[Subtotal1] Gross Sales Sum (Check) 1000.0000
[Subtotal2] Net Sales Sum (Check) 909.0909
[Subtotal3] Tax Amount Sum (Check) 90.9090
[Subtotal4]
[Subtotal5]
[Subtotal5]
[Subtotal7]
[Subtotal8]
[Subtotal9]
[Subtotal10]
[Subtotal11]
44
[Subtotal12]
[TaxTtl1]
[TaxTtl2]
[TaxTtl3]
[TaxTtl4]
[TaxTtl5]
[TaxTtl6]
[TaxTtl7]
[TaxTtl8]
[ExtraField1] Fiscal Code (Codice XXXXXXXXXXXXXXXX

Fiscale)
[ExtraField2] Tax ID 12345678901
[ExtraField3] Name ^ Surname John^Doe
[ExtraField4] Company Name Company Name
[ExtraField5] Tax Country^Codice ITALY^1234567

Destinatario
[ExtraField6] Address including house Via Garibaldi 55
number
[ExtraField7] ZIP^City 12345^City Name
[ExtraField8] Municipality ^Province ^ ^ME^ITALY

Country
[PropertyID] Property ID 1
[FCRID] Sequential sequence 1

incrementing
[StoreID]
[SerialID] Fiscal Check Number/FCR 15/99123456789/231

Serial Number/Z-Report Or
Number (Fiscal Check 0/99123456789/231
Number = 0 means direct
invoice)
[DocumentType] Customer Type IP
IP: Italian Private

IC: Italian Company
NIP: Non-Italian Private
45
NICL: Non-Italian
Company + Legal
Represantative
NIC: Non-Italian Company
[DataType]
[SysDocID]
[FiscalRef]
[Subtotal13]
[Subtotal14]
[ExtraField9]
[ExtraField10] Representative Sarah Smith
[ExtraField11] Representative Tax ITALY^pec@xxx.it

Country^PEC Destinatario
[ExtraField12] Representative Fiscal XXXXXXXXXXXXXXXX
Code
[ExtraField13] Representative Tax ID 12345678901
[ExtraField14] Micros Check Number 100001
[ExtraField15] Workstation Object 11111111

Number
[ExtraField16] Table Identifier (Always) IT_Invoices
[ExtraDate1]
[ExtraDate2]
[ExtraDate3]
[ExtraDate4]
[ExtraDate5]
[PurgeStatus] 0 no transferred to CAPS, 0

1 transferred to CAPS
FCR_TTL_DATA Table
This table stores check items and tax data for related issued invoice.
For the check items data, the column FCRInfo16 has the “marker” IT_ItemDetail;
46
For the tax data, the column FCRInfo16 has the “marker” IT_TaxData;
That is, there is a many to one relationship between the FCR_TTL_DATA table and
the FCR_INVOICE_DATA table.
Table C-4 - FCR_TTL_DATA Table for TAX DATA (FCRInfo16 = IT_TaxData)
IT_TaxData
[FCRBsnzDate] Now() 2016-11-23 12:00:00.000
[FCRID1] FCRInvNumber from 14

FCR_INVOICE_DATA
[FCRID2 Tax ID 1
[MicrosBsnzDate] Business Date 2016-11-23 12:00:00.000
[FCRInfo1] Tax Rate Number 1
[FCRInfo2] Taxable Totals by Rate 54.5500
[FCRInfo3] Tax Amount by Rate 5.4500
[FCRInfo4] Tax Percentage by Rate 10.0000
[FCRInfo5] Gross Amount 60.0000
[FCRInfo6]
[FCRInfo7]
[FCRInfo8]
[FCRInfo9]
[FCRInfo10]
[FCRInfo11]
[FCRInfo12]
[FCRInfo13]
[FCRInfo14]
[FCRInfo15]
[FCRInfo16] Table Identifier (Always) IT_TaxData
47
IT_TaxData
[PurgeStatus] 0 not transferred to CAPS, 1 0

transferred to CAPS
48
Table C-4 - FCR_TTL_DATA Table for CHECK ITEM DETAIL (FCRInfo16 =
IT_ItemDetail)
IT_ItemDetail
[FCRBsnzDate] Now() 2016-11-23 12:00:00.000
[FCRID1] FCRInvNumber from 14

FCR_INVOICE_DATA
[FCRID2 Row Number 0001
[MicrosBsnzDate] Business Date 2016-11-23 12:00:00.000
[FCRInfo1] Item Type M(*)
[FCRInfo2] Item Description Spaghetti alla carbonara
[FCRInfo3] Item Price 5.00
[FCRInfo4] Item Quantity 3.00
[FCRInfo5] Item Tax Rate 22.00
[FCRInfo6] Item Object Number 210000523
[FCRInfo7] A number to link a Menu 1

item with his Item Discount
[FCRInfo8]
[FCRInfo9]
[FCRInfo10]
[FCRInfo11]
[FCRInfo12]
[FCRInfo13]
[FCRInfo14]
[FCRInfo15]
[FCRInfo16] Table Identifier (Always) IT_ItemDetail
[PurgeStatus] 0 not transferred to CAPS, 0

1 transferred to CAPS
49
Note:
(*)The field [FCRInfo1] can contain the following values:
 M = Menu Item
 ID = Item Discount
 SD = Subtotal Discount
 S = Service Charge
 Tnnn = Tender Media (T0=Cash / T1=Credit Card / T6=Change / T701 to
T709=Ticket)
The field [FCRInfo7] contains a number to link together a Menu Item (M) with the
respective Item Discount (ID).
50
Appendix D
Invoices Export (CSV)
The CSV Invoices Export functionality requires parameters to run. The parameters
are located in the Micros.FiscalClient.Properties.xml, which is loaded as Extension
Application content.
Basic knowledge of Extensible Markup Language (XML) is required.
It is recommended that you use one of several available XML editors when modifying
the configuration file to ensure that the structure remains intact and that XML parsers
can read the file correctly.
51
The following fields are exported in the CSV file:
Table D-5 – Exported Fields
Field Description Note Comment
tipo di comunicazione: 0
Tipo comunicazione · 0 - Fatture emesse
· 1 - Fatture ricevute
Contribuente - Partita IVA partita IVA del contribuente Tax payer's TAX ID
Contribuente - codice fiscale codice fiscale del contribuente Tax payer’s FISCAL CODE
codice della nazione riferita
alla partita IVA
Cliente/Fornitore - codice
del Cliente/Fornitore in
paese
formato ISO 3166-1 alpha-2 Country ISO 3166-1 alpha-2
code code
codice della nazione riferita
Cliente/Fornitore - Paese alla partita IVA
del Cliente/Fornitore Country
Codice Destinatario
partita IVA italiana, estera del
Cliente/Fornitore - Partita IVA
cliente/fornitore Company Tax ID
Cliente/Fornitore - codice fiscale del
Codice fiscale cliente/fornitore Client fiscal code
ragione sociale del
Cliente/Fornitore -
Cliente/Fornitore se
Ragione sociale
società. Social reason code
Cliente/Fornitore - nome del Cliente/Fornitore se
Persona fisica - Nome persona fisica Contact person first name
Cliente/Fornitore - cognome del Cliente/Fornitore
Persona fisica - Cognome se persona fisica Contact person second name
se il cliente/fornitore si avvale
Cliente/Fornitore -
di un
Rappresentante fiscale
rappresentante fiscale
all'estero
all'estero Company representative
l’indirizzo del Cliente/Fornitore
relativo:
Cliente/Fornitore -
· alla sede legale per le
Sede legale/Residenza -
società
Indirizzo
· al Residenza per le persone
fisiche Company address
il numero civico del
Cliente/Fornitore - Sede Cliente/Fornitore relativo:
legale/Residenza - Numero · alla sede legale per le
civico società
· al Residenza per le persone Street Number
CAP del Cliente/Fornitore
relativo:
Cliente/Fornitore - Sede
legale/Residenza - CAP
società
· al Residenza per le persone Postal code
comune del Cliente/Fornitore
Cliente/Fornitore - relativo:
Sede legale/Residenza - · alla sede legale per le
Comune società
· al Residenza per le persone Commune
52
provincia del Cliente/Fornitore
relativo:
legale/Residenza - Provincia
società
· al Residenza per le persone City
codice dello stato del
Cliente/Fornitore
relativo:
legale/Residenza - Codice
Stato
società
· al Residenza per le persone Country code
stato del Cliente/Fornitore
relativo:
legale/Residenza - Stato
società
· al Residenza per le persone Country
Se il Cliente/Fornitore si
Cliente/Fornitore -
avvale di una stabile
Stabile organizzazione -
organizzazione, indicare
Indirizzo
l’indirizzo ALWAYS EMPTY
Cliente/Fornitore - Stabile
organizzazione - Numero
organizzazione, indicare il
civico
numero civico ALWAYS EMPTY
organizzazione - CAP
organizzazione, indicare il cap ALWAYS EMPTY
Cliente/Fornitore -
Stabile organizzazione -
organizzazione, indicare il
Comune
comune ALWAYS EMPTY
Cliente/Fornitore - Stabile avvale di una stabile
organizzazione - Provincia organizzazione, indicare la
provincia ALWAYS EMPTY
organizzazione, indicare lo
organizzazione - Codice
stato
Stato
in formato ISO 3166-1 alpha-2
code ALWAYS EMPTY
Cliente/Fornitore - Stabile avvale di una stabile
organizzazione - Stato organizzazione, indicare lo
stato ALWAYS EMPTY
Cliente/Fornitore -
avvale di un rappresentante
Rappresentante fiscale -
fiscale indicare il codice paese
Codice Paese
riferito alla partita IVA ALWAYS EMPTY
Cliente/Fornitore -
fiscale indicare il paese riferito
Paese
alla partita IVA ALWAYS EMPTY
Cliente/Fornitore
PEC (indirizzo Posta
elettronica certificata)
53
Cliente/Fornitore -
fiscale indicarne la partita IVA
Partita IVA
personale ALWAYS EMPTY
Cliente/Fornitore -
fiscale indicarne la
Denominazione
denominazione se società ALWAYS EMPTY
Cliente/Fornitore -
fiscale indicarne il nome se
Nome
persona fisica ALWAYS EMPTY
Cliente/Fornitore -
fiscale indicarne il cognome
Cognome
se persona fisica ALWAYS EMPTY
Può assumere i seguenti
valori:
· TD01 - Fattura
· TD04 - Nota di credito
· TD05 - Nota di debito
· TD07 - Fattura semplificata·
TD08 - Fattura
Tipo documento semplificataTD10 - Fattura per
acquisto intracomunitario
beni
· TD11 - Fattura per acquisto
intracomunitario
servizi
TD10 e TD11 valgono solo
per le fatture ricevute TD01
Data documento Data della fattura
Numero documento Numero della fattura
Da compilare solo per le
fatture ricevute
Data registrazione
Data di registrazione della
fattura ALWAYS EMPTY
Imponibile indicato sulla riga
Imponibile della fattura senza separatore
di decimali Absolute invoice value
Imposta indicata sulla riga
Imposta della fattura senza separatore
di decimali Absolute tax value
Aliquota IVA senza separatore Tax rate
di decimali
Aliquota
Dato alternativo al campo
Natura.
54
Può assumere i seguenti N4
valori:
· N1 - escluse ex art.15
· N2 - non soggette
· N3 - non imponibili
· N4 - esenti
· N5 - regime del margine/IVA
Natura
non esposta in
fattura
· N6 - Inversione contabile
· N7 - IVA assolta in altro
stato UE
Dato alternativo al campo
Aliquota.
Dato richiesto dalla
Detraibile
comunicazione EMPTY
valori:
Deducibile
· SI
· NO NO
valori:
· I – IVA ad esigibilità
Esigibilità IVA
immediata
· D – IVA ad esigibilità differita
· S – Scissione dei pagamenti I
The following example shows an invoice with three different rates. The three related
rows are exported to the CSV file. If an invoice has more than one rate, one row is
exported for each rate.
55
CSV Content Example:
0;00000000000;AAAAAAAAAAAAAAAA;IT;Italia;XYZ1234;;abcxyz65b26g674y;;John
Smith;;Via Roma
156;;20100;Milano;MI;IT;Italia;;;;;;;;;;;;;;;TD01;15/01/2019;74;;000000000000455;000000000
000045;001000;;;NO;I
Smith;;Via Roma
000180;002200;;;NO;I
Smith;;Via Roma
000000;000000;N4;;NO;I
0;00000000000;AAAAAAAAAAAAAAAA;IT;Italia;QWERTYU;012345678901;;Mr. Best;;;;Via
Roma
123;;20100;Milano;;IT;Italia;;;;;;;;;;;;;;;TD01;15/01/2019;75;;000000000000859;00000000000
0086;001000;;;NO;I
0;00000000000;AAAAAAAAAAAAAAAA;IT;Italia;QWERTYU;012345678901;;Mr. Best;;;;Via
Roma
123;;20100;Milano;;IT;Italia;;;;;;;;;;;;;;;TD01;15/01/2019;75;;000000000002951;00000000000
0649;002200;;;NO;I
Smith;;Via Roma
000231;001000;;;NO;I
Smith;;Via Roma
000357;002200;;;NO;I
0;00000000000;AAAAAAAAAAAAAAAA;IT;Italia;;012345678901;;Mr. Best;;;;Via Roma
123;;20100;Milano;;IT;Italia;;;;;;;;;;email@pec.server.it;;;;;TD01;15/01/2019;77;;0000000000
00182;000000000000018;001000;;;NO;I
Smith;;Via Roma
000056;001000;;;NO;I
Smith;;Via Roma
000131;002200;;;NO;I
Smith;;Via Roma
000000;000000;N4;;NO;I
56
Appendix E
Courtesy Invoices Export
After exporting the courtesy invoices into the csv format, you can generate the xml
files compliant for the Italian Tax Agency (Agenzia delle Entrate) using the tool
InvoiceExportXml.exe. To do so, first you must retrieve the CSV file previously
generated on CAPS on the computer running the InvoiceExportXml.exe application.
1. Open the InvoiceExportXml.exe. The application displays.
NOTE
You can disable the XML/XSD validation feature (a warning message
appears).
2. When running for the first time, insert your company registry and tax information.
To do this, select Impostazioni, and then select Anagrafica Esercente.
3. Enter your information in each of the four tabs: Cedente Prestatore,

Rappresentante Fiscale, Imponibili, and Esenzione.
57
NOTE
 All yellow fields are mandatory.
 Some fields are prefilled.
4. When finished, click the X in the upper right corner to save data and close the
window.
5. Select File, and then select Converti Fatture Standard or Converti fatture con
dettagli if you have generated the CSV with all the check/invoice details.
58
6. Browse to the folder where you exported the invoice’s CSV files, and then select
the file that you want to generate the XMLs:
7. Click on the selected file, and then select Open. The XML files will be generated
instantly.
NOTE
Check for error messages.
8. The XML files are saved under the folder fatture created were the application
started from.
Be aware that this application can only be executed on a Windows operating system.
59
Appendix F
Additional Functions for RT Printer
RT Printer Status
The RT Fiscal printer has a more complex and detailed status.
With the Page Design button “rt-status” it is possible to show the detailed printer
information:
RT Status Sample
RT Printer available status:
MAIN: 1=Non in Servizio, 2=In Servizio
SUB: 5=Da Censire, 6=Censito, 7=Attivato, 8=Programmato RT
The RT printer type can only be used when Main status equals 2 and Sub status
equals 8. Any of the other states require a printer configured as legacy fiscal printer.
60
Reso Merce Procedure (ex Nota di credito)
This procedure is engaged by the EMC Page Design button “fiscal-transaction-
return”, and requires POS Operations to be in an opened check status. The “fiscal-
transaction-return” function must be called before performing any other activities with
the opened check.
Follow the steps shown in the help form using the correct data format.
If the transaction is not complete but is stored with a service total, the procedure
listed above must be followed again.
61
Void Check (Annullo conto e scontrino)
This procedure is engaged by the EMC Page Design functions “Storno conto chiuso”
or “Storno conto chiuso da lista”.
Storno conto chiuso Storno chiuso da lista
The procedure involves several passages, as listed below:

1. A check number must be entered (or selected from the Void Closed Checks List).
2. Confirm void the closed check.
3. If Yes, the following instructions appear:
4. Insert the date, Fiscal Printer, Serial Number, Zreport number, and Check
number (0000-0000).
5. If required, select the void reason applied to this void.
6. A further cancellation request is shown.
62
7. The "commercial document issued for cancellation" (DOCUMENTO
COMMERCIALE emesso per ANNULLAMENTO) is printed and the confirmation
message appears.
Possible warning messages:

Lo scontrino 0000-0000 del gg/mm/aaaa non esiste su questa cassa,
probabilmente è stato stampato da un'altra cassa.
Verificare la matricola fiscale inserita '99MEY000000'.
Il collegato conto nnnnn è annullabile solo dalla cassa che lo ha
emesso.
In alternativa si suggerisce di effettuare una PRATICA DI RESO (Nota
Credito).
La matricola fiscale '99MEY000000' coincide con questa cassa ma lo

scontrino 0000-0000 del gg/mm/aaaa non esiste su questa cassa.
Il conto nnnnn non è stato cancellato.
Verificare i dati inseriti.
I dati inseriti si riferiscono ad uno scontrino di RESO MERCE.

E' impossibile annullare il conto.
Lo scontrino richiesto è già stato annullato in precedenza.

E’ Impossibile procedere
I dati inseriti si riferiscono ad uno scontrino di RESO MERCE.

E’ impossibile procedere
I dati inseriti si riferiscono ad uno scontrino di ANNULLO.

E’ impossibile procedere
If the workstation is configured to work with a normal fiscal printer (not RT type), this
message appears:
La funzione 'Annullo conto chiuso' è disponibile solo per le Workstation

con stampanti RT.
63
Appendix G
Interfaces to Third-Party Systems
Mandatory Simphony Configuration
At the Enterprise level in the Format Parameters module, check the Number of
Guest Check Information Lines and set the value to 30.
Courtesy Invoices Interface

This function applies mainly for Electronic Invoices interface. When the Fiscal
Interface receives a special command line from a third party system, a new row
appears in the opened check (Guest check Information line)*.
Possible 3 different special command
lines:
1. NO_FISCAL_CHECK
When option 1 is activated, the fiscal check
will not be printed and the relative data are
stored in the workstation database.
2. STORE_FISCAL_CHECK
When option 2 is activated, the fiscal check
will be printed and the relative data are
stored in the workstation database (see
below ** in FCR_TTL_DATA Table).
64
WARNING
Check data older than 15 days will be automatically and permanently
deleted from the datastore db.
Invoices Data Dictionary

Check Data for Electronic invoices are stored in the table FCR_TTL_DATA in the
Datastore db on the workstation, and can be accessed from there to generate specific
exports.
FCR_TTL_DATA Table
This table stores various kind of data. The records for the electronic invoice can have
the strings IT_Text_Check_Detail or IT_Fiscal_Check_Detail in the column
FCRInfo16.
Table G-1 - FCR_TTL_DATA Table

[FCRBsnzDate] Now() 2018-11-23 12:35:10.030
[FCRID1] Not used for this 0
functionality
[FCRID2 Not used for this 0
functionality
[MicrosBsnzDate] Now() 2018-11-23 12:35:10.030
[FCRInfo1] Simphony check 100083
number
[FCRInfo2] Workstation ID 23
[FCRInfo3]** Fiscal Check Number 53
[FCRInfo4]** Fiscal Printer Serial 99123456789
Number
[FCRInfo5] Fiscal Check ZReport 31
Number
[FCRInfo6] Not used for this Null
functionality
functionality
functionality
functionality
functionality
functionality
functionality
65
functionality
functionality
functionality
[FCRInfo16] Table Identifier IT_Text_Check_Detail
**IT_Fiscal_Check_Detail
[PurgeStatus] Not used for this 0

functionality
IT_Text_Check_Detail Records example:
**IT_Fiscal_Check_Detail Records example:
WARNING
Check data older than 15 days will be automatically and permanently
deleted.
66
Custom Header and Trailer Rows Interface
EMC Configuration
1. Create a new Extension Application (name or number not relevant) and insert a
new Application Content (Names not relevant). Change the Type of the Content
to 19 - Sim Script.
Import the SIM script either from File or Copy&Paste the sample at the end of
this document. Save you changes.
Click the General tab of the Extension Application and ensure that Option Bits 2
is enabled and that both Target and Version will not create any limitations.
2. In the Guest Check Trailers module, print Guest Check Trailers on non-fiscal
checks. Add the line “@@PRINT_CUSTOM_TRAILER” (w/out the quotes) in any
of the 12 Trailer lines as shown below:
3. In the Guest Check Headers module, print Guest Check Headers on non-fiscal
checks. Add the line “@@PRINT_CUSTOM_HEADER” (w/out the quotes) in any
of the 6 Header lines as shown below:
67
4. In the Tender/Media module, ensure that Printing Options 22 and 28 are enabled
and that the check is printed for any Tender/Media that should be used for QA.
Printing Option 23 is needed if you want to print non-fiscal checks (for example, if you
are using a non-fiscal tender media).
68
Appendix H
How to Report an Issue
Understanding the architecture and troubleshooting the Fiscal solution, use the
following guidelines when reporting issues to second support level or to product
development.
1. Ensure that the workstation log verbosity is set to high enough.
2. Collect the log file described in the previous section, being sure to have enabled
the higher verbosity and being sure the issue is present in the log file.
3. Specify the issue occurrence time and ensure that the log files provided contain
referring entries.
4. Describe the steps to reproduce (if known) and all other relevant aspects that
may help to understand and reproduce the problem.
5. Always provide the following additional information:
- Simphony version
- Simphony deployment (On-premises, Cloud Standard, Cloud Enterprise)
- Workstation model (operating system)
- Fiscal printer model and type
- Fiscal printer connectivity (RS directly, USB converter, other)
- Fiscal printer firmware version
- Fiscal solution extension application configuration level (Enterprise, Zone,
Property, or Revenue Center).
Other details may be requested depending on the issue.
69
Appendix I
XML 7.0/RT2.0 Changes
This fiscal solution supports firmware capable of RT 2.0 (XML 7.0). Several
functionalities have been extended to comply with the related requirements. Starting
from this version, firmware not supported with RT 2 .0 XML7.0 cannot be utilized.
Table I-6 – New Functions in XML 7.0/RT2.0

Adapted/New Behavior
Function
VOID/REFUND New options available to process a void/refund receipt.
Data Security To access specific reports, it is now necessary to use an
access code. The fiscal application allows the user to save
the access code locally and in the printer. The function to
store the access code should be restricted (the same for
the functions required to print the reports affected).
End of day A new function is available to set an automatic end of day,
including the printout of the Z report, if needed. The
authority highly suggests to close the day before midnight.
Cash amount Round cash payments to 5 is now possible. Only full
rounding rounding in negative and positive is permitted. In case of
multiple payments, the rounding is not permitted. In such
cases the cash payment must be processed before the
final payment. It is necessary to enable rounding manually
in the fiscal printer and in EMC using option 87 - Rounding
for the cash tender media defined under Tender/Media
parameters as default cash tender solely.
Voucher/Coupon Tender Media type option, use type 81 for dedicated
payment for the redemption of the gift certificates. When
the gift certificate is sold as an item, this item shall not be
taxed, as the taxes will be applied during the redemption
operation. Verify with your tax advisor.
Account receivable Tender Media type option, use type 50 for receipts paid in
payment a second moment.
Goods and Services A new option available on each printer available in
departments. The menu item classes must be linked to a
tax class configured as goods or as services. It may be
necessary to create multiple departments using the same
tax rate but defined as goods or as services.
ATECO Code It is necessary to set an ATECO code in the departments
related to the activity. The code is transmitted to the tax
authorities. Only one ATECO code can be set (the same
code for all printers).
70

Simphony Fiscal Italy - Installation Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Simphony Fiscal Italy - Installation Guide

Uploaded by

Copyright:

Available Formats

Oracle® Food & Beverage

Installation Guide for

1 Fiscal Implementation for Simphony 1

6 Conversion Invoice Electronic Format 30

7 Transaction Services Fiscal Plugin 31

Appendix A Uncollected Payments 36

Appendix C Courtesy Invoices and Customer Data 39

Appendix D Invoices Export (CSV) 51

Appendix E Courtesy Invoices Export 57

Appendix F Additional Functions for RT Printer 60

Appendix G Interfaces to Third-Party Systems 64

Appendix H How to Report an Issue 69

Appendix I XML 7.0/RT2.0 Changes 70

Date Description of Change

Implementation Model Examples

Table 4-1 - Data Extensions

Table Extra Column Type Data Translatable Translatable Help

Tender/Media FLC_RecCopyCount Number 0-9 Number of Non Number of extra copies

Revenue FLC_InvoiceCounterLevel Big Text Invoice Counter Invoice Counter Level

Workstation FLC_BaudRate Lookup Fiscal Printer Serial connection baud rate.

Workstation FLC_HandShake Lookup Fiscal Printer Serial connection hand

Workstation FLC_UseLocalDevice Boolean Fiscal Printer local RT printer attached to

Property FLC_VirtualPrinterEnabled Boolean Enable Virtual Enable network printer

Property FLC_VirtualPrinterPort Number Virtual Printer Network printer emulator

Property FLC_VirtualPrinterCodePage Text Virtual printer Network printer emulator

Workstation FLC_TrnTimeOut Text FL Transactions Change default timeout for

Workstation FLC_RptTimeOut Text FL Reports time Change default timeout for

All data extensions must be editable, downloadable, and viewable.

 FLC_RemoteDeviceIP: In case of remote fiscal device, IP address of the

Adding a Data Extension (On Premises)

Creating an Extension Application

8. Double-click the record that you created (Micros.FiscalLayerClient), and then

Display Welcome Messages

Fiscal Printer Serial Port Number

1. Select the property, click Configuration, and then click Tender/Media.

Payment groups must be configured as a part of the Fiscal Printer configuration.

See example configuration above. Additional details are available in Departments

The Tax Parameter options 4, 6, and 8 must be enabled.

All the tax rates must be printed.

Printing Documents with Copies

4. Save the changes.

Function Name Description

fiscal-invoice The receipt will be printed as Invoice, so the

fiscal-transaction-return Sets transaction as RESO MERCE (ex Nota di

ask-customer-piva Ask for customer Partita Iva to print on Fiscal

ask-customer-codfisc Ask for customer Codice Fiscale to print on

courtesy-receipt After the fiscal receipt is printed, a non-fiscal

group-menu-items Group all menu items in one row by tax rate.

ask-customer-lotterycode Ask for customer Lottery Code to print on Fiscal

direct-invoice A courtesy invoice is generated, prompting the

Function Name Description

version Show working Fiscal Client version number.

z-report Close a day on fiscal printer and print Z

fiscal-sum-report Prints fiscal summarized report by date.

get-inv-cnt Retrieve configured invoice parameters.

rt-lottery-status Shows detailed Lottery status.

rt-single-lottery-status Shows the Lottery status of a single receipt.

rt-lottery-set-company-name Set Company Name for Lottery XML Files

rt-lottery-move-rej-files Move rejected files to history folder.

rt-lottery-read-message Read and Show on screen the Lottery

get-automatic-z-report Automatic Daily Closure (set and get

view-ateco-codes Button must be restricted to selected