Late and short employer contributions, listed every weekday morning
Each weekday morning the flow compares expected against received contributions in your ledger and ranks employers by total shortfall, with the periods affected and the longest delay. Finance starts the day with the exceptions, and every figure comes from the database, not a model.
Finance · Pensions & retirement · On a schedule · Every weekday at 07:00 · 5 steps · Your database
On a scheduleOn a schedule
Query a databaseRead expected against received
Work out the numbersTotal by employer
AnswerWrite the exceptions
Answer shownThe answer
5 steps in the flowDrag the canvas, or any step, to move it around.
Why teams run it
Contribution exceptions are usually found at month-end, when someone reconciles a spreadsheet and discovers an employer has been short for weeks. By then the conversation with the employer is harder, and members' records carry the gap in the meantime.
How it is governed
- Read-only: the query can only SELECT, through an administrator’s connection.
- Shortfalls and delays are computed by the database, never estimated by the model.
- It reports exceptions; it contacts no employer and changes no record.
- Every run is kept in the run history.
- Who runs it
- Contributions and finance teams; Employer relationship managers; Pension operations managers.
- What you supply
- A read-only database connection to your contributions ledger, with the query pointed at your own tables.
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
- Point the query at your own contribution schedule and receipts tables; Change the schedule, for example to run after your bank file lands; Add a filter to ignore shortfalls below a threshold you set.
Questions buyers ask
- How do we know the figures are right?
- The shortfall and days late are computed in the SQL query and the totals by employer in the table step, both in code. The model is instructed to quote them exactly and never recalculate or round, so a figure in the report is a figure the database produced.
- Does it chase employers?
- No. It produces the exceptions report for your team, and there is no step that emails or messages an employer. The Employer relationship brief template can help prepare that conversation.
- What does our ledger need to be in?
- The database step connects to PostgreSQL through a read-only connection whose host is on your approved list. Other database engines are not yet supported by that step.
Related templates
All 60 templates- Payment reconciliationMatches payments received against contributions expected for a period, employer by employer, and lists what does not match with the difference computed in the database.FinanceSomeone asks5 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.