Start Your Project
Banking & Fintech Software

Client Money Reconciliation Software Run the Reconciliations the DFSA Rulebook Expects, and Evidence Every One

Custom client money reconciliation software for DIFC authorised firms. The DFSA's COB rules require a firm to maintain a system ensuring accurate reconciliations of client accounts - at least monthly, on a trade settlement date basis, and at least daily for firms providing money services - and fresh amendments to the COB and PIB modules came into force on 2 July 2026. Run across multiple banks, currencies and third party agents on spreadsheets, that cadence is where breaks hide and evidence gaps open. We build the reconciliation and evidence layer that sits alongside your ledgers and banking feeds; classification judgements and the auditor's report stay with your compliance team and auditors.

Paul Banks
Paul Banks Founder & Lead Consultant I handle all enquiries personally and look forward to hearing about your project.
CMR
Reconciliation Control Settlement-date basis
Reconciliation Cadence Breaks Status
Client USD accounts Daily 0 Complete
Client AED accounts Daily 2 ageing Investigate
TPA statements Monthly Matched Current
Resolution pack 5-day window 1 change Update
Preview shown is illustrative. Projects, values, and timelines are fictional examples — not real client data.
Part of our Banking Software Dubai guide — Custom client money reconciliation software for DIFC authorised firms - automated matching across banks and third party agents, break workflow, cadence control and examiner-ready evidence..
View the full guide

Why client money reconciliation breaks on spreadsheets

The rule sounds simple: reconcile the client accounts, at least monthly, daily if you provide money services. The operation is anything but. Ledger balances, cash books, unpresented items and formal statements from third party agents have to agree, on a trade settlement date basis, across every bank, currency and account - and the firm has to be able to show each reconciliation was actually performed, reviewed and resolved.

Daily cadence outruns manual process

A money services firm reconciling daily on spreadsheets is running a production line by hand. One absent analyst or one late bank statement and the cadence slips, and a slipped cadence is itself a finding.

Every source in a different format

Ledger extracts, bank statements, third party agent statements, cash books - each arrives in its own shape and timing. The matching work is mostly wrestling formats before reconciling anything.

Breaks investigated, resolution unevidenced

Differences get chased over email and fixed in the ledger, but the trail from break to explanation to correction lives in three inboxes. Months later, nobody can show how a difference was resolved.

Performance is the evidence

When the DFSA asks, the question is rarely whether a policy exists. It is show me the reconciliations: who performed each one, when, what it found, who reviewed it. A folder of spreadsheets answers that badly.

The reconciliation layer above your ledgers

Four capability areas that turn a manual reconciliation grind into a controlled, evidenced process, fitted to your account structure and sitting alongside the ledger and banking systems you already run.

Feed ingestion and matching

Ledger balances, cash books, bank statements and third party agent statements ingested in whatever format they arrive, normalised and matched on a trade settlement date basis, so the reconciliation starts from data rather than data entry.

Break and exception workflow

Every difference becomes a tracked item with an owner, an ageing clock, an explanation and its correction evidence, so a break is resolved once and provably rather than chased through inboxes.

Cadence and sign-off control

Daily, monthly and firm-specific frequencies scheduled per account group, with preparer and reviewer sign-offs, deadline escalation, and the previous-day balance check run as standard - so the cadence holds even when people are away.

Evidence and resolution pack

Each reconciliation stored as a versioned, timestamped record, exportable per account or period for the DFSA or your auditor, with the client asset resolution pack maintained current as account and agent details change.

A system, expressly

The rulebook language is worth reading literally: an authorised firm must maintain a system to ensure accurate reconciliations are carried out. The regulator has already told firms what the answer to how do you do this should look like - and it is not a spreadsheet folder.

Your reconciliation health at a glance.

A gauge view shows the control position. Reconciliations on cadence, breaks within ageing and evidence coverage tell compliance and finance what a supervisory visit would find, before one happens.

Discuss your reconciliation platform
Control Health (illustrative)
98%
Reconciliations on cadence
85%
Breaks within ageing limits
100%
Evidence coverage
Preview shown is illustrative. Projects, values, and timelines are fictional examples — not real client data.

Why DIFC firms invest in reconciliation control.

The standing rules and the fresh amendments behind them.

2 July 2026
PIB Rule-Making Instrument No. 441 and COB Rule-Making Instrument No. 442 of 2026 came into force, amending client money reconciliation and prudential calculation rules (DFSA)
Daily
The minimum reconciliation frequency for firms providing money services, against at least monthly on a trade settlement date basis for other authorised firms holding client money (DFSA COB App 5)
5 business days
The window within which the client asset resolution pack - master account lists, third party agent details, reconciliations - must reflect changes (DFSA COB, reported)
Talk to Us

Talk to us about client money reconciliation software.

A short call surfaces whether a custom reconciliation platform makes sense for you. Best positioned for DIFC authorised firms holding or controlling client money across multiple banks, currencies or third party agents, and for money services firms carrying the daily requirement. A firm with one client account and a handful of monthly movements is well served by a disciplined spreadsheet, and we will say so. We build the reconciliation and evidence system; we are not an auditor, a compliance consultancy, or a law firm. Whether money is client money, how the rules apply to your permissions, and the client money auditor's report stay with your compliance team, advisers and auditors. BY BANKS is an independent software engineering company: we design and build the platform and hand it over, your team operates it. Authority names on this page are referenced descriptively to describe scope, and imply no affiliation, endorsement, or approval. Rules summarised are point-in-time. This is not legal or compliance advice.

Paul Banks
Paul Banks Founder & Lead Consultant I handle all enquiries personally and look forward to hearing about your project.

How client money reconciliation software works for a DIFC firm

The detail behind the headline - from feed ingestion and matching, through the break workflow and cadence control, to the evidence record. Operation and evidence, not classification judgements and not an audit.

What changes, in practical terms

Before Reconciliation by spreadsheet
Statements chased and rekeyed from every bank and agent.
Daily cadence dependent on one analyst being at their desk.
Breaks resolved in inboxes, explanations lost.
Sign-off implicit, review undocumented.
A DFSA request answered by a folder and an apology.
After Reconciliation as a system
Feeds ingested and matched on settlement date basis automatically.
Cadence scheduled, escalated and held regardless of absences.
Every break tracked to explained, corrected and evidenced.
Preparer and reviewer sign-offs on every reconciliation.
A DFSA request answered by an export.
We reconcile, you judge

We do not determine what counts as client money, interpret how the rules apply to your permissions, or provide the auditor's report. The system runs the matching, the workflow and the evidence; the judgements stay with your compliance team, advisers and auditors.

The detailed questions DIFC firms ask us

Expand each to see how bespoke reconciliation software actually works.

What does client money reconciliation software actually cover?

Who this is for: DIFC authorised firms holding or controlling client money across multiple banks, currencies or third party agents, and money services firms carrying the daily requirement. A firm with one client account and light movement does not need it, and we will say so.

Four connected areas: (1) Feed ingestion and matching on a trade settlement date basis. (2) A break and exception workflow. (3) Cadence and sign-off control. (4) A versioned evidence record with the resolution pack maintained. It runs and evidences the process; it does not judge or audit.

What do the DFSA rules actually require?

In summary, and read the rulebook rather than this page for the detail: an authorised firm must maintain a system ensuring accurate reconciliations of client accounts at least monthly, performed on a trade settlement date basis, reconciling individual client ledger balances, cash book balances, unpresented items and formal statements from third party agents - with a check that client account balances covered the aggregate owed as at the previous close.

Firms providing money services must reconcile at least daily. Amendments to the COB and PIB modules came into force on 2 July 2026. How the rules apply to your specific permissions is a question for your compliance team and advisers.

How does the daily requirement change the build?

Daily reconciliation is a production process, and the build treats it as one: feeds collected automatically as statements arrive, matching run without manual triggering, and the day's reconciliation ready for review rather than started from scratch.

The cadence control matters as much as the matching. Deadlines, escalation when a feed is late or a reviewer unavailable, and a visible record that every day's reconciliation happened - because at daily frequency, the gap that opens when process depends on individuals is precisely what a supervisor will find.

How does the break workflow operate?

Every unmatched or mismatched item becomes a tracked break with an owner and an ageing clock. The investigation, the explanation and the correcting entry are recorded against it, and closure requires the evidence to be attached rather than asserted.

Ageing breaks escalate before they become stale, and the break history per account becomes its own signal - the same counterparty or process producing repeated differences is a control finding waiting to be made, and better made by you than by the DFSA.

Where does the data come from?

From the systems you already run: your ledger or core platform for client balances and cash books, bank feeds or statements for account balances, and third party agents' formal statements in whatever shape they arrive. The platform normalises each source once, then every subsequent reconciliation starts from clean data.

We do not replace your ledger, your banking relationships or your payment systems; the reconciliation layer sits above them. Integration approach is scoped during discovery.

Does it cover the prudential side too?

As a data layer, yes. The July 2026 PIB amendments touch how average balances feed prudential calculations, and a firm whose reconciled client money position is held in one system can feed those calculations and returns from clean numbers rather than assembled ones.

The calculations themselves, and the regulatory returns, remain your finance officer's and advisers' work - commonly alongside your reporting tooling. What the platform contributes is a reconciled, evidenced source.

What does this sit alongside in a typical firm?

Reconciliation control sits between the ledgers and the compliance function.

Core systems - it draws balances and transactions from your ledger, banks and third party agents without replacing any of them.

Compliance and audit - it feeds evidence to your compliance monitoring and gives your client money auditor a clean record to test. Integration approach is scoped during discovery, and we do not ask you to replace tools that work.

How long to go live, and what does it cost?

A scoping phase maps your account structure, feed sources, current reconciliation practice and break history. It produces a current-state map, gap analysis, recommended scope, integration scope and a fixed-price build proposal.

A core build runs from there, with ingestion and matching first, then the break workflow, cadence control and evidence record. Pricing varies by scope and account complexity, so a bracket is not published; scoping produces a fixed-price proposal with no obligation to proceed.

How each role experiences the change

Different roles feel client money control differently. Custom software works when it reduces friction for each one.

Compliance

Evidence that the system the rulebook requires actually exists and runs - every reconciliation timestamped, signed off and exportable on request.

Finance and operations

The daily grind of formats, matching and chasing replaced by review and exception handling, with the cadence holding through absences.

Auditors

A clean, versioned reconciliation record to test against, so the client money audit runs on evidence rather than reconstruction.

Senior management

Reconciliation health as a standing metric - on cadence, breaks ageing, evidence complete - instead of an assurance taken on trust.

Questions We Get Asked

Who is client money reconciliation software for?

DIFC authorised firms holding or controlling client money across multiple banks, currencies or third party agents, and money services firms carrying the daily requirement. A firm with one client account and light movement is well served by a disciplined spreadsheet, and we'll say so.

What do the DFSA rules require?

In summary: a system ensuring accurate client account reconciliations at least monthly, on a trade settlement date basis, covering ledger balances, cash books, unpresented items and formal third party agent statements - and at least daily for firms providing money services. COB and PIB amendments came into force on 2 July 2026. How the rules apply to your permissions is your advisers' question.

Does it replace our ledger or banking systems?

No. Balances and transactions flow in from your ledger, banks and third party agents; the reconciliation layer sits above them, matching on a settlement date basis and holding the evidence. Integration is scoped during discovery.

How does it handle the daily requirement for money services firms?

As a production process: feeds collected automatically, matching run without manual triggering, deadlines and escalation built in, and a visible record that every day's reconciliation happened - so the cadence survives absences and late statements.

What happens when a reconciliation finds a difference?

Every break becomes a tracked item with an owner, an ageing clock, an explanation and attached correction evidence. Ageing breaks escalate, and repeat patterns per account or counterparty surface as the control findings they are.

Does it produce evidence for the DFSA or our auditor?

Yes - that's the design centre. Each reconciliation is a versioned, timestamped record with preparer and reviewer sign-offs, exportable per account or period, and the client asset resolution pack stays current as details change.

Does it determine what counts as client money?

No. Classification, how the rules apply to your permissions, and the client money auditor's report stay with your compliance team, advisers and auditors. The system runs the process they rely on.

What does it cost and how long does it take?

A scoping phase produces a current-state map, gap analysis, recommended scope and a fixed-price build proposal. Ingestion and matching come first, then the break workflow, cadence control and evidence record. Pricing varies by account complexity; scoping gives a fixed price with no obligation to proceed.

Get in Touch

Let's Discuss Your Project

Fill in the form, message us on WhatsApp, or send an email.

Paul Banks
Paul Banks Founder & Lead Consultant I handle all enquiries personally and look forward to hearing about your project.

Quick Assistance

Chat with us directly on WhatsApp.

Open WhatsApp →

Email Us

Gmail, Outlook, Yahoo & more.

Choose your email app →

BY BANKS L.L.C-FZ

License No. 2425027.01

Meydan Free Zone, Dubai, UAE

Procurement-ready · UAE registered

Not ready to talk yet? See if we're the right fit Pick your preferred AI and it'll ask about your project, then assess whether BY BANKS is a good match. AI-generated output, not BY BANKS advice. See our Terms.

Web clients open in a new tab

Still exploring?

We'd love to help you find what you're looking for. Whether you have a project in mind or just want to learn more about what we do.