15.2 Purchase Invoicing, Recurring Lines & Blanket Orders

15.2 Purchase Invoicing, Recurring Lines & Blanket Orders

Quick Summary: Financial completion of procurement in Dynamics 365 Business Central involves Purchase Invoicing, which reconciles received inventory against supplier bills, liquidates interim accruals, and records Vendor Ledger Entries (Table 25). Routine procurement of standardized supplies is streamlined using Recurring Purchase Lines (Standard Purchase Lines, Page 459) configured to insert automatically or upon user prompt. Large-scale, long-term contracts are managed via Blanket Purchase Orders (Table 38 with Document Type = Blanket Order), which track total committed quantities and release partial fulfillment purchase orders via the Qty. to Receive field. Multi-period expenditures like annual service contracts are amortized across balance sheet schedules using Purchase Deferrals.

---

Purchase Order Invoicing Mechanics & Ledger Reconciliation

Invoicing converts operational warehouse receipts into formal financial liabilities. On a Purchase Order (Alt+Q -> type Purchase Orders, Page 50), the invoicing process matches the supplier's commercial bill against physical receipts.

Purchase Invoicing Reconciliation Flow:

[Physical Goods Received: Qty. Received = 100, Invt. Accrual (Interim) Credited]
                               │
                               ▼ Supplier Bill Arrives
[Purchase Order Header: Vendor Invoice No. = "INV-9942", Qty. to Invoice = 100]
                               │
                               ▼ Post (F9) -> "Invoice"
       ┌───────────────────────┴───────────────────────┐
       ▼                                               ▼
[Posted Purchase Invoice (Page 138)]        [Subledger & Financial Postings]
- Table 122 Header                          - Table 25: Vendor Ledger Entry (AP Credit)
- Table 123 Lines                           - Table 5802: Value Entry (Actual Cost)
                                            - Table 17: General Ledger Entries:
                                                Debit: Invt. Accrual (Interim) [Reversed]
                                                Credit: Inventory (Interim)    [Reversed]
                                                Debit: Inventory / Expense     [Actual]
                                                Credit: Accounts Payable       [Actual]

Critical Header Prerequisites for Invoicing

Before posting an invoice, the following header validations must be satisfied:

• Vendor Invoice No.: When Ext. Doc. No. Mandatory is checked in Purchases & Payables Setup, leaving Vendor Invoice No. blank blocks posting. This ensures every AP transaction references the vendor's external billing voucher.
• Posting Date: Dictates the general ledger accounting period and financial reporting date.
• Document Date: Reflects the supplier's invoice creation date, driving the calculation of Due Date and Pmt. Discount Date via payment terms.

The Invoicing Execution Pipeline

When posting with option Invoice:

1. The system validates that Qty. to Invoice does not exceed Quantity Received - Quantity Invoiced (unless receiving and invoicing simultaneously).
2. A Posted Purchase Invoice (Table 122 Purch. Inv. Header, Table 123 Purch. Inv. Line) is generated.
3. The interim expected cost entries in the General Ledger are reversed ($\text{Debit: Invt. Accrual Interim}$, $\text{Credit: Inventory Interim}$).
4. Actual inventory costs are posted ($\text{Debit: Inventory Account}$, $\text{Credit: Accounts Payable}$).
5. An open Vendor Ledger Entry (Document Type: Invoice) is inserted into Table 25, creating an outstanding balance payable to the vendor.
6. If the order is fully received and fully invoiced, Business Central either deletes the purchase order automatically or archives it, depending on the Archive Orders setup.

---

Recurring Purchase Lines (Standard Purchase Lines)

Organizations frequently reorder predictable groups of items, services, or freight charges from specific suppliers (e.g., monthly breakroom supplies, recurring packaging cartons, scheduled janitorial services). Rather than keying these lines manually, administrators configure Standard Purchase Lines (Alt+Q -> type Standard Purchase Lines, Page 459 / Table 173).

Recurring Purchase Lines Setup and Trigger Flow:

[Standard Purchase Code: PKG-SUPPLIES] ──► Page 459
  ├── Line 1: Item BOX-MED (Qty = 100)
  ├── Line 2: Item TAPE-CLR (Qty = 20)
  └── Line 3: G/L Account 60100 Freight (Qty = 1)
            │
            ▼ Assign to Vendor Card (Page 26 -> Recurring Purchase Lines)
[Standard Vendor Purchase Code] ──► Page 175
  ├── Insert Rec. Lines on Quotes:    [Always Ask]
  ├── Insert Rec. Lines on Orders:    [Automatic]
  ├── Insert Rec. Lines on Invoices:  [Always Ask]
  └── Insert Rec. Lines on Cr. Memos: [Manual]

Defining Standard Purchase Codes & Lines

On Page 459, users define a code (e.g., OFFICE-MONTHLY) and specify multiple lines supporting all standard line types (Comment, G/L Account, Item, Fixed Asset, Charge (Item)), units of measure, and default quantities.

Vendor Assignment & Insertion Triggers

From the Vendor Card, selecting Related -> Purchases -> Recurring Purchase Lines (Page 175 / Table 175) attaches the standard code to that specific vendor. Administrators configure how the lines are inserted across four document categories (Quotes, Orders, Invoices, Credit Memos):

• Manual: Lines are never inserted automatically; the user must explicitly choose Actions -> Functions -> Get Recurring Purchase Lines... on the document.
• Automatic: Lines are inserted automatically as soon as the vendor number is validated on a newly created document.
• Always Ask: A notification bar or prompt appears when creating the document, asking: "Recurring purchase lines exist for vendor %1. Do you want to insert them on this document?" Clicking Yes inserts the lines immediately.

---

Blanket Purchase Orders (Master Call-Off Agreements)

A Blanket Purchase Order (Alt+Q -> type Blanket Purchase Orders, Page 509 / Table 38 with Document Type = Blanket Order) represents a long-term commercial agreement with a vendor to purchase negotiated volumes at locked prices over an extended period (e.g., contracting 12,000 widgets across an annual cycle), without committing to specific delivery dates upfront.

Blanket Purchase Order Release Lifecycle:

[Blanket Purchase Order: BPO-1001]
  Line 1: Item WIDGET | Total Quantity = 1,200 | Qty. Received = 400 | Outstanding = 800
  Target Action: Release 200 units for immediate delivery
            │
            ├── 1. Enter "200" in [Qty. to Receive] on Blanket Order Line
            │
            ▼ 2. Click Action: "Make Order" (Codeunit 97 Blanket Purch.-Order to Order)
[Purchase Order: PO-2045] ──► Created for Qty = 200
  ├── Warehouse receives 200 units (Post -> Receive)
  └── Accounting invoices 200 units (Post -> Invoice)
            │
            ▼ Updates Flow Back to Blanket Order Line
[Blanket Purchase Order: BPO-1001]
  Line 1: Item WIDGET | Quantity = 1,200 | Qty. Received = 600 | Outstanding = 600 | Qty. to Receive = 0

The Dual Role of "Qty. to Receive" on Blanket Orders

On standard purchase orders, Qty. to Receive dictates the warehouse intake quantity. On Blanket Purchase Orders, Qty. to Receive has a fundamentally different architectural role:

• Blanket Order Qty. to Receive: Defines the quantity to be extracted onto the next child Purchase Order when the Make Order action is triggered.
• After executing Make Order, Business Central resets Qty. to Receive on the blanket order line back to 0 to prevent accidental duplicate releases.

Tracking Blanket Order Quantities

• Quantity: Total contracted master volume.
• Quantity Received: Running total of items received across all child purchase orders generated from this blanket line.
• Quantity Invoiced: Running total of items invoiced across all child purchase orders.
• Outstanding Quantity: Remaining unreceived master units ($\text{Quantity} - \text{Quantity Received}$).
• Child purchase orders retain a permanent link to the originating blanket order via the Blanket Order No. and Blanket Order Line No. fields on Table 39.

---

Purchase Expense Deferrals & Amortization

When purchasing prepaid expenses—such as annual software subscriptions, insurance premiums, or equipment maintenance contracts—accounting standards require recognizing the expense incrementally across future periods rather than taking an immediate lump-sum hit to the P&L.

Purchase Expense Deferral Posting Architecture:

[Vendor Invoice: $12,000 for 12-Month SaaS License]
  Line Type: G/L Account 60200 (Software Expense)
  Deferral Code: 12-MONTHS (Deferral Account: 13100 Prepaid Expenses)
             │
             ▼ Post Invoice (F9)
[Immediate Posting Date Entries]
  Debit:  Prepaid Expenses (13100) ............ $12,000  (Asset)
  Credit: Accounts Payable (20100) ............. $12,000  (Liability)
             │
             ▼ Automated Amortization Postings (Straight-Line across 12 Periods)
  Period 1 (Jan): Debit 60200 Expense $1,000  / Credit 13100 Prepaid $1,000
  Period 2 (Feb): Debit 60200 Expense $1,000  / Credit 13100 Prepaid $1,000
  ... through Period 12

Configuring Deferral Templates

Administrators configure templates via Deferral Templates (Alt+Q -> type Deferral Templates, Page 1700 / Table 1700):

• Deferral Code & Description: Unique identifier (e.g., 12-STRAIGHT, Annual Insurance).
• Deferral Account: The balance sheet asset account where the unamortized prepaid expense resides (e.g., Account 13100 Prepaid Expenses).
• Deferral %: The portion of the line amount to defer (typically 100%).
• Calc. Method: Governs distribution: Straight-Line (evenly divided), Equal per Period, Days per Period (weighted by calendar days per month), or User-Defined.
• Start Date: Determines the initial period: Posting Date, Beginning of Period, End of Period, or Beginning of Next Period.
• No. of Periods: Duration of amortization (e.g., 12 for monthly amortization over one year).

Applying Deferral Codes on Purchase Lines

• On a Purchase Line where Type is G/L Account, Item (Non-Inventory or Service), or Fixed Asset, select the Deferral Code.
• Selecting Line -> Deferral Schedule opens Page 1702, allowing the user to review or manually adjust individual period dates and amounts prior to posting.
• When the invoice is posted, Business Central generates balanced G/L entries that credit Accounts Payable, debit the Deferral Account on the invoice date, and generate future-dated G/L entries amortizing the expense across each scheduled period.

---

Procurement Mechanisms Comparison

---

Step-by-Step UI Execution Workflows

Workflow A: Configuring and Triggering Recurring Purchase Lines

1. Press Alt+Q, type Standard Purchase Lines, and select New (Page 459).
2. Create Code JANITORIAL, Description Weekly Cleaning Consumables.
3. Add lines: Line 1 = Item CLEAN-01 (Qty = 10), Line 2 = Item TRASH-50 (Qty = 5). Click Back.
4. Open Vendor Card 20000 (Alt+Q -> Vendors).
5. Select Related -> Purchases -> Recurring Purchase Lines (Page 175).
6. Insert Code JANITORIAL. In the Insert Rec. Lines on Orders column, select Always Ask.
7. Create a new Purchase Order for vendor 20000. Observe the system notification prompting to insert recurring lines. Click Yes to verify automated line population.

Workflow B: Managing Blanket Purchase Order Releases

1. Press Alt+Q, type Blanket Purchase Orders, and click New (Page 509).
2. Select Vendor 30000, set Location Code EAST.
3. On the Lines FastTab, add Item COMP-200, Quantity = 1000, Direct Unit Cost = $45.00.
4. In the Qty. to Receive field on the line, enter 250 (the first release batch).
5. In the action bar, click Process -> Make Order (Codeunit 97). Confirm the prompt to create a purchase order.
6. Business Central opens the newly created Purchase Order for 250 units. Note that the blanket order line now reflects Outstanding Quantity = 1000 and Qty. to Receive = 0.
7. Post the receipt and invoice on the child purchase order. Reopen the blanket order to confirm Quantity Received = 250 and Outstanding Quantity = 750.

---

Common Configuration Pitfalls & Exam Traps

• Pitfall 1: Confusing Blanket Order Qty. to Receive with Warehouse Intake. Entering 100 in Qty. to Receive on a blanket order line does not receive inventory into the warehouse. It strictly instructs the Make Order routine to create a child purchase order for 100 units.
• Pitfall 2: Blank Vendor Invoice Number Blocking Document Post. If a company enables Ext. Doc. No. Mandatory in Purchases & Payables Setup, attempting to post a purchase invoice without populating Vendor Invoice No. on the header will trigger a hard error: "Vendor Invoice No. must have a value in Purchase Header...".
• Pitfall 3: Invoicing Beyond Received Quantity. Attempting to invoice a purchase order where Qty. to Invoice exceeds Quantity Received will fail unless the user selects Receive and Invoice on the posting dialog. A document cannot post pure invoices for unreceived stock on standard inventory items.
• Pitfall 4: Deferral Template with Mismatched G/L Account Types. Assigning an expense account as the Deferral Account on a Deferral Template instead of a Balance Sheet Prepaid Expense account causes prepaid amounts to hit current-period expenses immediately, defeating the entire multi-period amortization structure.