Check If Your Invoice Was Opened Before You Chase It

You sent an invoice eight days ago on Net 30 terms. It is not overdue yet, but you want to nudge. Before you write a single word, answer one question: did the client actually open it? The answer changes everything about your next move. A polite reminder to someone who has never seen the invoice is a waste of a message. A polite reminder to someone who opened it twice and went quiet is a different conversation entirely.

Here is the sequence a careful sender runs before following up, and how the view status decides both timing and tone.

Step one: open the invoice and read the status

Before drafting anything, look at where the invoice sits. In JupiterInvoice, the lifecycle runs Draft, Sent, Viewed, Change Requested, Approved, Locked. If the status still says Sent, the private link has not been opened. If it says Viewed, someone loaded it. That single distinction tells you which of two problems you have: a delivery problem or a decision problem.

The reason this works is that the recipient opens a link, not a PDF attachment. When they load it, that event is recorded. You can see whether the customer actually opened it without asking them, which means you never have to send the awkward "just checking you received this" email that clients ignore.

Step two: if it was never opened, fix delivery first

A status stuck on Sent almost always means the message did not land, not that the client is stalling. The invoice email went to spam, got clipped by Gmail, or hit an inbox nobody checks. Chasing for payment here makes you look pushy about money the client does not yet know they owe.

So your follow up is not a payment reminder. It is a delivery check. Resend the link through a channel you know they read, a direct reply to a recent thread, or a Slack message if you have one. Keep it short: "Sent your invoice on the 3rd, here is the link again in case it got buried." If this keeps happening, the underlying issue is worth solving properly, and the reasons an invoice ends up in spam are fixable.

Two things help before you even hit send. Confirming the invoice looks complete cuts down on silent rejections, so run through a quick check before sending. And if you suspect the client never got the original, the practical steps for handling "I never received it" are worth knowing in advance rather than improvising.

Step three: if it was opened, read the timing signal

A Viewed status changes your job. The client has seen the amount, the terms, and the due date. Silence now is a choice, not an accident. But do not assume the worst. There are three common patterns, and each one calls for a different message.

Opened once, right after you sent it, then nothing. This is normal. The invoice landed, someone glanced at it, and it is sitting in a queue waiting for the due date. If you are still inside terms, do nothing yet. Chasing a Net 30 invoice on day eight when it has been calmly received just trains the client to see your reminders as noise.

Opened several times, or opened recently after a gap. Repeat views usually mean the invoice is moving through an internal process, forwarded to a manager, checked against a purchase order, or sitting with accounts payable. This is a good moment to be helpful rather than impatient. Ask if they need anything to process it: a PO number, a different billing entity, an accounts payable contact. Since the recipient can add those details on the invoice themselves, you are pointing them at a fix, not creating more back and forth.

Opened once, then the due date passed with no approval and no change request. Now you follow up on payment directly, and the tone can firm up because you know they saw it. "The invoice we sent on the 3rd is now past its due date. Can you confirm when payment will go out?" You are on solid ground because the view history removes the excuse.

Step four: match the message to what you know

The whole point of checking views first is that you stop sending generic reminders. Compare the two:

If you would rather not write these from scratch, the follow-up email generator gives you a starting draft you can adjust to the situation. And when an invoice has been opened but not opened, a fuller plan for the unopened case walks through the delivery angle in more detail.

Step five: escalate only when the signal justifies it

Escalation should track the evidence. An unviewed invoice never justifies a stern letter, because the client has done nothing wrong yet. A viewed and overdue invoice does justify escalation, and you can raise late fees or a payment deadline knowing the client cannot claim ignorance. If late payment is a pattern with this client, the deeper causes behind Net 30 invoices that pay late are worth reading, because view analytics often reveal the invoice was seen on day one and simply parked.

The habit is simple. Before you follow up, look at the status. Let the view history tell you whether you have a delivery problem or a decision problem, then write the message that problem actually needs. When you are ready to put this into practice, create your next invoice and watch the status move from Sent to Viewed before you decide anything.