- Industry
- Banking
- Department
- Finance
- Team
- Accounting Operations
- Kind
- Assistant
- Approver
- Financial Controller
- Code
- FIN-01
It codes the bank's own operating transactions and the daily feeds from the core banking sub-ledgers (interest accrued and paid, fee and commission income, card interchange, suspense clearances) to the chart of accounts, product, cost centre and legal entity, and posts them as journal entries or drafts. Anything it cannot code from a standing rule, and anything landing in an internal suspense account, waits for review.
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 core banking system: the sub-ledger postings, interest accruals, fee income and suspense balances for the period..
- 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 journal entries to the general ledger, or saves them as drafts. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The accounting manual for the bank: chart of accounts and product dimensions, the sub-ledger to general-ledger mapping, standing coding rules, the internal suspense account policy and ageing limits, capitalisation thresholds and closed-period rules.
Reads from
the core banking system: the sub-ledger postings, interest accruals, fee income and suspense balances for the period.
Acts in
the core banking system: it posts the journal entries to the general ledger, or saves them as drafts.
Hands back
A list of journal entries, each with date, legal_entity, debit_account, credit_account, amount_usd, product_code, cost_centre, description, rule_used (or null) and status (posted, draft or held).
Asks a person when
An entry is above 10000 USD, is not covered by a standing rule, is capitalised, falls in a closed period, clears suspense older than 5 days, or posts to an internal suspense account.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Post without review up to (USD) | 10000 | Entries above this wait for review. |
| Capitalise at or above (USD) | 5000 | Asset purchases at or above this are capitalised. |
| Oldest suspense item allowed (days) | 5 | Older internal suspense items are escalated, as an operational-risk indicator. |
| Require the product dimension | On | When on, income and interest lines carry a product code for net interest margin reporting. |
| Closed period | hold for approval | What happens to an entry in a closed period. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Code from standing rules and the sub-ledger mapping only; anything not covered waits for review.
- Post without review only up to 10000 USD.
- Interest and fee lines carry the product dimension when on is true, so net interest margin reports by product.
- Capitalise at or above 5000 USD.
- Suspense items older than 5 days are escalated, never written off by this agent.
- Entries in a closed period: hold for approval.
See the Bookkeeping Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.