Book a Discovery Session

Union

Thank you!

We've received your details. Our team will contact you shortly to arrange a call.
Sorry, that didn't go through. Please try again, or message us on WhatsApp at +971 52 674 7295.
Logo with stylized lowercase letters 'pe' above the words 'PURE ELEMENTS'.
Contact Us
Book a Discovery Session
arrow-sm-right
Back

Dynamics 365 Finance integration: connecting a custom portal without breaking finance

Hamad Rashid
Hamad Rashid
14 November 2026
7 min read
Integrations
Cover for: Dynamics 365 Finance integration: connecting a custom portal without breaking finance

A good Dynamics 365 Finance integration lets your portal own the customer experience while Finance stays the system of record for money. You get there by choosing the right pattern for each data flow, agreeing who owns each record, and building for failure from day one. Most sync problems come from skipping one of these, not from the API itself.

This guide is for CIOs, IT heads and finance systems leads in the UAE who are connecting an admissions, booking or customer portal to D365 Finance. It covers the patterns that work, the pitfalls we see most, and the questions to settle before anyone writes code.

Why connect a custom portal to Dynamics 365 Finance?

Off-the-shelf portals rarely match how a school, developer or service business actually sells. A custom portal can fit your journey exactly, but only if what happens in it lands correctly in Finance.

Without an integration, someone re-keys customers, invoices and payments by hand. That costs hours every week and produces the mismatches that surface at month-end.

With one, a family registers or a buyer pays in the portal and Finance has the customer, the invoice and the payment posted against the right legal entity. Your finance team reviews exceptions instead of typing.

Which integration pattern should you use?

There is no single right pattern. Each data flow gets the one that matches how fast it must arrive and how much volume it carries.

Pattern How it works in D365 Finance Use it for Trade-offs
Real-time API Portal calls OData data entities or a custom service, authenticated through an Entra ID app registration Customer creation, balance lookups, anything a user waits on Subject to service protection (throttling) limits; the portal must handle Finance being slow or unavailable
Scheduled batch Files or packages through the Data Management Framework on a recurring job High-volume imports, nightly payment files, historical loads Data is only as fresh as the last run; failed rows need a clear review process
Event and queue Finance raises business events; a queue such as Azure Service Bus, or Logic Apps, carries messages between systems Status changes Finance owns, such as an invoice posted or a payment settled More moving parts to monitor; messages must be processed exactly once

Most real integrations combine all three. A typical school portal creates customers in real time, sends settled gateway payments in a scheduled batch, and listens for posting events to update what parents see.

If you also run Dynamics 365 Customer Engagement, Dual-write can keep some shared records in sync between CE and Finance. It does not replace an integration for your custom portal.

Who owns each record?

Decide the source of truth for every entity before design starts. Write it down and get finance and IT to sign it.

  • Customers: often created in the portal, owned in Finance once created. Edits flow one way only.
  • Invoices and fees: defined in Finance, shown in the portal.
  • Payments: captured by the gateway, recorded by the portal, posted in Finance.
  • Reference data: legal entities, financial dimensions, payment methods and number sequences live in Finance; the portal reads them.

Two systems both allowed to edit the same field is the most common root cause of drift. Pick one owner per field, not per system.

How does payment reconciliation work with Dynamics 365?

Dynamics 365 payment reconciliation starts in the portal, not in Finance. Every payment needs a unique reference that travels from the gateway, through the portal, into the payment journal.

The portal sends the settled payment with that reference, the customer account, the legal entity and the financial dimensions. Finance records it in a customer payment journal and settles it against the open invoice.

A daily reconciliation report then compares three totals: what the gateway settled, what the portal recorded, and what Finance posted. Any difference is a named exception for a person to resolve, not a month-end surprise.

Pitfalls that break a Dynamics 365 Finance integration

These are the failures we design against on every project. Use the list as a checklist in your own design review.

  • Duplicate payments. Retries happen. Make every write idempotent, keyed on the payment reference, so a resent message never posts twice.
  • Unclear master data ownership. Two systems editing the same customer field will drift. One owner per field.
  • Poor customer matching. Match on a stable key, such as the portal customer ID stored in Finance, never on name or email alone.
  • Wrong legal entity or dimensions. Map each portal transaction to the correct legal entity and financial dimensions, and validate before sending.
  • Posting directly when you should stage. Land data in journals or staging first, validate, then post. Direct posting turns small errors into reversals.
  • No error queue. Failed messages need a dead-letter queue, automatic retries with backoff, and a screen where someone can see and replay them.
  • No monitoring or alerting. Track sync failures, queue depth and job runs, and alert your team before users notice a gap.
  • Testing only in production. Run every change through a sandbox environment with realistic data, including Finance updates on Microsoft's release schedule.
  • Credentials that never rotate. Store app registration secrets in a vault, rotate them on a schedule, and know who is alerted when one expires.
  • Changes on one side breaking the other. A new field in the portal or a renamed entity in Finance can break the sync. Version the contract between systems and test both sides on every release.
  • No reconciliation report. Without a daily gateway, portal and Finance comparison, nobody can prove the integration is correct.

What does this look like in practice?

We have been working alongside Emirates National Schools since 2021 on admissions, fee payments and a parent portal connected to Dynamics 365 Finance. The lessons in this guide come from that kind of long-running work, where the integration has to stay correct term after term.

The same approach applies beyond education: property bookings and payment plans, service subscriptions, or any portal where money moves. See how we approach ERP and school-system integration and school admissions and fee payments.

How do you keep the integration healthy after launch?

An integration is never finished. Finance receives regular updates, your portal changes, and business rules move.

Treat it as a running system with an owner: monitoring, alerting, a support agreement with agreed response times, and a change process that tests both sides. Our approach to this is on the support and maintenance page.

Questions IT teams ask

Do we have to replace our ERP to get a modern portal? No. Dynamics 365 Finance stays the system of record. The portal handles the user journey and reads and writes through the integration.

Real-time or batch: which is better? Neither on its own. Use real time where a user is waiting, batch for high volume, and events for status changes Finance owns.

What happens when Finance is unavailable? The portal queues the message and retries. Users can still complete their step, and the record posts once Finance responds.

Who owns the integration code? You do. The full source code, documentation and credentials are handed over to you on final payment.

Talk it through

Planning a portal on top of Dynamics 365 Finance, or fixing one that drifts? Book a discovery session and we will map your data flows, owners and risks with your team.

bulb
Planning a portal, an integration or a support contract?
Union
Book a Discovery Session

Recommended Posts

Union
View All Posts
Cover for: School admissions portal: how it should work, from application to paid fees
School admissions portal: how it should work, from application to paid fees
What a good admissions portal does at each stage, from first application to paid fees and ERP posting.
Read the admissions guide
Read More Arrow
Cover for: Build vs Run: What a Software Maintenance Contract Should Cover in Year One
Build vs Run: What a Software Maintenance Contract Should Cover in Year One
What a maintenance contract should cover in the first year after launch, and the red flags to spot before you sign.
Read the support guide
Read More Arrow
Cover for: School admissions portal: how it should work, from application to paid fees
School admissions portal: how it should work, from application to paid fees
What a good admissions portal does at each stage, from first application to paid fees and ERP posting.
Cover for: Build vs Run: What a Software Maintenance Contract Should Cover in Year One
Build vs Run: What a Software Maintenance Contract Should Cover in Year One
What a maintenance contract should cover in the first year after launch, and the red flags to spot before you sign.
Book a Discovery Session
Link Copied