Skip to learning content

Module 1 · Set up Business Central · 150 min estimate

Company foundations, migration and security

By the end, you can

  • Create an appropriate company through Assisted Setup and distinguish production from a sandbox.
  • Build a configuration worksheet and package, validate dependent master records and reconcile opening journals.
  • Create users, assign profiles and company-scoped permission sets through security groups, apply security filters and inspect security auditing.

Implementation evidence gates

  1. DesignDefine company, region, licence and accounting decisions.
  2. PrepareCreate lookup data and map dependent master records.
  3. ValidateTrial-import, preview posting and reconcile subledgers.
  4. AuthorizeTest effective permissions with a limited user.
  5. AcceptRecord agreed opening totals and release evidence.
Original conceptual learning diagram. Read the sequence with its explanation below; this is not a product screenshot.

Start with the implementation decision

Northstar Supplies is a fictional distributor preparing to move to Business Central. Its implementation team needs a working company, trustworthy opening data and controlled access before the first sale. Treat setup as a sequence of business decisions. Record the legal entity, local currency, country or region, financial year, inventory policy and required business processes. A company is an accounting and operational boundary within an environment. An environment is the application and service boundary. Creating another company does not create a separately isolated tenant.

Use Assisted Setup for supported guided tasks. Select a company creation experience that matches the purpose: demonstration data helps learning, setup data provides a starting configuration, and an empty company requires more decisions. Check the available options in your environment rather than memorising one screenshot. Keep training changes in a clearly named sandbox company. Regional functionality, extensions, licensing and the company experience influence the fields and features available. A profile changes a person’s workspace; it does not decide their licence entitlement or grant data permissions.

Move data in a controlled dependency order

A configuration worksheet helps organise the tables and sequence of an implementation. A configuration package carries selected table fields and records for migration. Choose only needed fields, preserve primary keys and validate relationships before applying imported records. Load supporting lookup records before the master records that depend on them. For example, create payment terms, posting groups, units of measure and dimension values before customers, vendors and items. Otherwise, a valid spreadsheet row can fail because its referenced code is absent.

Run a small trial import, review errors, correct the source and revalidate. Keep a mapping log that records source column, destination field, transformation, owner and reconciliation check. Never assume that importing a row proves that its posting setup is usable. Test one customer, one vendor and one item through posting preview. Configuration packages move and validate records; they do not replace every application process or justify bypassing business rules. Compare record counts, duplicate keys and control totals before accepting the migration.

Opening balances must agree across ledgers

Assume the approved conversion trial balance contains bank 30,000, receivables 12,000, inventory 18,000 and payables 15,000, with equity 45,000. The assets total 60,000 and liabilities plus equity total 60,000. These are invented local-currency values with tax excluded. A balanced G/L import is necessary, but it is insufficient if the customer ledger, vendor ledger, bank ledger or inventory valuation contains no supporting detail.

Plan the opening journals and migration method together so each control account receives its corresponding subledger entries exactly once. If detailed customer invoices already create the receivables control total, a separate 12,000 direct G/L posting would duplicate the balance. Reconcile customer ageing to receivables, vendor ageing to payables, bank ledger to the bank G/L account and inventory valuation to inventory control. Retain document numbers and dates needed for later application. Investigate a mismatch by ledger and source batch before adjusting a balancing account.

Separate workspace convenience from authority

Create or synchronise a suitably licensed user using the supported Business Central online process. Assign a profile to provide relevant Role Center actions, cues and reports. Then assign permission sets that match the person’s tasks, ideally through managed security groups with company scope where required. Test with a nonadministrator account. A hidden action or filtered list is not a substitute for an enforced permission or security filter.

A security filter restricts accessible records within a permission assignment. Evaluate the user’s effective permissions across all assigned sets: a broad assignment can undermine the intended restriction. For separation of duties, a purchaser should create orders without automatically receiving authority to approve their own requests or alter payment details. Use the change log for configured business-data auditing and inspect the security audit trail for changes to users and permissions. Record who changed access and when. Do not put real learner identities, customer records or exported audit data in a public course repository.

Sandbox lab: Build a disposable company and prove the opening controls

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. Validate an authorised sandbox and record its application version. Use fictitious data only.
  2. Create a company with a training name through the available Assisted Setup experience. Record which starting-data option you chose and why.
  3. Prepare a five-record customer import in a configuration worksheet/package. Include an intentionally invalid payment-term code, validate it and document the error before correcting it.
  4. Design opening journal entries for the example trial balance. Preview posting and explain how receivables, payables, inventory and bank detail will reconcile without duplication.
  5. Assign one test user a role profile and limited permission sets in the training company. Test a permitted read, permitted task and denied task.
  6. Inspect the security audit/change-log evidence for a controlled permission change. Follow the existing environment-validation and migration labs where applicable.

Expected observations

  • The corrected package validates and produces five intended customer records with no duplicate keys.
  • The proposed journal debits equal credits and each control account has a documented subledger reconciliation.
  • The test user can perform the intended task and receives an access denial for the prohibited task.

Evidence to retain

  • Company-creation decision record
  • Redacted import validation and before/after counts
  • Opening balance reconciliation table
  • Effective-permission positive and negative test results

Cleanup

Export only synthetic evidence, revoke temporary user permissions and remove the disposable company if authorised. Do not delete a shared instructor company.

Common pitfalls

  • Using a demonstration company as production without validating configuration and data.
  • Posting opening control balances twice through both direct G/L and subledger migration.
  • Treating a profile, hidden field or saved view as a security boundary.

Check your understanding

1. A new user can see the correct Role Center but cannot post a purchase invoice. What should you inspect?

The user’s licence/entitlement and effective permission sets, including company scope.

The profile provides the workspace. Posting authority comes from applicable entitlements and permissions.

2. The G/L receivables balance is 24,000 but detailed customer entries total 12,000 after migration. What is a likely cause?

The 12,000 opening receivables balance was loaded both through customer entries and directly to G/L.

Trace the migration batches. Correct the duplicate through an approved accounting process instead of forcing the subledger to match.

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.