Newgate Systems

For Dynamics 365 partners and ISVs

The AL and X++ workstream your architects have no time for.

You have signed the client. The project carries a heavy extension, integration or migration workstream, and your senior people are being pulled off billable work to cover it. We deliver that workstream as a scoped package, under your process.

01 — Scope

Bounded work, not a blended team.

We take a defined piece of the project and deliver it against acceptance tests.

Business CentralAL extensions, API and web service integrations, data migration
Finance & Supply ChainX++ development, data entities, SSRS reports, retail and POS customisation
IntegrationREST APIs, EDI, e-commerce and WMS integrations, Azure pipelines and Logic Apps
DataLegacy data migration and cleansing, cutover support
After go-liveHypercare and defect resolution for the workstream we delivered
For ISVsDynamics connectors built and maintained for your product

02 — Under your process

Your client, your process.

Your client stays yours

We sign a written non-solicitation covering your clients before any work starts.

Your brand or ours

We can appear as part of your team or as a named subcontractor. Your choice, per project.

A named technical lead

One lead owns the work package and is directly reachable by your architect and delivery lead.

Code review and acceptance tests

Every delivery is reviewed and passes the acceptance tests agreed at the start.

Client-owned repositories

We work in your repositories, or your client's. Nothing lives on ours.

Least-privilege access

We ask for the access the work needs, and it is removed when the work ends.

03 — Engagement

Start small, then decide.

Step 1

Scoped pilot · 2–4 weeks

One bounded piece of work with acceptance tests written before we begin. You judge the code, the communication and the delivery against your own standard.

Step 2

Named engineer or managed pod

If the pilot holds up, we continue as a named engineer or a small pod under the same technical lead, on fixed scope or ongoing capacity.

04 — Proof

Dynamics work in production.

05 — For ISVs

Your product, connected to Dynamics.

Your customers run Business Central or Finance & Operations and expect your product to work with it. We build the connector, handle the error cases and keep it supported as Microsoft ships updates.

  • Scoped against the entities and documents your product needs
  • Error handling, retries and logging built in, not added later
  • Maintained after release by the people who built it

We built the Dynamics 365 connector for Tipalti's accounts payable platform.

06 — GCC

Direct work in Saudi Arabia and the GCC.

In the GCC we also work directly with businesses running Dynamics, mainly on ZATCA e-invoicing, Arabic localisation and migration.

Where the work actually is

  • 01Legacy migration — extracting and cleansing decades of data out of whatever you're on now
  • 02Integration — the banking, logistics and government systems Dynamics has to talk to
  • 03ZATCA Phase 2 e-invoicing — direct integration with the Fatoora platform, clearance and reporting
  • 04Arabic & Hijri localisation — bilingual interfaces and calendars that behave correctly
  • 05After go-live — the support window where most implementations are actually judged

On ZATCA: Phase 2 integration now reaches businesses above SAR 187,500 in annual taxable turnover, with the latest wave due by 1 February 2027. If your ERP still isn't clearing invoices through Fatoora in real time, that is a deadline rather than a roadmap item — and it's the single most common reason we get called into an existing Dynamics estate.

07 — Contact

Discuss a work package.

Tell us the product, the workstream and the deadline. A technical lead replies the same working day.

ResponseSame working day

Or email co@newgatesystems.com directly.