3.1 Company Information, Number Series & Job Queues

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.

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.

Date Order Enforcement in Audit Compliance

When Date Order is checked on a Number Series Line:

1. When a record is assigned a number (e.g., Posting Date 2026-03-15, assigned INV-10045), the system caches the assigned date.
2. 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."
3. 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:

1. Create the primary number series (e.g., CUST).
2. Create the specialized secondary number series (e.g., CUST-DOM, CUST-EU, CUST-EXP).
3. Open the primary CUST series on the No. Series page.
4. Select Navigate > Relationships.
5. 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.

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:

1. Navigate to Sales & Receivables Setup or Purchases & Payables Setup.
2. Locate the Post with Job Queue boolean field and toggle it to true.
3. In Job Queue Category Code, assign a dedicated queue category (e.g., SALESPOST).
4. 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.