01 — The problem
Where month-end reconciliation breaks down in spreadsheets
Reconciliation often lives in a workbook of lookups and an "unexplained" tab. One person knows which bank descriptions map to which vendor. When they're out, the close slips.
The exceptions hurt: an invoice entered twice with a slightly different number, one payment covering three invoices, a payout net of fees, a PO price that doesn't match the invoice. Enterprise account reconciliation software handles this, but can be heavy for one narrow control.
02 — What to build
Matching rules, exception queues and sign-offs to include
Source imports for bank statements, invoice registers, PO lines and payout reports
Matching rules
exact reference and amount first, then date windows and amount tolerances
Duplicate invoice detection on vendor, amount, date and near-identical invoice numbers
Variance queue of unmatched items and differences above tolerance, with reason codes
AI-suggested matches for messy descriptions, shown as suggestions, never auto-cleared
Review and sign-off, with every decision logged by user and time
Roles
preparer, reviewer, controller, auditor (read-only)
This page is about control across sources. Creating and sending invoices belongs in an invoicing app.
03 — How to build it
Building a reconciliation tool in Henosia, from export to review queue
Create a private project
Nothing goes live until you publish.
Add mock data
a month of bank transactions, invoices and payouts as anonymized CSV.
Connect a database with a table per source.
Describe sources and tolerances in Plan mode
The agent asks questions and proposes a plan; nothing is built until you choose.
Build a first version and compare its result with last month's workbook.
Iterate on false matches.
Publish with access limited to finance roles.
Build a reconciliation app for our AP team using bank transactions, the AP invoice register and PO lines.
Auto-match when reference and amount match exactly; propose matches within 3 days and a $5 tolerance.
Flag possible duplicate invoices: same vendor and amount within 30 days, or invoice numbers one character apart.
Use AI only to suggest vendors for unclear bank descriptions; a preparer confirms each suggestion.
Variances over $500 need controller sign-off. Log who cleared each item and why.Paste it into a private Henosia project in Plan mode. The agent asks questions and proposes a plan first.
04 — Before you go live
Keeping people in charge of every financial adjustment
Before real financial data goes in, decide:
- Data owners for each source
- Read-only access to source systems. The app flags and documents; it does not post entries to your accounting system. Any write-back is a separate integration, scoped per system, data direction and approval step.
- Rules versus AI: fixed rules for stable matches, AI only for interpretation
- Review gates: who can clear items, who approves adjustments, who approves publishing
In a Henosia webinar, Danish e-commerce company 4tal shared a principle worth copying: let the system flag candidates like duplicate invoices and small deviations, and let people decide. The app supports your close; it doesn't replace your controller or auditor.
Start a private project in Henosia and plan the checks you run by hand today.
Start a private project05 — FAQ
Frequently asked questions
What does account reconciliation software do?
Account reconciliation software compares balances and transactions across sources, such as the bank, the ledger, invoices and payouts. It auto-matches clear items, lists exceptions and records who reviewed each one. A custom reconciliation tool follows your own matching keys, tolerances and sign-off rules instead of a vendor's defaults.
How is a reconciliation app different from an invoicing app?
A reconciliation app checks records that already exist across several sources and flags duplicates and variances for review. Henosia's separate invoicing app page covers creating and sending invoices from your billing rules. Many finance teams need both: one to issue invoices, one to control what was paid and received.
Do I need developers to build reconciliation software?
Not for a first version. A controller or AP lead can describe matching rules in Plan mode and build without writing code themselves. Involve IT when you connect live bank or ledger data, define read-only access to source systems, or decide who approves publishing.
How do you protect financial data and access?
Start with anonymized mock data in a private project. When you publish, Henosia Authentication ties the app to your company email domain and supports app-level access and optional IP restriction, so only finance roles see it. Confirm specific security requirements with Henosia for your setup.