5.2 Journal Control & Posting Restriction Rules

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

1. 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.
2. 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

1. Set How to restrict to By user group.
2. In the restriction grid, add the designated User groups (configured under System administration > Users > User groups).
3. 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:

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

1. General ledger > Journal setup > Journal names, select the journal name, then Journal control on the Action Pane.
2. On Which company accounts can be posted, add the legal entities the journal may be used in.
3. 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.
4. 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:

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.