Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Off-the-shelf invoicing does not match how my business bills

Short answer

Before choosing between a ready-made tool and custom software, write down how a job turns into an invoice: who triggers it, which rules change the amount, who approves and where the money is recorded. If a standard tool covers most of it, adapt your process. Build custom only for the rules that truly differ.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Every month I rebuild invoices in a spreadsheet because the tool cannot do my pricing.
  • Staff copy figures from one system into another to create a single invoice.
  • Some customers need a different layout, split or approval that the tool refuses.
  • I pay for several tools and still keep a manual workaround alongside them.
  • Only one person knows how invoices really get produced, and they are on leave.

Why does this happen?

  1. Standard tools are built around the common case

    A ready-made invoicing tool assumes a typical flow: a customer, a price list, a due date. Anything outside that, such as stage payments, usage-based amounts, split billing or multi-site contracts, becomes a manual step.

  2. The real rules were never written down

    Many businesses bill from habit. The discount that applies to one customer, the order a job is approved in and the exception for a large account live in somebody's head. Until they are written down, no tool, bought or built, can be judged against them.

  3. Data starts in a different system from the invoice

    Hours, orders, deliveries or bookings are recorded in one place and invoiced from another. The gap is filled by copying and retyping, which is where wrong amounts and duplicate invoices come from.

  4. The invoice is only part of the job

    Reminders for late payment, credit notes, links to the accounts and the audit trail matter as much as the PDF. A tool that creates the invoice but ignores these pushes the work back to staff.

  5. Custom software gets overbuilt

    The opposite failure is a large custom system for rules that a settings change in an existing tool would have covered. It then has to be maintained, backed up and updated like any other software.

What can I do about it today?

  1. Follow five recent invoices from start to finishPick five different customers. For each, note what started the invoice, where the numbers came from, who checked it and where it was recorded afterwards.
  2. List the rules that change the amountDiscounts, minimums, taxes your accountant applies, stage payments and customer-specific terms. One line each, in plain words.
  3. Mark what staff do by handCircle every step where someone copies, retypes or checks a figure. These are the cost of the current setup.
  4. Ask your accountant which records they needThey know which fields and reports the books depend on. Any new system has to keep producing those.
  5. Do not switch the live invoicing over in one goKeep the current process running. Any new tool should first run beside it on a few customers, so mistakes show up before they reach everyone.
  6. Keep a copy of your customer and invoice dataExport it now. Whatever you choose, you will need it to move or to check totals.

When should I bring someone in?

  • The workaround is now the most error-prone part of your month, and the written rules show a standard tool cannot cover them.
  • Invoices have to pull data from an app, a booking system or an order system that nobody else can change.

How do I handle it?

  1. Write the billing rules before the codeI turn your five traced invoices into a short written list of rules and exceptions, and ask you to confirm it.
  2. Check what an existing tool can already doIf settings or a small connection to a tool you already use closes the gap, I say so. Custom software is the last option, not the first.
  3. Keep the books as the source of truthAnything I build feeds your accounting records in the format your accountant expects, rather than replacing them.
  4. Run it beside the old process firstThe new flow produces invoices for a small group while the old one continues. Totals are compared line by line before anything is switched.
  5. Hand over with a backup and a rollbackA backup is taken before production changes, the way back to the old process is tested, and the rules are left written down for whoever comes next.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Should I buy a tool or build one?

Decide after the rules are written down. If most of them fit a ready-made tool, use it and change the odd process. Build only the part that is genuinely specific to your business.

Can the new system send invoices to my accountant's software?

Usually the invoice data can be exported or sent through the accounting tool's interface, if that tool offers one. I check what yours supports before promising a design.

What about tax rules on invoices?

Your accountant decides what an invoice must contain in your country. I build to the rules they give me and do not give tax advice.

Will old invoices move across?

They can be imported for reference. The totals are checked against your records before anyone relies on them.

How was this page made?

I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.