DEV Community: Karactif Tech

The Year-End Invoicing Checklist: Six Weeks Out, Two Weeks Out, and the Morning After

Karactif Tech — Wed, 11 Nov 2026 21:51:52 +0000

The Year-End Invoicing Checklist: Six Weeks Out, Two Weeks Out, and the Morning After

Year-end admin fails for a predictable reason: it competes with everything else in December. Clients go quiet, staff take leave, the work you meant to finish arrives all at once, and the records you meant to tidy in November become a January problem that eats three weekends.

The fix is not discipline in the abstract. It is sequencing — doing the money work while there is still time for a client to pay, and doing the record work while there is still time to find what is missing.

The checklist is organised by when to do it. Treat these as offsets from your own year-end date, not as dates — deadlines vary by jurisdiction and entity type.

Six weeks out: get the money moving

This is the only block where an action can still change this year's cash. Everything else is cleanup.

Invoice everything that is finished. Go through active jobs and ask, for each one, whether the work is complete but unbilled. In service businesses this is almost always the largest single number in the review, and it is the one most often discovered too late.
List receivables by age, not by value. The three oldest invoices are the priority. A large invoice at fourteen days will pay itself; a small one at ninety days will not.
Separate disputes from delays. A disputed invoice needs a conversation about the work; a delayed one needs a reminder. Filing them together means the dispute sits untouched while you chase the wrong thing.
Check deposits and credits are reflected. A deposit taken in March but not credited on the final invoice means the client was overbilled — or, worse, that you never noticed.
Confirm nothing was double-issued. Issuing twice for one job is rare, but around year-end, when other people help with admin, it happens.

If a client says payment will land in January, write it down with the date. A promise is not a payment, and the difference shapes your first week of the new year.

Four weeks out: fix the records before anyone asks for them

Now switch from chasing money to closing gaps.

Audit the numbering. Invoices should run in one unbroken sequence, with no gaps and no duplicates. A gap is not automatically a problem, but you should be able to say why it exists — a cancelled job should have a credit note, not a missing number.
Find the missing PDFs. Every issued invoice should exist as a file, named consistently, in one place. Reconstructing one from an email thread in February is far harder than checking a folder in December.
Check client details. Names, addresses, tax or registration numbers, and any PO reference. A wrong entity name on a December invoice becomes a January amendment request, and amendments are slow.
Reconcile payments against documents, including partial payments. A fully paid invoice still marked unpaid will trigger an awkward reminder — to a good client, at the worst moment.
Export and back up. Whatever system you use, take a copy of the year's invoices and payment records outside it. Accounts get closed, subscriptions lapse, phones get replaced.

Two weeks out: fix the process, not the paperwork

Small policy decisions made now save arguments next year.

Refresh your templates. Remove last year's dates, update bank details if they changed, and check that the fields you keep forgetting are actually on the document.
Review your payment terms. If most of your invoices are paid later than your stated terms, the terms are decorative. Either enforce them or change them to something you will enforce.
Decide your deposit and late-payment policy, and write it into your agreement template rather than deciding case by case.
Check subscriptions and seats. If you are paying for a tier you do not use, December is the cheapest month to notice.
Set next year's numbering convention if you use one with a year prefix, so the first January invoice does not restart the sequence.

The last week: do not save invoicing for the 31st

Two practical rules for the final days.

Issue before the break, not on it. An invoice sent on the last working day lands when the client's accounts payable team is gone, and is processed in the new year regardless. Three days earlier, it has a chance of making the last payment run.

Write down what carries over. Which invoices are still unpaid, which jobs are unfinished, which promises were made and by whom. One page, dated. The version of you who returns in January will not remember the details, and neither will anyone else.

The morning after: start clean

The first working day of the new year is not for strategy. It is for four small things:

Confirm the opening receivables list matches what you closed with.
Note the invoices you expect in the first two weeks, and diarise the follow-up.
Issue anything that was held back deliberately.
Check that the first invoice of the year is numbered correctly and carries the current details.

That is twenty minutes, and it is the difference between starting the year with a plan and with an archaeology project.

What people will ask you for

Whoever handles your accounts will ask for the same things: invoices issued, payments received, evidence of anything unpaid, and expenses tied to specific jobs. If those four exist as exports rather than memories, the conversation is short.

Tax treatment, filing deadlines and record-retention periods vary by country and by whether you are a sole trader or a company. This is a housekeeping checklist, not tax advice — confirm the specifics with a qualified professional.

Where the tool fits

Most of the checklist is habit. Software helps with the boring middle: knowing which invoices are paid, and producing a clean document on demand.

Invoice Maker is a free-to-download iPhone and Android app from Caractiv Tech: saved clients and reusable line items, 34 currencies, PDF export, and paid, unpaid and partially paid status recorded against each invoice. Manual invoicing works offline; the AI drafting, which turns a typed description or voice note into an editable draft you review and confirm before it becomes a document, needs a connection. Premium templates and branding are behind a subscription.

The one-page version

If you only do three things, do these: invoice the finished work now, chase the three oldest invoices personally, and export this year's records somewhere you will still have them next year. Everything else on this list is refinement.

Disclosure: I work with the team behind the app linked above, which is why it appears as an example. This article is general information, not tax, legal or accounting advice; year-end dates, filing obligations and record retention rules vary by jurisdiction, so check what applies to you.

Appendix: distribution assets (not part of the article body)

Social summaries

X: Year-end invoicing is a sequencing problem. Do the money work six weeks out, while a client can still pay; do the record work four weeks out, while you can still find what's missing. Saving it for the 31st just means doing it in January.

LinkedIn: The largest number in most year-end reviews is finished work that was never invoiced. It is also the easiest to miss, because there is no document to remind you. Chase the three oldest receivables personally, separate disputes from delays, and export the year's records somewhere you will still have them — three actions that do most of the work.

dev.to: The invoice numbering audit is the step people skip. Gaps in the sequence are not automatically a problem, but you should be able to say why each one exists — a cancelled job should leave a credit note behind, not a hole.

Image suggestion

Concept: A printed checklist on a clipboard with three sections marked "6 weeks", "4 weeks", "last week", a pen resting on it, a laptop edge showing a receivables list, and a coffee cup; cool December daylight, slightly cluttered desk.

Alt text: Printed year-end invoicing checklist divided into six-week, four-week and final-week sections.

Notes: 1200×800 for blog header, 1080×1080 for LinkedIn. Keep any visible invoice data fictional and avoid showing a real year-end date or tax form.

Agency Invoicing: Four Billing Models, One Month-End, and the WIP Number Nobody Checks

Karactif Tech — Wed, 11 Nov 2026 21:51:49 +0000

Agency Invoicing: Four Billing Models, One Month-End, and the WIP Number Nobody Checks

An agency invoice is a financial document doing a marketing job. It goes to a client who judges your work by how the paperwork feels, lands in a procurement process that has its own rules, and feeds a cash flow model that must survive payroll on the 25th. Get it wrong and the failure is undramatic: a month that closes late, a client who queries every line, a founder reconciling spreadsheets at 11pm.

Most agency invoicing problems trace back to one of four decisions: which billing model you promised, whether the milestone was evidenced, how pass-through costs were shown, and whether anyone counted the work you did but never billed.

Pick the model per client, and write down the rules

Agencies usually run several models at once, and the mistakes happen where the rules were never stated.

Retainer, billed in advance. The client buys capacity for the month. Billing on the 1st is cleaner for your cash flow, but it obliges you to define what happens to unused hours: roll over, expire, or accrue against a cap. Pick one, put it in the agreement, and repeat the rule on the invoice. "As per agreement" is not a rule a client's finance team can apply.

Retainer, billed in arrears. Common when the client wants proof of effort first. The invoice then needs a summary: hours by discipline against the allowance, plus any overage rate. Without it, every retainer invoice invites a meeting.

Milestone or fixed fee. Tied to deliverables, not dates. The invoice should name the deliverable and the approval it rests on.

Time and materials. Needs a rate card and a report. A lump "team time" line is the most queried item in agency billing: the client cannot see what they are paying for.

Whichever model you use, the client's finance team should be able to match the invoice to a contract clause without emailing you.

Milestones need an artefact

"Phase 2 complete — $18,000" is an invitation to argue about whether phase 2 was complete. The fix costs one sentence: reference the thing that was approved.

A milestone line item should carry the deliverable name, the date it was signed off, and who signed it off. If approval came by email, quote the date. If it came in a call, send a two-line confirmation — the invoice will need something to point at in twelve weeks, when the approver has changed jobs.

This matters more in agencies than almost anywhere else, because approval is distributed: a creative director approves the work, procurement approves the spend, finance pays the invoice. Those three do not talk to each other, so the document does the introducing.

Pass-through costs: show them, do not absorb them

Media spend, licences, freelance specialists, printing, travel, software bought on the client's behalf. Two rules:

Bill at cost, on a separate line, with the third-party invoice attached. Absorbing a $6,000 media buy into a "production" line destroys your margin reporting and muddies the client's accounting.

Decide the markup before the spend, not at invoice time. If you charge a handling percentage, say so in the agreement and show it as its own line. A markup that appears for the first time on an invoice reads as an ambush, even when it is entirely legitimate.

If a pass-through is large relative to the fee, bill it when incurred rather than at month-end. You are not a bank.

The procurement tax: POs, portals and formats

Every agency has one client whose invoice process is a separate job: a PO number for a specific field, a portal that rejects large attachments, a required cost-centre code, a PDF naming convention.

Handle it once, in writing, and reuse it:

Build a one-page requirement sheet per client: PO or reference format, portal, required fields, submission window, contact for queries.
Put the required fields into the invoice itself, not into the covering email. Portals strip email bodies.
Check the amount against the PO before submitting. An invoice that exceeds the PO balance is rejected, and rejection restarts the clock.

The agencies that get paid fastest are rarely the ones with the best relationships. They are the ones whose documents clear procurement on the first pass.

The number nobody checks: unbilled WIP

Work in progress is the money you have already spent — in salaries — and have not yet invoiced. It is the largest invisible number in most small agencies, and where profitable months quietly turn unprofitable.

A simple weekly check: for each active client, what has been delivered but not billed, at what value? Two patterns appear immediately. Projects finished weeks ago with no final invoice issued. Retainers where the overage was never billed because nobody wanted the conversation.

The second is a pricing problem in billing clothing; no invoicing discipline fixes it, but naming it is the first step.

Currency, if you bill across borders

An agency billing across borders has three decisions: invoice in the currency you quoted; state the currency code, never a bare symbol; and if you must convert, record the rate and date on the document. Then decide who pays the transfer fee — on a $300 invoice, $30 is 10% of the fee.

Where the tool fits

Agencies do not need invoicing software to be clever. They need it to be consistent: same numbering, same fields, same payment status, every client.

Invoice Maker is a free-to-download iPhone and Android app from Caractiv Tech that handles the repetitive part: saved clients, reusable line items, 34 currencies, PDF export, and paid, unpaid and partially paid status per invoice. Manual invoicing works offline; the AI drafting, which turns a typed description or voice note into an editable draft you review and confirm before issuing, needs a connection. Premium templates and branding are behind a subscription, which matters if the invoice doubles as a client-facing brand surface.

It will not enforce a PO number or chase a late payer. Those stay your process.

The month-end that takes two days, not five

Run the close in this order, and the sequencing does most of the work:

Finish the billing run first. Every client with delivered work gets an invoice or a note explaining why not.
Reconcile payments against documents, including partials, before checking the bank total.
Review unbilled WIP by client and confirm which items move to next month.
Check the aging list and decide which three invoices get chased this week.
Export and file every issued PDF with its PO reference.

Two days is achievable. Five usually means step one was skipped for a fortnight and step five never happened.

Disclosure: I work with the team behind the app mentioned above, which is why it appears as an example. This article is general business information, not accounting, tax or legal advice; contract terms, VAT/GST treatment and revenue recognition rules vary by jurisdiction, so take professional advice for your structure.

Appendix: distribution assets (not part of the article body)

Social summaries

X: Agency cash flow rarely breaks in one dramatic event. It erodes: a milestone invoiced without an approval reference, pass-through costs absorbed into a fee line, and WIP nobody counted. Five checks that catch it before month-end.

LinkedIn: Three people approve an agency invoice and they never talk to each other: the creative director approves the work, procurement approves the spend, finance pays the document. That is why a milestone line needs the deliverable name, the sign-off date and the person who signed it — the invoice has to do the introducing.

dev.to: The most useful agency metric I have tracked is not utilisation — it is unbilled WIP by client. Two patterns show up in the first week: projects finished with no final invoice sent, and retainer overages that were never billed because nobody wanted the conversation.

Image suggestion

Concept: A desk with three client folders, a laptop showing a retainer invoice with a time summary, a sticky note reading "PO: NW-88213", and a printed aging list with three lines circled in pen.

Alt text: Agency desk with client folders and a retainer invoice showing a time summary and PO reference.

Notes: 1200×800 blog header, 1080×1080 for LinkedIn. Use fictional client names and PO numbers; no real rate cards or bank details visible.

Gig Work Pays Weekly. Your Invoicing Records Shouldn't Live in a Shoebox.

Karactif Tech — Wed, 11 Nov 2026 21:46:44 +0000

Gig Work Pays Weekly. Your Invoicing Records Shouldn't Live in a Shoebox.

Gig work has a rhythm regular employment does not: money arrives in small amounts, from several directions, often before you have finished thinking about the job that earned it. A delivery app pays out on Tuesday, a marketplace releases a booking fee on Thursday, a private client texts a photo of a receipt on Friday.

That rhythm is why so many gig workers have no reliable record of what they earned. The payment arrives without an invoice, so the habit never forms. Then a client disputes a charge, a platform asks for proof of a job, or a filing deadline appears, and the answer lives in four apps and one camera roll.

Three kinds of gig income, three record types

Platform-collected work. The customer pays the platform, the platform pays you, a commission comes out in between. You usually cannot invoice the customer, but keep the platform's earnings statement: it is the only document showing gross, fees and net per job.

Direct clients. Someone found you through a marketplace, then hired you privately, or you picked up the work yourself. Here the document is your responsibility, and it is where most gig workers are unprotected, because the work feels casual and an invoice feels formal.

Mixed arrangements. The platform supplies the client but you invoice them directly, or you invoice the platform for a bonus or reimbursement. These are the ones where a missing document is hardest to reconstruct.

If you are unsure which applies, ask who decides when you get paid. That party needs either your invoice or your record of their statement.

An invoice that survives being questioned

Gig invoices are short because the jobs are short. That is fine, as long as five things are on the document:

Who you are, under the name your client knows.
A unique number, sequential across everything you issue — not restarted per client.
The date of service, not just the date you wrote the invoice. For gig work these differ, and the gap is what disputes turn on.
A reference the client recognises: booking ID, job number, address, platform order reference.
What was done, in units: hours, trips, deliveries, rooms. "Services rendered" is not a description.

Add a payment method and a due date. For a private client, a due date is the difference between "I will send it over" and a payment you can point at.

Bill the same day, from the same place

Gig work has one natural advantage: you are already holding the phone. Create the invoice at the end of the job, before accepting the next one, while you still remember the extra hour, the reimbursed parking, the Thursday second visit. A week later you are estimating, and estimating rounds in the client's favour.

Two things make this fast enough to actually happen: saved client details, and reusable line items for work you do repeatedly. When a job recurs, the invoice is a quantity change rather than a typing exercise.

Track what the invoice does not show

An invoice records what you charged, not what the work cost. Gig income is unusually cost-heavy — fuel, mileage, parking, tolls, equipment, platform fees, data. Capture those as they happen:

Mileage per job, with start, end and destination.
Platform fees, recorded separately from the gross.
Tips and cancellation charges as their own lines rather than folded into the base fee; mixing them makes reconciliation harder than it needs to be.
Job-specific materials, with the receipt photographed on the day.

Unglamorous, and the difference between a filing season that takes an evening and one that takes a fortnight.

One ledger, many payers

The defining feature of gig work is plurality: rideshare Monday, deliveries Wednesday, two private cleaning clients Friday, event shifts once a month. Do not build a separate system for each. One ledger, one numbering sequence, every document tagged by payer and work type. Then numbering stays unique, you can see which stream actually pays once costs are subtracted, and a payer's history is a filter rather than an excavation.

Multiple currencies, multiple platforms

Gig platforms are increasingly cross-border, and payouts can arrive in two currencies in the same week. Three rules keep it honest: write the currency code, because $400 is four different amounts depending on where the reader sits; record what actually landed, not what the platform said it would send; and keep the statement with the payout, so gross-to-net is reproducible rather than remembered.

Where the tool fits

The workflow needs three things: fast documents from saved data, a payment status per document, and records you can filter by payer.

Invoice Maker covers that narrow set on iPhone and Android, free to download from Caractiv Tech: saved clients and reusable line items, 34 currencies, PDF export, and paid, unpaid and partially paid status per invoice. Manual invoicing works offline, which suits job sites and basements; the AI drafting, which turns a typed or dictated description into an editable draft you confirm before issuing, needs a connection. Premium templates and branding sit behind a subscription.

What no app can do is decide the invoice gets written at all. That is the habit.

The twenty-minute weekly close

Once a week, same day:

Issue invoices for work already done. Anything older than seven days is a risk, not a receivable.
Reconcile platform payouts against the jobs they represent, noting fees.
Mark status: paid, unpaid, partial. A half-paid invoice is not paid.
Log the week's mileage and job-specific costs.
Note one thing that went wrong — a no-show, a chargeback, a client who haggled after the fact — and which term or deposit would have prevented it.

Twenty minutes weekly replaces a weekend in April. That is the trade: a little admin while the job is fresh, in exchange for never reconstructing your own year.

Disclosure: I work with the team behind the app mentioned above, which is why it appears as an example. This is general information, not tax, legal or accounting advice; record-keeping requirements and how gig income is treated vary by country and platform, so confirm the rules that apply to you.

Appendix: distribution assets (not part of the article body)

Social summaries

X: Gig work breaks the invoicing habit because the money arrives without a document. Three payer types, one numbering sequence, five fields on the invoice, twenty minutes a week. That is the whole system.

LinkedIn: The reason gig workers have poor records is structural, not personal: platforms pay out without ever asking for an invoice, so the habit never forms. Then a dispute or a filing deadline arrives and the answer is spread across four apps. The fix is a single ledger, one numbering sequence, a date-of-service field, and a weekly twenty-minute close.

dev.to: The most useful field I added to my gig invoices was the date of service, separate from the invoice date. For short jobs, that gap is what every dispute actually turns on — and it is the field most templates leave out.

Image suggestion

Concept: A kitchen table with a phone showing an invoice, a paper diary open to a week of mileage notes, a fuel receipt and a delivery bag in the background; warm evening light, deliberately unstyled.

Alt text: Phone showing a gig work invoice beside a mileage log, fuel receipt and delivery bag.

Notes: 1200×800 for blog header, 1080×1080 for LinkedIn. Keep the on-screen client as "Sample Client" and blur any real receipt details.

Seasonal Businesses Don't Have a Slow Season Problem. They Have an Invoicing Calendar Problem.

Karactif Tech — Wed, 11 Nov 2026 21:46:41 +0000

Seasonal Businesses Don't Have a Slow Season Problem. They Have an Invoicing Calendar Problem.

Every seasonal business owner has heard the same advice: save for the winter, budget for the quiet months, put something aside. It is correct and almost useless, because it describes the outcome rather than the mechanism. The money does not fail to appear in February because you forgot to save it. It fails to appear because the invoices that should have funded February were issued in September, paid in November, and spent in December on restocking.

The businesses that survive the off-season comfortably are not better savers. They bill differently during the peak — earlier, in more pieces, with terms written for a client who will still be there in six weeks.

The shape of seasonal cash flow

Seasonal revenue is concentrated and lumpy. A landscaping company might bill 70% of its year between April and September. A ski rental shop does the reverse. A wedding photographer books the calendar in spring for events in autumn.

Two things follow, and both are arithmetic rather than attitude:

Your invoicing workload is not evenly distributed. Peak season is also peak admin. The week you are busiest is the week you have the least time to send invoices, which is precisely when the most invoices need sending.

Your receivables are exposed to your own season. An invoice issued in the last week of peak, on net 30, lands in your bank account after the work has stopped. If that client pays in 45 days instead of 30, the money arrives in the middle of your slowest month — or does not arrive at all until you chase it.

Bill in smaller pieces, earlier

The highest-leverage change is to stop treating a seasonal job as one invoice at the end.

For a project that spans weeks, break billing into stages that map to work already completed: booking deposit, materials delivered, mid-project milestone, completion, and any retention balance. Each piece is smaller, easier to approve, and arrives sooner.

For repeat seasonal work — pool servicing, snow removal, seasonal maintenance contracts — a monthly invoice for the season is usually better than a single bill in October. The client budgets for it, you collect steadily, and a dispute about one month does not freeze the whole contract's revenue.

For high-demand windows, a booking deposit is not rude, it is standard. It also protects you against the specific seasonal risk: a client who reserves your busiest week, cancels in week three, and leaves you unable to resell the slot.

Write terms for the season, not the calendar

Net 30 is a habit, not a law. If your last invoices go out in September and your cash need runs to March, net 30 leaves a five-month hole that no amount of discipline fills.

The fix is a conversation at booking, not at invoicing: "For work in peak season we invoice on completion, due in 10 days." Most clients accept it, because they booked you for a reason. The ones who insist on 45 days are telling you something useful while you can still price the delay into the quote.

Two conventions worth adopting:

Give a date, not a duration. "Due 12 September" survives forwarding better than "net 30".
Invoice the day the work finishes. In peak season, a Friday invoice often means a Monday invoice, and Monday is three clients later.

Smooth the trough with billable things

The off-season is not only a cash problem; it is a capacity problem. You have time and no work. The standard answer is marketing, which costs money you do not have yet. A better answer is selling something that does not require you to be on site.

Depending on your trade, that might be:

Prepaid packages sold in the off-season for peak-season work: a spring cleanup bundle, five services bought in January for use in May. You get cash when you need it and a booked calendar when you need that.
Maintenance plans billed monthly across twelve months, with the site visits concentrated in the busy half. The revenue is smooth even though the labour is not.
Storage, winterisation or equipment servicing — adjacent services your existing clients already need and already trust you for.
Deferred-start projects: design, planning, permits and quotes done in the quiet months, invoiced as a professional fee, with the build scheduled for spring.

Each of these is an invoice you would not otherwise have issued, at a time when issuing invoices is the only productive thing available.

Protect the records when volume peaks

Peak season has a specific failure mode: invoices are created in a hurry, numbered inconsistently, and never reconciled, so the off-season becomes a forensic exercise in reconstructing what was billed to whom.

Three small controls prevent most of it:

Keep numbering sequential and never reuse a number, including for cancelled jobs — issue a credit note instead, so the sequence tells the truth.
Record payment status the day the payment lands, not at month end. A fully paid invoice marked unpaid is how businesses send awkward second requests to good clients.
Photograph or export every issued document. The person who did the job in July may not be the one answering questions in January.

Where the tool fits

Most of this is scheduling, not software. But two things help during a peak: documents that can be produced quickly from saved data, and payment status that does not live in a notebook.

Invoice Maker is a free-to-download iOS and Android app from Caractiv Tech built around repeat work: saved clients, reusable line items, and 34 currencies, with paid, unpaid and partially paid status recorded against each document. Manual invoicing works offline, which matters when the peak season happens somewhere with poor signal; the AI drafting, which turns a typed description or voice note into an editable draft you review before anything is issued, needs a connection. PDFs can be shared or printed on site, and a subscription adds Premium templates and branding. None of it decides your terms for you.

The four-week gutter check

Once a year, four weeks before your slow season starts, sit down with the invoice list and answer three questions:

What is issued but unpaid, and which of those will still be unpaid in eight weeks?
What work is finished but not yet invoiced? In a busy season, this is always more than you think.
What could I sell now that pays now and delivers later?

Question two is usually where the money is hiding. Finished, uninvoiced work is the most expensive thing a seasonal business owns, because it is a loan to a client you never agreed to make.

Disclosure: I work with the team behind the app linked above, which is why it appears as an example. This is general business information, not financial, tax or legal advice; contract terms, deposits and cancellation policies are governed by local law, so check what applies where you operate.

Appendix: distribution assets (not part of the article body)

Social summaries

X: Seasonal cash flow is not a savings problem, it is a billing calendar problem. If your last peak-season invoice goes out on net 30, the money lands after the work stops — or in your slowest month.

LinkedIn: Every seasonal business gets told to "save for the winter." That advice describes the outcome, not the mechanism. The mechanism is billing: smaller pieces earlier, terms written for the season rather than the calendar, deposits at booking, and prepaid packages sold in the trough. The most expensive thing a seasonal business owns is finished work it has not invoiced yet.

dev.to: The unglamorous lesson from a seasonal business: your busiest week is also the week with the most invoices to send and the least time to send them. Batching the document creation and recording payment status immediately is worth more than any forecasting tool.

Image suggestion

Concept: A wall calendar with peak months shaded dark and a phone in front of it showing four invoices dated across those months; a hand-drawn line beneath showing cash in versus cash out, with the gap labelled "this is the invoice that should have gone out in September".

Alt text: Calendar with shaded peak season beside a phone showing invoices dated across the busy months.

Notes: 1200×800 blog header, 1080×1080 crop for LinkedIn. Use fictional client names and amounts; keep the calendar generic, without a real year or local holidays.

The Three Invoice Numbers That Tell You Cash Flow Is About to Break

Karactif Tech — Wed, 11 Nov 2026 21:41:36 +0000

The Three Invoice Numbers That Tell You Cash Flow Is About to Break

Most small businesses discover a collections problem the same way: the bank balance is lower than the spreadsheet said it would be, and nobody can explain the gap without opening four tabs. Revenue looked fine. The pipeline looked fine. The money simply was not there.

Cash flow rarely breaks in a single dramatic event. It erodes — one invoice that slipped thirty days, one client who always pays "after the next funding round", one disputed line item nobody chased. By the time it is visible in the bank account, the problem is months old.

Three numbers catch that erosion early, and all three can be calculated from invoices you already have. No dashboard subscription, no accountant, no benchmarking data you cannot verify.

Why revenue is the wrong number to watch

Revenue measures work you have done. Cash measures work you have been paid for. A business can double revenue and still run out of money, because every new client adds a payment cycle you have to fund.

Profit and loss statements also smooth everything into a monthly figure. They cannot tell you that one client represents a third of your receivables, or that your average payment time has drifted from 21 days to 38 over two quarters. Those are the details that decide whether you make payroll in February.

Metric 1: Days sales outstanding

DSO answers one question: on average, how many days does it take to turn an invoice into cash?

The standard formula, for a period:

DSO = (average accounts receivable ÷ total credit sales) × number of days in the period

Average receivables means the opening balance plus the closing balance, divided by two. Use credit sales only — anything paid at the counter is not sitting in receivables.

A worked example. Over 90 days you invoice $160,000. Receivables were $40,000 at the start and $56,000 at the end, so average receivables are $48,000.

(48,000 ÷ 160,000) × 90 = 27 days

Now compare that to your stated terms. If you invoice on net 14 and DSO is 27, your real terms are twice what your paperwork says, and every forecast built on "net 14" is wrong by thirteen days of working capital.

DSO is a lagging average, which is its weakness. It moves slowly, so it will not warn you about the invoice that went bad last week. It is still the right number for tracking direction quarter over quarter.

Metric 2: Overdue rate — and the number hiding inside it

DSO tells you the average. Overdue rate tells you how much of the outstanding balance is already late.

Overdue rate = value of invoices past due ÷ total outstanding receivables

Two businesses can both sit at 30% and be in completely different situations. In one, the late money is five invoices at four days overdue. In the other, it is one invoice at ninety days and two at sixty. The second business has a collection problem; the first has a timing blip.

So calculate a second figure alongside it:

Weighted average days overdue = Σ (invoice value × days overdue) ÷ Σ invoice value

That single number resists the most common self-deception in receivables: a healthy-looking overdue rate held up by a large volume of small, slightly-late invoices, while the three invoices that actually matter quietly age out.

Metric 3: Aging concentration

Sort every unpaid invoice into buckets — current, 1–30 days late, 31–60, 61–90, 90+. Then look at two ratios:

Share of receivables in the 60+ bucket. This is the money most likely to become a write-off. A small share is normal; a growing share is a trend.
Share of receivables held by your largest client. If one customer is more than roughly a quarter of your outstanding balance, their payment behaviour is your cash flow, and you have no diversification.

Neither ratio needs a benchmark to be useful. Your own trend over three months is the comparison that matters, because collection norms differ wildly by industry, contract size and whether your customers are consumers or procurement departments.

What the numbers cannot tell you

Three limits worth knowing before you build a ritual around them:

They do not distinguish a dispute from forgetfulness. A disputed invoice needs a conversation about the work. A forgotten one needs a reminder. Same bucket, opposite fixes, which is why you should tag disputed invoices separately rather than letting them inflate your overdue rate.

They will not fix weak terms. If your invoices have no due date, DSO is measuring your own ambiguity. No metric repairs a document that never told the client when to pay.

Averages hide the tail. One invoice at 120 days can be invisible in a 24-day DSO and still be the thing that hurts. Always read the aging report next to the average.

The 15-minute weekly review

Metrics only work if the underlying data is current, and payment status is the field people stop updating first. Once a week, same day, same time:

Mark every invoice paid, unpaid or partially paid. Partials matter — an invoice half-paid is not paid.
List what is overdue, sorted by days late, not by value.
Circle the three oldest. Those get an action today, not a note.
Move disputed invoices to their own list with one line on what is disputed.
Note anything that changed since last week: a new large invoice, a client who suddenly went quiet.

Fifteen minutes, five checks, one page. Do it for a quarter and you will know your real payment cycle better than most accountants who see your books twice a year.

Where the numbers come from

The arithmetic is trivial; the discipline is keeping status accurate. That is easier when the payment record lives beside the document rather than in a separate spreadsheet that drifts out of sync.

One example of that pattern: Invoice Maker, a free-to-download iOS and Android app from Caractiv Tech, records paid, unpaid and partially paid status against each invoice, reuses saved clients and line items, and supports 34 currencies — which matters for reporting, because a receivables total mixing currencies is not a number, it is a guess. Manual invoicing works offline; the AI drafting, which turns a typed description or voice note into an editable draft you review and confirm, needs a connection. Premium templates and branding sit behind a subscription.

Start with one number

Pick DSO. Calculate it for the last quarter, then for the quarter before. If it moved by more than a few days in the wrong direction, you do not have a cash problem yet — you have a warning. That is the entire point of measuring: to get the warning while it is still cheap to act on.

Disclosure: I work with the team behind the app mentioned above. This article is general business information, not accounting, tax or legal advice; how you recognise revenue and report receivables depends on your jurisdiction and entity type, so confirm specifics with a qualified professional.

Appendix: distribution assets (not part of the article body)

Social summaries

X: Revenue is the number everyone watches. It is also the one that tells you least about whether you can make payroll. DSO, overdue rate, and aging concentration — three formulas, one 15-minute weekly review.

LinkedIn: A healthy-looking overdue rate can hide a dying business. If 30% of your receivables are late, that number means something very different when it is five invoices at four days versus one invoice at ninety. The fix is to read three numbers together: DSO for direction, weighted days overdue for severity, aging concentration for risk. All three come from invoices you already have.

dev.to: Wrote up the three receivables metrics I actually use, with the formulas and a worked example. The interesting part was not the math — it was realising DSO had drifted from 21 to 38 days across two quarters and nobody noticed because the monthly P&L looked fine.

Image suggestion

Concept: A simple three-panel dashboard sketch on paper beside a phone showing a list of invoices with mixed paid/unpaid status chips; one panel labelled DSO with an arrow drifting upward, hand-drawn aging buckets current → 90+.

Alt text: Hand-drawn receivables dashboard showing DSO, overdue rate and aging buckets beside a phone invoice list.

Notes: 1200×800 blog header, 1080×1080 for LinkedIn. If a screen is shown, use fictional data ("Sample Client", "INV-0042") and no real bank details.

The Shoebox Is Not a Record-Keeping System

Karactif Tech — Wed, 11 Nov 2026 21:41:32 +0000

The Shoebox Is Not a Record-Keeping System

Every year, a certain kind of small business owner empties a drawer onto a table: crumpled receipts, bank statements, a folder of invoices named scan001.pdf, and a phone full of receipt photos. Then they try to reconstruct twelve months.

The work was done and the money moved, but the record is scattered across four formats and two devices, and every accountant question takes a day to answer.

Record keeping is not paperwork for its own sake. It is the difference between a ten-minute handover and a two-week reconstruction, and between a deduction you can support and one you cannot.

What actually counts as a record

A record is evidence that something happened, and for invoicing there are usually four kinds:

The invoice itself. What you charged, to whom, for what, in which currency, on what terms.
Proof of payment. A bank statement line, a remittance advice, a receipt. An invoice proves you billed; it does not prove you were paid.
The agreement behind it. The quote, contract, purchase order or email that shows the client accepted the price. This is what settles a dispute six months later.
The costs. Supplier invoices, receipts, subscriptions, mileage, hardware. These are records too, and they are the ones people lose first.

A credit note belongs in the same chain as the original; keep them together, or the numbers look wrong to anyone reconstructing the year.

How long to keep it

Retention periods vary by country, tax type and company structure. They are usually measured in years, and they can restart when a return is amended, an audit opens or a dispute is live. Contracts and anything with ongoing liability are worth keeping longer than the minimum.

So the practical rule is not a number. It is: know your local minimum, then add a margin, and never destroy records while a period is open or a question is unresolved. Ask an accountant in your jurisdiction; the answer depends on where you trade, not on a blog post.

Paper, scans or both

Many tax authorities accept digital copies; others still expect originals for certain items. Details are local, including whether scans must be legible, complete and retrievable for the whole period.

The failure modes are universal: a thermal receipt faded to blank, a photo with the total cropped out, a scan named IMG_2231.jpg with no date or vendor.

Three habits fix most of it:

Scan or photograph at the point of receipt, not at the end of the month. Two seconds now, an hour later.
Check the image before you file it. Can you read the total, the date and the vendor? If not, retake it.
Keep a backup that is not the same device. A phone is not an archive; phones get lost, stolen and dropped in water.

A folder structure that survives

Fancy systems fail when they need maintenance. A structure that survives is boring and shallow:

2026/
  invoices-issued/
  invoices-received/
  receipts/
  bank/
  contracts/
  tax-returns/

Inside each folder, sort by date, and name files so they sort themselves:

2026-03-15_Acme-Studios_INV-1042.pdf
2026-03-16_Supplier-Co_receipt_0148.pdf

Date first, then who, then what. No spaces, no "final". With multiple currencies, add the currency code to the name or to the index.

One index file per year, listing what is where and anything unusual, is worth more than any app — and it is the fastest thing to hand to an accountant.

The twenty-minute monthly close

The single highest-return habit in record keeping is a short, fixed monthly pass. Once a month, on the same day:

Export every invoice you issued that month as a PDF, and file it.
Download the bank statement for the period.
Match payments to invoices. Mark what is paid, part-paid and outstanding.
File the receipts you collected, and note any that are missing.
Write one line in the index: anything unusual, any client dispute, any currency conversion.
Back up the folder.

Twenty minutes a month replaces the annual archaeology. It also means you notice an unpaid invoice in week four, not in April.

Currency and cross-border records

If you invoice in more than one currency, the record has two jobs: show what you billed in the original currency, and show what it became in your reporting currency. Keep both.

The invoice in the currency you issued it.
The exchange rate you used, and the date of that rate.
The payment as it arrived, including any transfer fee.
A note of who bore the fee, if it was not you.

Converting later from memory is how a tidy year becomes an argument. A rate and a date written on the document, or in the index, settles it.

Handing it to an accountant

An accountant does not need your entire life. They need a complete, consistent set for the period, and a short list of questions. Before you hand over:

One folder per year, with the structure above.
Every invoice and credit note, numbered and sequential.
The bank statements for the full period, not just the busy months.
A list of anything unusual: a client who paid late, a currency conversion, a refund, a written-off invoice.
Your questions, written down. They are cheaper to answer in one batch.

If your records are digital, ask what format they prefer and whether they need originals for anything. Ten minutes of setup saves a week of back-and-forth.

Doing it inside the app

The easier your invoicing records are to produce, the less likely they are to be reconstructed from memory. Invoice Maker is a free iOS and Android app from Caractiv Tech that keeps your issued documents in one place: describe a job in text or by voice, review and correct the editable invoice or quote draft, then export a PDF with a consistent number and layout. Saved clients and reusable line items keep names and details stable across the year, paid, unpaid and partially paid invoices are recorded so you can see what is outstanding, and 34 currencies cover cross-border work. Manual invoices can be created offline; the AI features need a connection. Free to download, with Premium available by subscription.

It produces documents. It does not decide what you must keep, for how long, or in what format — that is a question for your jurisdiction and your accountant.

The record-keeping checklist

Invoice, proof of payment, agreement and cost records — all four, per transaction.
Retention period confirmed locally, with a margin.
Digital copies legible, complete and backed up off-device.
A shallow folder structure, date-first file names, one index per year.
A twenty-minute close every month.
Currency, rate and fee recorded wherever a conversion happened.
A clean handover package, with questions in writing.

None of this makes you better at tax. It makes you the client whose accountant answers in a day instead of a fortnight, and that is worth more than the time it costs.

Disclosure: I work on the invoicing app linked above, which is why I write about this. This article is general information, not tax, legal or accounting advice. Retention periods, accepted formats and documentation requirements vary by jurisdiction — confirm yours with a qualified professional.

Appendix: distribution assets (not part of the article body)

Social summaries

X: An invoice proves you billed. It doesn't prove you were paid. The record set is four things: invoice, proof of payment, the agreement, the costs. Keep them together, name files date-first, and do a twenty-minute close every month instead of a weekend in April.

LinkedIn: Record keeping is not paperwork for its own sake. It's the difference between a ten-minute handover and a two-week reconstruction. Four records per transaction — invoice, proof of payment, the agreement behind it, the costs — a shallow folder structure with date-first file names, and one index per year. Retention periods vary by jurisdiction, and they can restart when a return is amended or a dispute opens, so know your local minimum and add a margin.

Reddit (r/smallbusiness — answer-first, no link): The habit that pays off: a twenty-minute monthly close. Export the month's invoices, download the statement, match payments, file receipts, back up. Do it on the same day every month and April stops being a crisis. Also: an invoice alone doesn't prove payment — keep the bank line or remittance with it. And check your local retention rules rather than trusting a number from the internet.

Image suggestion

Concept: An overhead shot of a tidy desk: a laptop showing a year folder with subfolders, a single labelled document wallet, a phone scanning a receipt, and a handwritten index card reading "2026 — index". Beside it, deliberately out of focus, a cardboard box of loose paper.

Alt text: A tidy digital filing setup with a year folder and index card next to a box of unsorted paper receipts.

Notes: 1200×800 header; 1080×1080 for LinkedIn. Keep documents fictional and avoid readable totals or client names. The contrast between the folder and the shoebox is the whole image.

The Invoice Was Real. The Bank Details Weren't.

Karactif Tech — Wed, 11 Nov 2026 21:36:28 +0000

The Invoice Was Real. The Bank Details Weren't.

The email comes from your client's real address, references the right project, and asks you to update their bank details. There is a new AP contact, a note about a banking migration, and a PDF attached.

The address is real; the person is not. Someone is reading the thread, waiting for you to pay the wrong account.

Invoice fraud is rarely a dispute about work — it is a redirect. Small businesses are targeted because amounts are large relative to controls and one person handles sales, invoicing and payments.

The attack targets the payment, not the document

Two directions, both common:

Someone impersonates you to your client. A fake invoice with near-enough letterhead and someone else's bank details. The client pays it; you chase money that was never coming.

Someone impersonates your client to you. A "new" supplier, a changed account, an urgent request before month-end. You pay it; the real supplier waits.

Five patterns worth recognising

1. The bank-detail change. "We've moved banks, please update your records." Often from a lookalike domain — acme-studios.co for acme-studios.com — or the real mailbox after it was compromised. The tell is usually timing: a change request just before a large payment, with pressure to act fast.

2. The new supplier with urgent terms. A first invoice from an unpaid vendor, for a plausible service, with a discount for paying within 48 hours. Urgency is the mechanism; the discount is the bait.

3. The edited PDF. An attacker intercepts an invoice, changes the bank details and forwards it. Layout, number and signature can be intact; checking that the PDF "looks right" misses it.

4. The overpayment refund. A client "accidentally" overpays and asks you to refund the difference to another account. The original payment is later reversed as fraudulent, and your refund is gone.

5. The mailbox rule. Nobody asks for anything. Someone with access to your email adds a forwarding rule, and copies of your invoices leave the account. You find out when a client pays one you never sent.

The control that stops the usual attack

Verify the change on a channel you already trusted before the request arrived.

That means calling the number in your contract, CRM or the client's website — not the one in the signature or on the new PDF. If the request came by phone, call back on a number you already had. Attackers control the channel they use; that is the point.

Two rules strengthen it:

Ask for a second person. Above a threshold you set, confirm with two named client contacts, not one.
Wait. A genuine bank change survives 24 hours; a fraudulent one usually cannot, because the attacker needs you to move before anyone notices. Build the wait into your process.

Urgency is not a personality trait of accounts payable; it is pressure applied on purpose.

Put change control on bank details

Write it down, because a rule you remember is not a control:

Bank details never change by email alone. Any change requires a call to a known number and a written confirmation from a second contact.
Nothing changes on a Friday. Give every change one business day; fraudsters work weekends and month-end.
Keep a record. Date, who you spoke to, what number you called, what was confirmed. If it goes wrong, that record is the difference between a dispute and an investigation.
Match the name, not just the number. An account in a different legal name is a stop sign, even if the email says the company restructured.

For outbound payments, one person can initiate, but a second check should confirm new payees.

Make your invoices harder to alter

You cannot control what happens in transit, but you can make tampering visible:

Consistent, branded PDFs. A standard layout with logo, invoice number and contact block makes an edited copy easier to spot; hand-made documents are easier to fake.
A payment-verification line. "Our bank details never change by email — call us on [number] before paying." Only include this if it is true of how you operate.
Invoice numbers in a sequence the client can check. If 1187 arrives when they expected 1184, ask.
Send from an authenticated domain. SPF, DKIM and DMARC make it harder to send mail as you, and easier for client filters to flag a fake.
Keep what you sent. A PDF in your sent folder is evidence if a client claims theirs had different details.

Harden the accounts that send invoices

Your email account is the most valuable thing in your business. Treat it that way:

Two-factor authentication everywhere, especially email and your invoicing tool.
No shared logins. One password on a shared billing@ mailbox is a single point of failure.
Review forwarding rules and connected apps quarterly. If you did not create a rule, delete it and change your password.
Be suspicious of address changes. "Please resend to my new address" is a standard opening move; confirm by call before sending a PDF with bank details.

If it happens

Call your bank immediately. Ask for a recall; time is the whole game.
Preserve the evidence. Original messages with full headers, the PDF, the account details. Do not delete the thread.
Tell the client — if your mailbox or invoice was used, they need to know before they pay the wrong account.
Report it. Many places have a police or cybercrime route; your bank can tell you which applies.
Change credentials if your account may have been accessed, and recheck forwarding rules.

Doing it inside the app

A consistent document helps. Invoice Maker is a free iOS and Android app from Caractiv Tech that produces a standard PDF with your business details, invoice number and line items, from a text or voice description you review and correct before anything is final. Saved clients and reusable line items cut retyping, 34 currencies cover cross-border work, and 40+ Premium templates keep the layout uniform enough that a modified copy stands out. Manual invoicing works offline; the AI features need a connection. Free download, with Premium by subscription.

It does not verify bank details, and should not be asked to. That confirmation is a phone call to a number you already trust.

The five-minute fraud check

Before paying a new supplier, or acting on any bank-detail change:

Is this the first payment to this payee, or a change to an existing one?
Did the request arrive with urgency, a deadline, or a discount?
Does the domain match exactly — not just the display name?
Have I called a number I already had, and spoken to a person I can name?
Would a 24-hour wait break anything except the attacker's plan?

Most invoice fraud works because the request arrived at a busy moment and looked normal. The defence is not suspicion of everyone. It is one boring, repeatable step that a rushed week cannot skip.

Disclosure: I work on the invoicing app linked above, which is why I write about this. This is general information, not legal, accounting or security advice, and no process can eliminate fraud risk entirely.

Appendix: distribution assets (not part of the article body)

Social summaries

X: Invoice fraud doesn't dispute the work — it redirects the money. The tell is rarely the email address; it's the urgency. One rule blocks the common case: verify any bank-detail change by calling a number you already had, never the one in the email signature.

LinkedIn: Two directions, one weakness: someone impersonates you to your client with a fake invoice, or impersonates your client to you with new bank details. The invoice looks fine either way. What works is unglamorous change control — bank details never change by email alone, a callback to a number you already had, a 24-hour wait, and a second named contact above a threshold. Urgency isn't an AP personality trait; it's pressure applied on purpose.

Reddit (r/smallbusiness — answer-first, no link): The bank-detail change email is the one to watch, especially near month-end. It often comes from a lookalike domain or a compromised real mailbox, and the tell is urgency. Call a number you already have on file — not the one in the signature — and give every change a business day. If a client ever "overpays" and asks for a refund to a different account, stop and verify; that's a known pattern too.

Image suggestion

Concept: A close-up of an invoice PDF where the bank account line is slightly misaligned — the visual hint that it was edited — with a phone beside it showing a call to a saved contact named "Acme — AP (verified)". Muted tones, one red circle around the account number.

Alt text: An invoice with an altered bank details line next to a phone call to a verified accounts payable contact.

Notes: 1200×800 header; 1080×1080 for LinkedIn. Use fictional account numbers and no real bank branding. Avoid anything that looks like instructions for committing fraud — the image should read as detection, not tutorial.

Your Invoice Isn't Late. It's in a Quarantine Folder.

Karactif Tech — Wed, 11 Nov 2026 21:36:24 +0000

Your Invoice Isn't Late. It's in a Quarantine Folder.

You have the sent item. Timestamped, correct address, PDF attached. The client's accounts payable team says, politely and repeatedly, that they never received it. Both of you are telling the truth.

The invoice is sitting in a quarantine folder, or was rejected at a gateway, or was delivered to a mailbox nobody reads. It never reached a human, so from the client's side it does not exist. From your side it was sent, so you stopped worrying.

This is the least discussed failure mode in small business billing, and almost never about content.

An invoice is transactional mail that looks like marketing

An invoice has the profile of a bulk email: an attachment, links, a template, a sending domain the recipient has never corresponded with. Spam filters do not know you are billing for three days of electrical work. They score patterns.

The traits that make an invoice look professional — a designed layout, a logo, a payment button, a PDF — are also traits filters associate with campaigns. Your invoice is legitimate mail dressed as the thing filters are trained to stop.

Four things that get an invoice filtered

An unfamiliar sending domain. A domain registered last month has no history for a receiver to score you on. New domain, attachment, link, first contact: a textbook bulk profile, even for a single invoice to a single client.

Heavy or scanned attachments. Filters cannot read an image-only PDF, and many corporate gateways quarantine anything above roughly 10 MB; a phone-scanned invoice with a photo attached can cross that line unnoticed.

Shortened links and tracking pixels. A bit.ly link and an open-tracking pixel are marketing signals; three links and a tracking image read as a campaign, because structurally they are one.

The recipient's own rules. Corporate quarantine, external-sender banners, attachment stripping, upload-only portals. None of that is your reputation, and none of it is visible from your outbox.

SPF, DKIM and DMARC, without the acronym soup

These three records are how a receiving server decides whether mail claiming to be from your domain actually is. In plain terms:

SPF is a DNS record listing the servers allowed to send mail for your domain. Mail from an unlisted server fails the check.
DKIM attaches a cryptographic signature to each message, so the receiver can verify it was not altered in transit.
DMARC tells receivers what to do when SPF or DKIM fails, and can send you reports about who is sending as you.

If you send from a Gmail or Outlook mailbox, your provider authenticates their domain, not yours — which is why a bill from yourbusiness@gmail.com can read as less than a business.

If you send from your own domain through an app or SMTP service, someone has to publish those records — most hosts have a wizard, but it is a task, not a default. A new domain starts from zero regardless.

Write the email like a bill

The subject line is the first filter and the first impression:

Invoice 1042 — Acme Studios — due 15 April

Specific, boring, expected. Compare with INVOICE!! PAYMENT REQUIRED IMMEDIATELY — the shape of the mail everyone is told to delete. Skip emoji, "free" and urgency punctuation.

The body should be three or four sentences: invoice number, amount, due date, what you want done with it, and who to contact if something is wrong. Plain text. One link, or one attachment — not both plus a portal plus a "view online" button.

A real signature helps twice: it gives the client a phone number, and it makes the message look like correspondence from a business rather than an anonymous template.

The PDF is part of deliverability

Text-based, not a photo. A PDF exported from an invoicing app is readable and searchable; a scan of a printed page is a picture, and filters treat it accordingly.
Keep it small. Under 5 MB clears most limits. A 15 MB scan is a delivery risk.
No ZIP files. Compressed attachments are heavily filtered, and "invoice.zip" has a bad reputation for good reason.
No password unless agreed in advance. A password-protected PDF that requires a second email is a support ticket.
A descriptive file name. 2026-04-15_Acme_INV-1042.pdf is legible to humans and harmless to filters.

Confirm delivery instead of assuming

"Sent" is not "delivered", and "delivered" is not "read". Build a small confirmation habit:

Watch for bounces, and read them — a soft bounce may succeed on retry, a hard bounce never will.
Ask for one line: "Can you confirm you've got invoice 1042?" It is a normal thing to ask and it closes the loop.
If there is no confirmation in two working days, use a second channel — phone, portal or message — and mention that you also emailed it.
Ask regular clients to add your address to their safe senders or AP allowlist. Once is enough for most.

When the client's AP system is the wall

Larger clients often run an approval and intake process that sits in front of the inbox. Two things help more than any subject-line tweak:

Do vendor onboarding before the first invoice. Supplier forms, bank-detail verification, portal registration. It is slow and it is the actual gate.

Ask what format their system accepts. Some strip attachments entirely and require a portal upload; some accept a link; some take a PDF only under a size limit. One question to the AP contact saves weeks of resends.

Keep a named contact in accounts payable, not only your project contact. The project contact approves the work; AP releases the money, and they are the person whose filters you are fighting.

Doing it inside the app

If you would rather not build the document by hand, Invoice Maker produces the PDF for you. It is a free iOS and Android app from Caractiv Tech: describe a job by text or voice, review the editable invoice or quote draft, then export a clean, text-based PDF. Saved clients and reusable line items keep repeat invoices consistent, and 34 currencies and 40+ Premium templates cover branding. Manual invoicing works offline; AI drafting needs a connection. Free to download, with a Premium subscription.

It cannot guarantee your mail reaches the client's inbox — that depends on your domain, their filters and your attachment size. The app makes a good PDF; deliverability is infrastructure you own.

The pre-send deliverability check

Send from a domain you control, with SPF, DKIM and DMARC published.
Subject line names the invoice and the client, nothing else.
Plain-text body, one clear action, one link or one attachment.
PDF under 5 MB, text-based, no password, no ZIP.
A bounce check and one confirmation request within two working days.

None of this is glamorous. It is the difference between an invoice that exists and an invoice that gets paid.

Disclosure: I work on the invoicing app linked above, which is why I write about this. The advice is general and applies to any billing tool. This article is general information, not legal, accounting or financial advice.

Appendix: distribution assets (not part of the article body)

Social summaries

X: An invoice can be "sent" and still never exist. Quarantine folders, gateway rejections, attachment limits. The fix isn't a better invoice — it's sending domain authentication, a boring subject line, a text-based PDF under 5 MB, and asking for one line of confirmation.

LinkedIn: The least discussed invoicing failure: the invoice was sent, correctly, and never reached a human. Filters score patterns, not intentions — and an invoice has the profile of bulk mail (attachment, links, unfamiliar domain, template layout). Four things to fix: authenticate your sending domain (SPF/DKIM/DMARC), keep the PDF text-based and small, write a subject line that reads like a bill, and confirm delivery instead of assuming it.

Reddit (r/smallbusiness — answer-first, no link): Before you blame the client, check three things: your attachment size (many gateways quarantine over ~10 MB), whether your domain has SPF/DKIM/DMARC set up, and whether the mail actually went to the AP address they monitor. A phone-scanned PDF is the usual culprit — it's big and unreadable to filters. Ask for a one-line confirmation; "sent" only means it left your outbox.

Image suggestion

Concept: A split image: on the left, an outbox showing a sent invoice; on the right, a corporate mail gateway queue with one envelope held behind glass. Overlay text: "Sent ≠ delivered." Keep the palette muted; this is an infrastructure story.

Alt text: A sent invoice email beside a mail gateway holding the message in quarantine, illustrating that sent does not mean delivered.

Notes: 1200×800 for the header; 1080×1080 for LinkedIn. Avoid real company domains and logos; a generic envelope icon works better than a screenshot of any real email client.

Sending an Invoice Is a Delivery Problem, Not a Click

Karactif Tech — Wed, 11 Nov 2026 21:31:19 +0000

Sending an Invoice Is a Delivery Problem, Not a Click

The invoice was correct. The amount matched the quote, the PO was on it, the bank details were right. And it still took eleven days to get paid, because the client's assistant could not open the attachment, the resend went to an address nobody monitored, and the version that finally reached accounts payable was a screenshot.

Invoicing advice focuses on what goes on the document. Almost none of it covers how the document travels — where a surprising share of delays, and nearly all of the embarrassment, live.

Four ways an invoice reaches a client

Every delivery method is a trade-off between familiarity, control and proof. Pick deliberately.

PDF attachment. The default, and for good reason: it looks the same everywhere, and it is easy to forward to an approver or file. The trade-offs are size limits and filters — a heavy, image-based PDF can be rejected by a corporate mail gateway before a human ever sees it.

A hosted link. Useful when the file is large or the client's mail system is strict. But a link is only as private as its permissions: an "anyone with the link" share is one forward away from public.

The client's supplier portal. Slowest to set up, best for repeat business. Portals give you a receipt and a status field, which email never will. Use them where they exist, and keep the login findable in six months.

Paper. Still expected by some trades and older clients. Fine, as long as you keep a digital copy of exactly what you handed over.

Filenames are part of the invoice

The file name is the first thing a client sees and the last thing anyone thinks about. invoice.pdf is invisible in a downloads folder. invoice_final_FINAL2.pdf tells the client you are not sure which one is real.

A name that survives being forwarded twice:

2026-03-15_Acme-Studios_INV-1042.pdf

Date, client, invoice number: sortable, searchable, unambiguous, and still workable three folders deep in someone's downloads. Avoid spaces, and avoid "final" — the invoice number is the only version control you need.

Send it to a person, not to an address book entry

Autocomplete is how an invoice ends up at the wrong client. Two clients with similar names, a personal Gmail that used to be the contact, a former employee still on the thread — it happens. The invoice carries your rates, your bank details and your client's address. A misdirected one is a small data breach with a PDF attached.

Three habits, ten seconds:

Read the domain, not just the display name. @acme-studios.com and @acmestudios.co are different companies.
Check the CC line before sending. An invoice copied to a shared inbox is fine; copied to a competitor is not.
Use a reply-to address you actually monitor, so questions come back to a human.

If you bill a company, ask which AP address receives invoices; that inbox is usually where approvals start.

Links, group chats and the wrong kind of sharing

A shared link is convenient and quietly dangerous. "A link I can forward to my accountant" is a request for a document that will travel: match the permissions to the destination, and prefer an expiring link where the tool offers one.

Group chats are worse. An invoice dropped into a project channel is visible to people with no business seeing your day rate, and one screenshot from leaving the company. Send invoices one-to-one, and keep the payment details out of any chat that is not a direct message.

When the client says "I didn't get it"

Work through this in order, because the obvious answer is usually wrong:

Check your sent folder. Confirm the address and the attachment, not just that the message left.
Check the size. Over roughly 10 MB is at risk of silent rejection at the recipient's gateway — a scanned, image-heavy PDF gets there fast.
Ask for the correct inbox. "I didn't get it" often means "it went to the address I don't check."
Resend as a link, or split the file. A link sidesteps attachment filters entirely.
Send it from a second channel — the portal, or the client's phone — and say that you did.
Ask them to confirm receipt in one line. "Got it, thanks" is the cheapest delivery receipt you will ever get.

Do not simply resend the same file to the same address four times. If the first one did not arrive, the fourth will not either.

One invoice number, one document

Version control is where small businesses get into trouble. If the amount was wrong, you do not send INV-1042-v2.pdf — that creates two valid-looking documents with the same number and no audit trail.

The cleaner pattern: a credit note for the original, then a new invoice with a new number referencing it. For a cosmetic fix — a typo in the client's address — say so in the covering email and state that the total is unchanged. Either way, the number and the amount must never drift apart silently.

Make it readable on the device it will be read on

Plenty of invoices are opened on a phone, often by someone who is not sitting at a desk. That has consequences:

Use a text-based PDF, not a photograph of a printed page. Text can be searched, copied and read by accounting software; a photo cannot.
Keep the total visible without zooming. If the client has to pinch to find what they owe, expect a question.
Test the file on your own phone before you send the first invoice to a new client.
Avoid password-protecting the PDF unless the client asks. A password sent separately is a support ticket waiting to happen.

Doing it inside the app

If you would rather not assemble the file by hand, Invoice Maker builds the PDF for you. It is a free iOS and Android app from Caractiv Tech: describe the job in text or by voice, review the editable invoice or quote draft it produces, and export a clean PDF to share or print. Saved clients and reusable line items keep repeat invoices consistent, and 34 currencies and 40+ Premium templates cover branding. Manual invoicing works offline; the AI drafting needs a connection. Free to download, with a Premium subscription.

The delivery decisions above still apply. The app produces the document; you still choose who receives it, and how.

The five-point delivery check

Before any invoice leaves your outbox:

File name carries date, client and invoice number.
Recipient domain checked, CC list checked.
Attachment under the size your client's mail system will accept — or sent as a link.
Total and due date readable on a phone screen.
A sentence in the email that tells the client exactly what to do next: pay, forward to AP, or query a line.

None of that is invoicing theory. It is the difference between an invoice that is correct and an invoice that gets paid.

Disclosure: I work on the invoicing app linked above, which is why I write about this. The delivery advice is general and applies to any billing tool. This article is general information, not legal, accounting or financial advice.

Appendix: distribution assets (not part of the article body)

Social summaries

X: The invoice was correct and it still took 11 days — because the attachment wouldn't open, the resend went to an unmonitored inbox, and AP finally got a screenshot. Delivery is half of invoicing. Name the file with date + client + invoice number, check the domain, and confirm receipt in one line.

LinkedIn: Most invoice disputes start with delivery, not content. Four channels, four trade-offs: PDF attachment (familiar, but size limits and filters), hosted link (handy, but "anyone with the link" is public), supplier portal (slow to set up, gives you a receipt), paper (fine, as long as you keep a digital copy). Then the unglamorous habits: a file name that survives forwarding, checking the domain instead of the display name, and never sending v2 of an invoice with the same number.

Reddit (r/smallbusiness — answer-first, no link): If a client says they didn't get the invoice, don't just resend. Check the size first — anything over ~10 MB can be silently rejected at their gateway. Then ask which inbox AP actually monitors, because "didn't get it" usually means "it went to the address I don't read." A link sidesteps attachment filters entirely, and asking for a one-line "got it" is the cheapest delivery receipt there is.

Image suggestion

Concept: A laptop screen showing an email with a PDF attached, the file name 2026-03-15_Acme-Studios_INV-1042.pdf clearly visible, and a phone beside it displaying the same invoice legibly at full-page width. A sticky note reads "check domain — not display name."

Alt text: An invoice email with a clearly named PDF attachment, next to a phone showing the same invoice readable at full width.

Notes: 1200×800 header; crop to 1080×1080 for LinkedIn. Use a fictional client and a generic domain; do not show real bank details or a real invoice number.

The Invoice Was Approved. So Why Hasn't It Been Paid?

Karactif Tech — Wed, 11 Nov 2026 21:31:16 +0000

The Invoice Was Approved. So Why Hasn't It Been Paid?

You finished the work three weeks ago and sent the invoice the same day. Yesterday the client's project manager told you, cheerfully, that it was "approved last week." It still isn't in your account, and nobody seems to think anything is wrong.

Nothing is wrong, exactly. You have simply discovered that in most companies, "approved" is not a decision. It is a queue.

Approval is a process, not a decision

For a solo business, approval is one person saying yes. For a company with more than a handful of staff, it is a chain: the person who received the work confirms it, a budget holder confirms the spend, finance confirms the vendor exists and the bank details match, and then the payment waits for the next scheduled run.

Four steps, four people, four chances for your invoice to sit untouched in an inbox for a week. Your document cannot skip that chain, but it can be built to move through it.

Design the invoice for the person who has to approve it

Approvers are not reading your invoice for pleasure. They are trying to answer three questions:

Did we agree to this?
Is the amount right?
Which budget does it come from?

Every field that answers one of those questions removes a round trip. That means:

The purchase order number, quoted exactly, in the reference field and in the line description.
The project name or cost centre, spelled the way the client spells it.
The name of whoever signed off on the work, if the approver is someone else.
Line items that map to the quote, in the same order, at the same quantities.
Payment terms restated clearly, not buried in small print.

The most common cause of a slow invoice is not a dispute. It is a mismatch. Your invoice says "Consulting — Phase 2"; their PO says "Q3 advisory retainer." Now someone has to email someone to find out whether those are the same thing, and that email takes three days, and the person who sent it is on leave on Thursday.

Map the chain before you send, not after

Ask four questions at kickoff, or when the first invoice goes out:

Who receives invoices, and at what address? An accounts payable inbox is not the same as your day-to-day contact. If they have a supplier portal, use it from the start.
Who approves, and is there a threshold above which a second person has to sign?
When does the payment run happen — weekly, twice a month, on the 1st and 15th?
What reference do they need to route the invoice to the right cost centre?

It is an awkward email to send at kickoff, and it is worth more than any invoicing feature you will buy this year.

Status you can actually see

Most invoicing tools can tell you an invoice was sent. Almost none can tell you it was approved, because approval happens inside the client's systems, out of your view. Do not confuse "sent" or "viewed" with "in the payment queue."

So track the states you can verify yourself:

Sent — you have a copy and a timestamp.
Received — a human confirmed it, or the portal shows it in their system.
Approved — someone told you, ideally in writing.
Scheduled — it has a payment date.
Paid — the money is in the account.

The gap between 2 and 3 is where invoices go to die. That is the only gap worth a follow-up.

The follow-up that isn't nagging

"Just checking in" gets ignored because it asks the approver to do work without telling them what work. A better message does the work for them:

Subject: Invoice 1042 — anything needed to get this approved?

Hi Sam — invoice 1042 for the March retrofit ($4,800, PO 88-441) was delivered on the 3rd. Is anything missing on your side to move it to approval? Happy to reissue with a different reference if that helps.

It names the document, the amount, the PO, the delivery date, and one specific question. If the answer is "we need a revised PO reference," you find out on day three instead of day thirteen.

Cadence: once three to five days after delivery, once around the payment-run boundary, then a firm note. Not daily. Daily is how you become the supplier people route to voicemail.

When the chain jams

Three jams explain a lot of late payments:

Missing or wrong PO. The invoice is unapprovable by rule, no matter how correct the work was. Ask for the correct PO in writing and reissue. Depending on their rules, that may mean a corrected reference or a credit note plus a new invoice. Do not invent a PO to get past a form.

A new AP system. Companies migrate to portals with no announcement. If your invoice went to an address that no longer accepts mail, you may not get a bounce, because the mailbox still exists and still swallows everything. Ask your contact to confirm the current submission route rather than resending into the void.

Approver on leave. There is nothing to do but know about it — which is why you ask about the chain at kickoff, before you need the backup.

The pre-send checklist

Before you send any invoice over a few hundred dollars:

PO number present and matching the client's record.
Legal entity name and address exactly as their vendor file has them.
Line items in quote order, same quantities, same descriptions.
Currency code written, not just a symbol.
The right inbox, not your contact's personal address.
Payment terms and a specific due date.

Two minutes, fewer delays.

Doing it inside the app

If you want the invoice to carry the right references without retyping them every month, Invoice Maker is a free iOS and Android app from Caractiv Tech built around repeatable billing. You can describe a job in text or by voice and get an editable invoice or quote draft to review and correct before anything is final. Saved clients keep the entity name and address consistent; reusable line items mean a repeat invoice maps to the original quote instead of drifting from it. It exports PDFs, tracks paid, unpaid and partially paid invoices, supports 34 currencies and 40+ Premium templates, and creates documents manually while offline — AI drafting needs a connection. Free to download, with a subscription for Premium.

One honest limit: it tracks what you have been paid, not what the client has approved. No invoicing app can see that. That part stays your job.

What actually changes

You cannot accelerate someone else's approval process. You can stop adding friction to it. The invoice that gets paid on time is rarely the prettiest one. It is the one that answers the approver's three questions without them having to ask, and arrives at the address where approvals actually happen.

Disclosure: I work on the invoicing app linked above, which is why I write about this. The workflow advice is general and applies to any billing tool. This article is general information, not legal, accounting or financial advice.

Appendix: distribution assets (not part of the article body)

Social summaries

X: "Approved" is not a decision. In most companies it's a queue: receiver confirms, budget holder confirms, finance confirms, then it waits for the payment run. Your invoice can't skip the chain, but it can be built to pass through it — PO number, cost centre, line items in quote order.

LinkedIn: Late payment is usually an approval-chain problem, not a billing problem. Four steps, four people, four chances for your invoice to sit for a week. The fix is unglamorous: ask at kickoff who receives invoices, who approves, what the threshold is, and when the payment run happens. Then build the document for the approver's three questions — did we agree to this, is the amount right, which budget. The gap between "received" and "approved" is where invoices die, and it's the only gap worth chasing.

Reddit (r/freelance — answer-first, no link): The thing nobody tells you: "approved" often just means one person signed off, not that finance has it. Ask three questions before your first invoice — who receives them, who approves above what threshold, and when the payment run is. Then put the PO number and cost centre on the document. Many "late payments" are invoices that were never routable in the first place.

Image suggestion

Concept: A clean overhead shot of a desk with a printed invoice, a sticky note reading "PO 88-441?", a coffee cup, and a laptop showing an email thread with the subject line "Invoice 1042 — anything needed to get this approved?" The invoice has one field circled in red: the reference number.

Alt text: An invoice on a desk with the purchase order reference circled, next to an email asking whether anything is missing for approval.

Notes: 1200×800 for a blog header; 1080×1080 crop for LinkedIn. Use a fictional client name and blur any account numbers. Keep the palette neutral — this is a process story, not a product shot.

AI Invoice Tools: A Safety Checklist Before You Let One Draft Your Invoices

Karactif Tech — Wed, 11 Nov 2026 21:26:11 +0000

AI Invoice Tools: A Safety Checklist Before You Let One Draft Your Invoices

A contractor I know dictates job notes in the van: "three hours on the valve, second visit, plus the parts from Thursday." One app turned that into a clean draft in seconds — and also carried a rate from a job in March that he had since raised, plus a goodwill discount nobody had offered. The total looked plausible, which is why he sent it.

He caught it two days later, when the client paid the lower amount and thanked him. Nothing catastrophic. But the failure mode scales: the more fluent the draft, the less likely anyone reads it closely.

This is a checklist, not a warning. Used properly, the tool removes twenty tedious minutes from every invoice. The point is to keep the review, not skip the tool.

What AI is good at here, and what it is not

Good at: turning unstructured description into structured rows. Pulling quantities and dates out of speech. Drafting a line description in professional language when you would otherwise write "stuff, Tuesday." Filling the boring fields so you start at eighty percent instead of zero.

Not good at: knowing your rates. Knowing what you agreed to with this specific client. Applying the right tax treatment. Deciding what is billable. Arithmetic you have not checked.

That split is the safety model: AI is a fast first draft, you are the approver. A tool that blurs the line is not saving work, it is moving it to after you have already sent something.

Seven failure modes

Invented line items. A plausible extra you never supplied, generated because the description implied more than it said.
Stale rates. A rate carried from an earlier draft, or from a client record you forgot to update.
Wrong quantity. "Three hours" becoming 3 units, or 3 days, depending on the default unit.
Currency confusion. The client's address sets the currency, not your agreement.
Default tax fields. A rate populated because the field exists, not because it applies.
Wrong client record. Two similar names, and the draft picks the one with the old address.
The confidence problem. Fluent prose suppresses the small doubt that would otherwise make you check.

The ten-point review, money first

Order matters: most people read the wording and skim the numbers, because wording is easier to have an opinion about. Reverse it.

Client legal name and address — the entity that will pay, not the person you spoke to.
Invoice number and date — unique, not a duplicate of something already issued.
Period covered — the dates of the work, not just the issue date.
Currency — correct and consistent across every line.
Each line: description, quantity, unit, rate. Quantity is where drafts go wrong most often.
Recompute the subtotal and total yourself. Calculator or by hand, not by re-reading.
Tax fields against your own records, not the draft's guess.
Payment instructions — are they yours, current, and complete?
Terms and due date — matching what you agreed, including any deposit paid.
Attachments and references — the PO number, the photo, the timesheet the client expects.

Then read the words: accurate, specific, and free of anything you would not say to the client's face.

Human confirmation is a workflow, not a checkbox

"Review before sending" fails when it is a single tap on the same screen that generated the draft. Four habits make it real:

Two passes, separate. Numbers pass, then words pass. Not one scroll.
Read the total aloud. It sounds silly and catches transposed digits faster than reading silently.
Keep the source. Retain the voice note or paragraph that produced the draft. When a client disputes a line, that is your evidence of what you actually said.
Sample audit monthly. Re-check three sent invoices against their source text. If you find nothing in three months, you are either very good or not looking.

The strongest version is a tool that treats the draft as a draft: it proposes, you edit, nothing leaves until you confirm. Worth checking before you trust any of them.

Questions to ask about your data

Invoice text carries client names, addresses, rates and sometimes bank details. Before you dictate, ask:

What leaves the device, and what stays on it?
Is the text stored, and for how long?
Is it used to improve or train models? Can you opt out?
Can you delete a draft and its source permanently?
Is the connection encrypted, and who inside the vendor can see content?

Ask in writing. A vendor who cannot answer clearly has answered.

Connectivity realism

Drafting usually needs a connection, so the feature disappears in a basement, elevator shaft or rural job. That is an architecture, not a scandal. Know which half of your workflow survives without signal — usually manual entry, PDF export and payment status — and keep that path familiar.

If a tool's offline story is "the app opens," test it before you rely on it: create, edit and export with the network off.

Put it in writing

Five lines, pinned where you invoice:

Draft → save the source → numbers pass → words pass → total check → send → log.

It takes ten minutes to write and is the difference between a tool that speeds you up and one that quietly costs you money.

The one-sentence test

Before you send anything a machine drafted: if a client asked me to justify every number on this invoice, could I? If not, do not send it. Fix it by hand or regenerate — either is faster than the conversation you are about to have.

Where this one sits

Invoice Maker is a free-to-download iOS and Android app from Caractiv Tech built around the draft-then-confirm pattern: describe the work in plain text or by voice, get an editable invoice or estimate, then review and correct before anything is final. It also handles PDF export, paid/partial/unpaid tracking per client, saved clients and items, and 34 currencies, with 40+ Premium templates on the branding side. The drafting needs a connection; manual invoicing works offline. It does not know your rates, your agreements or your tax obligations — no drafting tool does — so the checklist above still applies, including to us.

The short version

AI is excellent at the blank page and unreliable at the facts. Let it draft, keep the source, check money before words, recompute the total yourself, and treat confirmation as a step rather than a formality. The tool is not the risk; the unread draft is.

Disclosure: I work on the app linked above, so this checklist is written by someone with an interest in you trusting the category — carefully. This is general information, not accounting, tax, or legal advice; confirm your own obligations with a qualified professional.

Appendix: distribution assets (not part of the article body)

Social summaries

AI is excellent at the blank page and unreliable at the facts.

Check money before words: client entity, currency, quantity per line, then recompute the total yourself. Keep the voice note that produced the draft — it's your evidence when a line gets disputed.

LinkedIn:

A contractor dictated job notes in his van. The app produced a clean invoice in four seconds — with a rate from March and a discount nobody offered. He sent it, because it looked plausible. That's the whole risk in one story: fluency suppresses the doubt that would make you check.

What works is unglamorous. Two separate passes (numbers first, then wording). Read the total aloud. Keep the source text as an audit trail. Re-check three sent invoices a month against their originals. And ask any vendor, in writing, what happens to your client data.

The tool isn't the risk. The unread draft is.

Reddit (r/smallbusiness, r/freelance — answer-first, no link in the post body):

The failure I've seen with AI-drafted invoices isn't wild hallucinations, it's small carry-over errors: a rate from an old job, a quantity that became 3 units when you meant 3 hours, a currency picked from the client's address. All plausible enough to send. Fix that's worked for me: check the numbers before reading the wording, and recompute the total with a calculator instead of re-reading it. Also keep the original voice note — when a client queries a line, "here's what I dictated" ends the conversation fast.

Image suggestion

Close-up of a phone on a workbench showing an invoice draft with two lines highlighted in amber, beside a notepad with a hand-written seven-step checklist and a calculator showing a total. Work gloves at the edge of frame, no readable client data. Alt text: "Invoice draft on a phone with flagged lines beside a hand-written review checklist and calculator."

How to Compare Mobile Invoice Apps: A Buyer's Checklist, Not a Ratings Table

Karactif Tech — Wed, 11 Nov 2026 21:26:07 +0000

How to Compare Mobile Invoice Apps: A Buyer's Checklist, Not a Ratings Table

I once installed the highest-rated invoicing app in my store, spent twenty minutes setting up a client, then found that PDF export was a paid feature and my billing currency was not listed. The rating was probably deserved. It just measured a different job than mine.

Ratings tables compress a hundred jobs into one number, and none of the reviews were written by someone billing in your currency, from your phone, with your tolerance for fiddly forms.

The better approach: decide what you need first, then test each candidate against it — in minutes, not weeks.

Why ratings tables mislead

Three structural reasons:

Ratings measure the first week. People review after onboarding, when the app is new and the invoice is their first. Month three — the partial payment, the credit note, the accidental duplicate — is where tools get judged, and almost nobody goes back to write that review.

Reviewers are not you. A 4.6 rating says nothing about your currency, your tax fields, or your industry's line items.

Feature lists are marketing. Every app claims invoicing, tracking and templates. What separates them is behavior under bad conditions: no signal, wrong client, half a payment, a PDF that must look right in print.

Pricing and features change constantly, so check anything specific — including here — against the vendor's page on the day you decide.

Start with the job, not the feature list

Most people over-buy because they compare feature matrices instead of tasks. Rank these three for yourself:

Billing on site — you finish work and want the invoice out before you drive away.
Billing on a cycle — retainers, subscriptions, monthly service.
Billing across borders — a client in another currency, or several.

If job one is your priority, offline behavior and time-to-first-invoice dominate everything else; if job three matters, currencies and document formatting do. An app can be excellent and still wrong for you.

The twelve dimensions that decide it

Time to a sendable invoice. From opening the app to a PDF you would actually send. If the first try takes ten minutes, so will every one after it.
Offline behavior. What exactly works without signal? "Works offline" often means "opens offline."
AI assistance and its boundaries. What does it draft, and do you confirm before anything is final?
Document output. PDF quality, branding, template choice, how it prints.
Status tracking. Paid, unpaid, partial, overdue — per invoice and per client.
Reuse. Saved clients, saved items, duplicating last month's invoice.
Currencies. How many, whether the rate is editable, whether amounts read unambiguously.
Data portability. Export format — can you take your history with you?
Platform coverage. iOS and Android both, tablet layouts, a web view for desk work.
Pricing model. Free tier limits, subscription, per-document caps, seat costs.
Support. Can you find an answer at 9pm without emailing anyone?
Terms and data handling. What happens to invoice content, and who can see it.

The three archetypes

Almost every option is one of three shapes.

Full accounting suites — QuickBooks, Xero, Zoho Books and similar. The invoice is a by-product of a double-entry system: excellent if you need books, bank feeds and tax reporting in one place, heavier to set up than billing alone requires.

Freelancer invoicing apps — Invoice Simple, Bookipi and others. Fast to a first invoice, phone-first, with templates and status tracking; lighter on accounting, which is fine until you need accounts.

Template and PDF tools — Word, Excel, Canva and the free template economy around them. Maximum control, minimum cost, no tracking or reuse: perfect under ten invoices a month, a chore above it.

A fifteen-minute trial that beats a week of reviews

Install it, then do this with a real invoice:

Add a client with a tax number and a billing email.
Create a four-line invoice, including one line you would normally describe in a sentence.
Mark a partial payment against it. Check the remaining balance is right.
Turn off Wi-Fi and mobile data. Try to create and export an invoice.
Export the PDF, then view it at 70% scale.
Change the currency and check the total still reads correctly.
Duplicate the invoice, then find the data export.

Score each step 1–5; two apps tested this way beat fifty reviews.

What "free" usually means

Free to download and free to use differ, and both are legitimate — you just need to know which you are getting. Look at the shape of the pricing:

Is there a document limit per month, or a watermark on exports?
Which features are gated — branding, templates, currencies, multiple clients?
What happens to your invoices if you stop paying? Can you still export them?

For a solo operator, charging for branding and templates while invoicing stays free is usually a better deal than charging per document.

Red flags worth walking away from

No data export, or an export that produces something unusable.
AI that finalizes a document without a review step.
A currency list you cannot extend, or totals that do not recompute when you change it.
No partial payment support, in a tool that claims to track payments.
"Unlimited" with no stated cap anywhere in the docs.
Evidence that consists only of star ratings and screenshots of the marketing site.

Where this one sits

Full disclosure: I work on one of these, so treat the above as the framework and this as the placement.

Invoice Maker is a free-to-download iOS and Android app from Caractiv Tech aimed at on-site and small-service work: describe the job in text or by voice and it drafts an invoice or estimate you edit and confirm before anything is final. It covers PDF output, paid/partial/unpaid tracking per client, saved clients and items, 34 currencies, and 40+ Premium templates for branding. Manual invoicing works offline; drafting needs a connection. Not an accounting suite — for double-entry books, the archetypes above tell you what to look at.

Run the fifteen-minute trial on it as you would on anything else. If it fails step four or seven, that is a real answer — more useful than a rating.

The short version

Ratings measure day one; your workflow lives in month three. Rank your three jobs, compare on the twelve dimensions, test two apps with a real invoice in fifteen minutes, and check what "free" includes. The right app makes the second invoice faster than the first.

Disclosure: I work on the app linked above, so this comparison is written from inside one of the options rather than from a neutral review desk. This is general information, not accounting, tax, or legal advice; check current features, pricing and terms with each vendor before you commit.

Appendix: distribution assets (not part of the article body)

Social summaries

App store ratings measure the first week. Your billing lives in month three — the partial payment, the credit note, the duplicate you made by accident.

Compare on: time to a sendable invoice, what "offline" actually means, and whether you can get your data out.

LinkedIn:

I once installed the best-rated invoicing app in my store, set up a client, and found PDF export was paid and my billing currency was missing. The rating was probably deserved. It just measured a different job than mine.

Ratings compress a hundred workflows into one number, and reviews are mostly written in week one. A better process: rank your three jobs (on-site billing, cycle billing, cross-border), compare on twelve dimensions, then test two candidates with a real invoice in fifteen minutes — including one step with the network switched off.

What you learn from step four is worth more than any star average.

Reddit (r/freelance, r/smallbusiness — answer-first, no link in the post body):

The test that has saved me the most time: install the app, then do one real invoice with a partial payment on it, then turn off data and try to export a PDF. Plenty of apps that advertise offline mode only open offline — they can't create or export. Second test: find the data export before you enter real client data, not after.

Image suggestion

A phone on a desk showing a short invoice with a "partially paid" badge, next to a handwritten scoring card with seven numbered trial steps and small checkmarks. A second phone lies face down beside it, screen off. Clean daylight, no readable client details. Alt text: "Phone showing a partially paid invoice beside a handwritten app trial scoring card."