Skip to learning content

Module 6 · Perform Business Central operations · 180 min estimate

Purchasing, sales and document corrections

By the end, you can

  • Process quotes, orders, receipts, shipments, over-receipts, reversals, recurring lines and blanket orders.
  • Create invoices from orders, combine eligible shipments/receipts, use document deferrals and process prepayments.
  • Release/reopen documents and choose a supported correction, credit memo or return path for posted transactions.

Choose a correction using the posted state

  1. Still unposted?Reopen if permitted, edit and validate again.
  2. Received/shipped but not invoiced?Check whether the supported Undo action is eligible.
  3. Posted invoice and eligible?Evaluate Correct or Cancel and the generated audit documents.
  4. Paid, partial return or other restriction?Use an appropriate credit memo/return workflow.
  5. Validate the resultReconcile quantities, application, cost and G/L effects.
Original conceptual learning diagram. Read the sequence with its explanation below; this is not a product screenshot.

Read the document state before choosing an action

Commercial intent, physical fulfilment and financial posting are different stages. A quote records a proposal. An order records an agreed requirement. Receiving or shipping records physical movement. Invoicing records the financial transaction. A released document has passed the applicable business-control transition; it is not necessarily received, shipped, invoiced or paid. Reopening permits permitted editing and does not reverse posted entries.

Northstar orders twenty chairs but the supplier delivers twelve today and eight next week. Set Qty. to Receive deliberately and post only the actual receipt. If the supplier invoices twelve, invoice the eligible received quantity. Do not use one full receive-and-invoice action simply to close the order early. Review quantities ordered, received, invoiced and outstanding after each stage. On sales orders, use the corresponding shipment and invoice quantities. Read the exact action before confirming it.

Purchasing exceptions require explicit controls

Over-receipt allows a controlled quantity above the order where an over-receipt code and tolerance permit it. If ten units are ordered and the test tolerance is 10%, an eleven-unit receipt is within that simple limit. Approval requirements may add another condition. The presence of an extra unit on the dock is not permission to bypass the tolerance or receive against the wrong item.

An uninvoiced receipt can use a supported undo process when its conditions are met. Once invoiced, evaluate a return order or credit memo process instead. The exact path depends on the posted state and item/application constraints. A credit memo is a financial correction; a return order also models the physical return workflow. Recurring purchase lines insert a repeatable set of document lines. A blanket purchase order records an ongoing agreement and can create call-off orders. Neither is an automatic recurring journal.

Selling requires availability and fulfilment reasoning

Convert an accepted quote into the appropriate sales order or invoice according to the business process. Before promising stock, inspect availability by date, location and relevant variant. A purchase expected next week may not cover tomorrow’s shipment. Review reservations and other commitments where applicable. Use partial shipment when that is the actual fulfilment event rather than silently changing the ordered quantity.

An uninvoiced shipment may qualify for supported undo actions. An invoiced return requires the appropriate corrective sales process. Recurring sales lines provide reusable line content; blanket sales orders represent longer-running agreements. If the customer needs one invoice for multiple eligible shipments, use the supported combine/get-shipment-lines process and check customer, currency and other compatibility conditions. The equivalent purchase process combines eligible receipts. Combining is not a licence to merge unrelated customers or override incompatible header data.

Financial corrections preserve the audit trail

Never edit a posted invoice as though it were an unposted draft. First identify whether it is paid, whether physical items moved and whether only part is being returned. Correct and Cancel actions have eligibility restrictions and produce corrective posted documents when supported. Use a corrective credit memo or return process for other cases, including scenarios where the paid state prevents the direct action. Read the current documentation when a scenario includes partial posting.

For example, an invoice for six chairs was paid and the customer returns two. The business needs an approved partial return, a credit for two and a refund or application arrangement. Cancelling the whole sale would misstate the four chairs the customer kept. Select lines, quantities, cost application and original-document references intentionally. Compare posted customer/vendor, item, value and G/L entries after the correction. A return’s financial value should be traceable to its original transaction where the costing/application design requires it.

Prepayments and deferrals have different timing

Northstar requires a 20% prepayment on a tax-exclusive order value of 5,000. The simple deposit amount is 1,000. Configure the relevant prepayment settings/accounts, create and post the prepayment invoice through the supported order process, and verify settlement before final fulfilment where the policy requires it. At final invoicing, ensure the prepayment is deducted correctly so the customer is not charged 6,000 in total.

A deferral allocates revenue or expense across accounting periods. It does not collect a deposit. A sales document can therefore raise a recognition question independently of its payment schedule. Use posting preview to examine both. In practice exercises, isolate taxes and rounding first, then add realistic complications only after the learner can explain the base transaction. For exam reasoning, identify the requested outcome: physical movement, liability/receivable, recognition timing or settlement. That usually narrows the correct action more reliably than matching a familiar button label.

Sandbox lab: Run a partial fulfilment and a controlled return

Use synthetic records in your authorised sandbox. Record the company and work date before posting. Never run this exercise in a customer’s production company.

  1. In a disposable company create a purchase order for twenty units. Receive twelve and inspect outstanding quantities.
  2. Invoice the eligible twelve, then receive/invoice the remaining eight in a separate step. Retain document references.
  3. Create a sales quote, convert to an order and review availability at the intended location/date. Ship and invoice a deliberate partial quantity.
  4. Prepare separate scenarios for an uninvoiced shipment undo and an invoiced partial return. Determine eligibility before attempting an action.
  5. Prepare a 5,000 order with 20% prepayment and verify the 1,000 deposit calculation and final deduction in posting preview.
  6. Demonstrate recurring document lines, a blanket call-off and eligible combined shipment/receipt invoicing using synthetic records.

Expected observations

  • Ordered, received/shipped, invoiced and outstanding quantities remain explainable after each step.
  • The return corrects only the intended quantity and retains links to the original posting.
  • Prepayment and final invoice together represent the intended 5,000 order value under the simplified assumptions.

Evidence to retain

  • Document-state timeline
  • Quantity reconciliation after partial fulfilment
  • Correction-path decision record
  • Prepayment deduction and final balance calculation

Cleanup

Cancel unposted test requests and delete only eligible unposted documents. Use supported credit/return/reversal actions for posted transactions. Do not erase ledger history.

Common pitfalls

  • Equating Released with posted, paid or physically fulfilled.
  • Using Cancel for every posted invoice regardless of payment or return state.
  • Confusing recurring document lines, blanket orders and recurring journals.

Check your understanding

1. Twenty units were ordered and only twelve arrived. What should Qty. to Receive represent?

Twelve, assuming that is the verified delivery.

Posting should represent the actual event and leave eight outstanding.

2. A paid invoice contains six units and only two are returned. What type of process should be evaluated?

An appropriate partial sales return/credit memo process.

A whole-document cancellation would not represent the four units retained by the customer.

3. Is a 20% prepayment on a 5,000 order a deferral schedule?

No. The simple prepayment is 1,000; a deferral controls recognition periods.

Collection timing and revenue/expense recognition solve separate requirements.

Go to the source

Learn with an Academy instructor

Need guided labs or a study cohort? Enquire about MB-800 preparation and use course code MB-800-PREP. Exam booking and fees are handled separately through Microsoft’s official certification page.

Content revision 2026.11.16.2 · Skills outline effective 30 June 2026 · Sources checked 16 November 2026. Independent Academy preparation. Microsoft certification is awarded only through Microsoft’s assessment process.