Study guide
5.2 Journal Control & Posting Restriction Rules
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.2 Journal Control & Posting Restriction Rules
Key Takeaways Explain This Topic AI
Journal control restricts which company accounts, account types, and segment values may be used on a specific journal name.
Journal control restrictions apply per account structure, not globally — if the ledger has two structures, restricting one leaves the other unrestricted (Microsoft Learn, Create advanced rules for journals).
Journal control is open by default: with no rows defined, every account type and segment value is allowed.
Posting restrictions on the journal name limit posting to a named user group, allowing juniors to prepare and only managers to post.
Last updated: August 2026
5.2 Journal Control & Posting Restriction Rules
Quick Summary: Journal control and posting restrictions are the two governance layers on a journal name: one limits which accounts and dimension values may be entered, the other limits who may post. This section covers both, including the per-account-structure scoping rule that most candidates get wrong.
1. Journal Control Rules (Account Types & Dimension Governance)
Journal Control allows organizations to restrict the types of accounts and mandatory financial dimension segments permitted on a specific journal name, preventing erroneous postings and enforcing data segregation.
Navigation
Path: General ledger > Journal setup > Journal names > select record > click Journal control button in the Action Pane. +-----------------------------------------------------------------------------+
- | Journal Control Rules Setup |
- +-----------------------------------------------------------------------------+
- | Rule 1: Account Type Restriction |
- | - Allowed Account Types: [Ledger] |
- | - Blocked Account Types: [Customer, Vendor, Bank, Fixed assets, Project] |
- +-----------------------------------------------------------------------------+
- | Rule 2: Segment Dimension Governance |
- | - Segment: Department --> Operator: [Is not blank] |
- | - Segment: BusinessUnit --> Operator: [Equal to '001', '002'] |
- +-----------------------------------------------------------------------------+
- Key Capabilities of Journal Control
Account Type Restrictions: Restricts journal entry lines to designated account types.
Real-World Example: Create a journal name GL-DAILY configured with a Journal Control rule permitting only Account type = Ledger . If a user attempts to select Customer or Vendor as the account type on a line, the system throws a validation block. This guarantees that subledger transactions are never entered through daily GL journals.
Cash Control Example: Create a BANK-ADJ journal allowing only Account type = Bank and Offset account type = Ledger .
Financial Dimension Segment Rules: Restricts or mandates specific financial dimensions when using the journal name.
For instance, requiring that the CostCenter segment must be populated whenever the EXP-ADJ journal name is selected.
Note
Journal Control vs. Account Structures: Account structures enforce global dimension combinations across the entire legal entity. Journal Control adds an extra layer of granular operational governance specific to a single journal name without changing global account structure rules.
2. Posting Restrictions by User Group
Posting Restrictions establish role-based operational boundaries, enforcing strict separation of duties (SoD) by determining which user groups can create, view, or post specific journal batches.
Navigation
Path: General ledger > Journal setup > Journal names > select record > click Posting restrictions button in the Action Pane. +-----------------------------------------------------------------------------+
- | Posting Restrictions Matrix |
- +------------------------------------+----------------------------------------+
- | User Group | Permission Level |
- +------------------------------------+----------------------------------------+
- | Junior_Accountants | Can Edit / Prepare Journal Lines |
- | Senior_Accountants | Can Edit & Validate Journal Lines |
- | Finance_Controllers | Can Post Journal Batches |
- +------------------------------------+----------------------------------------+
- Configuration Steps
Set How to restrict to By user group .
In the restriction grid, add the designated User groups (configured under System administration > Users > User groups ).
Assign specific functional toggles:
Prepare / Edit: Authorizes group members to create new journal headers and enter lines.
Post: Authorizes group members to execute the final posting process to the General Ledger.
Operational Benefits & Workflow Integration
Separation of Duties: Junior accounting staff can prepare complex payroll or accrual entries using the PAY-ACCR journal name, but clicking Post returns an access denied error. Only members of the Finance_Controllers group possess posting rights.
Workflow Automation Alternative: When paired with the Journal approval workflow ( Approval FastTab on Journal names), posting can be locked until an automated multi-tiered approval hierarchy (e.g., Manager > Controller) signs off on the journal voucher batch.
3. Exam Traps & Real-World Best Practices
Warning
Exam Trap: Voucher Number Allocation Timing and Database Concurrency MB-310 questions frequently present high-volume transaction scenarios where users experience database deadlocks during journal entry. Selecting "Continuous number sequence with allocation in connection with balance" is a major trap! To achieve high-throughput concurrency and prevent numbering gaps from aborted journals, the consultant must configure Number allocation at posting = Upon posting with a Non-continuous number sequence.
Important
Consultant Pro-Tip: Journal Control vs. 'Do Not Allow Manual Entry' While the Main Account toggle Do not allow manual entry permanently blocks manual entry across all journals, Journal Control provides surgical, journal-specific governance. For example, you can allow manual entries to a payroll clearing account only when using the PAY-ADJ journal name, while blocking all other general journal names from touching that account.
4. The Per-Account-Structure Scoping Rule
This is the single most misunderstood behaviour in journal control, and Microsoft calls it out explicitly.
Journal control restrictions apply per account structure, not globally across the ledger.
The consequences are precise:
If no journal control segment values are specified for an account structure, all values for all segments of that structure are allowed. Journal control is open by default .
Adding a restriction for one account structure restricts only that structure. Every other structure on the ledger stays wide open.
To genuinely restrict a dimension value, you must add journal control segment values for every account structure assigned to the ledger.
Worked Example
A ledger has two active account structures:
- Structure Main account range
- BS-Structure 100000..199999
- PL-Structure 600000..699999
An administrator configures journal control on journal name GL-ADJ allowing only main accounts 110000..130000 on BS-Structure , expecting the journal to be locked down. In practice, a user can still post to any account in 600000..699999, because PL-Structure has no restriction row at all. The journal is not secured until a second restriction row is added for PL-Structure .
5. Configuring Journal Control
General ledger > Journal setup > Journal names , select the journal name, then Journal control on the Action Pane.
On Which company accounts can be posted , add the legal entities the journal may be used in.
On Which account types can be posted , restrict to Ledger when the journal must never touch Customer, Vendor, Bank, Fixed asset, or Project account types.
On Which segment values are valid for this journal , pick the account structure , the segment , and the allowed values — repeating for every structure on the ledger.
6. Journal Control vs. Posting Restrictions vs. Security
Three different mechanisms are easy to confuse on a case study:
Mechanism Question it answers Where configured
Journal control Which accounts and dimension values may be entered on this journal? Journal name > Journal control
Posting restrictions Which users are allowed to post this journal? Journal name > Posting restrictions (user group)
Security roles / duties Which users can open the journal form at all? System administration > Security
A requirement that "junior accountants may prepare but only managers may post" is a posting restriction on a user group — not a security role change and not journal control. A requirement that "this journal may only be used for ledger accounts" is journal control . Matching the requirement to the right mechanism is exactly what the drag-and-drop items in this domain test.