5.1 Journal Names & Voucher Number Sequences

5.1 Journal Names & Voucher Number Sequences

Quick Summary: In Microsoft Dynamics 365 Finance, journals are the transactional engine through which financial entries are entered, validated, approved, and committed to the General Ledger. Journal Names act as foundational configuration templates that establish the rules of engagement for each transaction batch—determining the journal type, voucher numbering sequence, voucher allocation timing, default offset accounts, posting layer, workflow requirements, account type controls, and user group posting restrictions.

---

1. Journal Names Architecture & Configuration

Every journal created in Dynamics 365 Finance must be instantiated from a predefined Journal Name. A journal name encapsulates accounting behavior, audit trails, and security boundaries.

Navigation

• Path: General ledger > Journal setup > Journal names

+-----------------------------------------------------------------------------+
|                             Journal Name Record                             |
|  Journal Name: GEN-ADJ             Journal Type: Daily                      |
|  Description: GL Daily Adjustments Voucher Series: VCH_GEN                  |
+-----------------------------------------------------------------------------+
|  - Voucher Allocation: Upon posting        - Posting Layer: Current         |
|  - Default Account Type: Ledger            - Default Offset: Ledger         |
|  - Workflow Approval: GL_Adj_Workflow      - Detail Level: Details summary  |
+-----------------------------------------------------------------------------+
        |                                              |                      
        v                                              v                      
+--------------------------------+   +--------------------------------+
|     Journal Control Rules      |   |      Posting Restrictions      |
| - Allowed Account Types: Ledger|   | - Create/Edit: Junior_Accts    |
| - Required Segments: Dept, BU  |   | - Post Only: Finance_Managers  |
+--------------------------------+   +--------------------------------+

Core Configuration Parameters on Journal Names

1. Journal name & Description: A unique alphanumeric code (e.g., GEN-ADJ, ALLOC-MO, PAY-DISB) and clear descriptive label.
2. Journal type: Classifies the operational domain and user interface behavior of the journal. The selected type dictates which modules and subledger tables can consume the journal.
3. Voucher series: The number sequence code linked to the journal name that generates unique voucher IDs for accounting entries.
4. New voucher by: Determines how voucher numbers are generated when users create new lines:
   • Entering a new voucher: A new voucher number is drawn whenever the user manually requests a new voucher or changes lines.
   • One voucher number only: Forces all lines in the entire journal batch to share the exact same voucher number.
   • In connection with balance: A new voucher number is assigned only when the previous voucher's debits and credits are fully balanced.
5. Voucher draw timing (Number allocation at posting): Selects whether the voucher number is consumed immediately during data entry or deferred until the instant of posting.
6. Posting layer: Specifies whether transactions post to the Current (statutory financial reporting), Operations (internal management), or Tax (statutory fiscal tax adjustments) layer.
7. Detail level: Controls how journal lines are summarized in the general ledger:
   • Details: Posts every individual journal line as a distinct subledger and general ledger distribution.
   • Summary: Aggregates lines sharing identical accounts, dates, dimensions, currency, and posting layers into a single ledger transaction, reducing database row bloat.
8. Account type & Offset account type: Sets default account classifications (Ledger, Customer, Vendor, Project, Fixed assets, Bank) for newly created lines.

Journal Types Matrix

---

2. Voucher Allocation Strategy & Number Sequences

One of the most critical architectural decisions for a Functional Consultant is configuring how and when voucher numbers are drawn from number sequences.

Voucher Drawing Timing Mechanisms

1. In Connection With Balance:
[User Enters Line 1 (Dr)] ---> [Voucher Drawn: VCH-001] ---> [Line 2 (Cr)] ---> Balanced (VCH-001 Closed)
                                                                    |
                                                     User deletes line? --> Number gap created / Status list lock!

2. Upon Posting:
[User Enters Lines 1..50] ---> [Draft Temp ID: *TEMP-01*] ---> [Click Post] ---> [Voucher Drawn: VCH-100] (0 Gaps, High Speed!)

• In connection with balance:
  • A formal voucher number is assigned as soon as the user begins entering a line or balances debits and credits.
  • Risk: If the user abandons the journal, deletes lines, or experiences a client crash, the consumed voucher number is either wasted (in non-continuous sequences) or trapped in the database status list (in continuous sequences), creating audit reconciliation friction.
• At transaction date:
  • Voucher numbers are assigned chronologically based on the accounting transaction date specified on the journal line.
  • Use Case: Required in legal jurisdictions where statutory tax vouchers must strictly follow date order without temporal inversion.
• Upon posting (Recommended Best Practice):
  • During data entry, the system displays a temporary placeholder identifier (e.g., *TEMP-0001* or line sequence).
  • The official general ledger voucher number is consumed from the number sequence at the exact millisecond the user clicks Post and the transaction commits.
  • Benefits: Completely eliminates numbering gaps from discarded drafts, prevents multi-user record locking during journal entry, and drastically boosts posting performance in high-volume shared environments.

Voucher Allocation Comparison Matrix

Number Sequence Properties: Continuous vs. Non-Continuous

Under Organization administration > Number sequences > Number sequences:

• Continuous: Enforces zero numeric gaps by utilizing a database-level Status List. If a transaction aborts, the uncommitted number is saved to the status list for reuse. Impact: Generates severe table-level pessimistic locks and latency. Use strictly when statutory tax authorities require unbroken document sequences.
• Non-Continuous: Pre-allocates blocks of numbers into memory cache (e.g., cache size = 20). If transactions abort, cached numbers are discarded. Impact: Maximum database throughput and concurrency; optimal for daily operating journals.

---