DEV Community

Karactif Tech
Karactif Tech

Posted on

Sending an Invoice Is a Delivery Problem, Not a Click

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:

  1. Check your sent folder. Confirm the address and the attachment, not just that the message left.
  2. 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.
  3. Ask for the correct inbox. "I didn't get it" often means "it went to the address I don't check."
  4. Resend as a link, or split the file. A link sidesteps attachment filters entirely.
  5. Send it from a second channel — the portal, or the client's phone — and say that you did.
  6. 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:

  1. File name carries date, client and invoice number.
  2. Recipient domain checked, CC list checked.
  3. Attachment under the size your client's mail system will accept — or sent as a link.
  4. Total and due date readable on a phone screen.
  5. 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.

Top comments (0)