Study guide
5.3 Journal Entry, the One-Voucher Rule, Validation & Posting
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.3 Journal Entry, the One-Voucher Rule, Validation & Posting
Key Takeaways Explain This Topic AI
Journal validation can be run before posting to surface dimension, account structure, and balance errors without committing the voucher.
'Post and transfer' posts the vouchers that pass validation and moves failing vouchers to a new journal instead of blocking the whole batch.
Subledger settlement controls on the journal determine whether customer or vendor transactions are settled during posting.
The one-voucher rule governs whether all lines share a voucher, which affects both balance validation and downstream ledger settlement matching.
Last updated: August 2026
5.3 Journal Entry, the One-Voucher Rule, Validation & Posting
Quick Summary: Efficient journal processing in Microsoft Dynamics 365 Finance demands mastery over transaction entry mechanics, validation routines, error resolution workflows, transaction reversals, and external spreadsheet integration. Functional consultants must understand how to enforce the One-Voucher rule , recover from posting failures using Post and Transfer , automate period-end accrual reversals, configure Storno (correction) postings , and leverage the Microsoft Dynamics Office Add-in for high-volume Excel-based journal management.
1. General Journal Entry & Data Modeling
General journals record financial adjustments, intercompany transfers, payroll accruals, and subledger clearing transactions.
- Navigation
- Path: General ledger > Journal entries > General journals
- Journal Header vs. Lines Architecture
When a user clicks New in the General journals form:
Journal Header: The user selects a Name (e.g., GEN-ADJ ). The system generates a Journal Batch Number (e.g., JB-000450 ), stamps the current user ID, locks the journal with In use by status during editing, and defaults the configured Offset account and Posting layer.
Journal Lines: The user clicks Lines to access the detailed transaction grid. Lines can be entered using two architectural patterns: Pattern A: Single-Line Self-Balancing Entry
- +---------------------------------------------------------------------------------------------------------+
- | Voucher | Date | Account Type | Account (Main-Dim) | Debit | Offset Type | Offset Account |
- +---------+------------+--------------+--------------------+------------+-------------+-------------------+
- | VCH-001 | 2026-08-31 | Ledger | 610100-001-022 | $5,000.00 | Bank | USMF-OPER (110110)|
- +---------------------------------------------------------------------------------------------------------+
- Pattern B: Multi-Line Split Voucher Entry (Sharing Voucher ID: VCH-002)
- +---------------------------------------------------------------------------------------------------------+
- | Line 1: | 2026-08-31 | Ledger | 610100-001-022 | Debit: $3,000.00 | Offset: [Blank] |
- | Line 2: | 2026-08-31 | Ledger | 610200-001-022 | Debit: $2,000.00 | Offset: [Blank] |
- | Line 3: | 2026-08-31 | Ledger | 110110-001-000 | Credit: $5,000.00 | Offset: [Blank] |
- +---------------------------------------------------------------------------------------------------------+
- Financial Tags vs. Financial Dimensions in Journal Lines
In modern Dynamics 365 Finance releases, Financial Tags provide a lightweight mechanism for tracking transactional metadata (such as custom Purchase Order references, internal project codes, or employee IDs) on general journal lines without creating new dimension combination records in the database, preventing index bloat and boosting performance.
2. The 'One-Voucher' Rule & Subledger Settlement Controls
A critical architectural topic on the MB-310 exam is the One-Voucher restriction .
General Ledger Parameter Setup
Path: General ledger > Ledger setup > General ledger parameters > Ledger tab > Allow multiple transactions within one voucher +-------------------------------------------------------------+
- | Allow Multiple Transactions Within One Voucher |
- +-------------------------------------------------------------+
- |
- +---------------------------------------+---------------------------------------+
- | | |
- v v v
- [ Reject ] [ Accept with warning ] [ Disallow ]
- (Strict MB-310 Standard) (Legacy Migration Only) (Hard System Exception)
- Blocks mixing Customer & Vendor - Displays warning toast - Completely blocks saving
- Blocks multi-subledger vouchers - Permits voucher commit - Throws runtime error
- Why Microsoft Deprecated Multiple Subledger Transactions in One Voucher
In legacy versions (AX 2012), users could post a single voucher containing multiple customer, vendor, or fixed asset subledger transactions. In Dynamics 365 Finance, this practice causes severe architectural failures:
Settlement Failures: When cash discounts or partial payments are applied across multiple subledger records in a single voucher, the AR/AP settlement engine cannot determine which subledger line owns the cash discount or realized exchange rate gain/loss.
Sales Tax Accounting Anomalies: Tax calculations depend on the relationship between an invoice line and a vendor/customer party. Multiple parties in one voucher result in corrupted tax settlement vouchers.
Foreign Currency Revaluation: Currency revaluation calculates unrealized gains/losses per subledger transaction. Multi-party vouchers cause cross-contamination of revaluation postings.
Important
Recommended Consultant Pattern: Always set Allow multiple transactions within one voucher to Reject . To record complex settlement transactions between multiple parties (e.g., offsetting a vendor balance against a customer balance), enter separate vouchers and route the offsetting entries through an intermediate Clearing Main Account ( 210999 - Subledger Clearing ).
3. Voucher Validation, Posting & 'Post and Transfer' Error Handling
Before journal lines can update the General Ledger, they must pass comprehensive validation checks.
Validation Methods
Validate > Validate: Evaluates account structure rules, financial dimension requirements, debit/credit balancing, fiscal period statuses, and currency exchange rates without committing data.
Validate > Validate voucher only: Validates only the currently highlighted voucher lines.
Simulate posting: Runs the complete posting pipeline in memory—evaluating accounting distributions, subledger posting profiles, and tax calculations—without writing records to ledger tables.
'Post' vs. 'Post and Transfer' (Batch Error Recovery)
When posting a journal batch containing hundreds of voucher lines, errors may occur (e.g., a missing dimension, an unmapped sales tax code, or a closed period for one voucher). +---------------------------------------------------------------------------------------+
- | Journal Batch: JB-000500 (100 Vouchers) |
- +---------------------------------------------------------------------------------------+
- | Click: POST AND TRANSFER |
- +-------------------------------------------+-------------------------------------------+
- | | |
- | 95 Valid Vouchers | 5 Erroneous Vouchers (e.g., Missing Dept) |
- | - Account structures valid | - Validation rule failed |
- | - Dates in open fiscal period | |
- | | |
- | v | v |
- | +------------------------------------+ | +------------------------------------+ |
- | | Posted Immediately to GL | | | Transferred to NEW Journal: | |
- | | (Batch JB-000500 Marked Posted) | | | JB-000500-1 (Unposted Draft) | |
- | +------------------------------------+ | +------------------------------------+ |
- +-------------------------------------------+-------------------------------------------+
Standard Post: If 99 vouchers are valid but 1 voucher has an error, the entire posting job aborts, and zero vouchers are posted .
Post and transfer: The system processes all valid vouchers, commits them to the General Ledger, marks the original journal header as posted, and automatically generates a new journal batch (e.g., JB-000500-1 ) containing only the failed voucher lines! Accountants can then correct the invalid lines in the new journal and post them without delaying month-end processing.