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.