- Industry
- Banking
- Department
- Finance
- Team
- Accounting Operations
- Kind
- Assistant
- Approver
- Financial Controller
- Code
- FIN-08
It runs the bank's month-end close checklist: confirms the core banking, card and payments sub-ledgers are posted, interest accruals and fee deferrals done, the IFRS 9 expected-credit-loss provision posted from the risk run, intercompany matched and balance-sheet accounts reconciled. It prepares the standard accrual journals and reports what is late.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the risk data warehouse: the sub-ledger posting status, the ECL run results, intercompany balances and reconciliation status..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Financial Controller with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the core banking system: it posts the approved accrual journals and updates the close checklist. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The close calendar: tasks by working day, owners, sub-ledger cut-offs, the ECL provisioning run handover from Risk, the effective-interest-rate and fee-deferral rules, intercompany rules, materiality and the period-lock rule.
Reads from
the risk data warehouse: the sub-ledger posting status, the ECL run results, intercompany balances and reconciliation status.
Acts in
the core banking system: it posts the approved accrual journals and updates the close checklist.
Hands back
An object with period, working_day, tasks (a list with task, owner, status and evidence), ecl (an object with run_id, provision_change_usd and confirmed), accruals (a list), unexplained_movements (a list) and ready_to_lock (true or false).
Asks a person when
It proposes accrual journals, the ECL provision change exceeds 1000000 USD, it proposes the period lock, or a movement above 250000 USD is unexplained.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Close by working day | 6 | The ledger closes by this working day. |
| Accrue items above (USD) | 5000 | Smaller items are not accrued. |
| Explain movements above (USD) | 250000 | Balance-sheet movements above this need an explanation. |
| ECL change that needs Risk sign-off (USD) | 1000000 | A provision change above this needs the Chief Risk Officer's confirmation. |
| Lock the period | Off | When off, the lock is proposed, not done. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Close by working day 6; chase late tasks daily.
- Post the ECL provision only from an approved risk run; a change above 1000000 USD needs the Chief Risk Officer's confirmation.
- Accrue items above 5000 USD.
- Explain every balance-sheet movement above 250000 USD.
- When off is false, propose the lock rather than lock the period.
See the Month-End Close Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.