Module 5 · Configure sales and purchasing · 150 min estimate
Inventory, trading master data, prices and discounts
By the end, you can
- Configure inventory, items, categories, attributes, units, variants, locations and stockkeeping units.
- Trace quantity to item ledger entries, valuation to value entries and accounting to G/L, and distinguish costing methods.
- Configure customer/vendor fulfilment data and test date/quantity/currency/unit-sensitive prices and discounts.
Quantity-to-accounting reconciliation ladder
- Document quantityConvert order units into base units.
- Item ledgerConfirm signed movement at the correct location/variant.
- Value entriesExplain expected and actual cost.
- Cost adjustmentPropagate subsequent cost changes where applicable.
- General ledgerReconcile posted inventory cost to control accounts.
Model a product before adding a price
Northstar sells a chair in blue and grey, purchases it in boxes of four and sells individual units. Create one appropriate item model, then use variants for meaningful versions and units of measure for packaging. Categories organise the product hierarchy; attributes describe searchable characteristics such as colour or material. An attribute is not a stock quantity and does not automatically create a separately stocked variant.
Confirm the base unit before posting transactions. If the base is EACH and BOX contains four, a receipt of three BOX represents twelve EACH. Test the conversion through the document and ledger, including rounding where relevant. A wrong unit conversion can make purchasing appear cheaper and availability appear larger than reality. Use consistent master definitions across the vendor price, sales price and order lines.
Location and SKU are different levels of configuration
Locations identify where stock is held. A stockkeeping unit records item configuration for a particular location and/or variant, enabling appropriate replenishment and planning differences. Northstar may replenish the same chair differently in Johannesburg and a smaller branch. This does not mean creating two unrelated item cards is always necessary. Identify the requirement first: distinguish physical location, product variant, unit conversion and replenishment policy.
Review Inventory Setup before testing posting. Decisions about automatic cost adjustment, cost posting and related controls affect when values appear in G/L. Test stock availability by the relevant location and date. Twenty units somewhere in the company do not prove that a specific location can fulfil an order tomorrow. A transfer and an adjustment solve different business events and should leave different evidence.
Separate quantity, value and financial effect
Item ledger entries track inventory quantity movements. Value entries carry valuation associated with item transactions. G/L entries carry the financial impact once the applicable costs are posted. For a purchase of ten items at 50 each, the physical receipt and final invoiced cost can occur at different times. An item quantity of ten with expected cost is not the same state as ten with final actual cost.
Costing methods decide how costs flow to outbound transactions. In a deliberately simplified example, ten units are acquired at 10 and another ten at 14 before a sale of twelve units. FIFO assigns 10 × 10 plus 2 × 14 = 128 to the issue. LIFO, where supported and suitable for the application scenario, would use 10 × 14 plus 2 × 10 = 160. A simple average across all twenty units is 12 each, giving 144 for twelve, but Business Central’s actual average-cost calculation depends on its configured period and calculation type. Standard uses the configured standard with variance handling; Specific follows identified cost where the tracking/application requirements support it. Physical picking order is not automatically the costing method.
Before accepting a valuation result, check the method, applications, invoice status, adjustment state and valuation date. The learner’s task is to explain the expected result under stated assumptions, not to choose whichever method produces the preferred profit.
Fulfilment data makes documents usable
Customers need delivery details such as ship-to addresses, location and shipping agent/service where applicable. Vendors need order addresses, lead time and location defaults suitable for purchasing. The bill-to or pay-to relationship can differ from the delivery or ordering party. Trace the selected address and dates onto a test document rather than assuming the card default always wins.
A vendor lead time can inform planning and expected receipts. It does not guarantee the supplier will deliver on that date. Document external commitments separately. Test a vendor with an alternative order address and a customer with two ship-to addresses so the distinction remains visible during exam-style scenarios.
Test prices as a matrix of conditions
A price or discount may depend on customer/vendor, group, item, date, currency, unit and minimum quantity. Prepare a small matrix that names each condition and expected result. For example, a chair’s test sales price is 100 per EACH and a ten-unit offer provides a 5% line discount. Ten units produce 1,000 before discount and 950 after line discount, excluding tax. If the document also qualifies for a 2% invoice discount on that eligible net amount, the illustrative total becomes 931. Do not assume invoice discount applies to every line or that all discounts simply add together.
Change one condition at a time: quantity nine versus ten, a date outside the offer, or BOX instead of EACH. Review which price and discounts Business Central actually selects. A purchase price is a supplier cost agreement, while a sales price is what the customer is charged. Updating one does not imply that the other will change. Record how an approved price is activated and how old orders are handled.
Sandbox lab: Prove packaging, location and price boundaries
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.
- Create a synthetic item with EACH as base unit and BOX=4 EACH. Add two variants, category and attributes.
- Create two locations and a suitable stockkeeping-unit record with deliberately different replenishment settings.
- Prepare a purchase document for three BOX. Verify that the intended base quantity is twelve before posting.
- Create customer ship-to and vendor order-address examples; verify the selected document addresses and location.
- Set up a ten-unit sales offer and test nine, ten and eleven units, a date outside the offer and an alternative unit. Record expected versus selected prices.
- Calculate the simplified FIFO/average examples independently, then inspect item/value/G/L entries for an authorised posted training transaction.
Expected observations
- Three BOX resolves to twelve EACH with the intended variant and location.
- Pricing boundary tests are explained by the configured conditions.
- Quantity and value are reconciled separately and any not-yet-posted G/L cost is identified.
Evidence to retain
- Item/unit/variant/location model
- Pricing decision matrix
- Independent costing calculations
- Ledger trace for one posted transaction
Cleanup
Remove unposted quotes/orders and inactive training prices. If transactions were posted, preserve entries and use authorised returns/adjustments instead of deleting history.
Common pitfalls
- Using attributes as though they automatically create separately stocked variants.
- Assuming company-wide availability guarantees fulfilment at one location.
- Adding line and invoice discount percentages without calculating their eligible bases.
Check your understanding
1. The base unit is EACH and a BOX contains four. What is the base quantity of three BOX?
Twelve EACH.
Unit conversion must be validated before valuation or availability can be trusted.
2. Where should you look for inventory quantity versus inventory valuation?
Quantity: item ledger entries. Valuation: value entries.
G/L entries show accounting effects after cost posting and are a separate reconciliation layer.
3. Ten units at 100 receive 5% line discount then 2% invoice discount on the eligible net. What is the illustrative tax-exclusive total?
931.
1,000 × 0.95 × 0.98 = 931. Eligibility and rounding still require configuration review.