SAP User Guide Certificazione Unica 2021

User Guide | INTERNAL
2021-01-21
SAP User Guide - Certificazione Unica 2021

© 2020 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 SAP User Guide - Certificazione Unica 2021. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 CU 2021 - Main Affected Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
1.3 Process Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4 Company Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.5 Sections and Boxes (Caselle). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Dati Anagrafici. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Section B. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Dati Relativi al Coniuge e ai Familiari a Carico. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Rimborsi di Beni e Servizi non Soggetti a Tassazione - Art 51 Tuir. . . . . . . . . . . . . . . . . . . . . . . . 54
Particolari Tipologie Reddituali. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Compenso Lordo Campione D’italia. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Redditti dei Punti da 1 a 5 al Netto dei Compensi di Campione D'Italia. . . . . . . . . . . . . . . . . . . . . 55
Dati Previdenziali ed Assistenziali . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Trattamento di Fine Rapporto (TFR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Annotations for CU Modello Ordinario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Section G. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Section P - Pignoramenti. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

2 INTERNAL Content
1 SAP User Guide - Certificazione Unica
2021
The SAP User Guide describes the Certificazione Unica (CU 2021) reporting functionalities.
1.1 Introduction
This SAP solution covers the whole process, providing features to extract data from the SAP database (payroll
cluster and master data), check, print, and save in a specific cluster of the CU form and data.
It is also possible to overwrite or add in a flexible manner each field of the form, by providing the information in
a dedicated table.
Every year, each employee must receive from his employer a form (printed or accessible via web) containing
data with all amounts that the employer paid in place of the employee to SI entities (INPS and INAIL). And to
AdE, regarding data relevant to taxes.
The Certificazione Unica model must be sent also as an e-form to the AdE. In fact, this data is used as input to
prepare the pre-filled e-form of 730, which is accessible via internet net to all Italian citizens. The aim of this
process is to facilitate the citizens’ tax declaration (made with 730). In theory, the citizen can just check and
confirm the data in the 730 e-form (additional data will come from banks, insurances, and other actors). If the
data are not correct or not all the needed data are in the 730, the citizen has to use the standard ways used
until 2015, that is filling the 730 manually or using the e-form as a basis, and submit it with a CAF.
The CU Modello Ordinario is composed of the following sections:
● Front page: corresponds to record B of CUR file. It is the frontespizio of the “communication”;
● Section CT: corresponds to record C (not supported in standard);
● CU certification: contains data corresponding to records:
○ D: frontespizio of single CU;
○ G: for employee records;
○ H: for freelances or professionals (lavoratori autonomi). This record is also used to handle
Garnishments (Pignoramenti) information.

SAP User Guide - Certificazione Unica 2021 INTERNAL 3
1.2 CU 2021 - Main Affected Areas
In 2021, the affected areas are the following:
● Added Boxes in the CU Form
Section Added Boxes Link to Section
Dati Anagrafici ○ 11 Dati Relativi al Dipendente, Pensio

nato o altro Percettore delle Somme
[page 13]
Dati Fiscali - Dati per la eventuale ○ 12 Dati Fiscali: dati per la eventuale com
compilazione della dichiarazione dei pilazione della dichiarazione dei red
Giorni
redditi diti [page 19]
○ 13
○ 14
Detrazioni e Crediti ○ 368 Detrazioni e Crediti - Dati Fiscali: dati

○ 375 per la eventuale compilazione della di
chiarazione dei redditi [page 34]
Trattamento Integrativo (new sub-
section)
○ 400
○ 401
○ 402
○ 403
○ 404
○ 405
○ 406
○ 407
○ 408
○ 409
○ 410
Altri Dati ○ 475 Altri Dati - Dati Fiscali: dati per la

○ 476 eventuale compilazione della dichiara
zione dei redditi [page 40]
Clausola di Salvaguardia (new sub-
section)
○ 478
○ 479
○ 480
Dati Previdenziali ed Assistenziali ○ 26 Section 2 - INPS Lavoratori Subordi

○ 27 nati Gestione Dipendenti Pubblici
[page 57]

4 INTERNAL SAP User Guide - Certificazione Unica 2021
Section Added Boxes Link to Section
Pignoramenti ○ 22 Section P - Pignoramenti [page 66]
● Added Sections in the CU Form
Section Link to Section
Sezione 4 INPS Soci Cooperative Artigiane Section 4 - INPS Soci Cooperative Artigiane [page 58]
● Renumbered Boxes in the CU Form
Section Boxes in CU 2021 Boxes in CU 2020 Link to Section
Detrazioni e Crediti ○ 369 ○ 368 Detrazioni e Crediti - Dati

○ 370 ○ 369 Fiscali: dati per la eventuale
○ 371 ○ 370 compilazione della dichiara

zione dei redditi [page 34]
○ 372 ○ 371
○ 373 ○ 372
○ 374 ○ 373
○ 376 ○ 374
○ 377 ○ 375
○ 378 ○ 376
○ 379 ○ 377
○ 380 ○ 378
○ 381 ○ 379
○ 382 ○ 380
○ 383 ○ 381
○ 384 ○ 382
○ 385 ○ 383

Dati Previdenziali ed Assis Sezione 2 - INPS Lavoratori Sezione 2 - INPS Lavoratori Section 2 - INPS Lavoratori
tenziali Subordinati Gestione Dipen Subordinati Gestione Dipen Subordinati Gestione Dipen
denti Pubblici denti Pubblici denti Pubblici [page 57]
○ 28 ○ 26
○ 29 ○ 27
○ 30 ○ 28
○ 31 ○ 29
○ 32 ○ 30
○ 33 ○ 31
○ 34 ○ 32
○ 35 ○ 33
○ 36 ○ 34
○ 37 ○ 35
○ 38 ○ 36
○ 39 ○ 37
○ 40 ○ 38
○ 41 ○ 39
○ 42 ○ 40
○ 43 ○ 41
○ 44 ○ 42
Dati Previdenziali ed Assis Sezione 3 - INPS Gestione Sezione 3 - INPS Gestione Section 3 - INPS Gestione
tenziali Separata Parasubordinati Separata Parasubordinati Separata Parasubordinati
○ 45 ○ 43 [page 57]
○ 46 ○ 44
○ 47 ○ 45
○ 48 ○ 46
○ 49 ○ 47
○ 50 ○ 48
○ 51 ○ 49
○ 52 ○ 50

Dati Previdenziali ed Assis Sezione 5 - Altri Entri Sezione 4 - Altri Entri ○ Section 5 - Altri Enti
tenziali [page 58]

○ 56 ○ 51
○ 57 ○ 52
○ 58 ○ 53
○ 59 ○ 54
○ 60 ○ 55
○ 61 ○ 56
○ 62 ○ 57
○ 63 ○ 58
○ 64 ○ 59
○ 65 ○ 60
● Deleted Boxes in the CU Form
Section Deleted Boxes Link to Section
Assistenza Fiscale 730/2020 Dichiar ○ 53 Assistenza Fiscale 730/2020 Dichiar

ante ante [page 22]
Detrazioni e Crediti ○ 384 Detrazioni e Crediti - Dati Fiscali: dati

○ 385 per la eventuale compilazione della di
○ 386 chiarazione dei redditi [page 34]
Compensi Relativi Agli Anni Prece ○ 517 Compensi Relativi Agli Anni Prece
denti ○ 518 denti [page 41]
Somme Erogate per Premi di Risultato ○ 621 Somme Erogate per Premi di Risultato
in Forza di Contratti Collettivi Azien in Forza di Contratti Collettivi Azien
dali o Territoriali dali o Territoriali [page 42]
Annotations for CU Modello Ordinario ○ 54 Annotations for CU Modello Ordinario

○ 55 [page 65]
1.3 Process Overview
The whole workflow for the process of the income declaration for Italy includes:
● Certificazione Unica (CU)

● Creazione file modello CU per Agenzia delle Entrate (CUR)
● Creazione file modello CU per Pignoramenti (CUP)
● Registrazione dati da file di attestazione CU (CUA)

Certificazione Unica Workflow
Steps Description
1 The employer runs the CU (RPC_PAYIT_CU) report for the employee, to gen
erate the CU declaration.
2 Then, runs the CUR (RPC_PAYIT_CUR) or CUP (RPC_PAYIT_CUP) report,

and generate the electronic file with the CU declaration to send to Agenzia
delle Entrate (AdE).
3 AdE receives the CUR file, with the CU declaration, then generates a receipt
file, which is sent to the employer.
4 The employer runs the CUA (RPC_PAYIT_CUA) report to load and update
the CU declaration.
In case the employee has to send the declaration back to AdE, the employer has to run the CUR or CUP report.
The system generates a file for substitution of the previous declaration, which can be sent to the AdE again, for
validation. The entire process follows according with the declaration of each employee.
 Note
CUR refers to the employee's declaration and CUP refers to the beneficiaries.
To save the receipt data in the CU cluster, you use the section R.
The fields that are saved in the section R are:
● PROTOCFILE: It is the protocol number inside the receipt file (field 1 from Attestazione File);
● PROTOCCU: It is the protocol number inside the receipt file for a declaration (field 5 from Attestazione
CUR);
● DATERECEIP: It is the date of dispatching inside the receipt file (field 6 from Attestazione File);
● HOURRECEIP: It is the hour of dispatching inside the receipt file (field 7 from Attestazione File);
● PROGCERTIF: It is the Progressivo certificazione inside the receipt file (field 33 from Attestazione CUR).
● STATUS: It is a code used to determine the current status of the declaration. The possible values are the
following:
● FLAG: This field indicates if the declaration is a Sostituzione or Annullamento;
● RECTYPE: It is the record type inside the receipt file (field 2 from Attestazione CUR).
The general workflow is described in the following images.

● Standard:

● Sostituzione:

● Annullamento:
For more information about the CU process, please access the following SAP Note:
● CU: SAP Note 2976227
1.4 Company Transfer
Starting from the refactoring in 2016, the Selezione Senza Società checkbox was removed, and the system
automatically identifies cases of company transfer. SAP supports only one case of company transfer per
employee per year.
To identify if the employee has a case of company transfer, the system compares the period set in the report's
selection screen and the data available in the employee's master data.
The possible behaviors are:
1. In case the company codes are different, it means that the report is ran for the Cedente company;
2. In case the company codes are the same, it means that the report is ran for the Cessionaria company.
In the section C of the CU form, the system considers the period that the employee is in the company that is
being processed, regardless if it’s Cessionaria or Cedente.
In section B:

● For the Cedente company, the system considers the period that the employee was in the company;
● For the Cessionaria company, the system considers the entire period – considering the period in cedente
company, except for the boxes 23 and 25 that consider only the periods that the employee is in the
cessionaria company.
For 730-4 boxes, the following logic is applied:
1. The Cedente company completes the payment before the employee’s transfer. All data are reported in the
CU of the Cedente company, but also the Cessionaria company.
2. The transfer occurs before the payment, the data are reported only in the CU Cessionaria.
3. If both companies paid, Cedente and Cessionaria, then, they handle partly the 730-4 data.
1.5 Sections and Boxes (Caselle)
In this section you can find information about all boxes that are in the Certificazione Unica.
 Remember
All entries delivered by SAP for CU boxes in table T5ITW5 are suggestions on how they can be filled.
Customers should change this customizing according to their specific scenarios and business
requirements, if needed.
1.5.1 Dati Anagrafici
To fill in the dati anagrafici section, you use the customizing T77PAYIT_CIA table.
The report uses the personal area (WERKS) and the personal subarea (BTRTL) of the employee to search this
table.
Fisrt, the system reads the area, subarea, and date. If the system does not find any information, it searches
with the area and date. Still, if it does not find any information, then it searches only for the date.
Therefore, it is possible to add specific entries for the personnel areas and subareas, or for the whole company.
The following table describes the relationship between the CU boxes of section 9 (Dati Anagrafici) and the
customizing of table the T77PAYIT_CIA table.

1.5.1.1 Dati Relativi al Datore di Lavoro, ente Pensionistico
o altro Sostituto d'Imposta
This subsection is the first part of the section A of the CU declaration.
Section A boxes's description
Box Description
1, 2 These boxes are filled in with information from the

T77PAYIT_CIA table.
3, 4, 5, 6, 7, 8, 9, 10, 11 These boxes use information from the

T77PAYIT_CIA_ADD table. It reads based on the area and
subarea.
1.5.1.2 Dati Relativi al Dipendente, Pensionato o altro

Percettore delle Somme
This section is filled with Master Data information.
Section A boxes's description
Box Description
1 For the employee, this box is filled with the information from
the PERID field, of Infotype 0002. For heirs (erede), the box
is filled with information from the CFCFM field, of Infotype
306 (subinfotype from Infotype 0021).
the NACHN field, of infotype 0002. For heirs, this box is filled
with information from the FANAM field, of Infotype 0021.
the VORNA field, of infotype 2. For heirs, this box is filled with
information from the FAVOR field, of Infotype 0021.
4 This box is filled with value 1 for men, and value 2 for women.
This information comes from the gender field, of Infotype
0002 for employee, and Infotype 0021 for heirs.

Box Description
5 For the employee, this box is filled with information from the
GBDAT field, of Infotype 0002. For heirs, this box is filled
with information from the FGBDT field, of Infotype 0021.
GBORT field, of infotype 2. For heirs, this box is filled with in
formation from the FGBOT field, of Infotype 0021.
GBDEP field, of Infotype 0002. For heirs, this box is filled
with information from the FGDEP, of Infotype 0021.
8 This box is filled only for heirs. The value is always Z.
20 First, this box loads information from Infotype 0156, that is

valid from January 2017. Then, using the MUNIC field it loads
the comune name of T5ITMX table.

valid from January 2017, using the PROVI field.

valid from January 2017, using the MUNIC field.

valid from January 2017, using the MERGED_COMUNE field.

valid from January 2017. Using the MUNIC field to load the
comune name from T5ITMX table.
 Note
This box is only filled if the address is different from the
one used in 2016.

valid from January 2017, using the PROVI field.
 Note
one used in 2016.

Box Description

valid from January 2017, using the MUNIC field.
 Note
one used in 2016.

valid from January 2018, using the MERGED_COMUNE field.
9, 10, 11 Not supported by SAP. These boxes can be filled in with val
ues from the V_T5ITUI_2_CU table view.
Domicilio Fiscale (boxes from 20 to 27)
The boxes 20, 21 and 22 must always be filled in. According to the specifications of AdE, the boxes 24, 25, 26
and 27 of this subsection are not generated if they are equal to the boxes 20, 21, 22 and 23.
The boxes 24, 25, 26 and 27 should only be filled in if the employee’s address has changed since the previous
year.
Regarding the boxes 23 and 27 (Fusione comuni), before CU 2018, the report used to load the information from
the Infotype 0156 for the previous and current year (01.01.2018 and 01.01.2019, for example) to compare the
Codice comune (MUNIC) field of both entries to check if the employee changed his or her address during the
year.
From CU 2018 version, if the field Fusione Comune:
● is filled in with entries for 01.01.2020 and 01.01.2021, the report compares them to verify if the employee
moved during the year;
● if the new field is filled in with entry for 01.01.2021 and not for 01.01.2020, the report compares the new
field (for 01.01.2021) with the MUNIC field (for 01.01.2020) to verify if the employee moved during the year;
● if the new field is not filled in with entry for 01.01.2021 and only filled in with entry for 01.01.2020, the report
compares the MUNIC field (for 01.01.2021) with the new field (for 01.01.2020) to verify if the employee
moved during the year;
● if the new field is not filled in with entries for 01.01.2020 and 01.01.2021, the report compares the MUNIC
fields for 01.01.2020 and 01.01.2021 to verify if the employee moved during the year.
See below the instructions on how to fill in the boxes 24, 25, 26 and 27 in the following scenarios:
● General case (no merging): the boxes must be filled in only if the fiscal address on 01.01.2020 is different
from the fiscal address on 0 1.01.2019. In other words, the comune on 01.01.2019 is different from the one
on 01.01.2020.
● Standard merging and merging of more than two comuni (the tax percentages of all the merging comuni
are uniform): the boxes must not be filled in. In this case the employee did not actually moved.

Example
On 01.01.2017, an employee lived in the comune of Mirabello (F235). During 2017, this comune merged with
another comune (Sant’Agostino – I209) to form the new comune Terre del Reno (M381). In this case, the
Codice comune (MUNIC) field entry for 01.01.2017 is Mirabello and the Codice comune (MUNIC) field entry for
01.01.2017 should be changed to Terre del Reno, nevertheless the boxes 24, 25, 26 and 27 must not be filled in.
● Change of fiscal address inside the same merged comune and merging with different tax percentages (the
tax percentages of all the merging comuni are not uniform): the boxes must be filled in. In this case, the
employee has actually moved. On this scenario, the Codice comune (MUNIC) field entry valid for 01.01.2017
(containing the new comune born from the merging) is the same of the Codice comune (MUNIC) field entry
valid for 01.01.2018 (still containing the new comune), but the old merging comune changed and, as
consequence, the tax percentage changed too. In this case the boxes 27 and 23 are different and contain
the codes of the old comuni.
Example
On 01.01.2018, an employee lived in the part of the new comune of Valfornace (M382) that corresponds to the
old merged commune of Pievebovigliana (G637). During 2018, the employee moved to another part of new
comune of Valfornace (M382) that corresponds to the old merged commune of Fiordimonte (D609). In this
case, both the entries in the Codice comune (MUNIC) field for 01.01.2018 and 01.01.2019 are the same
(Valfornace), but the boxes 24, 25, 26 and 27 must be filled in.
● Separation of a part of an old comune (that still exists) into a new comune: the boxes must be filled in. In
this case, the Codice comune (MUNIC) field entry valid for 01.01.2018 (containing the old comune still
existing) is different from the Codice comune (MUNIC) field entry valid for 01.01.2019 (containing the new
comune that came from a split from the old comune). On this scenario, the employee did not move
physically.
Example
On 01.01.2017, an employee lived in the part of the old comune of Settimo Torinese (I703) that, during 2017,
was removed from its territory to form the new comune of Mappano (M316). In this case, the employee did not
move physically, but the boxes 24, 25, 26 and 27 must be filled in with the data relevant to the new comune of
Mappano (M316).
In order to inform if the tax percentage between the merged commune and the original commune is different,
the Aliq. add. com. Differenziate checkbox has been created, as you can see in the image below.

The box 23 must be filled in when the comune is included in the list provided in the 730 instructions by the Tax
Agency. This list will be updated every year and contains all the comuni born from merging that still keep
different tax percentages for the parts of its territory that corresponds to the old comuni (that now form the
new merged comune).
See below the list included in the draft of 730-2018 instructions.
The box 27 must be filled in only if all the data relevant to “DOMICILIO FISCALE ALL’ 1/1/2018” exist (from
boxes 24 to 26), according to the rules described above.
This box must be filled in when the comune is included in the list provided in the 730 instructions by the Tax
Agency. This list will be updated every year and contains all the comuni born from merging that still keep

different tax percentages for the parts of its territory that corresponds to the old comuni (that now form the
new merged comune).
 Note
The comune list provided in the 730 instructions by the Tax Agency that is valid for box 23 is not the same
for box 27 (it depends on when the merging happened).
See below the list included in the draft of 730-2018 instructions.
1.5.1.3 Dati Relativi al Rappresentante
This subsection is not supported by SAP. The box can be filled in with values from the V_T5ITUI_2_CU table
view.

1.5.1.4 Riservato al Percipienti Esteri
This subsection is not supported by SAP. The boxes can be filled in with values from the V_T5ITUI_2_CU table
view.
1.5.2 Section B
1.5.2.1 Dati Fiscali: dati per la eventuale compilazione della

dichiarazione dei redditi
Boxes' description
Boxes Description
1 This box is filled in with the accumulated values in the

months where the contract is indeterminated, using the
T5ITW5 table.
This box verifies the payroll for all months, from the Infotype
0154 and T5ITNG table it defines what months have the in
determinate contracts, and what months have the determi
nated contratcts.
2 This box is filled in with the accumulated values in the

months where the contract is determinated, using the
T5ITW5 table.
This box verifies the payroll for all months, from the Infotype
0154 and T5ITNG table it defines what months have the in
determinate contracts, and what months have the determi
nated contratcts.
3, 4, 5, 7, 12 These boxes are filled in with values from the T5ITW5 table.

Boxes Description
6 First, this box gets value from the T5ITW5 table. If the value
is 0, then it reads the Infotype 0156 and uses dates from the
deduction type of the infotype to search in the T5ITDR ta
ble, through the absence wagetype. Using this wagetype, the
values of the payroll are read for the entire year. After that, it
reads the entries in the Infotype 0305 that contain the /D08
wage type. Then, it calculates the work period of the em
ployee in the year. From this period, are reduced the absence
days that are read in the T5ITDR table and those days read
in the Infotype 0305.
If the result is grater than 365, the value is always set for
365.
8 This box is filled in with the hire date of the employee.
The hire date is determined by RP_HIRE_FIRE function mod

ule. The function module uses the Infotypes 0000 and 0001
to make this decision.
It analyzes all the IT0000 based on the STAT2 (employee’

status) and IT0001 based on JUPER field, and, based on
that, it gets the first date the employee was active, which is
the hire date.
You can also change the value by implementing the BAdI

method CHANGE_PART_B.
9 This box is filled in with the fire date of the employee, if the
fire date is smaller than the end of the year.
10 This box is filled in with value X if the fire date is greater than
the end of the year (or if it doesn't exist).
11 If there are periods where the Infotype 0000 doesn't exist, it

is filled in with value 1. If there are days without deduction
(the wage type /401 is filled), it is filled in with value 2.
13, 14 These boxes are filled in with values from the T5ITW5 table.
The CU report displays warning messages if any of the fol
lowing conditions are met:
● The sum of boxes 13 and 14 is greater than box 6.

● The number of days in box 13 is greater than 181.
For all boxes regarding heirs (eredi), the accumulated value for the T5ITW5 is divided for all heirs. This division
is done by verifying the Infotype 0021, Subinfotype 0306. The SPERD field defines the percentage that is paid
for the heirs.

Heirs Boxes' Description
Boxes Description
1, 2 These boxes are filled in with value from the T5ITW5 table.
They select the contract in the same way as they fill for the
employee, but use the last value inserted to accumulate.
3, 4, 5 Thes boxes are filled in with value from the T5ITW5 table.
Example
The employee had 3 different periods during 2019:
1. First period as TD (Tempo Determinato – fixed-term contract) from 10/01/19 to 30/03/19. Relevant
income: EUR 4000.
2. Second period as TD from 10/07/19 to 30/10/19. Relevant income: EUR 6000.
3. Third period as TI (Tempo Indeterminato – open ended contract) from 01/11/19 and still ongoing. Relevant
income: EUR 8000.
Therefore, in this case we have 001= “8000”, 002 = “10000” (that is 6000+4000) and all the other boxes of
this subsection:
● 006 = 254 (sum of the days of the three periods (80+113+61)

● 008 = 10/01/2019 (first hire day of 2019)
● 009 and 010 = empty, because the employee is still working at 31/12/2019
● 011 = 1
1.5.2.2 Ritenute - Dati Fiscali: dati per la eventuale

compilazione della dichiarazione dei redditi
This section contains boxes from both CU modello sintetico and ordinario. All boxes from this section are
populated with wage groups in V_T5ITW5 customizing view.
Boxes' description
Boxes Description
21, 22, 23, 24, 25, 26, 27, 28, 30, 31, 32, 33, 34, 35, 36 These boxes are filled in with values from the T5ITW5 table.

Boxes Description
29 This box is filled in with values from the T5ITW5 table, con
sidering the amounts of post conguaglio, which refers to the
following year that the CU is being executed to the next year
of income year. By what was defined in the Macud constant.
The Mcud constant has the possible values:
● 1: January
● 2: February
This box is not going to be generated if the employee has left

the company before of 01.03 of the next year of the income
year.
for the heirs.
Box Description
21 This box is filled in with value from the T5ITW5 table.
1.5.2.3 Assistenza Fiscale
The following subsections are related to the balance of the 730-4 data done by the employer during the year.
1.5.2.3.1 Assistenza Fiscale 730/2020 Dichiarante
This subsection refers to the CU modello ordinario. The CU modello sintetico contains a limited subset of
boxes.

Boxes' description
Boxes Description
51 If the Conguaglio non eseg. field from the Infotype 0483 is

filled, the value is inserted in this box. The box searches for
what has been inserted.
In case of company transfer: if the cedente has not com

pleted all payments or reimbursements (in this case the sec
ond (or unique) installment has been paid by cessionaria)
then this field is filled in with value F.
52 This box uses the fiscal code of the Infotype 0483 (CODFIS)
to search in the T5ITPC table. If this information is found it
is filled in with value X. All valid entries of the infotype 0483
are verified.
54 This box is filled in with the values '1, 2 or 3' from the Info
type 0483 (INTEG) when the employee has 730-4 integra
tivo during the period in which the report is being executed.
55 This box is filled in with the value from the Infotype 0483
(TIPOR). If the TIPOR field is filled in, the field 55 is filled in
with value 1.
Saldo IRPEF 2019
Boxes' description
Boxes Description
If the sum of the deduction (trattenute) is greater than the

sum of the reimbursement (rimborsi), the difference is filled
in with value 61. If the sum of the reimbursement is greater,
the difference is filled in with value 62. If there are any differ-
ence between the values, no field is filled.

Boxes Description
63, 64 These boxes are filled in with the comparison of values in the
483 infotype with the values actually paid.
The accumulated debit and credit values are reported to the

employee in the IRPEF section, of infotype 0483 (only the
last one that isn't integrative, and one integrative are consid
ered|). Comparing this value with the one that was filled in
the field 61 and 62. If the value is the same, the fields 63 and
64 are filled. If there are differences, the value is reported in
the right field (63 if it was paid less than expected and 64 if
the reimbursement was less than expected).
Addizionale Regionale 2019
Boxes' description
Boxes Description
If the sum of the deductions (trattenute) is greater than the


employee in the IRPEF section, of Infotype 0483 (only the
75 This box verifies if the CRED1 and CRED2 fields, of Infotype

0483. Priority order: rettifica entries, date. Integrative type is
not considered.

Saldo Addizionale Comunale 2019
Boxes' description
Boxes Description


85 This box verifies if the CRED1 and CRED2 fields, of Infotype

0483. Priority order: rettifica entries, date. Integrative type is
not considered.
Saldo Cedolare Secca Locazioni 2019
Boxes' description
Boxes Description


Boxes Description

Imposta Sostitutiva Premi di Risultato
Boxes' description
Boxes Description
101 This box is filled in with values from the T5ITW5 table.
102 This box compares value in the Importo Imposta field of the
employee in the Imposta Sostitutiva Premi di Risultato sec
tion. If this value is greater than the box 101, the difference is
filled in.
Acconto Tassazione Separata
Boxes' description
Boxes Description
112 This box compares value in the Importo Imposta field of the
employee in the Acconto Tassazione Separata section. If this
value is greater than the box 101, the difference is filled in.
121, 122, 124, 126, 127, 131, 132, 133 These boxes are filled in with values from the T5ITW5 table.
123 This box verifies if the Rich.riduz/blocco checkbox in the In

fotype 0483 of the IRPEF section.

Boxes Description
125 This box verifies the code field in theAcconto Addizionale

Comunale section in the Infotype 0483, if field Importo Ac
conto is greater than zero.
128 This box verifies Rich.riduz/blocco checkbox in the Infotype

0483 of the Cedolare Secca Locazioni section.
Interessi per Rateazione
Boxes' description
Boxes Description
141, 142, 143 These boxes are filled in with values from the T5ITW5 table.
These boxes exist only in the CU modello ordinario.
Interessi per Incapienza/Retifica
Boxes' description
Boxes Description
These boxes exist only in the CU modello ordinario.

1.5.2.3.2 Assistenza Fiscale Sospesa
The boxes of this subsection are relevant to taxes not paid due to exceptional events (for example,
earthquakes, floods, and so on).
Boxes' description
Boxes Description
161, 162, 163, 164, 165, 166 These boxes are filled in with values from the T5ITW5 table.
These boxes can be referred to employee and to the spouse, but they are recapped here in one box for every
type of tax.
1.5.2.3.3 Assistenza Fiscale 730/2020 Coniuge
All data in this section have the same meaning of the previous section for the employee (Assistenza Fiscale
730/2020 Dichiarante [page 22]), but are referred to the data of the spouse. Some of the employee's data are
valid also for the spouse so they don’t exist also in this section. This subsection refers to CU modello ordinario.
The CU modello sintetico contains a limited subset of boxes and the relevant two subsections also have a
different name (that refers to those boxes only): ASSISTENZA FISCALE 730/2020 CONIUGE and ACCONTI
2020 CONIUGE.

Boxes' description
Boxes Description
271, 272 If the sum of the deduction (trattenute) is greater than the
sum of the reimbursement (rimborsi), the difference is
281, 282
populated in field 261 (271, 281 etc.). If the sum of the reim
291, 292 bursement is greater, the difference is filled in the field 262
(272, 282 etc.). If there are any difference between the val
ues, no field is filled.
483 infotype and with the values actually paid.
273, 274
283, 284
293, 294 last one that isn't integrative, and one integrative are consid
the field 261 and 262 (271 and 272 etc.). If the value is the
same, the fields 263 and 264 (273 and 274 etc.) are filled. If
there are differences, the value is reported in the right field
263 (273, 283, 293) if it was paid less than expected and 264
(274, 284, 294) if the reimbursement was less than ex
pected).
 Note
Please note that the infotype 0483 to be selected is al
ways the last existing. In case of 483 rettificativo or inte
grativo of types 2 and 3, the last infotype contains the
real amount to be paid or withheld. A special case re
gards integrativo of type 1. In this case, instead, we need
to consider both the original 730-4 and the credits in
730-4 integrativo. Therefore, both fields are considered
to determine if the final amount is a debit or credit. De
pending on this, the report calculates the difference be
tween the debit (if the final amount is a debit) and box
261 (or 271, etc.) or between the credit (if the final
amount is a credit) and box 262 (272 etc.).
275, 285 These boxes verify the CREC1 and CREC2, of infotype Info
type 0483. Priority order: entries of the rettifica type and
date. Integrative is not considered.
301, 306, 311, 321, 322, 324, 326, 327, 331, 332, 333 These boxes are filled with value from the T5ITW5 table
view.

Boxes Description
302, 307, 312 These boxes compare value in the Importo Imposta field of
the employee in the Imposta Sostitutiva Incremento
Produtività section. If this value is greater than the box 101,
the difference is filled in.
These boxes are intended for reporting possible differences

between what was in 730/4 and what was paid or withheld.
Therefore, it is necessary to report the difference between
the relevant amounts in the Infotype 0483 and the corre
sponding boxes.
● The B0302 box is filled by P0483-ISLSC deducted by

B0301 box.
● The B0307 box is filled by P0483-CONTSTC deducted
by B0306 box.
● The B0312 box is filled by P0483-ACTSC deducted by
B0311 box.
323 This box verifies if the Rich.riduz/blocco of the last entry in

the Infotype 0483 , in section IRPEF.
325 This box verifies the code field in Acconto Addizionale

Comunale section in all entries of the Infotype 0483, if field
Importo Acconto is greater than zero.
328 This box verifies if Rich.riduz/blocco checkbox of the last en

try in the Infotype 0483, in the Cedolare Secca Locazioni sec
tion.

1.5.2.4 Oneri Detraibili
In this section, the employer (acting as a withholding agent) must place all the different kinds of expenses,
which are eligible for a tax deduction and that are notified by the employee for the final tax balance done in
December or when the employee has left the company.
Boxes' description
Boxes Description
341, 343, 345, 347, 349, 351 These boxes are filled in with values from the CDONE field, of
T5ITDQ table.
342, 344, 346, 348, 350, 352 These boxes are filled in with values from the accumulated
wage type filled in WTONE field, of T5ITDQ table.
 Note
The T5ITDQ table is read using dates of the report. For
each entry, we fill one pair of fields (341/342 or
343/344 or 345/346 or 347/348 or 349/350 or
351/352).

The different types of expenses are listed in CU instructions Table A and B:

These expenses are handled in the IT0156 at this point:
The expense legal code from CU instructions Table A and B must be placed in CDONE field, of V_T5ITDQ view,
in order to map the legal code to be issued in CU and the internal code used in Infotype 0156.
The CHANGE_T5ITDQ_TABLE is still available, in case you want to use it.
Multimodulo: boxes from 341 until 352 are Multimodulo. In fact, if the six available couples of boxes are not
enough (the kinds of deductions are more than six) another model(s) has(ve) to be created.

1.5.2.5 Detrazioni e Crediti - Dati Fiscali: dati per la
eventuale compilazione della dichiarazione dei
redditi
This section collects all deductions or credits used on behalf of the employee (taxpayer).
Boxes' Description
Boxes Description
361, 362, 363, 364, 365, 366, 367, 368, 369, 370, 371, 372, These boxes are filled in with values from the T5ITW5 table.
373, 374, 376, 377, 378, 379, 380, 383, 384, 385
375 This box is filled with the difference between the amounts in
boxes B0361 and B0374. That is: B0375 = B0361 - B0374
381, 382 These boxes are filled in with values from the
V_T5ITUI_2_CU table.
Credito Bonus IRPF
The boxes in this sub-section are only filled if B0001 or B0002 are filled.
Boxes' Description - Credito Bonus IRPF
Boxes Description
391 If the 392 field is filled, this box is filled with value 1, in any
other case the value is 2.
393 Not supported by SAP. This box can be filled in with values
from the V_T5ITUI_2_CU table view.
394 This box is filled in with values from the T5ITW5 table. But
fills only if the result is less than 0.
395 If boxes 396, 397 and 398 are filled, this box is filled in with
value 1.

Boxes Description
396, 397, 398 These boxes are filled in with values from the T5ITW5 table,
and from the Infotype 0305 - the values are in the Infotype
0305 and not in the payroll.
All entries for the Infotype 0305 of the report period are read
and copied. The preceding explanation is done for each en
try.
Entries in the Infotype 0305 from 1 through 8 are looped.
399 This box is filled in with value from the CODE field of the Info
type 0305.
Trattamento Integrativo
The boxes in this sub-section are only filled if B0001 or B0002 are filled.
Boxes' Description - Trattamento Integrativo
Boxes Description
406 This box is filled in with the value of wage type /D8H main
tained in the Infotype 0305.
407, 408, 409 These boxes are filled in with values from the T5ITW5 table,
and from the Infotype 0305 - the values are in the Infotype
0305 and not in the payroll.
All entries for the Infotype 0305 of the report period are read
and copied. The preceding explanation is done for each en
try.
Entries in the Infotype 0305 from 1 through 8 are looped.
410 This box is filled with the fiscal code of the employee's previ
ous employer. The fiscal code is read in table T77PAYIT_CIA.

Management of heirs' data and multimodulo
is done by verifying the Infotype 0021 and the Subinfotype 0306. The SPERD field defines the percentage that
is paid for the heirs.
Boxes Description
391 This box is filled if at least one of the two boxes B0001 and
B0002 is filled, in which case its value is "1" when the 392
field is filled, otherwise its value is "2".
392, 401 This box is filled in with value from the T5ITW5 table.
400 This box is filled if at least one of the two boxes B0001 and
B0002 is filled, in which case its value is "1" when the 401
field is filled, otherwise its value is "2".
Multimodulo: Also in this case these boxes are “multimodulo” (because in theory the amount in box 376 could
be the sum of incomes earned in different countries and in different years). These data have never been
managed by SAP standard solution. Customer can add new modules using the RPUDUII0 report and the CU
BAdI.

1.5.2.6 Previdenza Complementare - Dati Fiscali: dati per la
eventuale compilazione della dichiarazione dei
redditi
Boxe's description
Boxes Description
411 It reads T5ITP1 table (using the date and field CDFON of
Infotype 0548). If a record is found, the value from CDFON
field in T5ITP1 table is used. If no record is found, and
DTPOC field in Infotype 0548 has a value greater or equal to
01/01/2007, the used value is 3. This field is only filled if
fields 412, 413 or 415 are also filled in.
412, 413, 416, 418, 419, 421, 422, 423 These boxes are filled in with value from the T5TW5 table.

Boxes Description
415 This box reads the last entry (DTPOC field) in the Infotype
0548.
417 These boxes are filled in with value from the T5TW5 table.
If the value is not 0, it reads the IMPFC constant, of T511P

table using the final date of the report as a key. It reports the
accumulated value that exceeds the value in the read con
stant. For example, if the value is accumulated as 100, and
constant 25, the reported value in the field is 75.
420 This box is filled in with value from the T5TW5 table, but it
cumulates NUMBER and not value.
425 This box reads the last entry of the Infotype 0548 . It is read
in the T5ITP1 table, using date and code in the CDFON
field, of the Infotype 0548 for reading. The CFFP field is
used to fill this field.
1.5.2.7 Oneri Deducibili - Dati Fiscali: dati per la eventuale

Boxe's description
Boxes Boxes' description
431, 438, 439, 440, 441, 442, These boxes are filled in with value from the T5ITW5 table.
432, 433, 434, 435, 436, 437 Not supported by SAP. These boxes can be filled in with val

Boxes Boxes' description
443 This box reads:
1. The feature T5ITC is available to define the key for table

T5ITCF.
2. Based on the value returned by the feature (see exam
ple above), the view V_T5ITCF is read.
If an entry of the view matches with the value from the
feature, the view returns two data: a wage type and a fis-
cal code (see next figure). In case no entry matches, the
box of the CU will remain blank.
3. The wage type is searched in all the employee’s payroll
clusters of the relevant year. All the amounts are sum
med up in a total. If the wage type doesn’t exist the total
is zero.
4. If the total calculated is greater than zero then box
B0443 is filled with the fiscal code stored in table. Oth
erwise the box of the CU will remain blank.
Also please note that, in case of more than one fiscal code to
be filled in (because more than one “enti o casse” exists for
that employee), the “multimodulo” management is pro
vided.
The customizing will report all the relevant fiscal codes as in

the example of view V_T5ITCF in case of code 2000.
444 This box is filled in with value from the T5ITW5 table, if the
value is not 0, it fills with X.

1.5.2.8 Altri Dati - Dati Fiscali: dati per la eventuale
Boxes' description
Boxes Description
474, 475, 476
455 These boxes are filled in with values from the T5ITW5 table.
Only in months where the contract is indeterminate.
456 These boxes are filled in with values from the T5ITW5 table.
Only for months where the contract is determined
462, 464 Not supported by SAP. These boxes can be filled in with val
472 This box reads the last entry of the Infotype 0156, if the
APAIM field is greater than 0, it fills with X.
473 This box reads the last entry of the Infotype 0156. It fills with
B, if:
● The DTMIN field is not empty.

● The field 2 of part B is greater than 0.
● The value of the 367 field of part B is greater or equal to
1380.
478 This field works as a flag, and is selected if there's an

amount for wage types maintained for cumulation wage type
INCV in V_T596I or V_T596J. If it does, it's filled with value
1.
479, 480 These boxes are filled only if box 478 is checked (if its value
is 1). Boxes 479 and 480 are filled with values from T5ITW5
table view.

1.5.2.9 Redditi Assoggettati a Ritenuta a Titolo di Imposta
Boxes' description
Boxes Description
481, 482, 483, 485, 487, 488, 491, 492, 496, 497, 498, 499, These boxes are filled with value from the T5ITW5 table.
500, 501
484, 486, 489, 490, 495 Not supported by SAP. These boxes can be filled in with val
1.5.2.10 Compensi Relativi Agli Anni Precedenti
Boxes' description
Boxes Description
511, 512, 513, 514, 515, 516, 519, 520 These boxes are filled in with value from the T5ITW5 table.
for the heirs.
1.5.2.11 Dati Relativi ai Conguagli
Boxes representing amounts in this section can be customized as wage groups in V_T5ITW5 view but, in this
case, the wage type assigned to the box in V_T5ITW5 view is read from the Infotype 0305.
Boxes relevant to these data are all multimodulo, except the totals of incomes. In fact, the employer, acting as
withholding agent (Sostituto d’imposta), can be asked to balance more than one single income coming from
different previous employers. Therefore, CU report generates first module for the first previous employer, the
second module for the second one, and so on. In case of more than one previous employer is not so frequent
but anyway possible.
Boxes' description
Boxes Description
531 This box is filled in with the total modules of the field 538.

Boxes Description
536 If any field between 538 and 566 is filled, the value of the
CODE field, of the Infotype 0305 is filled in this box.
537 If any field between 538 and 566 is filled, this box is filled in
with value 1.
538, 539, 540, 541, 542, 543, 544, 545, 546, 547, 548, 549, These boxes are filled in with the amounts saved in Infotype
550, 552, 554 0305 in the wage type corresponding to the relevant box of
the CU.
In IT 0305, any amount (Q0305-AMT) is linked to a wage

type (Q0305-WGTYP) and the wage type is linked to the CU
box by means of customizing table V_T5ITW5 for part B.
In this way the wage type corresponding to the CU box cus

tomized in table V_T5ITW5 is searched in IT 0305, and, if
found, the corresponding amount is written in the CU box.
551, 553, 561, 562, 563, 564, 565, 566 Not supported by SAP. These boxes can be filled in with val
1.5.2.12 Somme Erogate per Premi di Risultato in Forza di

Contratti Collettivi Aziendali o Territoriali
This section was added in the CU 2017. The name was updated in the CU 2018
Boxe's description
Boxes Description
571 Check IMPDE constant of V_T511P. If it has an amount of

EUR 3000, the value should be 1. If it has an amount of EUR
4000, the value should be 2. This should be taken into ac
count when at least one of the following boxes exist: from
B0572 to B0580.

Boxes Description
594, 595, 596, 597, 598, 599, 600, 601, 611, 612, 615, 616,
617, 618, 619, 620, 631, 632
1.5.2.13 Casi Particolari Operazioni Straordinarie
This subsection exists only in the CU modello ordinario and is not supported in standard.
Should be used to register in rare cases, when the previous employer who did the final balance doesn’t exist
anymore. In these cases there is someone (the insolvency administrator) who must declare these data.
Customer can insert values on these boxes with the V_T5ITUI_2_CU table view.

1.5.3 Dati Relativi al Coniuge e ai Familiari a Carico
Boxes' description
Detra
Percen zione
tuale di de 100% affi
Col Codice fis N. mesi a Minore di tre trazione damento
umn Relazione di parentela cale carico anni spettante figli
1 C If the em If the em - - This

ployee has a ployee has checkbox
spouse, this a spouse is selected
box is filled that is de if the em
in with the pendent (a ployee re
fiscal code carico), this ceives
that comes box is filled 100% of
from the C: in with the the tax de
If the em number of duction for
ployee has a months a child
spouse, this that the who is in
box is filled spouse has foster care
in with value been de with
CFCFMIf the pendent on her/him in
employee the em case of di
has a ployee. vorce or
spouse, this legal sepa
The
box is filled ration. You
months are
in with the define it in
calculated
field, of Info the Info
based on
type 0306 type 0021.
the begin
(subinfo
ning and
type of Info
end date of
type 0021).
Infotype
0021.

Detra
Percen zione
2 F1: If the first D: If the first This box is If the first If the first If the first
child is not child is hand filled in with child is de child is less child repla
handicapped icapped fiscal code pendent (a than 3 years ces the
(PHNDC (PHNDC field, from carico), this (MITAN spouse, this
field) this box of Infotype CFCFM box is filled field, of Info box is filled
is filled in 0306), this field, of Info in with the type 0306), in with
with value X. box is filled in type 0306 number of this box is fil- value C, if
with value X. (subinfo months led in with not, the box
type of Info that the the number is filled in
type 0021). child has of months with from
been de until the child MSDTR
pendent. has com field, of In
pleted 3 fotype
The
years, ac 0306 (the
months are
cording to value is
calculated
the start and truncated).
based on
end date of
the start
the Infotype
and end
0021.
date of In
fotype
0021.

Detra
Percen zione
3 F: If the child If the child is D: If the child This box is If the child If the child is This box is
is not handi not the em is handicap filled in with is depend less than 3 filled in
capped ployee's ped (PHNDC the fiscal ent (a car years based in the
(PHNDC field child, this field, of Info code that ico), this (MITAN MSFTR
of Infotype box is filled type 0306), comes from box is filled field, of Info field, of In
0306), this in with value this box is fil- CFCFM in with the type 0306), fotype
box is filled in X. led in with field, of Info number of this box is fil- 0306 (the
with value X. value X. type 0306 months led in with value is
(subinfo that the the number truncated).
type of Info child has of months
type 0021). been de until the child
pendent. has com
pleted 3
The
years, ac
months are
cording to
calculated
the start and
based on
end date of
the start
the Infotype
and end
0021.
date of In
fotype
0021.

Detra
Percen zione
pendent. has com
pleted 3
The
years, ac
months are
cording to
calculated
the start and
based on
end date of
the start
the Infotype
and end
0021.
date of In
fotype
0021.

Detra
Percen zione
pendeo has com
quent. pleted 3
years, ac
The
cording to
months are
the start and
calculated
end date of
based on
the Infotype
the start
0021.
and end
date of In
fotype
0021.

Detra
Percen zione
(Subinfo that the the number truncated).
pendent. has com
pleted 3
The
years, ac
months are
cording to
calculated
the start and
based on
end date of
the start
the Infotype
and end
0021.
date of In
fotype
0021.

Detra
Percen zione
pendent. has com
pleted 3
The
years, ac
months are
cording to
calculated
the start and
based on
end date of
the start
the Infotype
and end
0021.
date of In
fotype
0021.

Detra
Percen zione
pendent. has com
pleted 3
The
years, ac
months are
cording to
calculated
the start and
based on
end date of
the start
the Infotype
and end
0021.
date of In
fotype
0021.

Detra
Percen zione
pendent. has com
pleted 3
The
years, ac
months are
cording to
calculated
the start and
based on
end date of
the start
the Infotype
and end
0021.
date of In
fotype
0021.

Detra
Percen zione
10 Percentuale If the em

di detrazione ployee has 4
spettante per or more
famiglie nu family
merose members,
this box
must be fil-
led in. If the
UDEFA
field, of Info
type 0156 is
filled in, the
box is calcu
lated in a
truncated
way. If not, it
uses the
higher value
of the
MSDTR
field, (trun
cated).
 Note
Regarding the Detrazione 100% affidamento figli checkbox, SAP has delivered the SAP Note 2411641 ,
which is optional. If you choose not to install it, it won't cause any issue to your CU run. But if you want to
use this field in the CU, you use the V_T5ITUI_2_CU table view (RPUDUII0 report) or the dedicated BAdI.

Related Information
Dati Relativi al Coniuge e ai Familiari a Carico [page 44]
1.5.4 Rimborsi di Beni e Servizi non Soggetti a Tassazione -

Art 51 Tuir
From CU 2017, this section is used to report a new measure introduced in 2016. The data to be reported in this
section is not managed in the standard. From CU 2018, this section has two subsections: Sezione Sostituto
Dichiarante and Sezione Altri Sostituti.
1.5.4.1 Sezione Sostituto Dichiarante
Boxe's description
Boxes Description
701 This box is filled in with the income year, only if the box 704
contains an amount.
704 This box is filled with information that comes from the table
V_T5ITW5.
702, 703, 705, 706 Not supported by SAP. These boxes can be filled in with val

1.5.4.2 Sezione Altri Sostituti
view.
1.5.5 Particolari Tipologie Reddituali
In this section (only for CU ordinaria), employers must enter the "peculiar" (particolari) types of income they
have paid the employee.
Boxes' descriptions
Boxes Description
741, 743, 745 These boxes are not supported by SAP.
742, 744, 746 These boxes are filled in with values that come from
V_T5ITW5 table view.
1.5.6 Compenso Lordo Campione D’italia
Boxes' descriptions
Boxes Description
761, 762, 763, 764, 765, 766 These boxes are filled in with values that come from
1.5.7 Redditti dei Punti da 1 a 5 al Netto dei Compensi di

Campione D'Italia
Boxes' descriptions
Boxes Description
771, 772, 773, 774, 775 These boxes are filled in with values that come from

1.5.8 Dati Previdenziali ed Assistenziali
1.5.8.1 Section 1 - Lavoratori Subordinati
Boxes' description - Sezione 1
Box Description
1 T5ITNB table. The fields used to load this information are

MODMN and INPSC, of Infotype 0154.
2 This box is filled in with value X, if the employee has the INPS
entity.
3 This box is filled in with value X, If the employee doesn't have

the INPS entity.
4 This box is filled in with the cumulation of the wage types. It

uses the customizing from the T5ITW5 table.


7 This box is filled in with value X if all months are reported by

UNIEMENS.
8 It selects the months that are reported by UNIEMENS.
The boxes 7 and 8 are filled depending on the value of the CUDUE constant. Therefore for every month of the
year the CU is related to, the following checks are performed if the value of the CUDUE constant is:
● 0: the existence of payroll cluster is checked

● 1: CU checks for the existence (in PCL1 table – cluster I2) of the Uniemens declaration, regardless if it is
marked as “sent to INPS” or not.
● 2: CU considers as the declarations are sent, those that are marked as “sent to INPS”. It can be done by
using RPUESBI0 report of Uniemens application.

Example
For boxes 4 and 6, supposing that the T5ITW5 table has the following configuration:
Example of T5ITW5 record for section INPS
Section Code Wagetype
PREV. SEZ. 1 0004 /zzz
This box is filled in with the information 0004 /yyy

that comes from the CHECK C. INPS
The resulting box 4 is composed as the sum of wagetype /zzz from the whole year of 2019 and plus the sum
of /yyy from 2020 (until February).
1.5.8.2 Section 2 - INPS Lavoratori Subordinati Gestione

Dipendenti Pubblici
This section is not supported by SAP. The boxes can be filled in with values from the V_T5ITUI_2_CU table
view.
1.5.8.3 Section 3 - INPS Gestione Separata Parasubordinati
Sezione 3
Boxes Description
45 This box is filled in with the cumulation wage types. It uses

the customizing from the T5ITW5 table.



49 It is selected if all months are declared by UNIEMENS.
50 It is selected by the months that are reported by UNIEMENS.

Boxes Description
51 This box is filled in with information from Infotype 0154.

1.5.8.4 Section 4 - INPS Soci Cooperative Artigiane
Section 4
Boxes Description
1.5.8.5 Section 5 - Altri Enti
Section 5
Boxes Description
56, 57, 58, 59 Not supported by SAP. These boxes can be filled in with val
60, 61, 62, 63, 64, 65 This box is filled in with the accumulation of the wage types.
It uses the customizing from the T5ITW5 table.

Dati Assicurativi INAIL
Dati Assicurativi INAIL
Boxes Description

72 This box is filled in with information that comes from the

PATIN field, of Infotype 0659.

BEGDA field, of Infotype 0659.

ENDDA field, of Infotype 0659.

MUNIC field, of V_T77PAYIT_CIA_A table. The search
uses the WERKS and BTRTL fields, of infotype 1.

VIAGG field, of Infotype 0659.
1.5.9 Trattamento di Fine Rapporto (TFR)
The data from this section is multi-modulo, since it’s frequent in case of multiple working periods in the current
year to receive the TFR payment for every different working period. This is relevant especially for re-hiring, but
since SAP does not provide a standard solution, customers can provide these data by means of the correction
table or with their BAdIs.
1.5.9.1 TFR, Altre Indenità e Somme Soggette a Tassazione

Separata
This merged section is represented in the customizing form in V_T5ITUD view as section T, instead of B. In the
wage types grouping customizing V_T5ITW5 view table, these sections is represented as TFR.

TFR boxes' description
Boxes description
801, 803, 804, 805, 809, 810, 811, 812, 813 These boxes are filled in with information that comes from
the customizing of the T5ITW5 table.
customizing of the T5ITW5 table.
It is only filled in if the box 801 is completed.
808 This box is filled in only for heirs. The value comes from the
SETFR, of Infotype 0306.
In case of deceased employees, the boxes 801 to 813 (except box 808 that is filled only for heirs) are removed
from the employee’s declaration and repeated in the heirs’ declaration.
1.5.9.2 Dati Relativi al Rapporto di Lavoro
All the boxes from this subsection are available in the CU modello ordinario only.
Boxes' description
Boxes Description
814 This box is filled in with the date of the seniority of the em
ployee. This date is composed by the DTCOA field, of Info
type 0155. If this value is empty, it uses the hire date of the
employee.

Boxes Description
815 Data of the end fund. This box uses the termination date of
the employee, if it occurred before the end of the income of
the report. If the employee is still working in the company
until that date, this box uses the final date of the /TA5 wage
type. If there is no date in this wage type, it uses the final
date of the /TAE wage type.
818 In case the employee has a fix term contract, this box is filled
in with value 1.
For the box 818, in the standard, the contract type is determined following the steps:
1. Get Infotype 0154 for a given WPBP split;

2. Check field CONTR;
3. If CONTR is D, then contract is fix-ended;

○ If CONTR is blank, the report tries another level of configuration:
4. Read Infotype 0001 and use employee type and status (PERSK and PERSG) to get key TRFKZ from table
T503;
5. Uses TRFKZ key, plus Infotype 0008 fields collective contract type and contract area (TRFAR and TRFGB),
together with field contract type (CTTYPE) from Infotype 0016. To read V_T5ITNG table,toget the contract
type;

1.5.9.3 Indennità Equipollenti ed Altre Indennità
Boxes' description
Boxes Description
820 This box is filled in with the customizing of the T5ITW5 ta
ble.
821, 822, 823, 824, 828, 829, 830, 831, 832, 833 This box is filled in with the customizing of the T5ITW5 ta
ble.
Deleted if box 820 doesn't exist.
ble.
Deleted if box 820 and 824 don't exist.
826, 827 Not supported by SAP. These boxes can be filled in with val

Boxes Description
from the V_T5ITUI_2_CU table view. Deleted in case the
boxes 820 doesn't exist.
1.5.9.4 TFR ed Altre Indennità Maturate al 31/12/2000
Boxe's description
Boxes Description
835 This box is filled in with number of months and years before
2001.
836, 837, 838, 839, 840, 844, 845, 846, 847, 848, 851, 852 These boxes are filled in with the customizing of the
T5ITW5 table.
841 These boxes are filled in with the customizing of the

T5ITW5 table.
Deleted if the box 840 doesn't exist.
849 This box is filled in with the value of box 869 multiplied for
the (839 / (861 + 839)).
ble. It is deleted if the box 849 doesn't exist.
1.5.9.5 TFR ed Altre Indennità Maturate dal 1/1/2001
Boxe's description
Boxes Description
854, 855, 856, 857, 858, 859, 860, 861, 866, 867, 868, 871, These boxes are filled in with the customizing of the
872 T5ITW5 table.

Boxes Description

T5ITW5 table.
It is deleted if the box 863 doesn't exist.

T5ITW5 table.

T5ITW5 table.

T5ITW5 table.
1.5.9.6 Prestazioni in Forma di Capitale Maturate

31/12/2000
view.
1.5.9.7 Prestazioni in Forma di Capitale Maturate dal

1/1/2001 al 31/12/2006
view.
1.5.9.8 Dati Riepilogativi

Boxes' description
Boxes Description
47, 48, 49, 50, 51, 52, 53, 54, 55, 894, 896, 897, 898, 899, These boxes are filled in with the customizing of the
900, 901, 902, 903, 904, 905, 906, 907, 908, 909, 910, 911 T51TW5 table.
896 This box is filled in with value A if the box 896 is the same as
the 2006 aliquot, and the actual percentage is greater than
2006. In any other case this box is filled in with value B.
897 This box is filled in with value A if the box 897 is the same as
the 2006 percentage, and the actual aliquot is greater than
2006. In any other case this box is filled in with value B.
914 This box is filled in with the fiscal code of the employee, for
heirs.
915 This box is filled in with the fiscal code of the heir, for heirs.
916 This box is filled with the aliquot of the SETFR field, of Info
type 0306. If it is empty, it uses the value of the SPERD field,
of Intoyppe 0306.
920 This box is filled with the customizing of the T51TW5 table.
1.5.10 Annotations for CU Modello Ordinario
Annotations boxes in the CU modello ordinario are imported from the CU modello sintetico. In the Annotations
section, only the annotation codes are imported from CU and placed in the annotations boxes.
These annotations must have been customized in T5ITAN table with the respective official 2-character code in
field ANOT. The annotation ‘*B’ is converted to ‘AB’ for heirs.
 Note
When forcing annotations in the input table, we don’t recommend inputting the annotation boxes from the
CU modello ordinario.
To force the annotations:
1. You have to input the annotations from the CU modello sintetico and, then;
2. The CU report generates the CU modello ordinario boxes.
 Note
It's not allowed to use special characters from ABAP to create annotation variables.

1.5.11 Section G
This section is used to define custom wagegroups in T5ITW5 table in order to be used as variables for
annotations.
For more information, see the Annotations (Annotazioni) topic in the SAP Implementation Guide - Certificazione
Unica 2021 ().
1.5.12 Section P - Pignoramenti
SAP does not support the section P. This section is managed by the CHANGE_VARTAB BAdI method.
Alternatively, data can be input as wagegroups of the T5ITW5 table. Boxes P101 to P104 refer to a single
garnishment. Boxes P105 to P108 can be used for a second garnishment. In case of more garnishments,
modulo keys must be used to add new records. Each modulo can handle up to two different garnishments.

Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Important Disclaimers and Legal Information INTERNAL 67
www.sap.com/contactsap
© 2020 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

SAP User Guide Certificazione Unica 2021

Uploaded by

Document Information

Original Description:

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

SAP User Guide Certificazione Unica 2021

Uploaded by

Copyright:

Available Formats

User Guide | INTERNAL

SAP User Guide - Certificazione Unica 2021

THE BEST RUN

1 SAP User Guide - Certificazione Unica 2021. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

SAP User Guide - Certificazione Unica 2021

The CU Modello Ordinario is composed of the following sections:

SAP User Guide - Certificazione Unica 2021

In 2021, the affected areas are the following:

● Added Boxes in the CU Form

Section Added Boxes Link to Section

Dati Anagrafici ○ 11 Dati Relativi al Dipendente, Pensio­

Detrazioni e Crediti ○ 368 Detrazioni e Crediti - Dati Fiscali: dati

Altri Dati ○ 475 Altri Dati - Dati Fiscali: dati per la

Dati Previdenziali ed Assistenziali ○ 26 Section 2 - INPS Lavoratori Subordi­

SAP User Guide - Certificazione Unica 2021

Pignoramenti ○ 22 Section P - Pignoramenti [page 66]

● Added Sections in the CU Form

Section Link to Section

● Renumbered Boxes in the CU Form

Section Boxes in CU 2021 Boxes in CU 2020 Link to Section

Detrazioni e Crediti ○ 369 ○ 368 Detrazioni e Crediti - Dati

○ 371 ○ 370 compilazione della dichiara­

SAP User Guide - Certificazione Unica 2021

SAP User Guide - Certificazione Unica 2021

tenziali [page 58]

● Deleted Boxes in the CU Form

Section Deleted Boxes Link to Section

Assistenza Fiscale 730/2020 Dichiar­ ○ 53 Assistenza Fiscale 730/2020 Dichiar­

Detrazioni e Crediti ○ 384 Detrazioni e Crediti - Dati Fiscali: dati

○ 386 chiarazione dei redditi [page 34]

Annotations for CU Modello Ordinario ○ 54 Annotations for CU Modello Ordinario

1.3 Process Overview

● Certificazione Unica (CU)

SAP User Guide - Certificazione Unica 2021

2 Then, runs the CUR (RPC_PAYIT_CUR) or CUP (RPC_PAYIT_CUP) report,

The fields that are saved in the section R are:

The general workflow is described in the following images.

SAP User Guide - Certificazione Unica 2021

SAP User Guide - Certificazione Unica 2021

SAP User Guide - Certificazione Unica 2021

● CU: SAP Note 2976227

1.4 Company Transfer

The possible behaviors are:

SAP User Guide - Certificazione Unica 2021

For 730-4 boxes, the following logic is applied:

1.5 Sections and Boxes (Caselle)

1.5.1 Dati Anagrafici

SAP User Guide - Certificazione Unica 2021

This subsection is the first part of the section A of the CU declaration.

Section A boxes's description

1, 2 These boxes are filled in with information from the

3, 4, 5, 6, 7, 8, 9, 10, 11 These boxes use information from the

1.5.1.2 Dati Relativi al Dipendente, Pensionato o altro

This section is filled with Master Data information.

Section A boxes's description

SAP User Guide - Certificazione Unica 2021

8 This box is filled only for heirs. The value is always Z.

20 First, this box loads information from Infotype 0156, that is

21 First, this box loads information from Infotype 0156, that is

22 First, this box loads information from Infotype 0156, that is

23 First, this box loads information from Infotype 0156, that is

24 First, this box loads information from Infotype 0156, that is

25 First, this box loads information from Infotype 0156, that is

Dati Anagrafici ○ 11 Dati Relativi al Dipendente, Pensio

Dati Previdenziali ed Assistenziali ○ 26 Section 2 - INPS Lavoratori Subordi

○ 371 ○ 370 compilazione della dichiara

Assistenza Fiscale 730/2020 Dichiar ○ 53 Assistenza Fiscale 730/2020 Dichiar

The hire date is determined by RP_HIRE_FIRE function mod

In case of company transfer: if the cedente has not com

123 This box verifies if the Rich.riduz/blocco checkbox in the In