The Hidden Clocks: Why Agreements and Payments Can Fall Into Different Italian Sunshine Reporting Periods
Author
Ned Mumtaz is an international transparency reporting expert with extensive experience producing accurate and compliant transparency reports for over 150 pharmaceutical companies globally.
He has held leadership positions at Pfizer and Otsuka, distinguishing himself by ensuring high standards of accuracy, reliability, and regulatory compliance in reporting processes. He is recognized in the industry for his contributions to the development of global transparency models and for promoting operational best practices in compliance.
Cerchi supporto per la compliance al Sunshine Act?
Hai domande pratiche?
Dai un’occhiata alla nostra sezione Domande Frequenti per risposte chiare su scadenze, obblighi e strategie.
Imagine a doctor is engaged in May to speak at an event on 5 June. The doctor invoices on 20 June, and the payment is made on 25 August. The activity, the agreement and the monetary transfer have now occurred at three different points in time, and the Italian Sunshine Act does not necessarily treat them as a single reporting event.
The speaking or consultancy agreement may need to be captured according to the semester in which the relationship was established, while the monetary transfer may fall into the semester in which the payment was made. The result is not simply a payment-timing problem. It is a reconciliation problem involving multiple legally relevant dates.
Most Italian life science and healthcare compliance teams are focused on the right things: understanding which interactions qualify, building data collection processes, and learning how to generate the XML file. What far fewer are modelling is the relationship between when activities happen and when they become reportable, and the two are rarely the same date.
Contractual payment terms and invoice-processing timelines vary considerably. Italian commercial law generally uses 30 days as the default period, although longer terms may be expressly agreed in business-to-business contracts, subject to safeguards against grossly unfair terms. A period of up to 60 days applies in certain transactions involving public healthcare entities. Administrative delays can extend the gap between an activity and the eventual payment even further. This creates a structural tension with transparency reporting that, if not planned for, may cause problems during the first reporting cycles.
The Act Creates More Than One Timing Trigger
For monetary transfers, Law No. 62/2022 requires the communication to state the date on which the transfer was made. For conventions and agreements, it instead requires the relevant reference period. The law further provides that transfers made and agreements or conventions established during each semester must be communicated by the end of the following semester. This means that an agreement and its related payment may carry different legally relevant dates and may fall within different reporting periods. (Law No. 62/2022, Article 3(4)(c) and Article 3(5)).
This distinction matters. A consultancy agreement established in June and paid in August may generate reporting information connected with two different semesters. Companies therefore need to track more than the invoice or payment date. The final technical model and authoritative implementation guidance will determine whether a particular engagement is represented through separate linked records or through an agreement record containing the contractual remuneration.
Consider a scenario in which the formal commencement notice is published in September. Article 3 reporting obligations apply from the second semester following the semester in progress when the notice is published. In that scenario, the first applicable reporting period would ordinarily begin on 1 July of the following year. Transfers made and agreements established before and after that date would therefore need to be separated carefully. (Law No. 62/2022, Article 9(1)).
A consultancy agreement established in June may fall within the first semester, while the related fee paid in August falls within the second. Similarly, a congress registration, travel arrangement or hospitality benefit may have its own relevant transfer date, generally connected to when the benefit is conferred on the recipient, subject to the applicable technical rules. The correct treatment therefore depends on the nature of the record, not simply on the date of the underlying event.
For companies with high volumes of HCP interactions, this is not a minor rounding error.
It is a systematic forecasting problem because the reporting semester may depend on payment dates that compliance teams cannot predict with certainty. It also creates significant data-classification and reconciliation challenges.
Payments Related to Pre-Period Activities
A further issue arises where an activity or agreement predates the first applicable reporting period, but the corresponding payment is made after reporting obligations begin. Article 3 applies to transfers made and agreements or conventions established during each reporting semester. On that wording, a monetary transfer made during an applicable semester may need to be assessed separately from the date on which the underlying activity occurred or the agreement was signed. (Law No. 62/2022, Article 3(4)(c) and Article 3(5)).
For example, an event may take place in November and the related invoice may not be paid until February. Whether the record involves only a later monetary transfer or also a separately reportable agreement will depend on the contractual structure and the applicable technical requirements. Until this point is addressed through authoritative implementation materials, companies should not automatically exclude a payment merely because the underlying activity predates the applicable reporting period. They should document the treatment adopted and the legal basis for it.
Building a Practical Reporting Calendar
The solution is not simply to change payment terms, as that could create separate commercial and contractual problems. The solution is to build a reporting calendar that works backwards from the filing deadline and accounts for payment lag explicitly.
This means identifying, for each transfer-of-value category, including consulting fees, educational grants, hospitality and equipment loans, which dates are legally and operationally relevant. Depending on the transaction, those may include the agreement date, service period, benefit date, invoice date, accounting-posting date and actual transfer date.
It also means communicating clearly with your finance team. Transparency reporting is not just a compliance function’s problem. The people who process payments need to understand that the date on which a transfer is actually made can affect the reporting semester, and that this date must be recorded accurately in finance systems. Compliance teams should therefore be informed when invoices are delayed, rejected, reprocessed or carried across a semester boundary.
Companies that build this awareness into their internal processes before the first reporting period will be better placed to manage the semester-based collection process and submit the relevant communications by the end of the following semester. Those that discover the timing problem only in retrospect may need to correct records, investigate apparent discrepancies and explain why related activities appear in different reporting periods.
The clock on Italian Sunshine Reporting was always ticking. The hidden clocks—the ones tracking the gaps between the activity, the agreement and the eventual transfer—have been running just as long. Many companies have not yet aligned them.
Want to assess your organisation’s readiness for Italian Sunshine Reporting?
Whether you are preparing for your first disclosure or looking to streamline an existing process, choosing the right transparency reporting partner and getting ongoing expert advice can help you map your data landscape, close compliance gaps, and generate Ministry-compliant XML files with confidence.
→ Attend our upcoming Italian Sunshine Reporting events, online or in person to work directly with us and learn to build structured, audit-ready Italian Sunshine transparency processes.
→ Get expert advice tailored to your situation by asking specific questions, whether that is about payments relating to earlier activities, field team workflows, or cross-border engagements.
→ Not sure where to start? Explore our resources and blogs to understand what Italian Sunshine Reporting means specifically for your organisation.
Imagine a doctor is engaged in May to speak at an event on 5 June. The doctor invoices on 20 June, and the payment is made on 25 August. The activity, the agreement and the monetary transfer have now occurred at three different points in time, and the Italian Sunshine Act does not necessarily treat them as a single reporting event.
The speaking or consultancy agreement may need to be captured according to the semester in which the relationship was established, while the monetary transfer may fall into the semester in which the payment was made. The result is not simply a payment-timing problem. It is a reconciliation problem involving multiple legally relevant dates.
Most Italian life science and healthcare compliance teams are focused on the right things: understanding which interactions qualify, building data collection processes, and learning how to generate the XML file. What far fewer are modelling is the relationship between when activities happen and when they become reportable, and the two are rarely the same date.
Contractual payment terms and invoice-processing timelines vary considerably. Italian commercial law generally uses 30 days as the default period, although longer terms may be expressly agreed in business-to-business contracts, subject to safeguards against grossly unfair terms. A period of up to 60 days applies in certain transactions involving public healthcare entities. Administrative delays can extend the gap between an activity and the eventual payment even further. This creates a structural tension with transparency reporting that, if not planned for, may cause problems during the first reporting cycles.
The Act Creates More Than One Timing Trigger
For monetary transfers, Law No. 62/2022 requires the communication to state the date on which the transfer was made. For conventions and agreements, it instead requires the relevant reference period. The law further provides that transfers made and agreements or conventions established during each semester must be communicated by the end of the following semester. This means that an agreement and its related payment may carry different legally relevant dates and may fall within different reporting periods. (Law No. 62/2022, Article 3(4)(c) and Article 3(5)).
This distinction matters. A consultancy agreement established in June and paid in August may generate reporting information connected with two different semesters. Companies therefore need to track more than the invoice or payment date. The final technical model and authoritative implementation guidance will determine whether a particular engagement is represented through separate linked records or through an agreement record containing the contractual remuneration.
Consider a scenario in which the formal commencement notice is published in September. Article 3 reporting obligations apply from the second semester following the semester in progress when the notice is published. In that scenario, the first applicable reporting period would ordinarily begin on 1 July of the following year. Transfers made and agreements established before and after that date would therefore need to be separated carefully. (Law No. 62/2022, Article 9(1)).
A consultancy agreement established in June may fall within the first semester, while the related fee paid in August falls within the second. Similarly, a congress registration, travel arrangement or hospitality benefit may have its own relevant transfer date, generally connected to when the benefit is conferred on the recipient, subject to the applicable technical rules. The correct treatment therefore depends on the nature of the record, not simply on the date of the underlying event.
For companies with high volumes of HCP interactions, this is not a minor rounding error.
It is a systematic forecasting problem because the reporting semester may depend on payment dates that compliance teams cannot predict with certainty. It also creates significant data-classification and reconciliation challenges.
Payments Related to Pre-Period Activities
A further issue arises where an activity or agreement predates the first applicable reporting period, but the corresponding payment is made after reporting obligations begin. Article 3 applies to transfers made and agreements or conventions established during each reporting semester. On that wording, a monetary transfer made during an applicable semester may need to be assessed separately from the date on which the underlying activity occurred or the agreement was signed. (Law No. 62/2022, Article 3(4)(c) and Article 3(5)).
For example, an event may take place in November and the related invoice may not be paid until February. Whether the record involves only a later monetary transfer or also a separately reportable agreement will depend on the contractual structure and the applicable technical requirements. Until this point is addressed through authoritative implementation materials, companies should not automatically exclude a payment merely because the underlying activity predates the applicable reporting period. They should document the treatment adopted and the legal basis for it.
Building a Practical Reporting Calendar
The solution is not simply to change payment terms, as that could create separate commercial and contractual problems. The solution is to build a reporting calendar that works backwards from the filing deadline and accounts for payment lag explicitly.
This means identifying, for each transfer-of-value category, including consulting fees, educational grants, hospitality and equipment loans, which dates are legally and operationally relevant. Depending on the transaction, those may include the agreement date, service period, benefit date, invoice date, accounting-posting date and actual transfer date.
It also means communicating clearly with your finance team. Transparency reporting is not just a compliance function’s problem. The people who process payments need to understand that the date on which a transfer is actually made can affect the reporting semester, and that this date must be recorded accurately in finance systems. Compliance teams should therefore be informed when invoices are delayed, rejected, reprocessed or carried across a semester boundary.
Companies that build this awareness into their internal processes before the first reporting period will be better placed to manage the semester-based collection process and submit the relevant communications by the end of the following semester. Those that discover the timing problem only in retrospect may need to correct records, investigate apparent discrepancies and explain why related activities appear in different reporting periods.
The clock on Italian Sunshine Reporting was always ticking. The hidden clocks—the ones tracking the gaps between the activity, the agreement and the eventual transfer—have been running just as long. Many companies have not yet aligned them.
Want to assess your organisation’s readiness for Italian Sunshine Reporting?
Whether you are preparing for your first disclosure or looking to streamline an existing process, choosing the right transparency reporting partner and getting ongoing expert advice can help you map your data landscape, close compliance gaps, and generate Ministry-compliant XML files with confidence.
→ Attend our upcoming Italian Sunshine Reporting events, online or in person to work directly with us and learn to build structured, audit-ready Italian Sunshine transparency processes.
→ Get expert advice tailored to your situation by asking specific questions, whether that is about payments relating to earlier activities, field team workflows, or cross-border engagements.
→ Not sure where to start? Explore our resources and blogs to understand what Italian Sunshine Reporting means specifically for your organisation.
Author
Ned Mumtaz is an international transparency reporting expert with extensive experience producing accurate and compliant transparency reports for over 150 pharmaceutical companies globally.
He has held leadership positions at Pfizer and Otsuka, distinguishing himself by ensuring high standards of accuracy, reliability, and regulatory compliance in reporting processes. He is recognized in the industry for his contributions to the development of global transparency models and for promoting operational best practices in compliance.
Recent Blogs
-
Gli orologi nascosti: perché accordi e pagamenti possono ricadere in periodi diversi ai fini della rendicontazione Sunshine in Italia
-
Perché il transparency reporting richiede una governance interfunzionale
-
La Legge italiana sul Sunshine Act: cosa devono sapere le aziende di dispositivi medici prima della prima comunicazione
Cerchi supporto per la compliance al Sunshine Act?
Hai domande pratiche?
Dai un’occhiata alla nostra sezione Domande Frequenti per risposte chiare su scadenze, obblighi e strategie.