Wevanza

Business Central AL Development

Custom Business Central extensions, built to survive every update.

When standard Business Central doesn't fit a process, we build it in AL — custom tables, pages, reports, workflows and integrations — as SaaS-compatible extensions that stay upgrade-safe.

A good fit if:

  • Your process needs logic that standard Business Central doesn't offer
  • You need custom reports, document layouts or Excel import/export
  • Old customizations break with every update
  • You're a partner who needs extra AL capacity

How we build

From requirement to deployed extension

Specify

Step 1
  • Requirement

    Agree the business outcome and acceptance criteria

  • Design

    Use events and standard objects wherever possible

Build

Step 2
  • AL development

    Tables, pages, reports, codeunits and APIs

  • Code review

    Source control and code analyzers on every change

Test

Step 3
  • Sandbox testing

    Validated in a sandbox before production

  • UAT

    Your users sign off against real scenarios

Deploy

Step 4
  • Release

    Deployed with version control and release notes

  • Handover

    Documentation and knowledge transfer

What's included

What you get, and what's often added

What we build

  • Custom tables, pages, reports, and codeunits
  • AL extension development
  • Custom workflows and business logic
  • Excel import and export functionality
  • Document layouts and reporting enhancements
  • SaaS-compatible extension design

Also available

  • Standard and custom Business Central APIs
  • Automated tests for critical extensions
  • Converting legacy C/AL changes to AL
  • Upgrade compatibility checks before each release

FAQ

AL Development: common questions

What is AL development in Business Central?

AL is the language used to build extensions for Business Central. Wevanza builds custom tables, pages, reports, workflows and integrations as SaaS-compatible extensions that stay upgrade-safe.

What does Wevanza build with AL?

Custom tables, pages, reports and codeunits, custom workflows and business logic, Excel import and export, document layouts and reporting enhancements, and SaaS-compatible extension design.

How are Business Central extensions tested and released?

Each change goes through source control and code analyzers, is validated in a sandbox, and is signed off by your users against real scenarios before being deployed with version control and release notes.

Can Wevanza convert old C/AL customizations to extensions?

Yes. Converting legacy C/AL changes is part of the work, so customizations that break with every update become upgrade-safe AL extensions.

Have a Business Central customization in mind?

Describe the process you need to support. We'll advise whether it fits standard BC or needs an AL extension — and what it takes.

Book a Consultation