Study guide
9.2 General Journal Templates, Batches & Number Series
Microsoft Dynamics 365 Business Central Functional Consultant MB-800
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Company Creation & Data Migration
1.1 Creating Companies & Assisted Setup Wizards 1.2 Configuration Packages & RapidStart Worksheets 1.3 Opening Balances & Data Migration Strategies
2 Chapter 2: Security, Profiles & Auditing
2.1 Users, User Setup & Role Center Profiles 2.2 Permission Sets & Security Group Management 2.3 Security Filters, Change Log & Security Auditing
3 Chapter 3: Core System Configuration, Number Series & Copilot
3.1 Company Information, Number Series & Job Queues 3.2 Report Layout Management & Copilot AI Capabilities
4 Chapter 4: Dimensions Architecture & Governance
4.1 Dimension Concepts & Dimension Values 4.2 Global Dimensions vs Shortcut Dimensions 4.3 Default Dimensions, Combinations & Priorities
5 Chapter 5: Workflows & Approvals
5.1 Native Workflow Templates & Approval Hierarchy 5.2 Workflow User Groups & Notification Configuration
6 Chapter 6: Financial Setup, Periods & Currencies
6.1 General Ledger Setup & Accounting Periods 6.2 Payment Terms, Payment Methods & Deferrals 6.3 Multi-Currency Setup & Exchange Rates
7 Chapter 7: Chart of Accounts, Categories & Allocations
7.1 Chart of Accounts Structure & G/L Account Cards 7.2 Account Categories, Subcategories & Financial Reporting 7.3 General Ledger Allocation Accounts & Sharing
8 Chapter 8: Posting Groups & Posting Setup
8.1 Specific Posting Groups: Customer, Vendor, Bank & Inventory 8.2 General Posting Groups & General Posting Setup Matrix 8.3 Inventory Posting Setup & Alternative Posting Groups
9 Chapter 9: General Journals & Recurring Methods
9.1 Bank Account Cards & Posting Setup 9.2 General Journal Templates, Batches & Number Series 9.3 Recurring General Journals & Allocation Methods
10 Chapter 10: Accounts Payable & Accounts Receivable Setup
10.1 Purchases & Payables Setup & Vendor Master 10.2 Sales & Receivables Setup & Customer Master 10.3 Payment Journals, Cash Receipts & Payment Registration Setup
11 Chapter 11: Fixed Assets Setup & Depreciation Books
11.1 Fixed Asset Setup, Classes & Depreciation Books 11.2 Fixed Asset Cards, Main/Component Assets & Depreciation Methods
12 Chapter 12: Inventory Setup, Costing & Locations
12.1 Inventory Setup, Item Types, Categories & Variants 12.2 Costing Methods (FIFO, LIFO, Average, Standard) & Ledger Architecture 12.3 Locations, Transfer Routes & Stockkeeping Units (SKUs)
13 Chapter 13: Logistics Master Data, Pricing & Discounts
13.1 Shipping Agents, Locations & Vendor Lead Times 13.2 Sales Prices, Purchase Prices & Price Lists 13.3 Line Discounts, Invoice Discounts & Thresholds
14 Chapter 14: User Interface, Views, Inspection & Excel
14.1 Personalization, Profile Customization & Designer 14.2 Searching, Advanced Filters, Saved Views & Page Inspection 14.3 Edit in Excel, OneDrive & Data Analysis Mode
15 Chapter 15: Purchase & Sales Order Execution
15.1 Purchase Orders, Receiving, Over-Receipt & Undo 15.2 Purchase Invoicing, Recurring Lines & Blanket Orders 15.3 Sales Quotes, Availability Checks & Order Conversion 15.4 Sales Shipping, Invoicing, Undo & Blanket Orders
16 Chapter 16: Invoices, Credit Memos & Document Corrections
16.1 Direct Invoices, Credit Memos & Document Reopening 16.2 Correct, Cancel & Corrective Credit Memo Procedures 16.3 Combined Shipments/Receipts & Prepayment Workflows
17 Chapter 17: Cash Management, Bank Reconciliation & Ledger Applications
17.1 Processing Payment Journals & Cash Receipt Registrations 17.2 Applying, Unapplying & Reversing Customer/Vendor Entries 17.3 Bank Account Reconciliation & Statement Matching Rules
18 Chapter 18: Operational Adjustments, Inventory & Asset Accounting
18.1 Exchange Rate Adjustments & Dimension Corrections 18.2 Inventory Adjustments, Transfers & Physical Counting 18.3 Fixed Asset Acquisitions, Depreciation Runs & Disposals
9.2 General Journal Templates, Batches & Number Series
Key Takeaways Explain This Topic AI
General Journal Templates (Page 101) establish the high-level operational rules, accounting classification, and assigned UI page through the Type field (e.g., General, Cash Receipts, Payments, Intercompany).
General Journal Batches (Page 251) divide templates into discrete user workspaces and can pre-populate default balancing accounts (Bal. Account Type and No.) to enable rapid single-line entry.
The Force Doc. Balance toggle on a journal template mandates that all journal lines sharing the same Document No. and Posting Date must balance to zero before posting is permitted.
Number Series can be defined on templates and overridden at the batch level; assigning a Posting No. Series guarantees an uninterrupted, chronological audit trail on posted ledger entries.
Posting Preview (Ctrl+Alt+F9) and the Journal Errors FactBox simulate transaction outcomes and surface validation errors in real time without writing to the database.
Last updated: September 2026
9.2 General Journal Templates, Batches & Number Series
Quick Summary: Financial transaction entry in Dynamics 365 Business Central is organized across a two-tier hierarchy consisting of General Journal Templates (Page 101) and General Journal Batches (Page 251). Templates define the functional nature, system window (Page ID), and posting rules (such as Force Doc. Balance ), while batches serve as individual user workspaces. Batches can define default balancing accounts to support single-line balanced entries or allow multi-line balanced vouchers. Configuring a separate Posting No. Series on batches ensures gapless chronological numbering on posted ledger entries. Prior to committing transactions, consultants leverage Posting Preview ( Ctrl+Alt+F9 ) and real-time error checking to inspect proposed ledger impacts.
The Two-Tier Journal Architecture
All financial transactions in Business Central that do not originate from dedicated commercial documents (such as Sales Invoices or Purchase Orders) route through the General Journal system (Table 81 Gen. Journal Line ).
To manage permissions, segregate accounting duties, and tailor user interfaces for specific accounting tasks, Business Central separates journals into two hierarchical levels: Journal Architectural Hierarchy:
- General Journal Template (Table 80 / Page 101)
- │ - Defines functional Type (General, Payments, Cash Receipts)
- │ - Assigns Page ID, Source Code, and Force Doc. Balance
- │
- ├──► General Journal Batch: 'DEFAULT' (Table 232 / Page 251)
- │ │ - User workspace, default balancing account, No. Series
- │ └──► Gen. Journal Lines (Table 81 / Page 39)
- │
- └──► General Journal Batch: 'PAYROLL'
- │ - Dedicated No. Series, specific balancing bank account
- └──► Gen. Journal Lines (Table 81 / Page 39)
- General Journal Templates (Page 101)
A General Journal Template establishes the foundational rules, underlying database behavior, and visual presentation for all batches created beneath it. Templates are managed on the General Journal Templates page ( Alt+Q -> type General Journal Templates ). UI Navigation Path:
- Tell Me (Alt+Q) -> General Journal Templates (opens Page 101)
- Critical Template Fields
Name: A unique alphanumeric code (up to 10 characters) identifying the template (e.g., GENERAL , PAYMENT , CASHRCPT , ASSETS , INTERCOMP ).
Description: A clear functional description of the template's purpose.
Type: A system option that governs business validation logic and controls which fields appear on journal lines:
General: Standard general ledger entries, accruals, and adjustments.
Sales: Direct customer receivable adjustments and sales invoices without inventory tracking.
Purchases: Direct vendor payable adjustments and purchase invoices without inventory tracking.
Cash Receipts: Incoming customer payments, bank deposits, and cash collections.
Payments: Outgoing vendor disbursements, check printing, and electronic bank payments.
Assets: Fixed asset acquisitions, depreciations, and disposals.
Intercompany: Transactions between affiliated entities linked via Intercompany Partners.
Jobs: Project cost adjustments and resource usage entries.
Page ID: The numerical object ID of the user interface page rendered when opening a batch under this template. For example, standard General templates render Page 39 ( General Journal ), Cash Receipts render Page 255 ( Cash Receipt Journal ), and Payments render Page 256 ( Payment Journal ).
Recurring: A boolean toggle. When set to Yes , lines are not deleted from the journal after posting, and recurring date formulas become active (rendering Page 283 Recurring General Journal ).
Source Code: An audit trail identifier (Table 230 Source Code ) stamped onto all G/L Register and ledger records posted from this template (e.g., GENJNL , PAYMENTJNL , CASHRCJNL ).
Reason Code: A default business reason code copied to journal lines to explain the commercial purpose of entries.
Force Doc. Balance: A vital accounting control toggle:
When Enabled (Yes): Business Central mandates that all journal lines sharing the exact same Document No. and Posting Date must balance to zero (debits equal credits). If a document is out of balance by even one cent, posting is blocked.
When Disabled (No): Individual document numbers do not need to balance independently, provided that the entire journal batch balances to zero overall. This allows multi-document, complex compound entries.
General Journal Batches (Page 251)
Within each template, organizations create one or more General Journal Batches ( Alt+Q -> type General Journal Templates -> select template -> choose Batches action, opening Page 251). Batches serve as independent workspaces where individual accountants or departments stage transactions concurrently without file contention or data collision. UI Navigation Path:
- Tell Me (Alt+Q) -> General Journal Templates -> Select Row -> Action: Navigate -> Batches
- Key Batch Configuration Parameters
Name & Description: The unique workspace identifier (e.g., ALEX , MONTHEND , PAYROLL ) and narrative title.
Bal. Account Type & Bal. Account No.: Establishes a default offset account for every line keyed into the batch. Supported account types include G/L Account , Customer , Vendor , Bank Account , Fixed Asset , and IC Partner .
No. Series: Specifies the Number Series code from which Document No. values are sequentially assigned as lines are inserted into the journal.
Posting No. Series: Specifies a distinct Number Series code used to re-number and stamp posted ledger entries upon posting.
Suggest Balancing Amount: A boolean helper flag. When entering multi-line transactions with the same Document No., Business Central calculates the remaining unbalanced amount and automatically populates the Amount field on the next line with the required offsetting value (with inverted sign).
Copy VAT Setup to Jnl. Lines: When checked, VAT calculation rules, VAT business posting groups, and VAT product posting groups are automatically derived from the selected G/L Account or balancing account.
Allow Payment Export: Mandatory on batches under Payment templates where users intend to export electronic payment files (EFT, NACHA, SEPA Credit Transfer).
Number Series Architecture: Regular vs. Posting No. Series
A critical functional governance capability in Business Central is the dual number series architecture: Number Series Flow:
- [Journal Line Entry]
- │ Document No. assigned from Batch 'No. Series' (e.g., 'DRAFT-0010')
- ▼
- [Journal Line Edited / Deleted / Re-ordered]
- │ (Potential gaps in line numbering occur if lines are deleted)
- ▼
- [Post Transaction Action]
- │
- ▼
- [Ledger Entries Created]
- │ Document No. reassigned from Batch 'Posting No. Series' (e.g., 'GL-2026-9001')
- └──► Guarantees continuous, gapless, chronological legal numbering
- The Operational Problem Solved by Posting No. Series
When users draft journal entries, they frequently create lines, delete erroneous entries, or leave journals unposted for weeks while awaiting manager approval. If the journal line Document No. (assigned from No. Series ) were stamped directly onto the permanent general ledger, the legal ledger would contain numbering gaps or out-of-sequence dates—a severe regulatory violation under European GAAP, Spanish SII, French FEC, and global audit standards.
By assigning a separate Posting No. Series on the batch:
The journal lines use the preliminary No. Series (e.g., DRAFT-0001 through DRAFT-0050 ) while being drafted and approved.
At the exact moment of posting, Business Central consumes the next available number from Posting No. Series (e.g., GL-2026-10401 ) and stamps this continuous number onto the resulting G/L Entry , Bank Account Ledger Entry , and Cust./Vend. Ledger Entry records.
The posted records remain perfectly sequential, chronological, and gap-free.
Voucher Architectures: Single-Line vs. Two-Line Balanced Entries
Business Central supports two distinct voucher design models for entering balanced financial transactions:
- Operational Attribute Single-Line Balanced Entry Two-Line (Multi-Line) Balanced Voucher
- Grid Structure 1 row in the journal grid 2 or more rows in the journal grid
Account Definition Account Type and Account No. specify the primary side; Bal. Account Type and Bal. Account No. specify the offset. Account Type and Account No. are defined on each line; Bal. Account Type and Bal. Account No. are left BLANK .
Document No. Unique per line (or shared across lines). Identical Document No. shared across all lines in the voucher.
Amount Sign Signed based on the primary account (Positive = Debit, Negative = Credit). Offsetting account receives exact opposite posting automatically. Line 1 has positive amount (Debit); Line 2 has negative amount (Credit). The sum of all line amounts must equal 0.00 .
Best Practice Use Case Repetitive standard transactions: vendor invoice payments from a bank account, customer receipt deposits, simple one-to-one expense allocations. Compound journal entries: payroll distributions, multi-department expense splits, sales tax adjustments, compound asset acquisitions.
Example: Paying a $500 Office Supply Vendor Invoice
Method A: Single-Line Balanced Entry Line 1: Posting Date = 09/15/2026 | Doc No = PMT101 | Account Type = Vendor | Account No = V10020
Amount = 500.00 | Bal. Account Type = Bank Account | Bal. Account No = BNK-01
Result: Debits Vendor V10020 for $500; Credits Bank Account BNK-01 for $500 in a single line.
Method B: Two-Line Balanced Voucher Line 1: Posting Date = 09/15/2026 | Doc No = PMT102 | Account Type = Vendor | Account No = V10020
- Amount = 500.00 | Bal. Account Type = [BLANK] | Bal. Account No = [BLANK]
- Line 2: Posting Date = 09/15/2026 | Doc No = PMT102 | Account Type = Bank Account | Account No = BNK-01
- Amount = -500.00 | Bal. Account Type = [BLANK] | Bal. Account No = [BLANK]
Result: Both lines share Document No. PMT102 . The net batch amount is $0.00. Posting executes successfully.
Pre-Posting Governance: Posting Preview, Error Checking & Background Posting
To ensure financial accuracy and eliminate posting failures, Business Central equips general journals with advanced validation and diagnostic tools:
1. Posting Preview ( Ctrl+Alt+F9 )
Selecting Posting Preview executes the complete posting routine in an isolated temporary SQL transaction. Business Central runs all validation triggers, tests posting date boundaries, verifies dimension rules, and calculates VAT, rendering a comprehensive list of all entries that would be created across every underlying ledger:
- G/L Entry
- Bank Account Ledger Entry
- Cust. Ledger Entry / Vendor Ledger Entry
- Detailed Cust. Ledg. Entry / Detailed Vendor Ledg. Entry
- VAT Entry
Consultants can drill down into each ledger table from the preview window to inspect debit/credit amounts and dimension assignments. Once closed, the transaction is rolled back, leaving live tables completely untouched.
2. The Journal Errors FactBox
When enabled via the Show Errors to Check action, the web client renders a dedicated Journal Errors FactBox on the right side of the screen. Business Central runs background validation routines in real time as users type, instantly displaying actionable error messages:
Document number out of balance under Force Doc. Balance .
Missing mandatory dimensions according to Dimension Value Posting rules ( Code Mandatory ).
Posting Date outside the user's Allow Posting From and Allow Posting To window.
Closed G/L accounts or blocked posting groups.
3. Background Journal Posting
For high-volume journal batches (e.g., thousands of e-commerce settlements or large payroll runs), organizations enable Post with Job Queue in General Ledger Setup . Rather than locking the user's browser during synchronous processing, Business Central packages the batch, submits it to a background Job Queue Entry, and notifies the user upon completion, keeping the client responsive.
Common Implementation Pitfalls & Exam Traps
Implementation Issue Root Cause System Impact Corrective Action
Posting Blocked: Document Out of Balance Force Doc. Balance is checked on the Template, and lines sharing a Document No. have unequal debits and credits. System throws error: "Document No. [X] is out of balance by [Y]." Batch posting halts. Adjust line amounts to balance each Document No. individually, or uncheck Force Doc. Balance on the Template if compound multi-doc vouchers are permitted.
Missing Default Balancing Account Accountant expects single-line entries, but Bal. Account No. is left blank on the Batch card. Users must manually type offset accounts on every row, or posting fails with unbalanced line errors. Populate Bal. Account Type and Bal. Account No. on the General Journal Batch card.
Number Series Gaps on Legal Registers Only No. Series is defined on the Batch; Posting No. Series is left blank. Deleted draft journal lines leave permanent numbering gaps in posted General Ledger Entries, failing legal audits. Configure and assign a dedicated Posting No. Series on the General Journal Batch.
Incorrect Journal Page Layout Template Type was set to General , but users require check printing and payment export fields. The journal opens Page 39 instead of Page 256 ( Payment Journal ), hiding payment export actions. Create a new template with Type = Payments and assign Page ID 256.