Replacement flags
The replacement flag in the header record tells the application how to initialize data fields in the target tax return before and during import. Exports default to an R flag. Use an M flag when you import. If the header record is missing the replacement flag, the import will fail.
M: Field level replacement flag
Use the M flag as your default flag for import. The application doesn’t clear any existing data in the return before it imports. It only replaces a field if the import file contains new data for that field. All existing group data remains in place. The application places any group data records from the import file exactly into the positions that the 5 group numbers in the 2nd through 6th columns of the import file specify.
If you are unsure about the existing group data structure, export the return first and review it. For example, a partner may appear 3rd in the list of partners, but have group number 4 because it was originally created in the 4th position and one of the first 3 partners was later deleted.
Don’t include placeholder fields with the word NONE. Doing so doesn’t minimize processing time.
U: Form level replacement flag
Before the import runs, the application wipes all data and group alignment from the return for every field whose form name appears in the import file. For example, if your U flag import file contains a single line with the form name GENERAL INFORMATION and the field name PARTNERSHIP EIN, the application erases all fields in the return that share the form name GENERAL INFORMATION. It then imports the PARTNERSHIP EIN value from the file into the return.
During a U flag import, the application ignores the group numbers in the import file. For example, if an import file has these 3 lines:
“D SCHEDULE K-1”,”0”, ”1”, ”0”, ”0”, ”0”,”PARTNER NAME LN 13”,”Partner One”,”O” “D SCHEDULE K-1”,”0”, ”7”, ”0”, ”0”, ”0”,”PARTNER NAME LN 13”,”Partner Seven”,”O” “D SCHEDULE K-1”,”0”, ”9”, ”0”, ”0”, ”0”,”PARTNER NAME LN 13”,”Partner Nine”,”O”
The application ignores group numbers 1, 7, and 9, and places the 1st data record in the 1st position, the 2nd data record in the 2nd position, and the 3rd data record in the 3rd position.
If you add these 2 lines to the 3 previous lines:
“D SCHEDULE K-1”,”0”, ”7”, ”0”, ”0”, ”0”,”PARTNER ADDRESS LN 1”,”777 Street”,”O” “D SCHEDULE K-1”,”0”, ”9”, ”0”, ”0”, ”0”,”PARTNER ADDRESS LN 1”,”999 Street”,”O”
The application ignores group numbers 7 and 9, and places the 1st address record in the 1st position with Partner One, and the 2nd address record in the 2nd position with Partner Seven. To keep each partner's name and address aligned, add an address row for Partner One before the other 2 address rows — using either a real address or a blank value — so that the positions of each partner's name and address rows match up in the file.
Start group numbers at 1 and use consecutive order. Group numbers don’t need to match partner numbers. Don’t include a form name in the file if it has no associated data. If a line item has data for some partners but not others, enter NONE for the partners with no data. The application may or may not import NONE depending on the field type, but it keeps the data aligned correctly and prevents issues. If a field doesn’t allow NONE in an e-file, the application removes it before it creates the e-file.
H: Hybrid replacement flag
The H flag deletes data the same way the U flag does, but imports data the same way the M flag does. The application places data from the import file exactly into the positions the group numbers in the import file specify.
R: Return level replacement flag
Before the import runs, the application deletes all data and group alignment for every field that appears on the Org Data Dictionary worksheet of the Direct K-1 file set. It then imports data the same way the U flag does: it ignores the group numbers in the import file and places each group data record into the next available position.
Start group numbers at 1 and use consecutive order. Group numbers don’t need to match partner numbers. Don’t include a form name in the file if it has no associated data. If a line item has data for some partners but not others, enter NONE for the partners with no data. The application may or may not import NONE depending on the field type, but it keeps the data aligned correctly and prevents issues. If a field doesn’t allow NONE in an e-file, the application removes it before it creates the e-file.
S: Field level replacement flag for large files
Use the S flag the same way you use the M flag, but only for import files that contain 500,000–800,000 lines of data.
Only use this flag when you have sorted the import file first by Group Number and then by Form Name. When you use the S flag with a sorted file, the application automatically splits the file by Form Name. This requires less memory and lets the import complete much faster. Don’t include placeholder fields with the word NONE. Doing so doesn’t minimize processing time.
Additional information
When you use any flag other than M, group all form and field names together in the import file.
Related Content
-
About Direct K-1
Format:
Article
