COOKED
This residual clerk category is built out of exactly the work software eats first: keying transactions into financial systems, reconciling account records against statements, checking documents for completeness, chasing missing paperwork, and generating routine reports. There is no licensure, no signature liability, and the modal worker executes defined procedures on defined inputs rather than making judgment calls. The small surviving slice is exception handling — the odd transaction that doesn't reconcile, the customer or vendor who needs a phone call, the audit request that requires digging through history.
Core tasks are already automatable. Matching remittance advice to open invoices, keying batch deposits, flagging accounts that don't tie, and pulling a standing weekly report are all structured-input/structured-output tasks that ERP modules and RPA scripts already do end-to-end — the 5 rather than a 0 reflects the residual chasing of a vendor whose paperwork never arrived and the unreconciled item nobody documented.
Fully desk- and screen-based. The physical component is walking to a printer, opening mail, pulling a folder from a file room, or scanning a stack for imaging — real but incidental, which is why it sits at 3 and not at 0.
No licence, no signature requirement. No state licence, no bonding requirement, no CPA-style attestation: your reconciliation is reviewed and signed off by an accountant or controller, and the 1 exists only because some employers require a bond or background check for cash-handling roles.
Anonymous artifact production. You have named counterparties — the AP contact at a recurring vendor, the branch that calls when a wire posts wrong — but the work product is a correct ledger entry that nobody attributes to you, so the relationship smooths the job rather than being the job.
Executes defined procedures on defined inputs. Discretion runs to deciding whether a $12 variance is worth escalating or whether a document is complete enough to process; the dollar thresholds, approval routes, and escalation rules come from a controller's written policy, which is why this is 4 and not the 8-plus you'd give someone setting those thresholds.
MVB Bank announced it has selected Bretton AI to run its back-office operations as it scales its fintech business.
Has AI actually changed your work?