The From line does half the work

A client owes you $8,400 on an invoice you sent six weeks ago. You can ask for it two ways. One arrives from billing@somepaymentapp.io with a logo header and a button. The other arrives from you, in the same thread as the original invoice, with a sentence about the project you just wrapped.

The second one gets answered. Not because it's cleverer — because of who it's from.

An AP inbox is a filter before it's a person

The person paying your invoice at a 200-seat client handles a few hundred emails a week. They triage by sender first, subject second, body maybe. Anything that looks like a vendor portal notification gets a glance and a later. Anything from a human they've corresponded with gets opened.

You already have that standing. You've been in their inbox for a year — kickoff notes, scope questions, the invoice itself. Sending the follow-up from somewhere else throws that away and starts from zero.

Deliverability is the boring reason, and the biggest one

Shared sending domains carry other people's reputation. If a hundred other senders are using the same infrastructure and some of them are careless, you inherit their score. Google and Microsoft both weight sender history with that specific recipient domain — a signal you have and a third-party sender doesn't.

Practical version:

• Get SPF, DKIM and DMARC right on your primary domain. If you're not sure, check with a DMARC report tool before you send anything that matters.
• Don't spin up invoices.youragency.com to keep billing separate. A fresh subdomain inherits none of your reputation and needs its own warmup period.
• Send from the same domain your project email comes from. That's the whole point.

Reply in the thread that already exists

The original invoice email is sitting in their mailbox. Reply to it rather than starting fresh. The attachment, the PO number, the approval trail — all of it stays in one place, so when AP forwards the message to the project manager for sign-off, the context goes with it.

This matters more than it sounds. Most late invoices aren't refusals. They're stuck at an internal step, and a message with the full history attached unsticks them faster than a message that makes someone go find the original.

Decide who the From line is

• Under about fifteen people: the person who signed the contract. That's the name with weight.
• Bigger than that: accounts@yourdomain is fine, but set a human display name and make sure a real person watches it.
• Never no-reply@. It says you don't want the conversation, and the conversation is where the money is.

Write like you'd write to them in person

Short. One ask. Put the invoice number, amount and due date in the body — not only in the attached PDF, because half of them are reading on a phone.

Then ask a question that routes:

Is #1042 waiting on a PO number, or is it in the run for the 15th?

That's easier to answer than "please remit." It gives them two doors, and whichever one they pick tells you exactly what to do next.

A ladder that stays in your voice

1. Day 3 past due — same thread, two lines, friendly.
2. Day 10 — same thread, cc the project contact. AP now has someone internal to ping.
3. Day 21 — new thread, invoice number in the subject, offer to split it.
4. Day 35 — owner to owner. Direct, no edge. Still from your mailbox.

Every rung is the same person writing. That consistency is what makes rung four land.

Payment plans are a conversation

When a client says cash is tight this month, the useful move is usually to split the invoice — three payments over six weeks, dates written down, confirmed in writing. Clients say yes to that far more often than they say yes to the full amount today. But it only happens if the reply lands somewhere a human can negotiate. A one-way sender kills that before it starts.

So where does software actually help?

Not as the sender. As the thing that watches the aging report, drafts the next note in your voice, reads what comes back, works out whether it's a promise, a question or a problem, and queues the right follow-up.

That's how FetchDue works. It chases from your own mailbox, in the existing thread, and you approve every send before it goes. Your client sees an email from you. You see a queue that never forgets an invoice.

The From line is the cheapest trust you own. Don't hand it to a tool.