Bank reconciliation automation for SMEs: Make vs custom build (2026)

The verdict in three sentences

For an SME handling fewer than 1,500 bank lines a month across one or two accounts, the built-in reconciliation module of the accounting tool (Pennylane, Agicap, Tiime) is enough and costs the least. Between 1,500 and 4,000 lines with specific business rules (split payments, batched direct debits, several banks), a Make or n8n scenario plugged into the bank aggregator gives the best cost-to-speed ratio. Beyond that, or as soon as the ERP enforces its own documents, a custom connector on PSD2 APIs at 8,000 to 20,000 EUR excl. VAT reaches 85 to 90% automatically matched lines and pays back in 12 to 20 months.

Why manual reconciliation costs more than it seems

In an 80-employee SME, bank reconciliation takes the accounting manager about 3 days a month on average: exporting statements, finding invoices, matching customers and suppliers, handling discrepancies. The direct cost is visible, the indirect cost much less so: month-end close pushed back by 4 to 6 days, cash managed on three-week-old figures, reminders sent to customers who have already paid.

The main gain does not come from data entry but from finding the matching document. That is where the three approaches differ.

Three approaches compared: costs, limits and lead times

Built-in modules rely on a bank aggregator (Bridge, Powens, GoCardless Bank Account Data) that pulls transactions through PSD2 APIs and suggests matches with invoices already in the tool. A Make or n8n scenario adds a layer of custom rules between the bank and the accounting software. A custom build creates a dedicated reconciliation engine connected to the ERP, with scoring rules and an interface to validate discrepancies.

Two things to watch. First, Make bills per operation: a scenario processing 2,500 transactions with five steps each uses about 12,500 operations a month, which puts the SME on the Pro or Teams plan rather than the entry plan. Second, PSD2 access requires the bank consent to be renewed every 180 days: an unmonitored process stops silently, whatever the approach.

What a well-designed reconciliation engine must handle

The 10 to 30% of lines that resist automation are always the same: customer transfers settling several invoices, partial payments, aggregated bank fees, batched SEPA direct debits, truncated labels. A serious engine combines several signals rather than a simple amount match.

The validation interface matters as much as the algorithm: the accountant must see suggestions ranked by confidence, validate in one click and leave an audit trail for the statutory auditor.

Mini case study

Nathalie, accounting manager at an 80-employee distribution SME in Nantes, reconciles 2,500 lines a month across three banks and spends 24 hours a month on it, at a loaded cost of about 45 EUR an hour. With a well-built Make scenario (4,000 EUR excl. VAT setup, 250 EUR a month all-in), she reaches 80% matching and spends only 6 hours a month: 18 hours saved, or 810 EUR a month, and payback in about 7 months. With a custom connector at 14,000 EUR excl. VAT and 200 EUR a month, matching rises to 88%, time drops to 4 hours, savings reach 900 EUR a month and break-even comes around month 20, but with native Sage integration and a close brought forward by 6 days.

FAQ

Can an SME access PSD2 APIs directly?

No, access to bank data goes through a licensed provider (aggregator) charging 50 to 200 EUR a month depending on the number of accounts. The SME signs with the aggregator and grants access, renewed every 180 days.

Is Make reliable enough for accounting?

Yes for 1,500 to 4,000 lines a month, provided every run is logged and an alert fires on failure. Beyond 10,000 operations a day or with several entities, versioned code becomes safer.

What auto-matching rate is realistic?

Between 70 and 90% depending on the quality of customer labels. The remaining 10% need human validation, which the tool should keep under 5 hours a month.

Will the statutory auditor accept automated reconciliation?

Yes if every match stays traceable: rule applied, date, validator. Plan an audit trail export, usually included in custom builds from 8,000 EUR excl. VAT.

How long does it take to go live?

Count 1 to 2 weeks for a built-in module, 3 to 5 weeks for a Make scenario and 6 to 10 weeks for a custom build, including 2 weeks running in parallel with manual reconciliation.

Let's scope your project. Send us your line volume, banks and accounting software: we will recommend the right approach, a budget between 2,500 and 20,000 EUR excl. VAT and a go-live date. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.