Glossary - Revision history

Cso: /* F */

2026-09-08T13:25:15Z

← Older revision		Revision as of 13:25, 8 September 2026
Line 205:		Line 205:
	<div class="mw-collapsible-content">		<div class="mw-collapsible-content">
	:In the '''eFile''' context, feedback is the official response sent by the regulator after a report has been transmitted, indicating its processing status (e.g. accepted, compliant, or rejected).		:In the '''eFile''' context, feedback is the official response sent by the regulator after a report has been transmitted, indicating its processing status (e.g. accepted, compliant, or rejected).
	:It is available to [[EndUser\|users]] via the [[TransmissionFollowUp\|Transmission Follow‑up]] module or in the [[Sending Service\|Sending Service]] and allows them to verify whether the filing has been correctly received and validated by the authority.		:It is available to [[#EndUser\|users]] via the [[#TransmissionFollowUp\|Transmission Follow‑up]] module or in the [[Sending Service\|Sending Service]] and allows them to verify whether the filing has been correctly received and validated by the authority.
	</div>		</div>
	</div>		</div>

Cso: /* F */

2026-09-08T13:23:38Z

← Older revision		Revision as of 13:23, 8 September 2026
Line 205:		Line 205:
	<div class="mw-collapsible-content">		<div class="mw-collapsible-content">
	:In the '''eFile''' context, feedback is the official response sent by the regulator after a report has been transmitted, indicating its processing status (e.g. accepted, compliant, or rejected).		:In the '''eFile''' context, feedback is the official response sent by the regulator after a report has been transmitted, indicating its processing status (e.g. accepted, compliant, or rejected).
	:It is available to [[EndUser\|users]] via the [[~~EndUser~~\|Transmission Follow‑up]] module or in the [[Sending Service\|Sending Service]] and allows them to verify whether the filing has been correctly received and validated by the authority.		:It is available to [[EndUser\|users]] via the [[TransmissionFollowUp\|Transmission Follow‑up]] module or in the [[Sending Service\|Sending Service]] and allows them to verify whether the filing has been correctly received and validated by the authority.
	</div>		</div>
	</div>		</div>

Cso: /* F */

2026-09-08T13:22:33Z

← Older revision		Revision as of 13:22, 8 September 2026
Line 205:		Line 205:
	<div class="mw-collapsible-content">		<div class="mw-collapsible-content">
	:In the '''eFile''' context, feedback is the official response sent by the regulator after a report has been transmitted, indicating its processing status (e.g. accepted, compliant, or rejected).		:In the '''eFile''' context, feedback is the official response sent by the regulator after a report has been transmitted, indicating its processing status (e.g. accepted, compliant, or rejected).
	:It is ~~made~~ available to [[EndUser\|users]] via the [[EndUser\|Transmission Follow‑up]] module and allows them to verify whether the filing has been correctly received and validated by the authority.		:It is available to [[EndUser\|users]] via the [[EndUser\|Transmission Follow‑up]] module or in the [[Sending Service\|Sending Service]] and allows them to verify whether the filing has been correctly received and validated by the authority.
	</div>		</div>
	</div>		</div>

Cso: /* S */

2026-09-08T13:13:30Z

← Older revision		Revision as of 13:13, 8 September 2026
Line 253:		Line 253:

	:The '''Sending Service''' is our [[Sending_Service_home\|solution for the automatic transmission ]] of reports and documents to the authorities, by a simple deposit of files in a designated directory.		:The '''Sending Service''' is our [[Sending_Service_home\|solution for the automatic transmission ]] of reports and documents to the authorities, by a simple deposit of files in a designated directory.
	:It is particularly interesting '''for bulk filing.'''		:This is a machine-to-machine tool, particularly interesting '''for bulk filing.'''
	</div>		</div>
	</div>		</div>

Cso: /* E */

2026-09-08T13:11:44Z

← Older revision		Revision as of 13:11, 8 September 2026
Line 169:		Line 169:
	:It supports report generation, manual or automated transmission, validation controls, and status follow‑up with authorities.		:It supports report generation, manual or automated transmission, validation controls, and status follow‑up with authorities.
	:The solution centralises [[Transmission_Module\|filing activities]] , [[UCITS_Cross-Border_Notifications\|notifications]], and auditability across multiple regulatory reporting use cases.		:The solution centralises [[Transmission_Module\|filing activities]] , [[UCITS_Cross-Border_Notifications\|notifications]], and auditability across multiple regulatory reporting use cases.
	~~: On eFile there is a dedicated module [[UCITS_Cross-Border_Notifications\|UCITS Cross-border Notification]]~~
	</div>		</div>
	</div>		</div>

Cso: /* S */

2026-07-06T07:20:03Z

← Older revision		Revision as of 07:20, 6 July 2026
Line 254:		Line 254:

	:The '''Sending Service''' is our [[Sending_Service_home\|solution for the automatic transmission ]] of reports and documents to the authorities, by a simple deposit of files in a designated directory.		:The '''Sending Service''' is our [[Sending_Service_home\|solution for the automatic transmission ]] of reports and documents to the authorities, by a simple deposit of files in a designated directory.
	:It is particularly interesting '''for ~~sending many documents~~.'''		:It is particularly interesting '''for bulk filing.'''
	</div>		</div>
	</div>		</div>

Cso: /* S */

2026-04-15T08:11:52Z

← Older revision		Revision as of 08:11, 15 April 2026
Line 263:		Line 263:
	<div class="mw-collapsible-content">		<div class="mw-collapsible-content">

	In eFile, a ''Sending Type'' defines how a report or document is technically transmitted to the authority, which sub-channel is used.		:In eFile, a ''Sending Type'' defines how a report or document is technically transmitted to the authority, which sub-channel is used.
			:By importing a file in the [[#TransmissionModule \| Transmission module]] the ''Sending Type'' is generally automatically selected by our tool.
	</div>		</div>
	</div>		</div>

Cso: /* S */

2026-04-15T08:09:39Z

← Older revision		Revision as of 08:09, 15 April 2026
Line 255:		Line 255:
	:The '''Sending Service''' is our [[Sending_Service_home\|solution for the automatic transmission ]] of reports and documents to the authorities, by a simple deposit of files in a designated directory.		:The '''Sending Service''' is our [[Sending_Service_home\|solution for the automatic transmission ]] of reports and documents to the authorities, by a simple deposit of files in a designated directory.
	:It is particularly interesting '''for sending many documents.'''		:It is particularly interesting '''for sending many documents.'''
			</div>
			</div>

			<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
			<span id=SendingType></span>
			<div style="font-weight:bold;line-height:2.5;">Sending Type</div>
			<div class="mw-collapsible-content">

			In eFile, a ''Sending Type'' defines how a report or document is technically transmitted to the authority, which sub-channel is used.
	</div>		</div>
	</div>		</div>

Cso: /* R */

2026-04-15T07:57:08Z

← Older revision		Revision as of 07:57, 15 April 2026
Line 232:		Line 232:
	:The '''Report Generation''' module in '''eFile''' allows users to prepare regulatory reports directly within the platform by entering required data.		:The '''Report Generation''' module in '''eFile''' allows users to prepare regulatory reports directly within the platform by entering required data.
	:It performs controls such as mandatory field and data‑consistency [[ReportGeneration\|to ensure reports comply]] with authority requirements before submission.		:It performs controls such as mandatory field and data‑consistency [[ReportGeneration\|to ensure reports comply]] with authority requirements before submission.
			: More details on [[ReportGeneration \| ReportGeneration Wiki page]]
	</div>		</div>
	</div>		</div>

Cso: /* F */

2026-04-15T07:55:19Z

← Older revision		Revision as of 07:55, 15 April 2026
Line 189:		Line 189:
	<div class="mw-collapsible-content">		<div class="mw-collapsible-content">
	:FATCA (Foreign Account Tax Compliance Act) is a US law requiring foreign financial institutions, including those in Luxembourg, to report information about financial accounts held by U.S. persons to local tax authorities ( [[#ACD\|ACD]] - Administration des contributions directes). The ACD then automatically exchanges this data with the US IRS to prevent tax evasion.		:FATCA (Foreign Account Tax Compliance Act) is a US law requiring foreign financial institutions, including those in Luxembourg, to report information about financial accounts held by U.S. persons to local tax authorities ( [[#ACD\|ACD]] - Administration des contributions directes). The ACD then automatically exchanges this data with the US IRS to prevent tax evasion.
			</div>
			</div>

			<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
			<span id=FDF></span>
			<div style="font-weight:bold;line-height:2.5;">FDF form</div>
			<div class="mw-collapsible-content">
			:Fundamental Data Form. To be filled in to ask creation or changes on fund's tree information in e-File’s referential
			:More information can be found on: [[E-file_Static_Data_Management#How_to_use_FSQ_IDs_in_the_Fundamental_Data_Form_(FDF) \| How to use the FDF form]]
	</div>		</div>
	</div>		</div>