Accounting Date Derivation During AutoInvoice Import

During a run of the Import AutoInvoice process, AutoInvoice derives the accounting date to assign to transactions using the following criteria:

• Does an accounting date exist for this transaction in the interface table?

• Does the transaction use rules?

• What is the setting of the Derive date option on the transaction source?

• What is the setting of the Accounting Date in a Closed Period option on the transaction source?

AutoInvoice derives the accounting date differently depending on these criteria:

• Invoices without Rules

• Invoices with Rules

• Credit Memos

Note:

If a transaction date isn't passed for an invoice or debit memo, AutoInvoice uses the derived accounting date as the transaction date.

Invoices without Rules

If an invoice doesn't use rules, AutoInvoice uses the following process to derive the accounting date:

1. AutoInvoice uses the accounting date in the interface table, if one exists and the date is in an open or future enterable period.

2. If no accounting date is provided in the interface table, and the Derive date option on the transaction source is set to No, AutoInvoice uses the value of the Default Date parameter of the Import AutoInvoice process as the accounting date.

3. If no accounting date is provided in the interface table, and the Derive date option on the transaction source is set Yes:

   1. AutoInvoice uses the ship date in the interface table.

   2. If the ship date doesn't exist, AutoInvoice uses the sales order date.

   3. If the sales order date doesn't exist, AutoInvoice uses the value of the Default Date parameter.

4. If the derived accounting date for a transaction line exists but is in a Closed or Not Open period, and the Accounting Date in a Closed Period option on the transaction source is set to Adjust, then AutoInvoice automatically adjusts the accounting date to the first accounting date in the next open or future enterable period.

Invoices with Rules

If the invoice uses the In Advance invoicing rule:

• AutoInvoice uses the accounting date provided in the interface table as the invoice accounting date.

• If no accounting date is provided in the interface table, then AutoInvoice uses the earliest revenue scheduling rule start date of all of the lines belonging to the invoice as the invoice accounting date.

If the invoice uses the In Arrears invoicing rule, AutoInvoice derives an end date for each transaction line based on the revenue scheduling rule, rule start date, and rule duration. Once AutoInvoice derives the end date for each transaction line, it takes the latest date and uses it as the invoice accounting date.

AutoInvoice uses the following process to derive the accounting date for invoices with revenue scheduling rules:

1. If the Derive date option on the transaction source is set to No, AutoInvoice uses the value of the Default Date parameter of the Import AutoInvoice process.

2. If no accounting date is provided in the interface table, and the Derive date option on the transaction source is set to Yes:

   1. AutoInvoice uses the last day of the prior period, if this period has a status of Open.

   2. If a prior period with a status of Open doesn't exist, AutoInvoice uses the first day of the subsequent period that has a status of Open.

      If there is more than one subsequent period with a status of Open, AutoInvoice can't adjust the accounting date, and the line is rejected.

   3. If an Open period doesn't exist, AutoInvoice uses the first day of the first subsequent period that has a status of Future.

      If there is more than one subsequent period with a status of Future, or if a future period can't be found, AutoInvoice can't adjust the accounting date, and the line is rejected.

Credit Memos

If no accounting date is provided in the interface table, AutoInvoice uses either the accounting date of the related invoice receivable distribution or the Default Date parameter of the Import AutoInvoice process as the accounting date, whichever is later.

Accounting Date Validation

AutoInvoice rejects lines using the following logic for accounting dates either passed by the user or derived by AutoInvoice:

• Accounting period for the accounting date isn't defined.

• Accounting date is in a Closed, Closed Pending, or Not Opened period, and the Accounting Date in a Closed Period option on the transaction source is set to Reject. If the invoice uses the In Arrears invoicing rule, then AutoInvoice only rejects lines that have an accounting date in a Closed period.

• Either the credit memo accounting date is earlier than the related invoice accounting date, or the credit memo transaction date is earlier than the related invoice transaction date, or both.

Revenue Scheduling Rule Start Date Validation

AutoInvoice rejects lines for revenue scheduling rule start dates either passed by the user or derived by AutoInvoice under these circumstances.

• If the invoice uses the In Advance invoicing rule, AutoInvoice rejects lines if either of these is true:

  • Rule start date is in a Closed or Not Opened period and the Accounting Date in a Closed Period option on the transaction source is set to Reject.

  • Accounting period for the rule start date isn't defined.

• If the invoice uses the In Arrears invoicing rule, AutoInvoice rejects lines if either of these is true:

  • Rule start date results in an accounting date in a Closed period and the Accounting Date in a Closed Period option on the transaction source is set to Reject.

  • Accounting period for the accounting date isn't defined.

Besides validating dates, AutoInvoice also rejects lines if:

• Revenue scheduling rule has overlapping periods.

• One or more accounting periods don't exist for the duration of the revenue scheduling rule.