Service · Web development

Custom mortgage portal development for advisers, lenders and customers.

Custom mortgage portals that digitise the entire process, from intake and customer profile through to approval, e-signing and deed execution. With HDN messages, BKR/UWV/Calcasa integrations and an audit trail that holds up under AFM supervision.

HDN integrationBKR & UWVWft audit trailE-signed deed

A mortgage portal is more than an application form.

A mortgage file touches ten to fifteen parties: the adviser, the lender, the valuer, 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. Each party has its own formats, deadlines and compliance requirements. A good portal ties that world together and gives both the customer and the adviser one clear 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.

Mortgage advisers licensed by the AFM, mortgage lenders, service providers, civil-law notaries handling the deed stage, and consumers with an existing mortgage each need a different side of the same portal. Advisers want efficiency in the client-profile flow, lenders want automated acceptance, providers want scalable processing, notaries want a handover instead of copy-and-paste, and clients mainly want to know where their application stands. 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 advise which type fits during the first conversation.

Adviser & client portal · fixed sprint budget

Mortgage adviser portal

A complete digital client journey: intake with DigiD or iDIN, income validation via UWV enquiry, client-profile questions for suitable advice, case building with a document vault, advice drafting and mortgage application submission via HDN. The client sees real-time status, upload actions and e-signing in their own environment, while the adviser has a deeper workspace on the same data layer, with client profile, case history, valuation status and HDN exchange on one screen.

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

Acceptance and back-office portal

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

Acceptance engineOCR documentsCalcasa/NWWIWft audit trail
Mortgage-as-a-service · fixed sprint budget

White-label or MaaS platform

A mortgage platform you roll out as a white-label to sister firms, intermediaries or fintech partners. Multi-tenant architecture, per-tenant branding, separate 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, client interaction is handled per label, so the holding keeps oversight and each label keeps its own brand. We see this model growing as fintechs want to add a mortgage layer to their existing financial proposition without Stater- or Quion-scale volume requirements.

Multi-tenantWhite-labelAPI-firstSLA monitoring

What you receive at the end of the project.

A production-ready mortgage portal, plus everything around it needed to run it yourself and to explain it to supervisors.

  • Production and staging environmentsRuns in your own cloud (AWS, Azure or GCP) or in an EU tenant managed by us — encrypted at rest, daily backups, IP whitelisting available.
  • HDN connectionSX message flow set up for your participant number, with regression tests across the full message set and monitoring for errors in the chain.
  • Integration layerBKR, UWV income enquiries, Belastingdienst, 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 enquiry.
  • Compliance reporting packageAudit log for Wft duty of care and suitable-advice documentation, DPIA report, data-flow diagram and a Wwft process description you can submit to AFM supervision.
  • Codebase + runbookFull source code, architecture documentation, build pipeline and an operational runbook with incident procedures for your IT or managed services partner.
  • Maintenance contract (optional)Monitoring, security patches, ongoing development and HDN version updates. A fixed monthly fee with several 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 becoming a bottleneck

Acceptance staff cut and paste between Adviesbox, a lender portal, the BKR portal and an Excel file of income rules. An acceptance engine can let 60 to 80 per cent of files pass through unseen and only refer the exceptions for review.

Compliance

Wft duty of care cannot be demonstrated

In an AFM investigation you must be able to show, per file, which questions were asked, which documents were reviewed and how the advice was reached. A custom client-profile flow with an audit trail produces that evidence automatically — often combined with a proper KYC and AML compliance layer for Wwft obligations around identification and the source of funds.

Scale

You are growing into a sister-brand 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.

Client experience

Clients drop out of the application flow

The paperwork surrounding a mortgage is impenetrable for consumers. A dedicated client portal with status tracking, structured document uploads and e-signing shortens turnaround times and reduces the call volume at your office.

Modules that make up a mortgage portal.

A full portal can do a great deal, but rarely is everything needed at once. Together we decide which modules are in scope and the order in which we roll them out — usually we start with the two modules that most affect your turnaround times or compliance risk.

Client side

Client onboarding and advice engine

DigiD or iDIN identification, automatic income checks via UWV with authorisation, a client-profile questionnaire, an advice engine that incorporates the IDD criteria for mortgages with protection cover, and a file vault in which payslips, annual tax statements, BKR reports and valuation reports arrive in a structured way. Every question, answer and document receives a timestamp and a user, so the Wft duty of care is evidenced in the file as well as on paper.

DigiD/iDINUWV authorisationClient profileIDD adviceDocument OCR
Back-office side

Acceptance engine and file workbench

A rules engine that executes your acceptance policy: income checks per lender, BKR checks, LTV and LTI limits, NHG criteria and exception rules per label. Files that fall within all the rules proceed without human intervention; files that reach a threshold appear on the acceptance workbench with the exact reason why. Every rule is version-controlled and execution is reproducible — useful during an audit.

Rules engineBKR/LTV/LTINHG flowExceptionsVersion control
Chain side

HDN, valuation and notary orchestration

The chain integrations that connect the portal with the rest of the Netherlands: HDN message flow to providers, valuation requests via Calcasa, NWWI or iValid with automatic status tracking, e-signing 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 by hand.

HDN SXCalcasa/NWWIE-signingKIK/CDR notaryStatus tracking
Not yet sure about a large project?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.

Explore OneDayBuild →

Compliance requirements we build to as standard.

The mortgage chain is subject to more regulatory frameworks than almost any other financial service. From sprint one, we build around those frameworks and deliver a compliance file that works hand in hand with your own compliance officer.

  • Wft and duty of careClient profile questions, suitable-advice requirements and documentation obligations are built into the flow itself, not delivered as a separate PDF alongside the file.
  • Conduct supervision (BGfo)The relevant parts of the Dutch Decree on Conduct Supervision of Financial Undertakings are translated into concrete control points within the portal.
  • AML/CTF and sanctions law (Wwft)Identification and verification via DigiD or iDIN, PEP and sanctions list checks, and source-of-funds questions become part of standard onboarding.
  • GDPR and special category personal dataPayslip data, BKR credit reports and health questions for mortality risk all fall under sensitive data. We apply encryption at rest, data minimisation and automatically enforced retention periods.
  • NHG guidelinesThe current NHG conditions are modelled in the acceptance engine. With each annual review, you receive a release containing the updated rules and a diff showing what has changed.
  • AFM reporting and audit trailA reporting module that can export on request, per file or in aggregate. Useful when the AFM requests a sample, or when you want to carry out periodic self-assessments.

How a mortgage portal project runs.

1

Introduction and process scan

We map out your current mortgage flow, from first client contact to deed signing. Which packages do you use today, such as Adviesbox, eAdviseur, NN Apparent, Stater or Quion back office, and where is the pain that justifies custom development?

2

Scope and compliance blueprint

A workshop with your compliance officer, an underwriter and an adviser. At the end: a functional blueprint, a data flow diagram, a first DPIA and a sprint plan that starts with the most valuable piece, usually the acceptance engine or client onboarding.

3

Build in sprints with live HDN testing

Every two weeks, a working build tested against the HDN acceptance environment and with real BKR and UWV stub queries. Your team tests alongside us, with an underwriter and an adviser seeing what we deliver each sprint.

4

Penetration test, AFM file and go-live

An external penetration 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 keeps pace with 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. With each HDN release, we incorporate 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 with for BKR, income and valuation?
BKR via the standard BKR-online interface, UWV income checks via the authorised brokers, the Tax Authority for income data with authorisation, the Kadaster for property information, the KvK for business parties, and Calcasa, NWWI or iValid for valuations. For each integration we provide documentation covering what we query, how we store the response and how long the data is retained under the GDPR.
How does it work with duty of care and suitable-advice evidence under the Wft?
The portal records every question, answer and document with a timestamp and user. The client profile flow is modelled so that it can be explained, allowing an AFM investigator to see, per file, how the advice was reached. We also deliver a DPIA, a dataflow diagram and a Wwft process description — standard components of an AFM file. We design the technology; your compliance officer remains ultimately responsible.
Do you also handle e-signing for the mortgage deed?
We sign the advice 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 flow: we deliver the structured file data via a KIK or CDR integration, so the notary does not 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 client portal for ongoing mortgages, or a connected vendor portal environment through which affiliated lenders and intermediaries see status in real time. We also integrate with the large service providers if you sit on the other side of that chain.
What determines the cost of such a project?
Four factors: the scope (which flows: advice only, acceptance too, or 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 as well) and how much of your own team can take part. We work with fixed sprint budgets so you can steer each phase, rather than an open-ended hourly budget.

Talk to us about your mortgage portal.

An introductory half-hour conversation, with no obligation. We listen to your current flow, probe the pain points and give direction you can act on — even if the outcome is that a standard package is sufficient.

Edit content