Invoice and reconcile without retyping

The problem it solves

An invoice usually gets written twice. Once when the work was agreed, in an order, an accepted quote or a signed service sheet. Again when somebody picks up that document and keys exactly the same information into the system that issues. At month end there is a third pass, because balancing means rewriting part of it somewhere else.

The effect shows up in the calendar and in confidence. Closing runs late, and one month's numbers arrive when the next is already well under way, so they serve to explain rather than to decide. Expense receipts turn up weeks afterwards, photographed in a message, and for at least one of them nobody remembers what it was. Collection gets worked whenever somebody finds a spare moment, which means the slowest-paying client tends to be the one who has been written to least. And a portion of the administrative day goes to spotting what was invoiced wrong or never invoiced at all.

None of this is fixed by working faster. As long as the document is generated far from the event that creates it, there will be double keying, differences that surface at the end, and a close that depends on one person being available.

What it covers

The session starts with the issuing map. For every document the company produces, the group identifies the event behind it: a delivery, an hour worked, an accepted order, a consumption. Then it marks where that same information is captured again and how many hands touch it between the event and the document. That map organises everything that follows, because it shows plainly which rewriting is avoidable and which reflects a decision somebody genuinely has to make.

The second block is capture at the point of origin. An expense recorded at the moment and place it happens arrives with its context attached; one recorded three weeks later arrives as a photograph with no explanation. The group works out the minimum information that must accompany each receipt, which classification rules can run on their own, and above all which cases should be set aside for a person to look at. Automatic classification earns its place precisely because it shrinks the volume that needs judgement, not because it removes it.

The third block is collection. Participants design a reminder scheme by client type and by age of the balance, separating what can go out on schedule from what requires a phone call. That distinction is not cosmetic: a long-standing client with an unusual delay is not the same case as one who has stopped replying, and treating them alike costs more than the reminder saves. Alongside it sits the record of what was sent and what each client answered, which is what allows the next decision to be made on information rather than impression.

The close reviews the controls, which stay intact whatever gets automated: approving, recording and reviewing remain in different hands, and parallel verification runs for an agreed period before the old method is retired. What the session settles is how the work flows; what any particular entry should be called remains a question for whoever keeps your books.

What participants learn

• Identify the event behind each document and issue from there instead of capturing it again.
• Design the capture of expenses and receipts at the point and moment they occur.
• Apply automatic classification rules and set aside the cases that need human judgement.
• Prioritise collection work by client type, separating scheduled reminders from calls.
• Evaluate whether approval, recording and review controls survive each automated step.

Agenda

1. 01From event to document: issuing without re-entry
2. 02Capturing expenses and receipts at their point of origin
3. 03Payment reminders and the particular treatment each client needs
4. 04Automatic classification and human review of the doubtful cases
5. 05Preparing reconciliation, and what arrives ready
6. 06Controls that survive the automation of the process
7. 07Parallel verification before trusting the result

What the organisation leaves with

• An issuing map for your company: the event behind each document and where it gets re-keyed today.
• A method for capturing expenses and receipts at source, with someone named to review the doubtful ones.
• A collection reminder scheme by client type, marking the point where a person takes over.
• A table of controls that are preserved: who approves, who records and who reviews each automated step.