Study guide
5.1 Journal Names & Voucher Number Sequences
Microsoft Certified: Dynamics 365 Finance Functional Consultant Associate MB-310
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: MB-310 Exam Overview & Financial Architecture
1.1 MB-310 Exam Structure, Skills Measured & Consultant Role 1.2 Dynamics 365 Finance Architecture, Legal Entities & Global Address Book 1.3 Hands-on Lab Strategy & Preparation Framework
2 Chapter 2: Chart of Accounts & Main Accounts
2.1 Designing Chart of Accounts & Main Account Types 2.2 Main Account Categories & Ledger Account Aliases 2.3 Balance Control Accounts & Year-End Opening Account Setup 2.4 Legal Entity Overrides for Main Accounts & Dimensions
3 Chapter 3: Financial Dimensions & Account Structures
3.1 Custom & Entity-Backed Financial Dimensions 3.2 Financial Tags: Limits, Storage & Ledger Settlement Use 3.3 Account Structures, Segment Criteria & Activation 3.4 Advanced Rules & Advanced Rule Structures 3.5 Derived Dimensions & Dimension Default Templates
4 Chapter 4: Ledgers, Calendars & Currencies
4.1 Fiscal Calendars, Period Statuses & Module Access Control 4.2 Posting Layers, Multi-GAAP Reporting & the Ledger Form 4.3 Currency Exchange Types, Rate Providers & Triangulation 4.4 Accounting & Reporting Currencies (Dual-Currency Architecture) 4.5 Foreign Currency Revaluation & Revaluation Posting Profiles
5 Chapter 5: General Ledger Journals & Allocations
5.1 Journal Names & Voucher Number Sequences 5.2 Journal Control & Posting Restriction Rules 5.3 Journal Entry, the One-Voucher Rule, Validation & Posting 5.4 Reversals, Storno Corrections & Excel Integration 5.5 Ledger Allocation Rules & the Four Allocation Methods 5.6 Allocation Processing & Periodic (Recurring) Journals
6 Chapter 6: Intercompany Accounting & Settlements
6.1 Intercompany Accounting Setup & Due-To / Due-From Postings 6.2 Intercompany Journal Processing & Multi-Company Vouchers 6.3 Ledger Settlements Configuration & Processing
7 Chapter 7: Cash and Bank Management
7.1 Bank Groups, Bank Accounts & Ledger Integration 7.2 Payment Formats, Bank FX Revaluation & Shared Payment Setup 7.3 Manual vs. Advanced Bank Reconciliation & Statement Formats 7.4 Matching Rule Sets, Reconciliation Execution & Reversals 7.5 Cash Flow Forecasting Setup & Automation 7.6 Customer and Vendor Netting
8 Chapter 8: Periodic Closing & Financial Consolidations
8.1 Financial Period Close Workspace, Closing Roles & Schedules 8.2 Year-End Close Configuration & General Ledger Balance Carryforward 8.3 Consolidations Online: Legal Entity Setup, COA Mapping & Currency Translation 8.4 Import Consolidations & Intercompany Elimination Rules
9 Chapter 9: Sales Tax & Withholding Tax
9.1 Sales Tax Engine Hierarchy, Authorities & Settlement Periods 9.2 Ledger Posting Groups, Sales Tax Codes & Calculation Methods 9.3 Sales Tax Groups, Item Sales Tax Groups & Tax Exemptions 9.4 Sales Tax Adjustments and Settle and Post Sales Tax 9.5 Withholding Tax & US 1099 Vendor Reporting
10 Chapter 10: Accounts Receivable Setup & Invoicing
10.1 Customer Master, Customer Groups & Shared Customers 10.2 Customer Posting Profiles & Account Code Precedence 10.3 Free Text Invoices, Recurring Invoice Templates & AR Charges 10.4 Sales Order Invoicing, Billing Classifications & Prepayments 10.5 Customer Payment Methods, Payment Processing & Customer Bank Accounts
11 Chapter 11: Credit Management & Collections
11.1 Credit Management Architecture & Customer Credit Groups 11.2 Risk Scoring, Credit Limits, Blocking Rules & Credit Holds 11.3 Aging Definitions, Collections Workspace & Customer Pools 11.4 Collection Letter Sequences & Interest Notes 11.5 Customer Write-Offs, Bad Debt & Write-Off Reversals
12 Chapter 12: Subscription Billing & Revenue Deferrals
12.1 Recurring Contract Billing, Billing Schedules & Milestones 12.2 Deferral Principles, Deferral Defaults & Schedule Calculation Methods 12.3 Recognition Processing, Expense Deferrals & Modifying Schedules 12.4 Multiple Element Revenue Allocation (MEA / ASC 606)
13 Chapter 13: Accounts Payable & Invoice Processing
13.1 Shared Vendors, Global Address Book & Vendor Groups 13.2 Vendor Posting Profiles, AP Parameters & Vendor Bank Accounts 13.3 Invoice Matching Setup (2-Way, 3-Way), Tolerances & Exceptions 13.4 Vendor Invoicing Methods, Journals & Invoice Automation
14 Chapter 14: Vendor Payments & Expense Management
14.1 Methods of Payment & the Vendor Payment Proposal Engine 14.2 Generating Payments, Centralized Payments & Check Lifecycle 14.3 Expense Management Configuration, Categories & Policies 14.4 Expense Reports Processing, Mobile Receipts & Intercompany Expenses
15 Chapter 15: Budgeting & Budget Control
15.1 Budget Models, Budget Codes & Allocation Terms 15.2 Budget Register Entries, Workflows & Budget vs. Actual 15.3 Budget Transfer Rules & Processing Budget Transfers 15.4 Budget Control Configuration, Cycles, Rules & Budget Groups 15.5 Budget Funds Available, Over-Budget Permissions & Document Budget Check 15.6 Budget Planning Framework, Organization Hierarchies & Planning Processes 15.7 Budget Plans, Scenarios, Allocations & Generating Register Entries
16 Chapter 16: Fixed Assets Configuration & Transactions
16.1 Fixed Asset Groups, Asset Records & Group/Book Mapping 16.2 Depreciation Profiles: Methods & Conventions 16.3 Fixed Asset Books, Derived Books & Posting Profiles 16.4 Fixed Asset Acquisition Pathways 16.5 Depreciation Proposals, Multi-Company Runs & Fixed Asset Budgets 16.6 Fixed Asset Disposals: Sale, Scrap & Disposal Accounting 16.7 Fixed Asset Splits, Transfers & Reclassification 16.8 Asset Leasing (IFRS 16 / ASC 842)
5.1 Journal Names & Voucher Number Sequences
Key Takeaways Explain This Topic AI
A journal name binds a journal type, voucher number sequence, default account type, and offset account into a reusable entry template.
The 'One voucher only' setting forces every line in the journal to share one voucher number; 'One voucher number only' allows the same voucher across multiple lines with balance validation deferred.
Continuous voucher number sequences serialize allocation and cause record locking when many users post concurrently; non-continuous sequences allocate in blocks and scale better.
Voucher series are assigned per journal name, so month-end adjustment journals can be numbered separately from daily operational journals.
Last updated: August 2026
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
Journal name & Description: A unique alphanumeric code (e.g., GEN-ADJ , ALLOC-MO , PAY-DISB ) and clear descriptive label.
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.
Voucher series: The number sequence code linked to the journal name that generates unique voucher IDs for accounting entries.
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.
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.
Posting layer: Specifies whether transactions post to the Current (statutory financial reporting), Operations (internal management), or Tax (statutory fiscal tax adjustments) layer.
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.
Account type & Offset account type: Sets default account classifications ( Ledger , Customer , Vendor , Project , Fixed assets , Bank ) for newly created lines.
Journal Types Matrix
Journal Type Primary Functional Area Target Transactions Associated Subledger Engine
Daily General Ledger Manual GL adjustments, accruals, reclassifications, intercompany transfers General Ledger core
- Periodic General Ledger Recurring journal templates (amortizations, subscriptions) Periodic Tasks engine
- Allocation General Ledger Execution target for automated Ledger Allocation Rules Ledger Allocation engine
Elimination Consolidation Intercompany elimination adjustments during legal entity consolidation Consolidation engine
Customer payment Accounts Receivable Customer check/EFT receipts, bank deposits, AR settlements Cash & Bank / AR
Vendor invoice recording Accounts Payable Initial registration of incoming vendor invoices (Invoice Register) AP Invoice Register
Vendor invoice approval Accounts Payable Financial distribution and posting of registered invoices AP Invoice Approval
Vendor disbursement Accounts Payable Outbound vendor payment runs, check printing, ISO 20022 XML EFT Cash & Bank / AP
Fixed assets Fixed Assets Asset acquisitions, adjustments, monthly depreciation runs, disposals Fixed Asset books
- Fixed asset budget Fixed Assets Asset capital expenditure budgeting and planned depreciation Asset Budgeting
- Budget Budgeting Budget register entries (Original, Amendment, Transfer) Budget Control engine
Asset lease Asset Leasing IFRS 16 / ASC 842 lease initial recognition, liability amortization Asset Leasing engine
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
- Parameter In Connection with Balance At Transaction Date Upon Posting
- Voucher Assigned When Line creation / Balancing Line creation / Date entry Final transaction commit (Posting)
Handling of Aborted Lines Creates gaps or status list locks Creates gaps or status list locks Zero gaps; temporary IDs simply discarded
Database Lock Contention High (locks sequence table during typing) High (locks sequence table during typing) Low (locks sequence only at commit)
Temporary Voucher ID Shown No (Official ID shown immediately) No (Official ID shown immediately) Yes ( *TEMP-XXXX* shown during edit)
Audit Gap Risk Moderate to High Moderate Virtually Zero
Recommended Workloads Low-volume single-user journals Statutory date-sequenced invoices High-volume GL, batch imports, integrations
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.