E-fileWiki - Recent changes [en]

E-file Administration

Cso — Thu, 21 May 2026 09:58:55 GMT

Groups' management

← Older revision		Revision as of 09:58, 21 May 2026
Line 1,351:		Line 1,351:
	\| CSSF		\| CSSF
	\| SFDR reporting		\| SFDR reporting
	\| KS		\| S3
	\|- style="vertical-align:bottom; background-color:#CAEDFB;"		\|- style="vertical-align:bottom; background-color:#CAEDFB;"
	\| Investment Funds		\| Investment Funds
Line 1,358:		Line 1,358:
	\| CSSF		\| CSSF
	\| SFDR reporting		\| SFDR reporting
	\| KS		\| S3
	\|- style="vertical-align:bottom;"		\|- style="vertical-align:bottom;"
	\| Investment Funds		\| Investment Funds

Cso — Thu, 21 May 2026 09:58:05 GMT

← Older revision		Revision as of 09:58, 21 May 2026
Line 1,591:		Line 1,591:
	\| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) F: Pension Fund		\| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) F: Pension Fund
	\| CSSF		\| CSSF
	\| KS		\| S3
	\| no		\| no
	\| SFDR Reporting		\| SFDR Reporting
Line 1,601:		Line 1,601:
	\| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) F: Pension Fund		\| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) F: Pension Fund
	\| CSSF		\| CSSF
	\| KS		\| S3
	\| no		\| no
	\| SFDR Reporting		\| SFDR Reporting

Cso — Thu, 21 May 2026 09:55:13 GMT

← Older revision		Revision as of 09:55, 21 May 2026
Line 1,046:		Line 1,046:
	\| self-assessment questionnaire PDAOFI		\| self-assessment questionnaire PDAOFI
	\| <span style="color: #868686"> <small>''88-PDAOFI reporting''</small/> </span>		\| <span style="color: #868686"> <small>''88-PDAOFI reporting''</small/> </span>
			\|
			\|-
			\| reportingSFDR.state=up
			\| ReportingDiffusion/SFDR
			\| <small>SFDR Reporting</small/>
			\| Sustainable Finance Disclosure Regulation
			\| <span style="color: #868686"> <small>''87-SFDR reporting''</small/> </span>
	\|}		\|}

Cso — Wed, 06 May 2026 15:08:53 GMT

Cso uploaded a new version of File:E-fileLuxtrustCertificateProcess.mp4 Without the 2 last minutes

New page

== Summary ==
Video tutorial

Cso — Tue, 05 May 2026 12:31:20 GMT

* keystore system, Luxtrust certificate, SSL security

← Older revision		Revision as of 12:31, 5 May 2026
Line 1,887:		Line 1,887:
	<div class="mw-collapsible-content">		<div class="mw-collapsible-content">

	You can find a video tutorial <b> <u>[[Media:e-fileLuxtrustCertificateProcess.mp4\| here]]</u> which summarises the below process</b>		You can find a video tutorial <b> <u>[[Media:E-fileLuxtrustCertificateProcess.mp4\| here]]</u> which summarises the below process</b>

	Certain reporting files transmitted to the supervisory authorities must be encrypted.<br>		Certain reporting files transmitted to the supervisory authorities must be encrypted.<br>

Cso — Tue, 05 May 2026 12:29:53 GMT

New page

== Summary ==
Video tutorial

Cso — Tue, 05 May 2026 12:27:32 GMT

Security's management

← Older revision		Revision as of 12:27, 5 May 2026
Line 1,887:		Line 1,887:
	<div class="mw-collapsible-content">		<div class="mw-collapsible-content">

			You can find a video tutorial <b> <u>[[Media:e-fileLuxtrustCertificateProcess.mp4\| here]]</u> which summarises the below process</b>

	Certain reporting files transmitted to the supervisory authorities must be encrypted.<br>		Certain reporting files transmitted to the supervisory authorities must be encrypted.<br>

Cso — Mon, 04 May 2026 09:19:09 GMT

Certificate Update

← Older revision		Revision as of 09:19, 4 May 2026
Line 839:		Line 839:
	= Certificate Update =		= Certificate Update =

	Once your Luxtrust certificate is activate in E-file, you need to replace de new keystore in the sending service.		Once your Luxtrust certificate is activate in E-file, you need to replace the new keystore in the sending service.

	If you have followed the renewal process, the '''updated keystore should have the same password''' as the old one <br>		If you have followed the renewal process, the '''updated keystore should have the same password''' as the old one <br>
	In this case you can use a simplified process by '''<u>simply ~~replace~~ the keystore:</u>'''		In this case you can use a simplified process by '''<u>simply replacing the keystore:</u>'''
	(-) Stop the Sending Service		(-) Stop the Sending Service
	(-) Rename the existing (previous) .ks found in the sending service keystores folder (to ***_old.ks for example.)		(-) Rename the existing (previous) .ks found in the sending service keystores folder (to ***_old.ks for example.)
	(-) Copy the ~~attached~~ keystore (to the sending service keystores folder.		(-) Copy the new keystore (to the sending service keystores folder.
	(-) Rename this copy as the previous one.		(-) Rename this copy as the previous one.
	(-) Restart the Sending Service		(-) Restart the Sending Service

Cso — Mon, 04 May 2026 09:18:40 GMT

Certificate Update

← Older revision		Revision as of 09:18, 4 May 2026
Line 1,473:		Line 1,473:
	= Certificate Update =		= Certificate Update =

	Once your Luxtrust certificate is activate in E-file, you need to replace de new keystore in the sending service.		Once your Luxtrust certificate is activate in E-file, you need to replace the new keystore in the sending service.

	If you have followed the renewal process, the '''updated keystore should have the same password''' as the old one <br>		If you have followed the renewal process, the '''updated keystore should have the same password''' as the old one <br>
	In this case you can use a simplified process by '''<u>simply ~~replace~~ the keystore:</u>'''		In this case you can use a simplified process by '''<u>simply replacing the keystore:</u>'''
	(-) Stop the Sending Service		(-) Stop the Sending Service
	(-) Rename the existing (previous) .ks found in the sending service keystores folder (to ***_old.ks for example.)		(-) Rename the existing (previous) .ks found in the sending service keystores folder (to ***_old.ks for example.)
	(-) Copy the ~~attached keystore~~ (to the sending service keystores folder.		(-) Copy the newkeystore (to the sending service keystores folder.
	(-) Rename this copy as the previous one.		(-) Rename this copy as the previous one.
	(-) Restart the Sending Service		(-) Restart the Sending Service

Cso — Mon, 04 May 2026 08:43:42 GMT

Solving known problems

← Older revision		Revision as of 08:43, 4 May 2026
Line 834:		Line 834:

	After each change through the administration module, please [[#Stop_the_application\|stop]] and [[#Start_the_application\|start]] the sending service again.		After each change through the administration module, please [[#Stop_the_application\|stop]] and [[#Start_the_application\|start]] the sending service again.



			= Certificate Update =

			Once your Luxtrust certificate is activate in E-file, you need to replace de new keystore in the sending service.

			If you have followed the renewal process, the '''updated keystore should have the same password''' as the old one <br>
			In this case you can use a simplified process by '''<u>simply replace the keystore:</u>'''
			(-) Stop the Sending Service
			(-) Rename the existing (previous) .ks found in the sending service keystores folder (to ***_old.ks for example.)
			(-) Copy the attached keystore (to the sending service keystores folder.
			(-) Rename this copy as the previous one.
			(-) Restart the Sending Service


			In case of a '''different kesytore password''', you '''<u>will have to reinstall the Sending Service</u>'''.<br>
			You need import the new keystore and then [[#Change_your_setup\|change the step-up ]] of your Sending Service

Cso — Mon, 04 May 2026 08:35:42 GMT

Certificate Update

@@ Line 1,474: / Line 1,474: @@
 Once your Luxtrust certificate is activate in E-file, you need to replace de new keystore in the sending service.
 Please find below what you need to do:
 * Stop your sending service