Newgate Systems Start a conversation

Case study · Integration

The operational core
behind open banking.

Tarabut provides the APIs and infrastructure that let banks and fintechs across MENA connect financial data, move payments and embed financial services.

Client
Tarabut
Industry
Open banking & embedded finance
Region
MENA — regulated in Bahrain, active in Saudi Arabia
Platform
Dynamics 365 F&O on AWS

01

The client

Tarabut is a regulated open finance company — licensed by the Central Bank of Bahrain and active in Saudi regulatory sandboxes. It sells Banking-as-a-Service, data products, embedded finance and account-to-account payments to institutions that are themselves heavily regulated.

That regulatory position is the whole business. A platform banks connect to has to be auditable end to end, which means the internal systems behind it are not back-office admin — they are part of the compliance surface.

02

The problem

Tarabut was running a fast-growing regulated business on disjointed tools. Partner onboarding, KYC/AML tracking, financial reconciliation and revenue forecasting each lived somewhere different, which meant the picture of the business had to be assembled by hand.

For a company whose customers are banks, that is not just inefficient. Onboarding speed is a competitive feature, and reconciliation that depends on manual effort is a finding waiting to happen at the next audit.

03

Requirements

  • R1A single operational backbone replacing disconnected tools
  • R2Partner management and onboarding workflows in one system
  • R3KYC/AML tracking auditable from end to end
  • R4Automated financial reconciliation and billing
  • R5Revenue forecasting from live data rather than exports
  • R6Real-time analytics on compliance, payments and API usage

04

The solution

We architected a Dynamics 365 operational core and integrated it directly into Tarabut's API ecosystem, so the ERP works from the same data the platform runs on rather than from periodic exports.

The design decision that mattered: wiring the ERP into the API ecosystem rather than syncing to it. Anything batch-based would have meant the compliance view was always slightly out of date — which for a regulated business is the same as being wrong.

05

The work

  • 01CRM module. Partner management, KYC/AML tracking and onboarding workflows unified in one place.
  • 02ERP module. Automated financial reconciliation, audit readiness, billing and revenue forecasting.
  • 03Data intelligence layer. Real-time analytics dashboards covering compliance, payments and API usage.
  • 04Cloud infrastructure. AWS-hosted, microservices-driven and containerised for scale and resilience.
  • 05API integration. The operational core connected into Tarabut's existing API ecosystem.
D365 Finance & OperationsAWSMicroservicesKYC / AMLReconciliationPower BI

06

Outcome

60%

Reduction in partner onboarding time

80%

Of manual reconciliation and compliance reporting automated

360°

Visibility across financial, operational and regulatory workflows

More work

Other records.

Next

Facing something like this?