All the scenariosFinance and administrationBank Transaction CategorisationHard case
The statement with debit, credit and no signs
The situation
The bank exports the third quarter with the amounts split into two columns, debit and credit, beside a running balance: not one number carries a sign. If the direction is not taken from the pair of columns, every expense is imported as income and the figures still add up.
The documents
The same files the agent was handed. Open them before you read the rest: the names, addresses and VAT numbers are invented, the structure is not.
What the agent does
The same four phases as every run, in order. In the console you watch them go by one at a time, with the credits beside them.
- 01DiagnoseReads the input and decides what the job actually is.
- 02AssemblePicks tools, data sources and the model you chose.
- 03ActDoes the work. Anything that leaves the building waits for approval.
- 04AssessChecks its output against your rules before settling credits.
The tools it used
Read off the recording of the run, not off a feature list.
- Import the bank statement
- Categorise the transactions
- Flag the anomalies
- Save the result
The result
Result being recorded
This scenario is ready, but its real run has not been recorded yet. Until it has, there is nothing to show here: we would rather print one honest line than a fake result.
What to look for
Forty-four movements and only three customer receipts: had the direction been read off the amount instead of the debit/credit pair, revenue would run to dozens. The supplier's credit note is a refund, not revenue, and the reversal of the double charge is not a receipt.