Hello,

I’m also interested in getting an answer in the subject raised by Łukasz. 

I hope there is some update prepared for adjustment of IFS10 to the requirements of JPK_CIT reporting. As we are approaching the second half of 2024 it’s high time for us to get prepared for possible changes in our processes. 

Awaiting any info, thx.

Karolina

Hello again and just to make a note, It’s really important to start gathering an information related to JPK_CIT project as it was mentioned by Karolina as soon as the go-live planned for it starts from 2025 and we can't see any tag related to it within a community portal. 
Can anyone from IFS can take a lead on that?

thanks , regards
Łukasz

Hi,

I have just received this information related to JPK_CIT from IFS and I want to share it here:

“This new legal requirement has been reported to R&D for both IFS10 and IFS Cloud version.

R&D has approved this request and directed it for further work, but has not yet provided an exact due date.”

Regards,
/Rafal

Thank you @SCEMYSRAMW for sharing this info. We are waiting then for any further updates from their side. 

Hi Rafal and thanks a lot for an answer.

We are looking forward for more news. 

regards

Łukasz

Hi @SCEMYSRAMW , you can read more about the new legal requirements in Poland in our Service Center article: 

https://support.ifs.com/csm?id=kb_article_view&table=kb_knowledge&sys_kb_id=f13012c0473e829858119642036d433c 

Let us know if you can access the article. If not, we will post the details here. 

Hi Mateusz,

Thank you for the link. I can access the article, but...is this a correct link?

The title of the article is “Introduction of Mandatory KSeF System in Poland (National E-Invoicing)” and it is not related to the subject of this thread (JPK_CIT).

Best Regards,

/Rafal

Hello SCEMYSRAMW - this is link related to the new legal requirement called KSEF ( B2G - business to government project where whole EDI stream beetween companies will be directed to the governemt portal.  JPK_CIT is a kind of sub KSEF requirement. 

Refferring to my understanding both are independent technical aspects of IFS system , for instance our company will try to adapt XML to the KSEF validation and this is something we could try do it ourselfe hence JPK_CIT this is something where system by default has to extract it and output it to the xML form for companies to be able to send it to the tax authority. Last changes within JPK file were done on a level of UPD16 so I'm expecting to have similar action - IFS team should raise an internal R&D discussion to agree the way new format will be delivered to the customers ( possible to delivers as another Release number or UPD).
What is confirmed now by the tax authority - final XML schema is known and we can start checking how far we are from newest standard with latest JPK file definition on our ends.

with best regards
Łukasz

HI

Decree of the Minister of Finance on additional data by which the books kept must be supplemented has been signed. It will apply from the date on 2025-01-01.

According to Art. 193a. § 1. In the case of keeping tax books using computer programs, the tax authority may require the transmission of all or part of such books and accounting evidence by means of electronic communication.

In connection with the above, please provide dates when new features are planned to be released for version IFS10 and IFS Cloud.

Best regards

Joanna Muszyńska

#legalrequirement #localization

Hello  IFS Team, are there any news related to the new JPK_CIT ??
I would like to be sure that something started happening in the background.

Hello

For the IFS10 version, the functionality will be added to UPD26 and will be made available as a single patch – the patch is planned for the second half of November.

For the IFS Cloud version, the changes will be added to versions 24R1 SU6 and 24R2 SU1. The planned release date for these versions is 2024-12-19

Hello all and there’s one more question on the topic.

We are trying to define the best time to deploy the JPK patch, given that the time between now and the end of year is quite short.

Which of the scenarios is the correct one:

1. As the first of the new JPK files must be generated in early 2026 to report 2025 transactions, we can deploy the new JPK patch any time in 2025, because the patch provides only a procedure for creating the required file, while all necessary data are gathered in the application already before installing the patch. In other words, deployment of the patch e.g. in March 2025 will enable us to safely create correct files in the new format also for Jan and Feb 2025.

OR

2. Despite the fact that first of the new JPK files must be generated in early 2026 to report 2025 transactions, we must deploy the patch before 1 Jan 2025 because the patch not only provides a procedure for creating the required file, but also alters the way transactional data are created. In other words, if we deployed the patch e.g. in March 2025 then we would not be able to create correct files for Jan and Feb 2025.

Which one is true – 1 or 2?

Hello,

Definitely 2nd option. At least any documentation on how to configure it.