Business Central has become one of the more accessible entry points into the Microsoft Dynamics ecosystem. Businesses of every size run it, and they need people who can configure it, extend it and support it. This guide explains the two main career paths, what to learn in what order, and how to prove you can do the job. It makes no promises about salaries or placements, because these depend on you, the market and the employer.
Functional or technical: which path suits you?
Most Business Central roles fall into one of two families, and many senior people eventually work across both.
| Functional consultant | Technical consultant / developer | |
|---|---|---|
| Core question | How should the system be configured to fit this business process? | How do we build or connect what standard functionality does not cover? |
| Daily work | Workshops, fit-gap analysis, setup, test scenarios, user training | AL extensions, APIs, integrations, reports, debugging, deployment |
| Background that helps | Accounting, supply chain, operations, or another ERP | Programming in any language, databases, REST and JSON |
| You will enjoy it if | You like understanding how businesses work and explaining it clearly | You like building, debugging and solving logic problems |
If you are unsure, spend a week on each. Set up a sandbox company and post a few sales and purchase invoices, then write a small AL extension. Which one did you want to keep going with?
A sensible learning order
For the functional path
- Accounting basics. Double entry, ledgers, receivables, payables, trial balance. Business Central models all of it.
- Navigate the system. Role centres, search, lists and cards, filters, and how to read posted documents and ledger entries.
- Core setup. Chart of accounts, posting groups, dimensions, number series, payment terms, users and permissions.
- Trade processes. Sales and purchase cycles from quote to invoice, and inventory costing and valuation.
- Extended areas. Warehousing, manufacturing, fixed assets, projects, approvals and reporting.
- Implementation concepts. Fit-gap analysis, data migration, testing and go-live. See our implementation process guide.
For the technical path
- Understand the product as a user first. You cannot extend a sales order process you do not understand.
- Learn AL fundamentals. Read what AL is and how extensions work, then practise with tables, pages, table extensions and page extensions.
- Add logic. Codeunits, triggers and event subscribers. Learn why extensions subscribe to events instead of editing base code.
- Reports and queries. Data items, layouts, and API queries for reporting.
- Integration. API pages, web services, and calling external services with HttpClient and JSON. Read the comparison of API pages and web services.
- Professional habits. Git and source control, debugging, automated tests, code analyzers and deployment to a sandbox.
Practise on realistic scenarios
Reading feature lists does not make you a consultant. Give yourself small, realistic tasks and finish them end to end.
- Functional: Set up a trading company with two dimensions, three customers and vendors, and a purchase-to-pay cycle. Post it, then trace a purchase invoice through to the general ledger and explain every entry.
- Technical: Add a custom field to the customer card, show it on a sales order, and block posting if it is empty. Then expose the customer data through a custom API page and call it from a REST client.
- Both: Write a one-page description of a business problem, the standard feature that covers most of it, and the gap. That is the essence of a fit-gap analysis.
What interviewers actually test
Interview questions vary, but they tend to probe understanding, not memorization. Expect questions like these:
- Walk through what happens when you post a sales invoice. Which ledger entries are created?
- What are dimensions, and how would you design them for a company with several departments and projects?
- Why should customizations be built as extensions rather than modifying base code?
- How does an event subscriber differ from a trigger, and when would you use each?
- How would you expose Business Central data to an external application?
- A user reports that a posting fails with an error. How do you investigate?
Answers that use a concrete example from something you built are far more convincing than a textbook definition.
Certifications, courses and self-study
Microsoft offers role-based certifications and free learning paths on Microsoft Learn, and they are worth using as a structured syllabus. Check Microsoft's current certification list, because names and exam codes change over time. A certificate can help a résumé get noticed, but the practical skills above are what get you through the interview and the first month on a project.
Structured training helps if you learn better with guidance and feedback. We run practical Business Central functional and Business Central technical programs. Batch details are shared on enquiry, and we do not promise placements or specific job outcomes.
Common mistakes to avoid
- Jumping into AL before understanding standard functionality, and rebuilding what already exists.
- Learning only on demo data without ever doing a data migration or a reconciliation.
- Treating the two paths as rivals. Developers who understand accounting and consultants who can read AL are noticeably more valuable.
- Collecting courses without building anything you can show.
Where to go from here
Pick a path, set up a sandbox this week, and complete one of the scenarios above. To see how consultants and developers work on real projects, browse our Business Central consulting and AL development pages, or ask us about training.
Key takeaways
- Choose functional if you enjoy business processes, technical if you enjoy building and debugging.
- Learn by working in a sandbox on realistic scenarios, not by reading feature lists.
- Understand accounting and inventory basics, because Business Central models both.
- Certifications and courses help, but demonstrable practice is what interviewers test.
