Service · Software development

Custom financial sector software development.

Custom software for banks, insurers, pension funds, asset managers and fintech start-ups. Customer portals, KYC flows, compliance platforms, risk and portfolio tooling, financial modelling apps and white-label tools — built around the regulations you know, alongside the packages you already run.

Customer portalsKYC / AMLDORA & WftQuant & modelling

We don't replace Temenos or Mambu.

Let's be clear about that from the start: an enterprise bank that wants to replace its entire core, or an insurer rebuilding its policy administration from scratch, is looking at a programme of many years and millions of euros — the territory of Temenos, FIS, Finastra, Mambu, SS&C, Avaloq and the like. That's not what we do. The same goes for standard suites such as Wolters Kluwer OneSumX, ING tools or the Adyen platform: buy the package, and we'll integrate with it.

What we do do: build the software that's missing alongside those standard packages. A modern customer portal for account access, transactions or policies. Digital onboarding with KYC and Wwft (Dutch anti-money laundering act) checks. A platform where your compliance team records DORA incidents and third-party risk. Risk and portfolio management tooling that runs your own models, instead of the generic version from a Bloomberg add-on. Quant apps for financial modelling, treasury tools for corporates, claims platforms for insurers, and fintech MVPs for start-ups that don't even have a core yet.

Our clients: banks that want to renew a specific flow, insurers that need digital claims or policy portals, pension funds modernising their participant environments, asset managers whose client reporting is still sent as PDFs, payment institutions launching a product under PSD2 or PSD3, family offices that no longer want their consolidated reporting in Excel, asset managers with factor models, trust offices digitalising their client files, and accountants or tax advisers developing a fintech arm. The common thread: you know the regulations and the market, and we deliver the software that makes it work.

What we build.

Three types of projects where our experience with regulated financial platforms, custom fintech and compliance software comes into its own. In the first conversation, we determine which path fits your scope, your existing IT landscape and the regulator keeping an eye on things.

Customer-facing application · alongside your existing core

Customer portal, onboarding app or policy environment

Your core systems work perfectly well — it's just the layer your customers use every day that feels outdated. We build the modern customer portal for account access and transactions, the participant portal for a pension fund, a policy and claims environment for an insurer, or an onboarding app with integrated KYC and Wwft checks. With SSO via your IdP, iDIN or DigiD for identity, push notifications on every status change, and an API layer that talks neatly to your existing core instead of replacing it.

Customer portaliDIN / DigiDKYC / AMLMobile & web
Compliance and risk platform · operational tooling

Custom compliance, DORA or risk platform

For the teams that work with regulation and risk: a platform where you record DORA incidents, third-party risk and ICT resilience, a KYC and AML environment that supports your onboarding, a DORA platform — see also DORA compliance software — or a risk management tool in which you track limits, exposures and stress scenarios without replacing your core system. With auditable logging, dashboards for your board, and a data model that can feed AFM, DNB or internal audit reports directly.

DORA registerRisk dashboardsWwft & AMLAudit trail
Fintech platform or quant app · scale-up or corporate

Fintech MVP, modelling app or white-label platform

For fintech start-ups, asset managers, family offices and quant teams that need their MVP, V2 or a specific modelling application. Financial modelling software that takes Python models from research into production, a treasury tool for corporates that consolidates liquidity across multiple banks, a white-label platform for financial tools that you deliver to partners under your own brand, or a wealth platform with client reporting and portfolio analytics. Open Banking integrations via PSD2, a calculation engine that scales, and all DORA, GDPR and MiFID II requirements built in.

Some financial entities are designated for threat-led penetration testing, with its own separation of roles and its own deliverables. See the page on TLPT software.

Quant & modellingOpen BankingWhite-labelPortfolio analytics

What we do and don't deliver.

The financial sector draws a sharp distinction between standard suites, licensing and custom software. We deliberately operate in the latter domain, and we are transparent about that.

For packaged software work, such as a new core system, a Solvency II reporting engine or an EMIR transaction reporter, you work with the specialist vendors. For licences, you work with a Wft lawyer or compliance adviser. We connect to those technically and build the part where the existing offering falls short.

  • Customer-facing applicationsCustomer portals, mobile apps, policy and claims environments, participant portals for pension funds, and wealth reporting for private clients.
  • Compliance and risk softwareDORA registers, third-party risk modules, KYC/AML onboarding, transaction monitoring dashboards, Wwft controls and audit trails. Not a separate procedural layer, but built into the software.
  • Quant and modelling appsFinancial modelling software that takes Python or R models from research into a production-grade environment, with version control, reproducible runs and explainable results.
  • Integrations with core and standard packagesIntegrations with Temenos, FIS, Finastra, Mambu, SS&C, Avaloq, OneSumX, Adyen, ING tools and aggregators such as Tink or Yapily. Via REST, SOAP, ISO 20022 or file exchange, depending on what the vendor offers.
  • What we do NOT deliverNo replacement of your core administration or policy package. No DNB or AFM licence applications. No in-house Solvency II or EMIR reporting engine. No accounting engine that produces an IFRS ledger or tax returns.

Compliance and regulation in software.

The financial sector is a layered stack of regulation, and software you deploy there has to support that layering properly. We build software around Wft, DORA, MiFID II, IDD, EMIR, PSD2 and, in the foreseeable future, PSD3, GDPR, Wwft, Solvency II, IFRS and, for parties under direct DNB supervision, BIO as a framework. We build the controls into the software rather than adding them as a separate procedural layer on top; that way every transaction and every user action automatically passes through the checks your compliance team has defined.

In practice, that means an immutable audit trail on every change, recording who, what, when and why. A role and authorisation model that makes segregation of duties demonstrable. KYC and Wwft checks that trigger the right level of due diligence for each client category. Transaction monitoring with rules your compliance officer can adjust themselves, plus alert flows to AFM notifications or FIU reports where relevant. And for DORA: a register of ICT third parties, a classification scheme for incidents, and exportable overviews for your regulator.

On the privacy and data side: encryption in transit and at rest as standard, secret management via an HSM or cloud equivalent (AWS CloudHSM, Azure Key Vault Managed HSM), pseudonymisation wherever the business allows it, and retention periods derived from the legal regime rather than an arbitrary default. We document the controls in a way your compliance or internal audit team can reuse directly for DNB, AFM or EBA reporting: not a loose spreadsheet, but output from the system itself.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

When an engagement with us is a good fit.

Four recognisable patterns in which we often get involved in the financial sector. If one sounds familiar, we're happy to talk further.

Modernisation

Your customer portal feels outdated

Your core administration works fine, but the customer environment hasn't been touched in years. Account views, policy changes or transaction history sit on a legacy skin that's unusable on mobile. A new portal alongside the core system, with an API layer that leaves the core untouched, is then the smartest route.

Compliance deadline

DORA, Wwft or MiFID II requires action

The DORA deadline is approaching and your incident management lives in a shared mailbox. Your Wwft onboarding consists of separate Word forms. Or MiFID II requires call recordings and suitability checks that your current stack can't handle reliably. A modular compliance app that digitises this flow tightly, without you having to replace your core system.

Fintech MVP

You're launching a new proposition

You have a fintech idea (a savings product, a payment app for a community, a wealth tool for a niche group) and the first version has to reach the market without a weak foundation. With a BaaS rail underneath, integrations with Adyen or a PSP, and an architecture that scales towards V2 without starting over again.

Quant & data

Your models deserve a production platform

Your quant or research team runs financial models in Python or R, in notebooks nobody else can reproduce. A modelling app that puts those same models into production reproducibly, with version control, governance and explainable results, for risk management or client reporting, and also suitable for supervisors who ask for model explanations.

How an engagement works.

1

Introduction & scope

A conversation in which we understand which product you're bringing to market, which standard packages you already run, which regulations apply and what your own team can already handle. By the end we have a shared picture of the scope and the first demarcation between off-the-shelf and custom domains.

2

Architecture and compliance mapping

A workshop with your tech and compliance team. We map the relevant requirements (DORA, Wft, MiFID II, GDPR, Wwft, and where applicable Solvency II or PSD2) to concrete software controls. This results in an architecture document, a data model and the first screen flow for the highest-priority use case.

3

Building in sprints

Every two weeks a working build in a feature-flagged staging environment, so that compliance and security reviews can run in parallel with the build. We schedule a pen test well before go-live and involve your internal audit early, so you avoid endless rounds of review at the end.

4

Production and ongoing management

A phased go-live, with a controlled rollout to an initial customer or team group. After that, ongoing maintenance: monitoring, security patches, changing regulation (PSD3, the AI Act, the revision of the DORA RTS), and further development based on what your customers and your compliance team actually need.

Frequently asked questions.

The questions we get most often before starting a project for the financial sector.

Do you replace Temenos, Mambu or another core banking or policy package?
No. A complete core replacement in banking or insurance is work for specialist vendors: Temenos, FIS, Finastra, Mambu, SS&C and Avaloq on the banking side, and large suites such as Guidewire, Sapiens or the Wolters Kluwer stack on the insurance side. We build the layers on top and the modules alongside: customer portals, onboarding flows, compliance platforms, claims portals and risk tooling. That is where we add value too: in the software your customer sees and that sets you apart. For a bank, see our page on building a core banking platform; for an insurer, our page on developing insurance software.
Which compliance frameworks do you build into software?
The usual set for digital financial services in the Netherlands and the EU: the Wft (Dutch Financial Supervision Act) as the overarching framework, DORA for ICT resilience, MiFID II and IDD for investment and insurance advice respectively, EMIR for derivatives reporting, PSD2 (and soon PSD3) for payments, GDPR and, for organisations supervised by DNB, BIO as the security framework, the Wwft (Dutch anti-money laundering act) for anti-money laundering, Solvency II for insurers and IFRS for financial reporting. We build the controls into the system: audit trails, segregation of duties, transaction monitoring, KYC flows and the related reporting. Legal interpretation remains the job of your compliance or legal department, sometimes together with an external Wft lawyer.
Do you help with DORA compliance?
Yes, on the software side. We build registers for ICT third parties, classification schemes for incidents, exportable reports for your regulator and the monitoring layer that makes incident detection demonstrable. For the substantive DORA gap analysis and governance questions, you work with a specialist adviser or your own compliance officer; we turn their output into working software. See also our dedicated page on DORA compliance software.
How do we handle Wwft and KYC checks during onboarding?
We build an onboarding flow in which Wwft and KYC checks trigger the right level of due diligence per client category: simple for low risk, enhanced for PEPs or complex structures. Identity via iDIN or a KYC provider such as Onfido, Veriff or Signicat, UBO extracts via the KvK (Dutch Chamber of Commerce), sanctions screening and PEP checks via providers such as ComplyAdvantage or Refinitiv. For the software layer around this, see KYC/AML compliance software. We don't choose which vendor you contract for you; we integrate with whatever fits your risk appetite and budget.
Do you help with a DNB or AFM licence?
No, for that you work with a Wft lawyer or compliance consultant who knows the application procedure in detail. We align technically with the requirements that come out of that process: making sure the software demonstrably delivers the required controls, that the logging architecture meets DNB standards, and that your licence-holder status is maintained after go-live. For the legal files and discussions with the regulator, you are better off with a specialist than with us.
Do you also build financial modelling software and quant apps?
Yes. Many finance teams have models in Python or R notebooks that work, but that nobody else can reproduce and that fall outside any governance. We bring those models into a production-grade environment: version control in Git, reproducible runs with pinned dependencies, a calculation service that can scale, dashboards for risk or portfolio managers, and an audit trail per model version and per result. For regulators who ask for model explainability, or for an internal model validation, the system is ready: no more black-box notebook.
Can you integrate with our existing packages or legacy systems?
Yes. We have experience with the REST APIs of modern cores and BaaS providers, with SOAP services, ISO 20022 messages, SWIFT files, batch exchange and, not infrequently, message queues on mainframes. For insurers: integrations with policy and claims systems, loss adjusters and reinsurers. For banks: SWIFT, SEPA, Adyen, ING tools. Where needed, we build an anti-corruption layer, so the new application doesn't inherit the quirks of the legacy system and a later replacement doesn't break through your new layer. For larger projects, we also involve our enterprise software team.
What determines the lead time and costs?
Scope is by far the biggest factor: a standalone module alongside an existing core is a different project from a full customer portal with onboarding, transactions, KYC and compliance reporting. Other factors include the number of integrations with existing systems, the complexity of your business logic, how much compliance evidence your regulator expects, and whether you serve one or several entities or countries. After an initial workshop, we give you a concrete estimate with several scope options, so you can choose based on risk, priority and investment, rather than on a price that has nothing to do with your situation.

Talk to us about your financial platform.

A no-obligation introductory call of half an hour. Tell us about your product, the systems you already run and the regulations that apply, and we'll give you direction you can actually use, even if you end up working with someone else. For larger fintech, insurance or compliance challenges, we also involve our enterprise software team.

Want to look at this challenge from the custom software side? On applatenmaken.com you'll find a write-up of Financial software and insurance.

Edit content