Get Paid Faster: Client Portals, QR Codes & Partial Pay

Sending an invoice is the easy part. Almost any tool can generate a PDF with a total and a due date on it. The harder problem — the one that actually determines whether you get paid on time — is everything that happens after you hit send: whether the client can actually find and open the invoice, whether they can pay from whatever device they happen to have in hand, and whether there's any real consequence if the due date slides by unnoticed.

A cluster of features in Invoice Generator exists specifically to address that second half of the problem. None of them make the invoice itself prettier. All of them are aimed at shortening the distance between "invoice sent" and "invoice paid."

The Client Portal: A Link Instead of an Attachment

Every invoice can be shared as a hosted link rather than (or alongside) a PDF attachment. The client opens the link and sees a clean, read-only view of the invoice — no account, login, or app download required on their end.

This sounds like a minor convenience until you think through what actually happens to a PDF attachment in practice. It gets downloaded once, maybe renamed something like "invoice_final_v2.pdf," and then buried in a downloads folder or an email thread within a few days. If the client wants to reference it again — to check the amount, confirm the due date, or forward it to their bookkeeper — they're searching their inbox for an email from three weeks ago.

A link doesn't have that problem. It can be reshared instantly in a text message, a Slack DM, or a follow-up email without re-attaching anything, and it always shows the current state of the invoice — which matters if a partial payment has since been applied, because the client sees an updated balance rather than a static PDF that's gone stale.

Practically, this also removes a common client excuse for delayed payment: "I couldn't find the invoice." A link that can be resent in ten seconds closes that excuse off almost entirely.

QR Codes: Built for Phones, Not Desktops

For saved invoices, the generated PDF can embed a scan-to-view QR code that links straight to that same shareable client-portal view. It's a small addition, but it solves a specific, common scenario: a client who's reviewing invoices on their phone, or who received a printed copy, and doesn't want to type a URL or search their email to look something up.

Scanning takes them directly to the live version of the invoice — the same one reflected in the client portal, including any partial payments already applied. It's worth noting this only applies to saved invoices tied to an account; a one-off guest invoice generated without saving doesn't have a persistent link to point the QR code at, since there's no hosted record to scan through to.

Partial and Deposit Payments: A Status That Matches Reality

A lot of invoicing tools only support two states: paid or unpaid. That binary breaks down constantly in real client work — a 50% deposit up front with the balance due on delivery, a client who pays most of an invoice and promises the remainder next week, a large project billed in stages where payments trickle in over time.

Invoice Generator supports a genuine partially_paid status, derived from the actual payment records logged against the invoice rather than a manual flag you have to remember to set. If a client pays half of a $4,000 invoice, the invoice reflects a $2,000 balance and a partially-paid state automatically — both on your end and on the client-facing portal view — instead of you tracking the remainder separately in a notebook or spreadsheet.

This matters for more than bookkeeping accuracy. It means a client checking the portal link sees an honest, current balance rather than a total that no longer reflects what they actually owe, which is exactly the kind of small mismatch that turns into a "wait, I thought I already paid this" conversation later.

Automatic Late Fees: A Policy That Enforces Itself

Late fee policies are common in freelance and agency contracts, and almost universally unenforced in practice — not because the freelancer doesn't want to charge them, but because manually noticing an overdue invoice, calculating the fee, and adding it to the balance is one more task competing for attention against actual client work.

Each workspace can define a late fee rule — either a flat amount or a percentage of the invoice total — and a background process applies it automatically, once per invoice, after the due date passes. You don't have to notice the invoice is overdue for the fee to apply; the system does.

This changes the practical value of having a late fee policy at all. A late fee clause that's stated in a contract but never actually enforced trains clients, over time, to treat your due dates as soft suggestions. A late fee that reliably shows up on the balance the moment an invoice goes overdue is one of the more effective, low-effort ways to make due dates mean something — our guide on late fee policies clients actually respect covers how to set the policy itself up correctly, including where percentage caps and disclosure rules vary by state.

A Concrete Example: Flat vs. Percentage Late Fees

Choosing between a flat fee and a percentage isn't purely cosmetic — the two behave very differently depending on invoice size, and it's worth thinking through before setting the workspace-wide default.

A flat $25 late fee is easy for a client to understand and predict, and it works fine on invoices in the low hundreds to low thousands of dollars, where $25 is a noticeable but proportionate nudge. On a $600 invoice, that's roughly a 4% penalty — enough to matter, not enough to feel punitive. On a $15,000 project invoice, the same $25 flat fee is close to meaningless as a deterrent; a client who's forty-five days late on a five-figure invoice is unlikely to be moved by a charge that small.

A percentage-based fee — commonly 1.5% to 5% per month, though this should always be checked against state-specific caps — scales with the invoice instead, which makes it the more sensible default for anyone whose invoice sizes vary widely across clients or projects. The tradeoff is that it's slightly less predictable for the client to eyeball in advance, though the portal view showing the updated balance in real time largely offsets that, since there's never any ambiguity about the actual current total owed.

Most freelancers and small agencies end up choosing a percentage as the workspace default and treating a flat fee as the exception for a specific recurring low-dollar client relationship where a percentage would round down to something trivial anyway.

Recording and Reconciling Payments

Not every payment arrives through the same channel, and Invoice Generator doesn't assume it will. Payments can be logged manually against a specific invoice, imported in bulk from a CSV export (useful if you're pulling a batch of transactions from a bank statement or payment processor), and matched — reconciled — against the outstanding invoices they correspond to.

This is what keeps invoice statuses trustworthy over time. If you're getting paid through a mix of bank transfers, checks, and card payments handled outside the platform, reconciliation is the step that turns "I think this got paid" into a confirmed, dated payment record tied to the correct invoice — which is exactly the kind of record an accountant or a future dispute will need.

Putting the Pieces Together: A Full Payment Lifecycle

Here's how these features typically play out across a single invoice, end to end:

1. You send an invoice with a link to the client portal, optionally with a deposit due up front.
2. The client opens the link — no login required — and sees the current balance.
3. They pay the deposit; you log it (or it's reconciled from an import), and the invoice status updates to partially paid automatically.
4. As the due date for the remaining balance approaches, the client can reopen the same link — or scan the QR code on a printed or forwarded copy — to check what's still owed.
5. If the due date passes unpaid, the configured late fee applies automatically, updating the balance without you having to notice or intervene.
6. The final payment comes in, gets reconciled, and the invoice closes out — with a payment history you can hand to an accountant without reconstructing anything from memory.

None of these features is complicated on its own. What makes them effective together is that they remove the manual steps — checking, remembering, calculating, re-explaining — that usually stand between an invoice going out and the money actually landing in your account.

Where to Start

If you're only using the free PDF invoice generator today, the highest-leverage next step is turning on the client portal link for your next invoice instead of sending a plain PDF attachment. It costs nothing to try, and it's the feature most of the others — QR codes, live balance updates, late fees — are built directly on top of.

None of these features individually guarantee faster payment — a client determined to pay late will usually find a reason regardless of how convenient the invoice is to view. What they do reliably remove is friction that has nothing to do with a client's willingness to pay: not being able to find the invoice, not being sure of the current balance after a partial payment, or a late fee policy that exists in a contract but never actually shows up on a bill. Removing that friction is a smaller, more mundane win than it sounds, but it compounds across every invoice you send, month after month, in a way that's easy to underestimate from a single invoice in isolation.