AutoInvoice and Legal Entity Document Sequencing: How
Transactions are Processed
If the primary ledger is enabled for document sequencing at the legal entity level, AutoInvoice validates and assigns document numbers to transactions according to the requirements of the ledger settings. However If an imported transaction line already has a document number, then AutoInvoice accepts this document number without further validation.
How Transactions Are Processed
1. Validate and group transaction lines into transactions.
2. Derive the legal entity for each transaction and assign the legal entity to the transaction.
3. If the transaction does not have an accounting date, then derive the accounting date.
4. If the primary ledger option Enforce Chronological Order on Document Date is not enabled:
a. Retrieve the document sequence for the document category of each transaction type assigned to
transactions.
b. Assign the document number to the transaction according to the combination of legal entity, transaction type,
document sequence and accounting date.
5. If the primary ledger option Enforce Chronological Order on Document Date is enabled:
a. Order transactions by legal entity and then by transaction type.
b. Retrieve the document sequence for the document category of each transaction type assigned to
transactions.
c. Order transactions by document sequence and then by accounting date in ascending chronological order.
d. Compare the document sequence accounting date to the accounting date of the transaction.
e. If the transaction accounting date is equal to or later than the document sequence accounting date, assign
the document number to the transaction according to the combination of legal entity, transaction type,
document sequence and accounting date.
f. If the transaction accounting date is earlier than the document sequence accounting date, retrieve the value of
the Receivables system option Accounting Dates Out of Order.
g. If the Accounting Dates Out of Order option is set to:
• Reject: Reject the transaction and transfer the transaction to the error table.
• Adjust: Update the transaction accounting date with the document sequence accounting date.
2. Derive the legal entity for each transaction and assign the legal entity to the transaction.
3. If the transaction does not have an accounting date, then derive the accounting date.
4. If the primary ledger option Enforce Chronological Order on Document Date is not enabled:
a. Retrieve the document sequence for the document category of each transaction type assigned to
transactions.
b. Assign the document number to the transaction according to the combination of legal entity, transaction type,
document sequence and accounting date.
5. If the primary ledger option Enforce Chronological Order on Document Date is enabled:
a. Order transactions by legal entity and then by transaction type.
b. Retrieve the document sequence for the document category of each transaction type assigned to
transactions.
c. Order transactions by document sequence and then by accounting date in ascending chronological order.
d. Compare the document sequence accounting date to the accounting date of the transaction.
e. If the transaction accounting date is equal to or later than the document sequence accounting date, assign
the document number to the transaction according to the combination of legal entity, transaction type,
document sequence and accounting date.
f. If the transaction accounting date is earlier than the document sequence accounting date, retrieve the value of
the Receivables system option Accounting Dates Out of Order.
g. If the Accounting Dates Out of Order option is set to:
• Reject: Reject the transaction and transfer the transaction to the error table.
• Adjust: Update the transaction accounting date with the document sequence accounting date.
h.Assign the document number to the transaction according to the combination of legal entity, transaction type,document sequence and accounting date.