16.1 Direct Invoices, Credit Memos & Document Reopening

16.1 Direct Invoices, Credit Memos & Document Reopening

Quick Summary: In Microsoft Dynamics 365 Business Central, organizations that do not require separated warehouse logistics can streamline operational accounting by utilizing Direct Financial Documents: Sales Invoices (Page 43), Purchase Invoices (Page 51), Sales Credit Memos (Page 44), and Purchase Credit Memos (Page 52). Unlike multi-stage sales or purchase orders that separate shipment/receipt from financial voucher recognition, posting a direct invoice executes an atomic transaction that simultaneously decreases or increases inventory in the Item Ledger (Table 32), creates Value Entries (Table 5802), updates subledgers (Customer Ledger Table 21 or Vendor Ledger Table 25), and posts balanced debits and credits to the General Ledger (Table 17). Document lifecycle control relies on the Status field (Open, Released, Pending Approval), where the Reopen action allows necessary line and header edits before financial commitment.

---

Direct Financial Documents vs. Order-Based Processing

Business Central provides two distinct architectural paths for processing sales and procurement transactions: Order-Based Processing and Direct Document Invoicing.

Document Architecture Decision Path:

Operational Requirement: Does the location require separate shipping/receiving,
advanced warehousing (picks/put-aways), or partial staggered shipments?
                     │
         ┌───────────┴───────────┐
         ▼ YES                   ▼ NO
[Sales / Purchase Orders]     [Direct Invoices / Credit Memos]
  - Tracks Outstanding Qty      - Atomic single-step posting
  - Supports Whse. Receipts     - Simultaneous Inventory & G/L impact
  - Partial Shipments/Receipts  - No outstanding order balance
  - Advanced Logistics          - Streamlined accounting overhead

When to Use Direct Invoices and Credit Memos

Direct financial documents are ideal for:

1. Service and Expense Invoicing: Invoicing non-inventory operating expenses (e.g., legal counsel, utilities, facility leases) or consulting revenues where physical tracking is non-existent.
2. Direct Retail or Point-of-Sale Deliveries: Immediate over-the-counter sales where physical goods leave the facility at the exact moment billing occurs.
3. Drop-Shipments without Physical Handling: Straightforward procurement where materials are delivered directly to an end-destination without internal warehouse staging.
4. Small-Scale Facilities: Warehouses and offices where Require Receive or Require Shipment is disabled on the Location Card (Page 5703).

Posting a direct Sales Invoice (F9) immediately registers an outbound negative inventory movement (Quantity), issues the customer billing statement, records sales tax/VAT liabilities, and books Cost of Goods Sold (COGS) and Revenue in one operation.

---

Document Status Progression: Open, Released & Pending Approval

To preserve data integrity and govern audit controls, sales and purchase documents enforce a strict lifecycle state machine managed by the Status field on Table 36 (Sales Header) and Table 38 (Purchase Header).

Document Status State Machine:

       [Open] ◄─────────────────────────┐
         │                              │
         │ Action: Release              │ Action: Reopen
         ▼                              │ (Clears Approvals!)
    [Released] ─────────────────────────┘
         │
         ├──► Workflow Active? ──► [Pending Approval] ──► Approved ──► [Released]
         │
         ▼ Action: Post (F9)
   [Posted Document / Immutable Ledgers]

Document States Defined

• Open: The default draft state for new documents. Users can freely add lines, delete lines, alter quantities, update unit costs/prices, change dimension values, and modify payment terms or shipping addresses.
• Released: Signifies that the document has completed preparation and commercial verification. In Released status:
  • Line items, quantities, and prices are locked against editing.
  • The document is exposed to batch routines (such as automated batch posting or batch creation of pick activities).
  • An invoice must be in Released status to be posted.
• Pending Approval: Triggered when an automated Power Automate or Business Central approval workflow is active (e.g., purchase invoice total exceeds a manager's approval limit). All fields are locked until designated approvers approve or reject the request.

The Reopen Action Mechanics

When a sales coordinator or purchasing agent discovers an error on a Released document (such as an incorrect item variant, wrong discount code, or missing dimension), the document cannot be edited directly. The user must click Process -> Reopen.

[!IMPORTANT] If a document reached Released status via an approval workflow, selecting Reopen resets the approval cycle! Business Central sets the status back to Open and cancels existing approval entries. Once modifications are complete, the document must be re-submitted via Send Approval Request and re-approved before posting is permitted.

---

Multi-Ledger Posting Architecture

When a user presses F9 (or selects Post) on a direct invoice or credit memo, Business Central executes core posting codeunits (Codeunit 80 Sales-Post, Codeunit 90 Purch.-Post).

Direct Sales Invoice Posting Ledger Flow:

[Sales Invoice: Page 43 / Table 36 & 37]
                   │
                   ▼ Post (F9) -> Codeunit 80
   ┌───────────────┼───────────────────────────────┐
   ▼               ▼                               ▼
[Customer Ledgers] [General & Tax Ledgers]         [Inventory Ledgers]
- Table 21: Cust.  - Table 17: G/L Entry           - Table 32: Item Ledger Entry
  Ledger Entry       Debit: Accounts Receivable      Negative Qty (Sale)
  (Doc Type: Inv)    Credit: Sales Revenue         - Table 5802: Value Entry
- Table 379: Dtl.    Credit: Sales Tax / VAT         Actual Invoiced Cost
  Cust. Ledg. Entry  Debit: COGS Expense             Sales Amount Expected/Actual
                     Credit: Inventory Asset
                   - Table 254: VAT Entry

Subledgers Updated During Direct Posting

1. Customer / Vendor Subledger:
   • Table 21 (Cust. Ledger Entry) or Table 25 (Vendor Ledger Entry): Creates an open entry with the total invoice amount including tax, tracking Remaining Amount, Due Date, and Payment Terms.
   • Table 379 (Detailed Cust. Ledg. Entry) or Table 380 (Detailed Vendor Ledg. Entry): Records the underlying initial transaction value.
2. General Ledger (Table 17):
   • For Sales: Debits the customer receivable account (governed by Customer Posting Group), credits revenue (governed by General Posting Setup via combination of Gen. Bus. Posting Group and Gen. Prod. Posting Group), credits sales tax/VAT liabilities, debits COGS, and credits Inventory.
   • For Purchases: Debits inventory asset or expense accounts, debits recoverable VAT/tax, and credits accounts payable (governed by Vendor Posting Group).
3. Tax Subledger (Table 254 VAT Entry): Records base taxable amounts, tax percentages, and calculated tax amounts mapped to tax jurisdictions or VAT posting setups.
4. Item & Valuation Subledgers:
   • Table 32 (Item Ledger Entry): For tangible items, posts an entry with Entry Type = Sale (negative quantity) or Entry Type = Purchase (positive quantity).
   • Table 5802 (Value Entry): Records actual inventory cost and sales amounts, establishing complete inventory valuation without requiring intermediate expected cost accruals.

---

The Copy Document Functionality

The Copy Document function (Actions -> Functions -> Copy Document..., executing Codeunit 492 Copy Document Mgt.) allows users to rapidly generate new sales or purchase documents by duplicating lines and headers from existing records.

Copy Document Configuration Window:

Document Type:          [Posted Invoice               ▼]
Document No.:           [PSI-103022                   ...]
Include Header:         [YES / NO                     [x]]
Recalculate Lines:      [YES / NO                     [ ]]

Critical Copy Document Parameters

• Document Type: Source selection supporting both unposted documents (Quote, Order, Invoice, Credit Memo) and posted historical documents (Posted Invoice, Posted Shipment, Posted Receipt, Posted Credit Memo).
• Include Header:
  • When set to True (Yes): The target document's header information (payment terms, payment method, currency code, dimensions, and shipping addresses) is overwritten with the header data from the source document.
  • When set to False (No): The target document retains its existing header information; only the line items are imported.
• Recalculate Lines:
  • When set to False (No): Business Central copies the exact historical unit prices, discounts, and line amounts from the source document. Essential when processing credit memos for promotional or grandfathered pricing.
  • When set to True (Yes): Business Central queries the current item master, active sales price lists, and current customer discount groups as of the target document's posting date, recalculating line amounts.

[!TIP] When creating a Credit Memo to issue a refund or return for a posted invoice, leave Recalculate Lines = False. Enabling recalculation might alter line prices if base prices have shifted, resulting in an incorrect refund amount to the customer.

---

Direct Financial Document Comparison

---

Step-by-Step UI Execution Workflows

Workflow A: Processing a Direct Sales Invoice with Status Governance

1. Press Alt+Q, type Sales Invoices, and select the related link (Page 9301).
2. Click New (Page 43). Select Customer 10000 (Adatum Corporation).
3. In the Lines FastTab, enter Type = Item, No. = 1928-S (Antwerp Conference Chair), Quantity = 4, Unit Price = $250.00.
4. In the action bar, click Process -> Release. Observe the Status field transitions from Open to Released. Notice that the line fields are now read-only.
5. To correct a pricing error, click Process -> Reopen. The Status field reverts to Open.
6. Adjust the Unit Price to $240.00. Click Process -> Release.
7. Press F9 (or Posting -> Post). Select Yes to post. Confirm that the invoice is committed to historical ledgers.

Workflow B: Duplicating a Historic Purchase Invoice via Copy Document

1. Press Alt+Q, type Purchase Invoices, and click New (Page 51).
2. In the Buy-from Vendor No. field, select Vendor 20000 (First Up Consultants).
3. In the action bar, select Actions -> Functions -> Copy Document....
4. In the dialog, set Document Type = Posted Invoice.
5. In Document No., look up and select Posted Purchase Invoice 107033.
6. Ensure Include Header is toggled to True and Recalculate Lines is set to False.
7. Click OK. Business Central imports all lines with historical pricing and populates header terms from the posted invoice.

---

Common Configuration Pitfalls & Exam Traps

• Pitfall 1: Modifying a Released Document Directly. A common user mistake is attempting to alter quantities on a released document. Business Central blocks line edits with the error: "Status must be equal to 'Open' in Sales Header...". Users must execute Reopen first.
• Pitfall 2: Recalculate Lines Overwriting Return Values. When copying a posted invoice onto a corrective credit memo, turning on Recalculate Lines will pull current price list rates. If prices increased since the sale, the credit memo will refund an inflated amount.
• Pitfall 3: Missing External Document Number. On purchase documents, if Ext. Doc. No. Mandatory is enabled in Purchases & Payables Setup, posting will fail unless the vendor's billing reference is populated in Vendor Invoice No. on the header.
• Pitfall 4: Direct Invoicing with Warehouse Locations. Attempting to post a direct sales invoice using a Location Code configured with Require Shipment = Yes will trigger an error: "Location %1 requires warehouse shipment. You cannot post direct sales invoices." Order documents must be used instead.