Service · Web development

Custom mortgage portal development for advisers, lenders and customers.

Custom mortgage portals that digitise the entire process — from intake and customer overview to acceptance, e-signing and deed execution. With HDN messages, BKR/UWV/Calcasa integrations and an audit trail that stands up to your AFM supervision.

HDN integrationBKR & UWVWft audit trailE-sign deed

A mortgage portal is not an application form.

A mortgage file involves ten to fifteen parties: the adviser, the lender, the appraiser, the notary, BKR, UWV, the Tax Authority, the Land Registry, NHG, any service provider such as Stater or Quion, and last but not least the customer themselves. Each party has its own formats, its own deadlines and its own compliance requirements. A good portal glues that world together and gives both the customer and the adviser a single readable overview — without anyone having to switch between four different portals to move a file forward.

Since 2015 we have been building custom software for financial service providers: banks, intermediaries, insurers and fintechs. We do not replace Adviesbox, eAdviseur, Figlo or AOV-online where they are sufficient: for the standard advice calculation and basic HDN exchange, those packages are continuously maintained to keep up with changing laws and regulations. We only build when your flow is more specific than a standard package can handle: a custom acceptance engine with rules you want to manage yourself, a white-label customer portal for sister firms, back-office automation between HDN and your core system, or a mortgage-as-a-service layer that you offer to third parties as a proposition. For the wider financial sector we see the same pattern with custom insurance software: standard packages cover the middle of the market, while custom software covers the edges where your firm stands out and where your competitive advantage lies.

AFM-licensed mortgage advisers, mortgage lenders, service providers, notaries on the deed-execution side and consumers with an existing mortgage each need a different side of the same portal. Advisers want an efficient client-profile flow, lenders want automated acceptance, providers want scalable processing, notaries want a simple confirmation instead of copy-and-paste, and clients mainly want to know where their application stands in the process. We design these portals in layers, so the same data layer serves all these stakeholders without us having to build five separate systems.

Three portal types we build.

Depending on your role in the chain (licensed adviser, lender or service provider), a portal looks fundamentally different. We will advise which type fits in the first conversation.

Adviser and client portal · fixed sprint budget

Mortgage adviser portal

A complete digital client flow: intake with DigiD or iDIN, income validation via UWV queries, client-profile questions for suitable advice, file building with a document vault, advice drafting and application submission via HDN. Clients see real-time status, upload actions and e-signing in their own environment, while the adviser works in the same data layer with a deeper workbench showing the client profile, file history, valuation status and HDN exchange on a single screen.

DigiD/iDINHDN applicationClient profileDocument vault
Back-office automation · fixed sprint budget

Acceptance and back-office portal

For lenders and service providers who process mortgage files: parsing HDN inbound messages, OCR on payslips, annual statements and employment contracts, a rules engine for income assessment, BKR credit checks, LTV and LTI checks and NHG criteria, and orchestration of valuation requests via Calcasa, NWWI or iValid. With an underwriter workbench that puts only the genuine exceptions on your desk and automatically passes routine files on to the lender or service provider, plus explanation logging for every decision so an external audit is always reproducible.

Acceptance engineDocument OCRCalcasa/NWWIWft audit trail
Mortgage-as-a-service · fixed sprint budget

White-label or MaaS platform

A mortgage platform that you roll out as white-label to sister firms, intermediaries or fintech partners. Multi-tenant architecture, per-tenant branding, your own acceptance rules per label and an API layer for PSPs or digital challengers who want to offer mortgage flows without building the system themselves. Rules and HDN versions are managed centrally, while client interaction stays decentralised, so the holding company keeps an overview and the labels keep their own brand. We see this model growing as fintechs want to add a mortgage layer to their existing financial proposition without Stater or Quion volume requirements.

Multi-tenantWhite-labelAPI-firstSLA monitoring

What you get at the end of the project.

A production-ready mortgage portal, plus everything around it to manage it yourself and explain it to regulators.

  • Production and staging environmentRuns in your own cloud (AWS, Azure or GCP) or in an EU tenant managed by us, with encryption at rest, daily backups and IP whitelisting available.
  • HDN connectionSX message flow set up for your participant number, with regression tests on the full message set and monitoring for errors in the chain.
  • Integration layerBKR, UWV income queries, Tax Authority, Kadaster, KvK, Calcasa, NWWI, iValid and your lender portals, set up as described in our approach to smart API integrations, with retry logic and explanation logging for every query.
  • Compliance reporting packAudit log for the Wft duty of care and suitable-advice documentation, DPIA report, data flow diagram and a Wwft process description that you can present to the AFM.
  • Codebase + runbookFull source code, architecture documentation, build pipeline and an operational runbook with incident procedures for your IT or support partner.
  • Support contract (optional)Monitoring, security patches, ongoing development and HDN version updates. Fixed monthly price with multiple response-time tiers.

When custom is the right choice.

Adviesbox, eAdviseur and Figlo cover the standard flow very well. We build when you run into one of these patterns, or a combination of them.

Back office

Manual acceptance is overflowing

Underwriters copy and paste between Adviesbox, a lender portal, the BKR portal and an Excel sheet of income rules. An acceptance engine can let 60 to 80 per cent of files pass through untouched and only put the exceptions in front of a person.

Compliance

Your Wft duty of care can't be demonstrated

In an AFM investigation, you must be able to show for each file which questions were asked, which documents were assessed and how the advice came about. A custom customer-profile flow with an audit trail provides that evidence automatically, often combined with a proper KYC and AML compliance layer for Wwft obligations around identification and source of funds.

Scale

You're growing towards a sister-firm model

What works for one label does not scale to three or five labels within the same holding company. White-label multi-tenancy with central rules management and separate branding per label then becomes unavoidable, the same architecture we describe under custom enterprise software.

Customer experience

Customers drop out of the application flow

The paperwork around a mortgage is impenetrable for consumers. A custom customer portal with status tracking, structured document uploads and e-sign improves completion rates and reduces call volume to your office.

Modules a mortgage portal is made up of.

A full portal can do a lot, but rarely is everything needed at once. Together we choose which modules are in scope and in what order we roll them out. We usually start with the two modules that have the biggest impact on your turnaround time or compliance risk.

Customer side

Customer onboarding and advice engine

DigiD or iDIN identification, automatic income retrieval via UWV with consent, a customer-profile questionnaire, a suitable-advice engine that incorporates the IDD criteria for non-life mortgage products, and a document vault where payslips, annual statements, BKR report and valuation report arrive in a structured way. Every question, answer and document gets a timestamp and a user, so the Wft duty of care is not only on paper but also in the file.

DigiD/iDINUWV consentCustomer profileIDD adviceDocument OCR
Back-office side

Acceptance engine and file workbench

A rules engine that executes your acceptance policy: income assessment per lender, BKR checks, LTV and LTI limits, NHG criteria and exception rules per label brand. Files that meet all the rules pass through without human intervention; files that hit a threshold appear on the underwriter workbench with the exact explanation of why. Every rule is version-controlled and execution is reproducible, which is handy in an audit.

Rules engineBKR/LTV/LTINHG flowExceptionsVersion control
Chain side

HDN, valuation and notary orchestration

The chain integrations that connect the portal to the rest of the Netherlands: HDN message flow to lenders, valuation requests via Calcasa, NWWI or iValid with automatic status tracking, e-sign of the quote and advice agreement via DocuSign or AdobeSign, and notary handover via a KIK or CDR integration. The chain runs without anyone having to forward a PDF manually.

HDN SXCalcasa/NWWIE-signKIK/CDR notaryStatus tracking
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 →

Compliance requirements we build on as standard.

The mortgage chain is subject to more regulatory frameworks than almost any other financial service. We build on those frameworks from sprint one and deliver a compliance dossier that works hand in hand with your own compliance officer.

  • Wft and duty of careCustomer profile questions, suitable-advice reasoning and documentation requirements are built into the flow, not bolted on as a separate PDF alongside the file.
  • BGfo conduct supervisionThe relevant parts of the Dutch Financial Institutions (Conduct Supervision) Decree are translated into concrete control points in the portal.
  • Wwft and sanctions legislationIdentification and verification via DigiD or iDIN, PEP and sanctions list checks, and source-of-funds questions become part of the standard onboarding.
  • GDPR and special category personal dataSalary details, BKR credit reports and health questions for life cover count as sensitive data: encrypted at rest, data minimisation by design, and retention periods enforced automatically.
  • NHG guidelinesThe current NHG (National Mortgage Guarantee) conditions are modelled in the acceptance engine; with every annual revision you receive a release containing the updated rules and a diff of what has changed.
  • AFM reporting and audit trailA reporting module that can export on request, per file or aggregated. Handy when the AFM requests a sample, or when you want to run periodic self-reviews yourself.

How a mortgage portal project works.

1

Introduction and process scan

We map your current mortgage flow, from first customer contact to deed execution. Which packages do you use now (Adviesbox, eAdviseur, NN Apparent, Stater or Quion back office) and where is the pain that justifies a custom solution?

2

Scope and compliance blueprint

A workshop with your compliance officer, an underwriter and an adviser. At the end you have a functional blueprint, a data flow diagram, the start of a DPIA and a sprint plan that begins with the most valuable part, usually the acceptance engine or customer onboarding.

3

Build in sprints with live HDN testing

A working build every two weeks, tested against the HDN acceptance environment and with real BKR and UWV stub queries. Your team tests along with us: an underwriter and an adviser who see what we deliver each sprint.

4

Pen test, AFM file and go-live

An external pen test in the final sprint, delivery of the compliance file for the AFM and a phased rollout: first one adviser or one label portal, then wider. With monitoring and a support team that continuously handles new HDN versions and changing NHG guidelines.

Frequently asked questions.

What mortgage advisers, lenders and service providers ask before we start.

Do you replace Adviesbox, eAdviseur or Figlo?
For the standard advice flow: no. Those packages handle suitability-advice calculations and HDN exchange well and are continuously maintained to keep up with changing laws and regulations. We do build custom software around them: a customer portal that integrates with Adviesbox, a back-office layer that orchestrates HDN output from eAdviseur, or a custom acceptance engine that runs your lender rules.
How do you handle the HDN connection?
We connect using your HDN participant number and build the SX message flow in line with the current HDN schemas. Messages are validated, logged and version-controlled, and with every HDN release we include the new version in a maintenance sprint. For lenders we also build the inbound side: receiving applications, parsing them and passing them on to your underwriting workbench.
Which sources do you integrate for BKR, income and valuation?
BKR via the standard BKR online interface, UWV income queries via the authorised brokers, the Tax Administration for income data (with authorisation), the Land Registry for property information, the Chamber of Commerce (KvK) for business parties, and Calcasa, NWWI or iValid for valuations. For each integration we provide documentation on what we query, how we store the response and how long the data is retained under the GDPR.
What about Wft duty of care and proof of suitable advice?
The portal records every question, every answer and every document with a timestamp and user. The customer profile flow is modelled to be explainable, so an AFM investigator can see for each file how the advice came about. We also deliver a DPIA, a data flow diagram and a Wwft process description, which are standard parts of an AFM file. We design the technology; your compliance officer remains ultimately responsible.
Do you also handle e-signing of the mortgage deed?
We sign the advisory agreement, intake authorisations and mortgage quote digitally via DocuSign, AdobeSign or an equivalent qualified provider, depending on your eIDAS level requirements. For the notarial deed itself, we work with the notary's workflow: we deliver the structured case data via a KIK or CDR integration, so the notary doesn't have to retype anything by hand.
Do you also build for service providers such as Quion, Stater or Hypocasso?
Yes. If you are a service provider yourself or fulfil a comparable back-office role, we build operational software on top of or alongside your existing core system. Think of a case workbench for underwriters, a customer portal for existing mortgages, or a connected vendor portal that gives linked lenders and intermediaries real-time status. We also integrate with the large service providers if you sit on the other side of that chain.
What determines the cost of a project like this?
Four factors: the scope (which flows: advice only, underwriting as well, back office as well), the number of external integrations (HDN, BKR, UWV, valuers, banks), the depth of compliance (audit trail only, or white-label multi-tenant too) and how much your own team can contribute. We work with fixed sprint budgets so you can adjust course per phase, with no open-ended hours budget.

Talk to us about your mortgage portal.

A no-obligation introductory call of half an hour. We listen to your current flow, dig into the pain points and give you direction you can actually use, even if the outcome is that an off-the-shelf package is enough.

Edit content