Asio Services
All articles

Business Central

14 Business Central AL Extensions Every Developer Should Know in 2026

Thousands of AL extensions exist on AppSource and GitHub, and quality varies wildly. Here is our curated 2026 list of 14 we trust in production, plus the ones we stopped recommending.

A widescreen monitor on a wooden desk in a dark blue office, showing a code editor with coloured AL syntax on the left and a four-by-three grid of teal tool icons on the right, beside a small plant, a dark mug and a keyboard.

14 Business Central AL Extensions Every Developer Should Know in 2026

Business Central’s AL extension model is one of Microsoft’s quietest engineering successes. It forces partners and developers to package customizations as clean, versioned, upgrade-safe modules. The downside: there are thousands of AL extensions on AppSource and GitHub, and the quality varies wildly.

This article is our curated 2026 list of 14 AL extensions we consider high-value for serious BC implementations. We use most of these in production. We have stopped using a few. The selection is biased toward extensions that solve real problems without locking you in.

What makes an AL extension worth installing

Before the list, our selection criteria. A worthwhile AL extension does five things.

It installs and uninstalls cleanly. No leftover tables, no orphan fields. You should be able to remove it without scarring your tenant.

It respects the standard BC data model. The best extensions add fields and pages without touching base objects. The worst ones modify standard tables and break on the next update.

It has visible engineering. Source on GitHub, semantic versioning, a changelog, real support contact. Vapor-ware is everywhere on AppSource.

It has a clear use case. « Universal toolkit » extensions are usually solving everything badly. Specialized extensions solving one problem well are worth more.

It has a sustainable business model. Free open-source is great. Paid is also great if the price reflects the value. Beware of « free » extensions that monetize through implementation services.

Four pale trays of raised icon tiles on a white background: a blue tray with code brackets and cursors, a green tray with shields, a checkmark, a gauge and a bug, an orange tray with documents and an invoice, and a slate tray with a plug and network diagrams.
The four families the list is built on: developer productivity, quality and lifecycle, functional extensions, integration and platform.

Developer productivity extensions (5)

  1. AL Code Outline (free, by Andrzej Zwierzchowski). A clean Visual Studio Code panel showing the outline of any AL object. Removes the pain of hunting for procedures in 5,000-line codeunits.
  2. CRS AL Language Extension (free, by Christian Rosa Svejstrup). A bundle of refactoring and snippet tools for AL development. Auto-rename, format-on-save, quick navigation to triggers. Essential for any serious AL dev.
  3. AL CodeActions (free, by David Feldhoff). Generates boilerplate for table extensions, page customizations and pre-defined patterns. Saves hours over a quarter.
  4. AL Test Runner (free, by James Pearson). Run BC unit tests directly from VS Code without leaving your editor. The closest thing to a real test feedback loop.
  5. AL Object Designer (free, by Márton Sági). Browse and search standard BC objects from VS Code. Replaces the old NAV Object Designer for the AL era.

Quality and lifecycle extensions (3)

  1. AL Language Tools (Microsoft, free). Microsoft’s official linter and code analyzer. Run it in CI to catch warnings before they reach production.
  2. AL Cops (free, by Arthur van de Vondervoort). A modern set of domain-specific AL code analyzers, the successor to Stefan Maron’s BusinessCentral.LinterCop. Catches anti-patterns the built-in cops miss.
  3. Performance Toolkit (Microsoft, free). Measure performance of AL operations across releases. Helps prove you have not regressed on the latest BC update.

Functional extensions (3)

  1. Document Capture (Continia, paid). The gold-standard for invoice and document automation. Worth its price for any BC implementation processing more than 200 supplier invoices per month.
  2. Expense Management (Continia, paid). Mobile expense reporting integrated to BC purchase invoices. Replaces five disconnected tools with one workflow.
  3. Power BI Embedded Reports for BC (Microsoft, free with BC). Out-of-the-box BI on top of BC entities. Start here before you build custom Power BI from scratch.

Integration and platform extensions (3)

  1. Business Central API v2.0 enhancements (Microsoft, free). The standard API set has matured into a genuinely powerful integration surface. Combined with Power Automate, you can replace 90 percent of legacy middleware.
  2. EDI Connector (varies by partner, paid). For B2B-heavy companies, an EDI extension automates the EDIFACT/X12 message flow. Saves weeks of manual integration code per partner.
  3. Business Central Connector for Power Pages (Microsoft, free). Build customer portals on top of BC data without exposing the back-office UI. The right pattern for self-service customer access.

Extensions we have stopped recommending

We have removed three categories of extensions from our standard kit since 2023.

First, « UI super-customizers » that re-skin BC pages. Microsoft has caught up with the standard role centers and most of these extensions are now redundant. They also tend to break on the next BC update.

Second, « Excel-everything » extensions that aggressively replace BC reporting. The native Excel layouts and Power BI options have closed the gap. Adding a heavyweight reporting extension on top is usually unnecessary.

Third, « AI add-ons » that wrap GPT around BC pages. Microsoft Copilot is being natively integrated into BC. Third-party AI wrappers will become obsolete in 12 to 24 months.

How to evaluate an AL extension before installing

Five minutes of due diligence before any extension install saves weeks of regret.

Check the publisher’s GitHub. A real publisher has commits in the last 90 days, semantic versioning, and a tagged release per BC version.

Read the manifest. The app.json tells you which BC version is supported, which permissions the extension requires, and whether it modifies standard tables.

Test in a sandbox tenant first. Always. Installing directly in production is a habit that ends in disaster sooner or later.

Run your test suite after install. If you don’t have a test suite, this is a sign that you should build one before adopting more extensions.

Verify the uninstall procedure. Some extensions cannot be removed cleanly. Know this before you commit.

The Asio Services way: fewer extensions, more discipline

Our philosophy on AL extensions is the same as our philosophy on Business Central development and customization: less is more. Every extension is a dependency. Every dependency is a future maintenance cost. We aim to ship BC implementations with the smallest possible extension footprint that still delivers the business value, leaning on the standard platform and the Business Central API wherever they already reach.

On a dark blue field, a dense tangle of dozens of grey icon tiles wired together on the left narrows through a funnel of light into four cleanly connected teal tiles on the right.
The clean-up we have run on real tenants: from 60-plus accumulated extensions down to a healthy ten, with no business functionality lost.

If you are evaluating which extensions to include in your BC project, or auditing what your existing tenant has accumulated, we can help. Rescuing a Business Central tenant is a large part of what we do: we have taken tenants from 60+ extensions back to a healthy 10, with zero loss of business functionality.

Is your Business Central the problem, or the symptom?

We audit what you actually run, name what is worth keeping, and kill the rest. One conversation is usually enough to tell which one you are dealing with.

Start with clarity

Read next