Guide · 6-minute read
Give every invoice one clear place to check and pay.
Payment follow-up slows down when the invoice, timesheet, receipts, bank instructions, and status are scattered across an email thread. A client portal or stable invoice page creates one current destination without making private billing pages searchable.
Last updated August 18, 2026
Make the invoice link the source of truth
The client should be able to open the sent invoice, download its PDF, review the balance and due date, inspect permitted supporting documents, and see the payment methods you chose for that invoice. Email remains the delivery channel; the hosted page is the stable reference when attachments get lost or forwarded.
Use a high-entropy share token or passwordless client identity, HTTPS, and server-side authorization. Public invoice and portal URLs should carry noindex controls and stay out of XML sitemaps. Search discovery is useful for product documentation, not for a customer’s commercial record.
Follow up from observable facts
View tracking can tell the sender that the hosted invoice was opened; it cannot prove that the right decision-maker approved it. Use the signal to time a helpful note, not as a threat. A concise reminder should restate the invoice number, due date, balance, and stable link, then ask whether anything is blocking payment.
Choose a reminder cadence per invoice and stop automated reminders when the balance is settled or the invoice is cancelled. Keep an activity record of sends and status changes. A reminder system should reduce manual work without surprising a client or sending messages the workspace owner never opted into.
Keep online and manual payment paths understandable
If card payment is available, say where the money settles and disclose any processing fee before checkout. If the client pays by bank transfer, Wise, UPI, cheque, or another manual method, show the current instructions and let the sender record the payment without pretending the product observed an off-platform bank event.
Partial payments need a visible remaining balance. A fully paid page can become a receipt at the same stable URL; a cancelled invoice should revoke the public payment path. These lifecycle rules matter more than decorative portal features because they keep the client-facing record aligned with the ledger.
How Hoursmith does it
How Hoursmith handles client access and follow-up
Every sent invoice has a shareable noindex page, PDF, and view tracking. Studio and Agency add a passwordless client portal plus one-click and scheduled reminders. Optional supporting timesheets and selected expense receipts remain client-safe and tied to the sent snapshot.
Studio and Agency can offer Stripe Connect card payment into the workspace’s own Stripe account. Configured bank and custom methods can appear alongside it, including disclosed processing-fee instructions. Manual payments and partial balances remain part of the same invoice history.