Bank reconciliation & matching General ledger reconciliation Month-end close

Custom financial reconciliation software development

Appfront builds custom software for financial reconciliation: importing bank transactions from CAMT.053 and MT940, automatically matching transactions against open items, reconciling the subledger with the general ledger and handling differences as a workflow instead of a spreadsheet. Tailored to your accounts, your payment flows and your matching rules, so the month-end close shifts from a manual peak to a controllable process. For finance departments, accounting firms, accountants and organisations in the financial sector.

What is financial reconciliation software?

Financial reconciliation software compares two data sources and shows where they differ. The best-known form is bank reconciliation: the transactions on the bank statement are matched against the open items in your accounts, so the general ledger agrees exactly with the bank. The software also reconciles subledgers with the control accounts in the general ledger, payment service provider settlements with the sales ledger, and clearing accounts that should be at zero at the end of the period.

This is deliberately different from an accounting package. A package records entries and maintains the general ledger, but in practice matching and reconciling often happens in separate spreadsheets alongside it. That shadow administration takes time, is error-prone and, at month end, doesn't show who checked what. Reconciliation software takes that work out of Excel and turns matching into a traceable process with matching rules, exceptions and approvals.

Standard packages often force your matching rules into a fixed pattern, while every set of accounts has its own payment flows, references and links. Custom software fits <em>your</em> situation and lets you adjust the rules as your processes change. Also read more about our accountancy software and about building custom software.

Automatic matching

Bank transactions are matched to the right open item on amount, payment reference and counterparty account. Anything that matches unambiguously is cleared automatically, so your team can focus on the items that need attention rather than on the ones that simply add up.

Reconciliations that balance

The total of the subledger agrees with the control account in the general ledger, down to the individual item. The software calculates that reconciliation per period and immediately flags when a receivables, payables or clearing account is not at zero.

Exceptions in view

Partial payments, combined payments and differences caused by bank charges don't slip through unnoticed, but end up in a workflow with context and an approval step. This keeps it traceable how each difference was resolved and who approved it.

How we build your reconciliation software

We work step by step and involve your finance and control staff early in the process. From a thorough exploration of your payment flows, matching rules and reconciliations through to go-live and ongoing maintenance. Every step is aimed at software your team trusts and your auditor can follow.

1
Discovery and scope

We map out your reconciliations: which bank accounts, which PSP settlements, which subledgers and which clearing accounts. Together we determine which attributes you match on and where most differences currently arise.

2
Design

We design the data model, the matching engine and the matching rules, plus the reconciliation logic between subledger and general ledger, the permissions structure and the audit trail. Where you use the Dutch Reference General Ledger Scheme (Referentie Grootboekschema), we align with it.

3
Build and iteration

We build in short sprints with automated tests and test the matching rules against your own statements and settlements. You see working versions along the way and help steer the rules that save the most time.

4
Go-live and management

A controlled go-live with a first parallel close as a safety net, followed by ongoing maintenance and refinement of matching rules as your payment flows or accounts change.

What reconciliation software actually does

We tailor every application to your payment flows, accounts and matching rules. Below are the features we deliver most often for teams that match transactions and monitor reconciliations.

Importing bank statements

Daily statements are imported from MT940 and the ISO 20022 format CAMT.053, plus CSV exports and, where possible, direct bank and PSP integrations under PSD2. Transactions are normalised and enriched with attributes such as the SEPA reference or iDEAL transaction, ready for the matching rules.

Transaction matching

The matching engine links bank transactions to open items on amount, payment reference, counterparty account, date and invoice number. You set the rules and thresholds yourself, and the software learns recurring patterns, such as a regular customer who always pays a rounded amount.

General ledger reconciliation

Each period, the software checks whether the sub-ledger agrees with the control account in the general ledger, for example accounts receivable or accounts payable. Differences are broken down to individual items, and clearing accounts that don't stand at zero are flagged before you close.

PSP and payment reconciliation

For organisations with a high volume of online payments, the software matches the payouts from a payment service provider to sales orders and bank receipts. For each payout you can see which transactions, chargebacks and transaction fees it contains, so revenue agrees with cash.

Differences and exceptions

Anything that doesn't match automatically appears as an exception in a workflow, together with the relevant context. The employee splits, links or writes off a difference, and the software remembers the choice so similar cases take less manual work next time.

Closing and audit trail

A closing checklist shows the status of each reconciliation, the assigned employee and the sign-off, with a four-eyes check on discrepancies. Every match, correction and approval is recorded, so the month-end close can be demonstrated to your control function and auditor.

Who we build reconciliation software for

Matching and reconciling is a concern for any organisation with a large number of transactions, but the matching rules and reconciliations differ greatly from one situation to the next. For each of the groups below, we build software that fits their payment flows and accountability requirements.

Finance and administration departments

In-house finance teams that reconcile bank, cash, receivables and payables every month and keep an eye on reconciliations. We connect this to your existing accounting system, or to a custom ERP system, so that matching and posting run in a single flow.

Accountancy firms and auditors

Firms that keep the books for many clients and want to standardise reconciliations across all those files. The software shows the status of reconciliations per client and provides a watertight audit trail. See also our audit software.

E-commerce & webshops

Webshops and marketplaces with high volumes of iDEAL, SEPA and card payments via a payment service provider. The software matches PSP payouts to orders and bank receipts and processes chargebacks and transaction fees, so revenue agrees with cash.

Financial sector and fintech

Organisations that process payment flows themselves and have high requirements for control and traceability. Reconciliation between internal ledgers, counterparties and the bank is part of their core process. See also our software for the financial sector.

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 →

Technology and integrations

We build with a modern, maintainable web stack and integrate with the sources your transactions come from. For reconciliation, the most relevant are: bank statements in CAMT.053 (ISO 20022) and MT940, bank and PSP integrations under PSD2, and a chart of accounts aligned with the Dutch Reference General Ledger Scheme (RGS) where you use it. We tailor the matching engine and reconciliation logic to your own rules.

Node.js / Python / .NET React / Vue front end PostgreSQL / SQL database REST and web service integrations CAMT.053 (ISO 20022) MT940 processing SEPA and iDEAL references Bank and PSP APIs (PSD2) Custom matching engine RGS chart of accounts OAuth 2.0 / SSO Role-based authorisation Segregation of duties and four-eyes Audit logging Encryption in transit and at rest Automated tests Monitoring and alerting CI/CD pipelines

Why choose Appfront for your reconciliation software?

Appfront builds custom software and always starts with a thorough analysis of your payment flows, matching rules and reconciliations. Reconciliation must not only be technically correct, but also traceable for your control function and auditor. That is why we establish early on which attributes you match on, where most differences currently arise and which reconciliations must be demonstrable.

Best-of-breed platforms such as BlackLine, Trintech and FloQast offer broad close and reconciliation functionality, and SAP S/4HANA, Dynamics 365 Finance and NetSuite also have built-in bank reconciliation. These don't always fit your data flows or your own rules. We build custom software where the standard falls short, or an integration layer that connects your existing systems, and we're honest about which approach delivers the most in your situation.

We write clear documentation of the data model, the matching rules and the reconciliation logic, so your team understands the software and can develop it further later. No black box, but transparent code and clear agreements on authorisation, logging and maintenance.

Also see our related services: accounts payable software, accounts receivable software and a management reporting system. Have any questions? Get in touch.

  • Custom reconciliation software, tailored to your payment flows
  • Matching engine with your own rules, thresholds and patterns
  • Familiar with CAMT.053, MT940, SEPA and iDEAL references
  • Reconciliation of the subledger to the general ledger down to the individual item
  • PSP reconciliation for organisations with many online payments
  • Segregation of duties, four-eyes approval and a watertight audit trail
  • Working in design and development sprints
  • Clear documentation that your team can read and maintain
  • Built in line with OWASP standards and the GDPR
  • Ongoing maintenance and refinement of matching rules

Control and security in reconciliation software

Reconciliation touches payment and general ledger data, so internal control is central. We build in role-based authorisation and segregation of duties, so the employee who matches items is not automatically the one who approves them. We add a four-eyes step for discrepancies, and every match, correction and reconciliation is recorded in an audit trail. This keeps it demonstrable who matched and approved what, which supports the work of your control function and auditor.

We work to the OWASP security standards and the GDPR, with encryption in transit and at rest, separate environments and careful management of access to bank and PSP integrations. We document data flows and authorisations, so you can demonstrate that you are in control of who can view and change which financial data.

More about our approach to security: information security policy and coordinated vulnerability disclosure policy. Discuss your situation without obligation via our contact form.

  • GDPR-compliant processing of payment and general ledger data
  • Role-based access and least-privilege principles
  • Segregation of duties between matching and approving
  • Four-eyes approval on differences and discrepancies
  • Watertight audit trail of matches, corrections and reconciliations
  • Encryption in transit (TLS 1.2+) and at rest
  • Secure management of bank and PSP integrations under PSD2
  • Built in line with OWASP standards, with documentation for your control function

Frequently asked questions about reconciliation software

Answers to the questions we get asked most often about custom software for matching and reconciling.

Financial reconciliation software compares two data sources and shows where they differ. The best-known form is bank reconciliation: the transactions on the bank statement are matched against the open items in the accounts receivable and payable ledgers, after which the general ledger agrees with the bank. The software also reconciles subledgers with the control accounts in the general ledger, payment flows from a payment service provider with the sales ledger, and clearing accounts that should be at zero at the end of the period. Custom software lets you configure the matching rules and reconciliations to fit the way your own accounting is structured.

Accounting software records journal entries and maintains the general ledger, but the reconciliation itself often happens in separate spreadsheets alongside it. Reconciliation software focuses on exactly that: importing bank statements from CAMT.053 or MT940, matching transactions automatically, flagging differences and closing the period in a way you can demonstrate. We build this layer as custom software or as an addition to your existing accounting or ERP environment. For the wider finance process, see our page on accountancy software.

Dutch and European banks deliver daily statements in MT940 and in the ISO 20022 XML format CAMT.053, which is gradually replacing MT940. Our software reads both formats, plus CSV exports and, where possible, direct bank and PSP integrations under PSD2. Transactions are normalised, enriched with attributes such as the SEPA payment reference or iDEAL transaction, and prepared for the matching rules, so that reconciliation is largely automatic.

The matching engine compares attributes such as amount, payment reference, counterparty account, date and invoice number, and links a bank transaction to the corresponding open item. Anything that matches unambiguously is reconciled automatically. Anything that doesn't, such as a partial payment, a combined payment or a difference caused by bank charges, ends up as an exception in a workflow. For each difference, the employee sees the context and splits or links it manually, and the software remembers recurring patterns, so the amount of manual work falls rather than reappearing every month.

Yes. A core principle of a balanced set of books is that the total of a subledger agrees with the corresponding control account in the general ledger, for example the accounts receivable or accounts payable account. The software calculates that reconciliation per period, shows the difference down to the individual item and flags when a clearing account is not at zero. We align the chart of accounts with the Dutch Reference Chart of Accounts (RGS) where you use it, so that reconciliations and reports stay consistent.

The month-end close is the periodic process in which all transactions are checked, reconciled and recorded before the figures are final. Reconciliation software supports this with a close checklist, a status per reconciliation, task assignment and four-eyes approval, so the team can see what is still open and what has been approved. Because reconciliation runs throughout the month rather than only on the last day, the close shifts from a manual peak to a controllable process.

Both are possible. Best-of-breed platforms such as BlackLine, Trintech and FloQast offer broad reconciliation and close functionality, and SAP S/4HANA, Dynamics 365 Finance and NetSuite also have built-in bank reconciliation. Such packages don't always fit your data flows, your PSP settlements or your own matching rules. We build custom software where the standard falls short, or an integration layer that connects your existing systems, and we set out up front which approach delivers the most in your situation.

Reconciliation touches payment and general ledger data, so internal control is central. We build role-based authorisation, segregation of duties between who posts and who approves, a four-eyes approval on discrepancies and a complete audit trail of every match, correction and reconciliation. We work to the OWASP security standards and the GDPR, with encryption in transit and at rest. That keeps it demonstrable who matched and approved what, which supports the work of your accountant and your control function.

Ready to build your reconciliation software?

Tell us how your accounts are set up and where matching currently gets stuck, from bank reconciliation and PSP settlements to reconciling subledgers to the general ledger. We are happy to think along with you on matching rules, integrations, control and the month-end close. In a no-obligation first conversation you get a clear picture of what is possible with custom software that fits your payment flows.

On applatenmaken.com, our platform about custom software development, you will find more in-depth information on Financial software and insurance.

Edit content