A period reconciled employer by employer, exceptions only
Enter a period and the flow matches bank receipts against the contribution schedule, keeps only employers that don’t reconcile, and lists them largest difference first. Owed and overpaid are labeled plainly, and every difference is the database’s arithmetic, not a model’s.
Finance · Pensions & retirement · Someone asks · 5 steps · Your database
Why teams run it
Matching bank receipts to expected contributions is still a spreadsheet exercise at many funds, repeated for every employer and every period. It is slow, it depends on whoever built the spreadsheet, and one sorting mistake can hide a missing payment.
How it is governed
- Read-only: SELECT queries only, through an administrator’s connection.
- The period is bound as a value, so input cannot alter the query.
- Differences are computed by the database and table step, never by the model.
- It reports and posts no adjustment to any ledger.
- Who runs it
- Pension accountants; Contributions and finance teams; Finance controllers.
- What you supply
- A read-only database connection holding both the bank receipts and the contribution schedule.
It ships with test questions
- 2026-08
From template to a live agent
The same builder, tests and release review apply to a template as to anything built from scratch.
- Open it as a working flow
- Every step, source, branch and approval is already in place, and every one of them can be changed before it runs on your data.
- Prove it before it ships
- An evaluation set can gate the release, so a change that breaks an answer never reaches anyone. A question it cannot answer from the sources leaves the gate unproven, not passed.
- Keep a person on the decisions
- A run that needs a decision stops and says exactly what approving will do, and who it is waiting for.
- Publish where people work
- A form, an embedded widget, Microsoft Teams or a scheduled batch — with its own access and limits per deployment.
- What teams usually change
- Map the query to your own receipts and schedule tables and references; Ignore differences under a tolerance by adding a filter condition; Put it on a schedule to run after month-end.
Questions buyers ask
- What does it need to connect to?
- A read-only PostgreSQL connection that holds both your bank receipts and the contribution schedule, with the query rewritten for your tables. The database host must be on your approved list before a connection opens.
- How does it treat overpayments?
- A positive difference is reported as money still owed and a negative one as an overpayment, exactly as the database computed it. The model is instructed never to recalculate either.
- Does it correct the ledger?
- No. The connection is read-only and the flow produces a report; any adjustment is made by your finance team in your own systems.
Related templates
All 60 templates- Contribution monitoringRuns every weekday morning and lists the employers whose contributions are late, short or missing, with the arithmetic done in the database rather than by a model.FinanceOn a schedule5 steps
- Investment performance reportOn the third of each month, sets each fund’s return against its benchmark and target and names the ones that deviate — from your performance data, not a model’s memory.FinanceOn a schedule5 stepsa recorded run
- Member 360Everything the fund holds on one member — status, employer, contribution record and any gap in it — read from your administration system rather than recalled by a model.SupportSomeone asks5 steps
- Member service copilotAnswers a member’s question from the plan documents with the section quoted, drafts the reply, and hands anything the documents do not settle to a person.SupportSomeone asks7 stepsa person approvesa recorded run
See it run on your own data
We open it in the builder, point it at a sample of your documents and systems, and run it with you.