
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.
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.
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.
Decide the source of truth for every entity before design starts. Write it down and get finance and IT to sign it.
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.
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.
These are the failures we design against on every project. Use the list as a checklist in your own design review.
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.
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.
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.
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.

