Sending a SAFT(JPK) File

This article describes the procedure for sending a SAFT(JPK) file from Business Central.

Note

The procedure for sending a SAFT(JPK) file requires configuring the data encryption service. To learn more, read the Configuration of the Service article.

Warning

The procedure for sending a SAFT(JPK) file is the same for the test and production environments. When sending a SAFT(JPK) file, make sure which environment is currently selected.

Signing Metadata File

During the process of sending a SAFT(JPK) file from Business Central, you need to sign the metadata file generated by the application named initupload.xml. Available methods for signing metadata files are:

Qualified Signature - signing the metadata file using a qualified certificate, requires having the certificate installed in the operating system. Make sure that in the configuration of the program used to handle qualified signature, the correct XAdES-BES Enveloped format is selected. More information.
Trusted Profile (Profil Zaufany) - signing the metadata file through the ePUAP platform. More information.

To send a SAFT(JPK) File

To send a SAFT(JPK) file:

Select the search icon in the top right corner of the Business Central system, then enter SAF-T Send File Register and click on the link.
Click the Import SAF-T File button on the action bar to import the previously generated SAFT(JPK) file. The system will read its structure based on the specified file and fill in information about the file.
Click the Send SAF-T File button on the action bar.
Verify the correct validation of data and follow the instructions displayed in the wizard.

After sending the SAFT(JPK) file, information about the status of the sent file and a reference number will appear in the file record. Processing of the SAFT(JPK) file by the Ministry of Finance may take from several minutes to up to twenty-four hours. At any time, you can refresh the status of the Official Receipt Confirmation (UPO) by clicking the Refresh UPO Status button. A list of possible statuses is located in the table below.

Code	Description
100	Session importing files started
101	X of Y declared files received
120	Session completed successfully. Data saved correctly. Document verification is in progress
200	Processing document successful, download UPO
300	Invalid reference number
401	Negative verification – document does not match the XSD schema
405	Document with revoked certificate
406	Document with certificate from an unsupported Vendor
407	You sent a duplicate document. The original's reference number is XXXXXXXX
408	Document contains errors that prevent its processing
410	Uploaded files are not a valid ZIP archive
411	Negative verification - an identical document has already been submitted in the system
412	Document encrypted incorrectly
413	Document checksum inconsistent with declared value 35
415	Uploaded document type is not supported in the system
417	Document encrypted incorrectly. Decryption error of authentication data
418	Negative verification – authentication data does not match the XSD schema
419	Negative verification - error in authentication data
420	No current authorization/power of attorney to sign the document
422	Negative verification – a document signed with authentication data can only be submitted by a taxpayer who is a natural person
423	Document with a certificate missing required attributes
424	Negative verification - the document cannot be signed using authentication data
425	Negative verification – inconsistent data
426	Incorrect character encoding in authentication data
427	Document with a certificate with an incorrect path
428	Business rule validation error
430	Document with an invalid signature

Downloading Official Receipt of Delivery (UPO)

The option to download the UPO file is available only for files that have been sent and processed by the Ministry of Finance (status 200).

To download the UPO file: