Example of Enforcing Chronological Order on Invoice Voucher Numbers

You can enforce, for a specific legal entity and document sequence, a chronological order of voucher number assignment based on the invoice header accounting date.

Scenario

The following example illustrates chronological voucher number assignment for two legal entities belonging to the same ledger and using different document sequences.

The Ledger options are set as follows:

• Sequencing By is set to Legal entity.

• Enforce Chronological Order on Document Date is enabled.

The ledger has the following setup:

• Legal entity LE1

• Legal entity LE2

• Business unit BU1

You define two document sequences called Sequence 1 and Sequence 2 and assign:

• Both to document sequence categoryStandard Invoices

• Sequence 1 to LE1

• Sequence 2 to LE2

This table shows how voucher numbers are assigned to the invoices.

Business Unit	Legal Entity	Invoice	Accounting Date	Voucher Number
BU1	LE1	INV-1	April 7, 2014	100
BU1	LE1	INV-2	April 10, 2014	101
BU1	LE2	INV-3	April 14, 2014	100
BU1	LE2	INV-4	April 16, 2014	101

The maximum accounting date for:

• LE1 and Sequence 1: April 10, 2014

• LE2 and Sequence 2: April 16, 2014

This table shows how voucher numbers are assigned to the next two invoices.

Business Unit	Legal Entity	Invoice	Accounting Date	Voucher Number
BU1	LE1	INV-5	April 9, 2014	None. You can't save the invoice.
BU1	LE2	INV-6	April 16, 2014	102

You can't save invoice INV-5 because the accounting date of April 9, 2014 is earlier than the maximum accounting date of April 10, 2014 for LE1 and Sequence 1.

You can save INV-6 because the accounting date of April 16, 2014 is the same as or later than the maximum accounting date of April 16, 2014 for LE2 and Sequence 2.