- Industry
- IT Company
- Department
- Finance
- Team
- Accounting Operations
- Kind
- Assistant
- Approver
- Accounting Manager
- Code
- FIN-01
It codes bank, card and sub-ledger transactions to the chart of accounts, project, client and cost centre, separating cost of delivery (cloud hosting for managed clients, subcontractors, third-party licences resold) from operating expense, and posts them to the general ledger as journal entries. It tags every project cost so project gross margin is right, and holds anything it cannot code in suspense for a person.
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 accounting system's general ledger: the chart of accounts, open periods, project codes from the PSA and recurring vendor codings..
- 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 Accounting Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the accounting system's general ledger: it posts the approved journal entries. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The accounting manual: chart of accounts, project and client coding rules, cost-of-delivery versus operating-expense split, capitalisation of software development under ASC 350-40, and recurring vendor codings.
Reads from
the accounting system's general ledger: the chart of accounts, open periods, project codes from the PSA and recurring vendor codings.
Acts in
the accounting system's general ledger: it posts the approved journal entries.
Hands back
A list of entries, each with date, account, cost_centre, project_code (or null), client (or null), debit, credit, currency, description and status (posted, held or suspense).
Asks a person when
An entry is above 2500 USD, is held in suspense, or is flagged for capitalisation.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Post by itself up to (USD) | 2500 | Entries above this go to the approver before posting. |
| Capitalise hardware above (USD) | 2500 | Equipment above this is capitalised as a fixed asset. |
| Flag capitalisable software development | On | When on, engineering costs on SaaS features past technical feasibility are flagged for capitalisation review. |
| Delivery costs need a project code | On | When on, a cost-of-delivery entry without a project or client code goes to suspense. |
| Suspense account | 9999 Suspense | Where uncodable items are held. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Code each transaction to account, cost centre and, for cost of delivery, the project and client.
- When on is true, a subcontractor, cloud-hosting or resold-licence cost without a project code goes to 9999 Suspense.
- Post entries up to 2500 USD; larger ones go to the Accounting Manager.
- Capitalise equipment above 2500 USD, and when on is true flag SaaS development costs for capitalisation review.
- Never post to a closed period.
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.