Process Library

Business Central test scenarios, by business process

The eight standard business processes a Coverage Pack is built from, what each script covers, and a self-check to tell you whether your setup is Standard or Custom before you fill in anything.

Standard or Custom? See Coverage Packs

Standard processes

Pick your processes from this list

Pick three or five. Each becomes a parameterized script with the scenarios listed, validated against your own master data.

01

Order-to-Cash (Sales)

Sales quote or order through shipment, invoice posting and the customer ledger entry. Scenarios cover full and partial shipment, ship-then-invoice, prepayment, foreign-currency customer, credit limit warning, and a blocked customer. Validations check the posted invoice amount, the item ledger entry and the customer balance.

BC areas exercised: Sales Orders, Customer Card, Posted Sales Invoices, Customer Ledger Entries, Item Ledger Entries
Typical scenarios: 4–8
02

Procure-to-Pay (Purchasing)

Purchase order through receipt, invoice posting and vendor ledger entry. Scenarios cover receive-then-invoice, over-receipt, invoice with a different vendor invoice number, item charges for freight, and posting into a closed period. Validations check the vendor balance and the inventory value.

BC areas exercised: Purchase Orders, Vendor Card, Posted Purchase Receipts, Posted Purchase Invoices, Vendor Ledger Entries
Typical scenarios: 4–7
03

Item Journal / Inventory Adjustment & Costing

Positive and negative adjustments, reclassification between locations, and the Adjust Cost – Item Entries batch. Scenarios cover FIFO and Average costing items, adjustments with unit cost override, and the value entry that lands in the G/L after cost adjustment.

BC areas exercised: Item Journals, Item Reclassification Journals, Item Card, Value Entries, Adjust Cost – Item Entries, Post Inventory Cost to G/L
Typical scenarios: 3–6
04

Bank Reconciliation & Payment Reconciliation Journal

Import or manual entry of a bank statement, automatic matching, manual match of the remaining lines, and posting the reconciliation. Scenarios cover a statement with a bank fee, an unmatched deposit, and a payment reconciliation journal that applies a customer payment to two invoices.

BC areas exercised: Bank Account Reconciliations, Payment Reconciliation Journals, Bank Account Card, Bank Account Ledger Entries
Typical scenarios: 3–5
05

Month-End Financial Close Basics

The routine your controller runs on day one: recurring journals, accrual reversal, currency adjustment, running the Trial Balance and Aged Accounts Receivable reports, and closing the period in Accounting Periods. Scenarios validate that each report still exists, runs, and returns a balance that ties to the G/L.

BC areas exercised: General Journals, Recurring General Journals, Adjust Exchange Rates, Accounting Periods, Trial Balance, Aged Accounts Receivable
Typical scenarios: 4–7
06

Sales Return / Credit Memo Cycle

Return order created from a posted invoice via Get Posted Document Lines to Reverse, receipt of the return, credit memo posting and application to the original invoice. Scenarios cover a partial return, a return with a restocking fee, and a credit memo without a return order.

BC areas exercised: Sales Return Orders, Sales Credit Memos, Posted Sales Credit Memos, Customer Ledger Entries (Apply Entries)
Typical scenarios: 3–6
07

Approval Workflow

This is Business Central’s own Approval Workflow feature, so the name stays. A purchase document over the approval limit is sent for approval, the approver sees it in Requests to Approve, approves or rejects it, and the document status changes accordingly. Scenarios cover approve, reject, delegate, and a document under the limit that skips approval.

BC areas exercised: Workflows, Approval User Setup, Requests to Approve, Purchase Orders (Send Approval Request), Approval Entries
Typical scenarios: 3–5
08

Warehouse Pick/Ship

For locations that require shipment and pick: release the sales order, create the warehouse shipment, create and register the pick, post the shipment. Scenarios cover a pick from a specific bin, a partial pick, and a shipment covering two orders. Note: this process is only Standard if your location setup is already in place in the sandbox.

BC areas exercised: Warehouse Shipments, Warehouse Picks, Registered Picks, Location Card, Bin Contents
Typical scenarios: 3–6

Self-check

Standard or Custom?

Fixed-price packs cover the standard path. One rule tells you which side you are on.

Does the ISV or feature add pages or steps to the path the script must navigate?

Standard — fixed-price packCustom — scoped individually
ISV runs in the background — tax calculation, posting-time integration, reportingISV inserts UI the script must navigate — shipping workbench, document capture queue, replaced order entry page
Ship directly from the sales orderWarehouse shipment + registered pick
Single companyIntercompany or consolidation
Standard posting routinesManufacturing / assembly orders
Having an ISV installed does not make you Custom. Nearly every BC customer has one. It only matters if users interact with it during the process being tested. Avalara calculating tax at posting time: Standard. A document capture queue your AP clerk works from: Custom.

Custom also applies when you need more than 10 processes, a single process has more than 3 conditional branches, or the process needs master data that doesn’t yet exist in the sandbox.

Not sure which processes to start with?

Start with the ones that make you money. A 30-minute call is usually enough to pick five.

Book a demo