Perhaps the order of your fields doesn't matter, but I typically move the header fields to the top of the list (above the lines fields).

You need to have all the header records before you have the line records so first I would  move up all the fields that start with H above the ones that start with a L. The  fields on the right should be in the same order as the fields on the left because some fields are validated against field that come before them.

 Notice you have the check number at the bottom but on the left it is the second item.  This will cause a problem because the program will not know what check number all the data goes to because you have not set it yet.

I just rearranged the order of the data fields and re-ran, it does not seem to change things in the VI job's invoice dates

Yes, order the fields as they would be set when doing an entry manually, and sort your input data to have lines for each payment in order.

If dates are not working, be sure they are stored as M/D/Y (as indicated by your screenshot).

I've re-ordered the fields in the VI job and there does not seem to be any change in the invoice date. The invoice dates in the import spreadsheet are in the same format as the check dates. bummer!

This from the KB

These are the two scenarios we can import A/P Manual Checks for:

• A/P Check containing 1 invoice with multiple GL distributions
• A/P Check containing multiple invoices with 1 GL distribution

A/P Check containing 1 invoice with multiple GL distributions:

Create import into AP_ManualCheckHeader

Configuration Tab:

Header Separate From Line Record - Leave this Checkbox blank. Select only if sourcefile is formatted when Header information such as the Vendor Number, Check Number and Check Amount are in different rows than the Line information such as Invoice Number and Invoice Amount.

Data Tab:

The following fields should be included on the import:

• H.BatchNo - If Batch Processing is selected for Manual Check Entry in Accounts Payable, Setup menu, Accounts Payable Options 
• H.BankCode
• H.CheckNo
• H.CheckType
• H.CheckAmt
• H.APDivisionNo
• H.VendorNo
• L.InvoiceNo
• L.InvoiceAmt
• LL.AcountKey
• LL.DistributionAmt

Other fields may be added but are not required. For example, if a default value needs to be overridden, you may add the field to the import job.

Records Tab:

Change Next On - This must be defined if Header Separate From Line Record on the Configuration Tab is blank.

Special Consideration - Verify the amounts in the sourcefile are in balance. The Invoice Amount must equal the Line Distribution Amounts. The Check Amount must equal the Invoice Amounts.

_______________________________________________________

A/P Check containing multiple invoices with 1 GL distribution:

Create import into AP_ManualCheckHeader

Configuration Tab:

Header Separate From Line Record - Leave this Checkbox blank. Select only if sourcefile is formatted when Header information such as the Vendor Number, Check Number and Check Amount are in different rows than the Line information such as Invoice Number and Invoice Amount.

Data Tab:

The following fields should be included on the import:

• H.BatchNo - Only if Batch Processing is selected in AP Setup options for Manual Check Entry
• H.BankCode
• H.CheckNo
• H.CheckType
• H.CheckAmt
• H.APDivisionNo
• H.VendorNo
• L.InvoiceNo
• L.InvoiceAmt
• LL.AcountKey
• LL.DistributionAmt

Note: To prevent Out of Balance errors if using Multiple Invoice per Check, the field H.CheckAmt must have the following import properties:

• Operation = Calculated
  Calculation = {AP_ManualCheckHeader.CheckAmt}+NUM(IMP$[x]) where x = column in sourcefile that contains the Invoice amount.
  Other fields may be added but are not required. For example, if a default value needs to be overridden, you may add the field to the import job.
• If Out of Balance Errors are received, it might be necessary to add the L.LineKey Field to the Import job with an Operation of Incr Assign

Note: The fields LL.AcountKey& LL.DistributionAmt are required to properly write to the file AP_ManualCheckInvDetail.M4T. (Note: Check reversals do not use these fields.)

Records Tab:

Change Next On - This must be NOT be included in the Records Tab

Special Consideration - Verify the amounts in the sourcefile are in balance. The Invoice Amount must equal the Line Distribution Amounts. The Check Amount must equal the Invoice Amounts.

it looks like invoice date is not mentioned here, i may have to do two separate imports if I want invoice dates to be different. One to import invoices, one to import checks

btw, I was able to get multiple invoices per check with multiple GL distrubutions with the above VI job