1. Financial accounting with your chart of accounts
Standard G/L trainings use Microsoft's Cronus tenant with a generic chart of accounts. The problem: your chart is different — SKR03, SKR04, IKR, or a custom hybrid version with various tax codes. We train with a sandbox copy of your real tenant in which participants book against the real chart of accounts. That makes the difference between "training knowledge that evaporates on site" and "productive ERP user from day 1".
2. Inventory with locations and bins — the complexity levels
BC has three inventory complexity levels: simple inventory without locations, inventory with locations (one stock info per warehouse), inventory with locations and bins (granular stock per bin). Which level is the right one? We train the decision against real warehouse scenarios — and walk through the trap "we start simple, complicated comes later" (it is usually not as simple as expected).
3. Production — BOMs, routings, production orders
Production is the technically most complex BC module. Training focus: multi-level BOMs with phantom components and variant BOMs, routings with operations and setup times, production dispatch between order and capacity, feedback with material and time consumption, post-calculation and plan-vs-actual variance analysis. With a real production scenario from your company.
4. Purchasing with approval workflows and electronic invoice processing
Purchase approval workflows are possible with BC standard functions but are rarely optimally configured. We train the setup of multi-tier approvals with limits, deputies, and escalations. Plus: electronic incoming invoice processing with ZUGFeRD/XRechnung, PEPPOL connectivity, OCR pre-capture. With practical reference to the German e-invoicing obligation from 2025/2027.
5. Admin topics — permissions, extensions, releases
A Business Central admin maintains permission sets (manual or prebuilt), tenant setup wizards, extension management (AppSource, customer-specific per-tenant extensions), sandbox strategy, and update preparation. Microsoft publishes two major BC releases per year (Wave 1, Wave 2) — we train how a mid-sized company systematically reacts to new releases without every new wave triggering an emergency action.