UltraTax CS all entities: ELF rejection - PDF/TXT/XLSX is required by the electronic file but is not present in the transmitted package

Show expandable text

New (tax) year, new help!

Fixed Assets and UltraTax CS 2023 help is now on Help and Support. We're still moving articles, but you can find most content for the 2023 tax year there. Continue using the Help & How-To Center for tax years 2022 and older.

Electronic filing rejection: [FILENAME].PDF/TXT/XLSX is required by the electronic file but is not present in the transmitted package

FILENAME is the name of the PDF file that is being attached to the electronic file. This e-file error occurs when there is a problem with a PDF file that is attached to the electronic file or if there is a PDF required to be attached and it is missing. Try the following steps to resolve this error. 

There is a problem with the PDF file name
  • Reduce the PDF file name to 15 characters or less.
  • Remove any special characters from the PDF file such as underscores, dashes, apostrophes, etc. Only use alphanumeric characters when naming the PDF file. 
  • Remove spaces from the file name.

After updating the file name, re-attach the PDF file by choosing Edit > Electronic Filing Attachments while in the input screens of the client.

A PDF was attached from one workstation and the electronic file was created and transmitted from a different workstation

When attaching a PDF to an electronic file, it is best to either attach the PDF file at the workstation that you will be creating and transmitting the electronic file from or save the PDF to a location where both workstations can access it. If the PDF was attached at a different workstation, re-attach the PDF on the workstation where the electronic file will be created and transmitted from.

Environmental factors are preventing the PDF file from being attached to the electronic file

It is possible that the PDF files that are automatically generated by the application are not being created due to environmental issues. Re-creating and re-transmitting the electronic file may fix the issue. Some examples may be if the anti-virus software is scanning the UT18Data folder or the person creating the electronic file does not have full read and write rights to the UT18Data folder. 

Was this article helpful?

Thank you for the feedback!

Internal only

If a user is getting this rejection for a PDF file that is automatically attached, do the following:

  1. Re-create the electronic file and view it in the electronic filing status window to see what PDF attachments are listed in the e-file.
  2. Go to X:\WinCSI\UT[[ut_cy_yy]]Data\$SYSDATA\efiling
  3. Copy and paste the client's e-file (.XEF file) to a different location. 
  4. Rename the file and replace the file extension .XEF with .zip
  5. Double click the .zip file and verify the PDF files included. 

If the PDFs are listed in the e-file when viewing it but are not included in the e-file, then it is an environmental issue, See TFS871193.

This error used to say "File [FILENAME].PDF is in the XML but is not in the zip."