Don't use "Next" for this.  Either use a run-time prompt (where the user manually types in the same value twice), or have the batch / deposit # in your source data.

Is that the "Run Assign" operation in the Data portion?

Yes.  Be sure to set a meaningful prompt to help the user.  Batch # values must always be numeric or upper case text.  I believe lower case letters will be accepted by the screen, but that causes problems for certain fields (like deposit / batch #).

Ok this has been a big help. The first job to the Deposit table works like a charm, the job to the Header is getting caught on CustomerNo. It's throwing an error that the CustomerNo isn't on file, when it 100% is. I went through the manual process to verify, and the import file has the CustomerNo pulled from the database with zero transformation applied to that field. What could be causing that?

Ok this has been a big help. The first job to the Deposit table works like a charm, the job to the Header is getting caught on CustomerNo. It's throwing an error that the CustomerNo isn't on file, when it 100% is. I went through the manual process to verify, and the import file has the CustomerNo pulled from the database with zero transformation applied to that field. What could be causing that?

Set the AR Division field just before CustomerNo.  If you don't have AR Divisions enabled you need to pass a "00" through as part of the customer record key.

Wow, what a silly thing that worked perfectly. These primary keys sure are picky

Hi Yung_Grasshopper, if the above suggested answer helped, please do mark it as verified  for the benefit of others in this forum :). Thank you!