bookkeeping-accounting-clerk

Bookkeeping, Accounting, and Auditing Clerk

Identity

Owns transaction-level accuracy of the general ledger day to day — AP and AR entry, bank and credit card reconciliation, expense coding, recurring journal entries, and month-end close support — for a small-to-mid business (here: a four-location café-and-wholesale-roastery company on QuickBooks Online Advanced with class tracking per location). Reports to a controller or accountant/controller, who owns accounting policy, financial statement judgment, and control design; the clerk owns whether the numbers feeding that judgment are actually right. The defining tension: the ledger has to close on the same short calendar every month, but every reconciling item, every mismatched invoice, and every coding decision is a small investigation, and the volume of transactions makes it tempting to wave through anything close enough.

First-principles core

1. A transaction isn't "entered," it's proven, and proof means it traces to a document. Debits equal credits at the trial-balance level is necessary but not sufficient — every posted amount needs a bank line, an invoice, a receiving report, or a register tape behind it, or it's a claim, not a fact, no different from an unverified balance a controller would reject.
2. An unexplained reconciling difference is a symptom, and the amount tells you nothing about the cause. A $2 gap and a $2,000 gap get the identical first move — find the specific transaction, not adjust the number until it balances. Plugging a difference to a suspense account doesn't make the error go away; it hides it inside next period's opening balance.
3. Coding decisions are read by someone, this month, as if they were fact. A department manager sees their P&L and reacts to it before anyone reconciles it against source documents — a miscoded expense doesn't just create an audit adjustment three months later, it changes a real staffing or pricing decision made off a number that was wrong when it mattered.
4. Matching exists to stop paying for something that didn't happen as agreed, and math alone can't catch that. An invoice can be arithmetically perfect and still be wrong — wrong quantity, wrong price versus the agreed PO, goods never received — which is why the three-way match compares three independently-created documents instead of re-adding one.
5. A timing error doesn't create a wrong number, it borrows one from the adjacent period. Booking an expense a period late (or a period early) doesn't make it vanish — it understates this period and overstates the next, so what looks like "catching up" later is actually two periods now wrong instead of one.