Study guide
3.1 Company Information, Number Series & Job Queues
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
3.1 Company Information, Number Series & Job Queues
Key Takeaways Explain This Topic AI
The Company Information card (Page 1) centralizes legal entity metadata, default banking coordinates, communication details, brand logos, and Intercompany (IC) Partner Codes required for cross-company document routing.
Number Series lines govern sequential document numbering, chronological audit integrity via Date Order enforcement, warning thresholds before exhaustion, and fiscal year versioning using Starting Dates.
Number Series Relationships enable users to dynamically select from related numbering sequences (such as regional, domestic, or customer-tier series) when generating new master records or documents.
Job Queue Entries automate background batch execution for Codeunits and Reports, providing automated retry counts, rerun delays for transient error recovery, and background posting.
Last updated: September 2026
Company Information, Number Series & Job Queues
Exam Focus: In the MB-800 certification exam, candidates are expected to demonstrate deep mastery of legal entity configuration on the Company Information card, the setup and operational controls of Number Series (including date order enforcement, manual numbering overrides, and relationships), and the administration of Job Queue Entries for resilient background processing and asynchronous document posting.
Every Microsoft Dynamics 365 Business Central deployment begins with establishing the core identity of the legal entity, establishing rigid transactional numbering rules to meet statutory audit standards, and configuring asynchronous job execution. This section covers the fundamental configuration pillars that ensure operational integrity and compliance across all financial and operational modules.
1. Company Information Setup & Entity Governance
The Company Information page ( Page 1 ) serves as the central repository for master data defining the operating legal entity. The data maintained here directly populates headers, footers, tax blocks, and payment instructions on all outbound customer- and vendor-facing documents (such as Sales Invoices, Purchase Orders, and Remittance Advices), while also driving system-level integrations.
Step-by-Step Configuration Paths
To access and configure Company Information, search for Company Information via the Tell Me feature ( Alt+Q ) or navigate via Settings > Company Information .
FastTab Critical Fields Operational & Functional Impact
General Name , Address , Address 2 , City , Post Code , Country/Region Code , Picture (Company Logo), IC Partner Code Defines legal business identity. The Picture field stores the brand logo printed across all external reports. The IC Partner Code links this company to the intercompany network for cross-entity trade.
Communication Phone No. , Email , Home Page Printed on customer communications, order confirmations, and report letterheads.
Payments Bank Name , Bank Branch No. , Bank Account No. , SWIFT Code , IBAN , Giro No. , Payment Routing No. Injected into the footer of outbound sales invoices, collection letters, and electronic payment files. Establishes primary remittance coordinates for customer payments.
Shipping Ship-to Address , Location Code , Shipment Method Code , Shipping Agent Code Determines the company's default delivery address and primary physical inventory location when creating incoming purchase orders or transfer shipments.
Registration VAT Registration No. , Enterprise No. , Registration No. , Industrial Classification , Tax Representative Ensures statutory tax compliance. VAT Registration No. is validated against national or VIES registries and printed on all fiscal tax invoices.
Enterprise Multi-Site Nuance: Company Information vs. Responsibility Centers
While the Company Information card establishes the global default address and bank coordinates for the legal entity, multi-branch organizations often operate regional sales offices or distribution hubs. In Business Central, Responsibility Centers override Company Information on sales and purchase documents when assigned to specific users or customers:
If a user has an assigned Sales Resp. Ctr. Filter in User Setup , sales documents created by that user inherit the address, communication, and location coordinates of that Responsibility Center rather than the global Company Information record.
For intercompany consolidation and statutory tax filings, however, the central legal entity parameters on Company Information always take precedence.
2. Number Series Architecture & Master Configuration
Number Series are fundamental to internal controls and legal compliance in ERP systems. In many jurisdictions, commercial law and tax authorities mandate that all posted financial transactions (such as sales invoices and general ledger registers) follow an unbroken, strictly chronological sequential numbering scheme.
Anatomy of the Number Series Card and Lines
A Number Series consists of a Header ( No. Series table) and one or more Lines ( No. Series Line table). The header defines the identifying code and behavioral defaults, while the lines define the actual numerical ranges, starting dates, and sequential constraints.
Field Name Location Functional Purpose & System Behavior
Code Header Unique identifier (e.g., S-ORD for Sales Orders, S-INV for Sales Invoices, CUST for Customers). Maximum 20 alphanumeric characters.
Description Header Descriptive title clarifying where and how the sequence is applied.
Default Nos. Header When enabled ( true ), the system automatically assigns the next sequential number when a user inserts a new record or presses Enter in the No. field.
Manual Nos. Header When enabled ( true ), permits users to manually type a custom identifier instead of accepting the automated sequential number. If set to false , manual typing is strictly prevented.
Starting Date Lines Allows versioning a number series over time. If an organization requires invoice numbers to restart every calendar year (e.g., 2026-0001 ), multiple lines can be defined with distinct Starting Date values (e.g., 01/01/2025 , 01/01/2026 ). Business Central automatically draws numbers from the line whose Starting Date is on or before the document's Work Date.
Starting No. Lines The first number in the sequence (e.g., 1000 , INV26-00001 ). Must match alphanumeric pattern requirements.
Ending No. Lines The upper boundary of the sequence. Once this number is reached, Business Central prevents the generation of further records using this series until the range is extended.
Last No. Used Lines System-maintained counter displaying the most recently assigned value. Updating this field directly is restricted during active operations to maintain audit integrity.
Warning No. Lines A threshold number (e.g., INV26-09500 when the end is INV26-10000 ). When this number is assigned, the system presents a non-blocking notification warning administrators that the series is nearing exhaustion.
Increment-by Lines The step value added to generate each successive number. Defaults to 1 .
Date Order Lines When enabled ( true ), Business Central strictly enforces that documents assigned numbers from this line must have document/posting dates equal to or later than the date of the previously assigned number.
Date Order Enforcement in Audit Compliance
When Date Order is checked on a Number Series Line:
When a record is assigned a number (e.g., Posting Date 2026-03-15 , assigned INV-10045 ), the system caches the assigned date.
If a subsequent user attempts to post an invoice with Posting Date 2026-03-10 using the same series, Business Central throws a critical validation error: "You cannot post because the Posting Date is earlier than the Posting Date on the previously posted document."
This setting is mandatory for posted document series in statutory accounting environments (e.g., Italy, Spain, France) to prevent backdated invoices from disrupting chronological invoice reporting.
Setup Matrix: Default Nos. vs. Manual Nos.
Understanding how Default Nos. and Manual Nos. interact is essential for configuring user entry restrictions: +--------------------------------------------------------------------------------+
- | Default Nos. = TRUE | Manual Nos. = FALSE | Pure Automation (Standard Documents) |
- | | | System auto-assigns next number; user |
- | | | cannot overwrite or type custom numbers. |
- +--------------------------------------------------------------------------------+
- | Default Nos. = TRUE | Manual Nos. = TRUE | Hybrid / Flexible Entry |
- | | | System auto-assigns next number, but |
- | | | authorized users can backspace and type |
- | | | a custom code if needed. |
- +--------------------------------------------------------------------------------+
- | Default Nos. = FALSE | Manual Nos. = TRUE | Pure Manual Entry (Vendor Invoices) |
- | | | System does not auto-populate number. |
- | | | User must explicitly input the code. |
- +--------------------------------------------------------------------------------+
- | Default Nos. = FALSE | Manual Nos. = FALSE | Blocked / Inaccessible Configuration |
- | | | Neither system nor user can populate |
- | | | numbers. Results in validation error. |
- +--------------------------------------------------------------------------------+
- 3. Number Series Relationships & Setup Integration
In standard functional setup, master configuration pages (such as Sales & Receivables Setup and Purchases & Payables Setup ) allow you to designate only a single Number Series code for each document type (e.g., Customer Nos. = CUST ).
However, enterprises frequently require distinct numbering sequences for different customer segments, such as Domestic, European Union, and International Export accounts.
Configuring Number Series Relationships
To allow users to select from alternative numbering sequences without altering system setup:
Create the primary number series (e.g., CUST ).
Create the specialized secondary number series (e.g., CUST-DOM , CUST-EU , CUST-EXP ).
Open the primary CUST series on the No. Series page.
Select Navigate > Relationships .
In the No. Series Relationships page, insert the related series codes: CUST-DOM , CUST-EU , and CUST-EXP .
Operational Result: When a user creates a new Customer card, the No. field initially displays the default CUST sequence. If the user clicks the AssistEdit button ( ... ) next to the No. field, a modal window opens displaying the related series list ( CUST-DOM , CUST-EU , CUST-EXP ). Selecting an option assigns the next available number from that specific series.
Unposted vs. Posted Number Series Separation
A universal best practice and core MB-800 concept is maintaining distinct Number Series for unposted working documents versus posted financial ledgers:
Sales & Receivables Setup :
Order Nos. ( S-ORD ) generates numbers for unposted sales orders.
Invoice Nos. ( S-QUO / S-INV-TEMP ) generates working numbers for unposted sales invoices.
Posted Invoice Nos. ( PS-INV ) generates permanent, immutable numbers assigned upon posting.
Posted Shipment Nos. ( PS-SHPT ) generates delivery tracking numbers upon posting shipments.
Posted Credit Memo Nos. ( PS-CRMEMO ) generates posted credit numbers.
This separation guarantees that deleting or voiding an unposted sales order does not create gaps in the permanent general ledger register.
Performance Optimization: Allow Gaps in Nos.
By default, Business Central locks the No. Series Line table in SQL Server during number assignment to guarantee that numbers are strictly contiguous without gaps. In high-volume environments (such as webshop order ingestion), this table locking can introduce thread contention.
Enabling the Allow Gaps in Nos. toggle changes the underlying mechanism from database row-locking to an uncommitted SQL sequence. This dramatically improves insertion throughput but means that if a transaction is rolled back or aborted, the consumed number is discarded, leaving an intentional gap. Warning: This setting should never be used for posted invoice series subject to legal gap-free compliance audits.
4. Job Queues & Background Processing
Business Central relies on Job Queues to execute automated, scheduled, and asynchronous workloads. Through Job Queues, administrative routines, report generation, exchange rate updates, and heavy document postings run in background worker sessions without degrading interactive user interface performance.
Core Architecture: Job Queue Entries
A Job Queue Entry ( Page 672 ) defines the workload parameters, scheduling frequency, and execution target.
Setting / Field Technical Definition & Capabilities
Object Type to Run Specifies the AL execution object: Codeunit or Report . Codeunits execute core transactional processing, posting routines, or API synchronizations. Reports execute batch dataset calculations or generate scheduled output documents (PDF, Excel).
Object ID to Run The numerical ID of the AL object (e.g., Codeunit 80 for Sales-Post , Codeunit 8835 for Post Sales Batch , Codeunit 5330 for CRM Integration Table Synch ).
Report Request Page When running a Report, toggling this option allows the consultant to pre-define filters, options, and output formats (PDF, Word, Excel, Print) saved into the job definition.
Parameter String An optional text string passed to the running AL object, allowing dynamic filtering or behavioral flags without writing custom code.
Earliest Start Date/Time The exact timestamp before which the background task must not run.
Recurring Job Checkbox indicating that the job automatically reschedules itself according to defined recurrence rules upon completion.
No. of Minutes between Runs The idle interval between completed execution and the next scheduled run (e.g., 60 for hourly execution).
Inactivity Timeout Period Number of minutes after which an idle recurrent job is automatically placed On Hold to prevent unnecessary resource consumption when no new records exist.
Resiliency, Retries & Error Handling
Background processes in complex ERP systems occasionally encounter temporary failures, such as SQL database deadlocks during month-end closes or momentary third-party web service dropouts. If unmanaged, a single locked record would set the Job Queue status to Error and halt all subsequent runs.
To build resilient background routines:
Maximum No. of Attempts to Run : Specifies how many times Business Central retries a failed execution (e.g., 3 or 5 ) before finally marking the status as Error .
Rerun Delay (sec) : The pause interval in seconds (e.g., 30 seconds) the system waits before attempting a retry. During this retry window, the entry status is set to Waiting .
Job Queue Log Entries ( Page 673 ): Captures comprehensive historical logs of every execution, including Start Date/Time , End Date/Time , Status ( Success or Error ), execution duration, and the full text error callstack if an execution fails.
Background Document Posting Setup
To prevent the user interface from freezing while validating inventory availability and calculating general ledger postings, Business Central supports asynchronous background posting:
Navigate to Sales & Receivables Setup or Purchases & Payables Setup .
Locate the Post with Job Queue boolean field and toggle it to true .
In Job Queue Category Code , assign a dedicated queue category (e.g., SALESPOST ).
When a user clicks Post on a Sales Order, the order is flagged as Posting In Progress and queued. A background Job Queue Entry picks up the order, executes Codeunit 80 ( Sales-Post ), and updates the order status to Posted .
5. Common Implementation Pitfalls & Exam Traps
Pitfall 1: Modifying Starting No. on an Active Series. Changing the Starting No. on an active series line after transactions have posted can corrupt alphanumeric sequencing or cause collision errors with existing records. Consultants must adjust Ending No. or create a new line with a future Starting Date .
Pitfall 2: Bypassing Date Order on Fiscal Documents. Enabling Date Order on the unposted order series ( S-ORD ) instead of the posted invoice series ( PS-INV ). Sales orders are frequently created out of chronological sequence due to customer revisions; Date Order should be enforced strictly on the Posted series to satisfy audit rules without impeding day-to-day quote/order entry.
Pitfall 3: Failing to Link Relationships. Creating secondary series like CUST-EXPORT without linking them to CUST via Navigate > Relationships . As a result, users cannot choose the secondary series from the Customer card No. AssistEdit menu.
Pitfall 4: Neglecting Inactivity Timeout. Leaving high-frequency job queues (e.g., every 1 minute) running continuously on low-volume staging tables without configuring Inactivity Timeout Period , causing system log bloat and redundant compute usage.