Reprocessing Returns through G/L Bridge

If you process your return with G/L Bridge Client Selection importing from CCH^® ProSystem fx^® Engagement, you can use Quiklink to process non-extensive accounting system changes to your client’s data. However, if the changes are extensive or your accounting system does not support Quiklink, you must reprocess the return with G/L Bridge File Selection.

Warning!: Importing via G/L Bridge removes data placed on Partnership A-series entities higher than 1. After importing, you must review Entities 2 and greater, and then re-enter any data removed by the import process.

Reprocessing returns through G/L Bridge can produce different results depending on whether the accounting system you are importing from includes tax code identifiers. Click a link below to learn more about how G/L Bridge handles different types of accounting systems. For information about the accounting systems that use tax identifiers, see G/L Bridge Accounting Systems Processing Profiles.

Tax Code Identifiers Included in the Tax Interface File

Some accounting systems include tax code identifiers as part of the tax interface file data. When you reprocess your return through G/L Bridge, the exact tax code used for each detail data item in worksheet grids (i.e., open line description items such as Other Deductions, Other Current Assets, etc.) is stored in the tax return. During reprocessing, the system matches tax codes for repeated data. Listed below is a summary of the processing that occurs during the matching process.

Circumstance	G/L Bridge Reaction
Tax code of a detail item in the interface file is matched with an existing detail item in the return	The system overrides the existing description and applicable amount data with the new data from the tax interface file. If there are additional fields on the detail item other than description and amounts (for example, code boxes, option boxes), they are not affected by the reprocessing.
Tax code of a detail item in the interface file is not matched with an existing detail item in the return	If no match is found for a detail item tax code on the interface file, the system creates a new detail item and transfers the description and amount to the new record.
Tax code of an existing detail item is not matched on the tax interface file	If an existing detail item has a stored tax code and is not matched by any data from the tax interface file, then it is deleted from the return.
Data that has been entered through data entry in Tax Preparation	If you enter detail data through regular data entry methods after processing your return through G/L Bridge, the detail items will not have stored tax codes. Stored tax codes in detail data can only be supplied from processing with G/L Bridge. During reprocessing, these records, which are considered existing data, are processed according to your selection of the existing data options.

Note: You must always calculate the return to view data on government forms.

Tax Code Identifiers Not Included in the Import File

Special Considerations for Balance Sheet Data (No Tax Code Identifiers)

Matching Example

In the example below, no match was found for the description "Prepaid Rent," so a new detail data was created for the current year amount.

Other Current Assets Data
	Existing Return		Import Data File		Return After Processing
Description	Prior Year	Current Year	Prior Year	Current Year	Prior Year	Current Year
Office Supplies	1300	1600	1300	1200	1300	1200
Prepaid Insurance	700	900	700	800	700	800
Prepaid Office Rent	1000	700			1000	700
Prepaid Rent			1000	1100		1100

Note: After reprocessing a return through G/L Bridge when the Import beginning balance sheet data box was not checked, double-check your balance sheet detail data to make sure there are no duplicate detail data items resulting from data descriptions being slightly different between the return and the revised interface file.