Error “When Importing an Invoice Batch”

stone

Issue

During the import of an invoice batch, the following error may occur:

"Invalid input. Due data cannot be earlier than document data"

stone

Solution or Workaround
Starting with version 5.2, the invoice import file has new requirements which include due date and Term code fields. These are located in the Invoices section of the import file. The Due date field in the header record must have a date entered that represents the date the first scheduled payment is due to be paid and should always be the same date as the first associated detail line listed in the Invoice Payment Schedules section of the import file. Both due date fields are required for the import to be successful.

Dates entered in due date field in the Invoice Payment Schedules section are calculated starting with the date in the document data field plus the number of days specified in the terms code when the payments are due. For example, an invoice date of 01/01/2005 with Term code entry of "N30" (net amount due in 30 days) will require a due date entry of 01/31/2005.

stone

Solution or Workaround
Starting with version 5.2, the invoice import file has new requirements which include due date and Term code fields. These are located in the Invoices section of the import file. The Due date field in the header record must have a date entered that represents the date the first scheduled payment is due to be paid and should always be the same date as the first associated detail line listed in the Invoice Payment Schedules section of the import file. Both due date fields are required for the import to be successful.

Dates entered in due date field in the Invoice Payment Schedules section are calculated starting with the date in the document data field plus the number of days specified in the terms code when the payments are due. For example, an invoice date of 01/01/2005 with Term code entry of "N30" (net amount due in 30 days) will require a due date entry of 01/31/2005.