The library
Guides for people who need the finance work to actually be finished.
Everything here is written for the owner of a service business who has a finance problem and not much time. The guides diagnose before they recommend, and the standards in them are written to be used on any provider — including At Par.
Most of what goes wrong in a small finance operation is one of the same few things: an invoice issued and never chased, a bill owed and never scheduled, a filing due and never prepared, a transaction recorded and never explained. Each one is an obligation — something owed, owing or due. The failure is almost never the recording. It is that nobody carried it to closure.
Nothing here is gated. Nothing asks for an email. The tools run entirely in your browser and store nothing.
You are not sure you need anyone yet. Start here.
For the owner who has no finance background and has not concluded they need a provider at all. These pages answer the questions people usually ask an AI rather than a person, and none of them assumes you already know the vocabulary.
- Do I need an accountant yet? — A straight answer for a founder with no finance background.
- Behind on the books — Months or years behind is more common and more recoverable than founders think.
- If the books are wrong — Most errors cost nothing.
Recognise the problem. Before you choose anyone.
If something in your finance operation keeps costing you time and you cannot name what it is, start here. These pages diagnose; they do not sell.
- Why month-end is still messy — Automation records transactions.
- Still doing the bookkeeping — The software is doing its job.
- Profitable but no cash — Profit counts what you earned; cash counts what arrived.
- Ageing and arrival — An ageing report measures elapsed time, not arrival.
- Unmatched transactions — Automation should end in an exception, not a guess.
- Books vs documents — When the ledger and the document say different things, neither should quietly win.
- Month-end reconstruction — Month-end should close a period, not rediscover it.
- After you send a document — A document should be held, its meaning determined, its finance consequence recorded against evidence, what it commits you to tracked, and anything missing raised.
- Bank feeds & bookkeeping — A bank feed proves money moved; it does not say what for.
- The month-end handback — A monthly handback should say what changed, where cash stands, who owes what, what is at risk and what needs deciding — with the figures beneath each one openable.
Invoices, promises and cash that has not arrived.
The receivables pillar and the questions it raises. Each of these answers exactly one of them.
- Accounts receivable outsourcing — What you can hand off, and what should stay under your control.
- Who follows up overdue invoices — Someone must own invoice follow-up by name.
- Tracking payment promises — Record a payment promise as a dated commitment: which invoices, what was promised, who said it, on what channel, and the date it comes back for checking.
- Broken payment promises — A missed payment date needs a named action within a day or two: confirm nothing arrived, ask what changed, request a revised date, then escalate to the owner.
- Payment screenshots — No.
- Disputed vs overdue — An overdue invoice needs routine follow-up.
Choose the model. Then choose the provider.
Category decisions come before vendor decisions, and most disappointment comes from getting them the wrong way round. At Par is allowed to lose on every one of these pages.
- Outsourced bookkeeping vs an in-house accountant — Neither model is automatically better.
- What a provider should own — A provider should be judged by the finance outcomes it owns to completion — books current, reconciliations agreed, receivables tracked, the period closed,…
- Which model you need — A bookkeeper records what happened; an accountant makes it correct; a fractional CFO decides what to do next; an outsourced finance function runs the whole cycle.
- Keeping control — Control is not doing the work yourself.
- Founder time — A founder should own the decisions and almost none of the recurring execution.
- The threshold — Bookkeeping becomes a finance function when the numbers stop being something produced occasionally and start being something the business relies on.
- The monthly standard — Each month should deliver current books, agreed reconciliations, a receivables position, a dated close, management reporting, and a short list of decisions that…
- Software or a service — Software gives a business the machinery to keep its own books.
- QuickBooks or a bookkeeper — QuickBooks automates the steps — feeds, suggested categories, rules, receipts, reconciliation.
- Xero or a bookkeeper — Xero is built for two parties: a business, and an advisor who enters journals and sets lock dates.
- At Par vs a bookkeeping firm — A conventional firm is organised around periodic deliverables; a managed service around continuous ownership.
- At Par vs a freelance bookkeeper — A good freelance bookkeeper is often the right answer.
- AI software vs a managed service — The question is not whether AI touched the work, but whether it came back completed, evidenced and controlled.
Check the provider — including us.
Provider-neutral standards on evidence, automation, authority, switching and clean exit. Written to be used on anyone, and quoted freely.
- Evidence-backed bookkeeping — A figure is evidence-backed when it can explain itself — the document behind it, the transaction it settled, the reconciliation that agreed it, and any…
- When automation is unsure — Uncertainty should produce an exception, not a confident-looking answer — and how to tell from outside whether a provider’s automation is honest about what it…
- What is never automatic — Money leaving, filings submitted and messages in a client’s name should never be automatic.
- Changing providers — Financial history is rarely destroyed in a provider change — it expires, fragments, or lived in one person.
- What you are owed on exit — Everything recording your business rather than the provider’s method — in a format you can open, within agreed days, complete enough for a successor to continue.
- Who controls what — Preparation can be outsourced; commitment cannot.
Industry operating realities.
The finance mechanics that are genuinely specific to a business model, rather than the same page with the industry noun swapped.
- Agencies — How agency finances actually run: retainers and projects at once, pass-through media spend, freelancer costs, and the gap between delivered and invoiced work.
- Software & IT services — Foreign receipts that do not match the invoice, recurring and project billing together, contractor-heavy delivery, and per-seat tooling in three currencies.
- Consultancies & advisory firms — Work in progress that is real but uninvoiced, principal drawings that distort the profit line, recharged expenses, and clients who pay on a committee calendar.
- Foreign clients — The invoice, the bank credit and the ledger never agree.
- Export-service businesses — Earning abroad and spending at home makes finance one connected system, not a task list: books, receivables, contractors, payroll, evidence, close and reporting.
Free tools you can use on any provider.
No sign-up, no email, nothing stored. Everything you type stays in your browser.
- Capacity diagnostic — Twelve questions that work out whether your next move is an in-house finance hire, outsourced finance capacity, or a hybrid.
- Month-end readiness checklist — An interactive nine-area month-end readiness checklist: bank, receivables, payables, payroll, evidence, exceptions and reporting.
- Invoice follow-up health check — A nine-statement self-check on how receivables actually run: owner, next action, promise dates, broken promises, disputes, evidence, matching.
- Provider checklist — A provider-neutral checklist for buying outsourced accounting: thirty questions across ownership, close, evidence, systems, exceptions, continuity, approvals,…
- Handover checklist — A 48-item handover checklist for changing bookkeepers or reclaiming lapsed books: system access, statements, opening balances, source documents, AR, AP, payroll,…
- Overdue invoice follow-up pack — A seven-stage follow-up sequence for an unpaid invoice, with courteous professional wording to copy — from before the due date to the owner’s commercial decision.
Work we did ourselves.
Benchmarks and frameworks At Par authored, with the method stated so you can argue with it. Controlled synthetic corpora, not market statistics.
- Finance Work Completion Benchmark — A 160-item synthetic corpus scored against a seven-state rubric: 78.1% of finance work items completed and 21.9% stopped.
- Month-end exception map — An authored taxonomy of why finance work does not arrive cleanly at close: nine coded families, each with a definition, what it blocks, and who can clear it.
- Receivables operating-state benchmark — A constructed 60-invoice benchmark measuring the gap between an ageing view and an operating-state view.
One case, followed all the way through.
Illustrative worked examples using invented companies — not customer case studies. Each follows a single obligation — something owed, owing or due — from messy input to a completed outcome or an honest exception.
- One invoice, end to end — An illustrative walkthrough of a single invoice through every state — issued, due, followed up, queried, promised, broken, claimed, received, matched — showing…
- Worked example: a supplier invoice — An illustrative walkthrough of one awkward supplier invoice: what arrived, what it failed to say, the question that settled it, and what stayed attached afterwards.
- Worked example: an unmatched credit — An illustrative walkthrough of one bank line that matched nothing: three explanations that all fitted, three ways of being wrong, and what holding it protected.
- One month-end close — An illustrative worked example of one month-end close at a fictional design studio: what arrives, what is reconciled, what stays open, and what the founder gets.
- One broken promise — An illustrative worked example following one invoice through a promised payment date that passes — what changes at that moment, and the decision it puts to the…
- One payment run — An illustrative worked example of one fortnightly supplier payment run: how nine lines were assembled, the bills that never reached it, and who released the money.
- Seven months behind — An illustrative worked example of a catch-up: what could be rebuilt from bank data, what had to come from a person, four things found on the way, and what stayed…
- One filing obligation — An illustrative worked example of one filing obligation — identified early, calculated from closed books, validated, packaged, handed over, and closed only by a…
Read enough. Now show us the actual mess.
Bring last month — the bank statements, whatever the books look like, and the thing that keeps landing back on you. We will tell you plainly what we would own and what would stay with you.
Prefer to reach us directly? Tell us a little and we'll come back with a time.
Book a callWe use your details only to prepare for and hold this call. No spam, ever.
Reviewed by an ACCA on the At Par team · Last updated 29 July 2026 · Guides are provider-neutral standards, not descriptions of any single firm. See what we actually do.