Client experienceFiles & invoices
Client experience/Files & invoices
7 min read·06 / 08

Files & invoices

Invoices give the client a clear balance and one place to pay. Files are the section this page will grow into — the storage half is being built now, and this page says plainly which half exists today.

Files

Every file carries a visible-to-client flag, and the portal shows only the ones you've turned on — a client can never see a file you haven't shared, including one attached to their own project.

Uploads are not live yet
File storage is the feature we're building right now. Until it ships, the Files section renders what's there but there's no way to put anything in it — keep sending deliverables the way you do today. Client-side uploads land in the same release.

Invoices & payments

Issue invoices from the console with your own payment link on them. The client sees what's outstanding, what they've paid, and a Pay button that opens your processor — Stripe, or whatever you already use. You keep the payment relationship, and PortalTable never touches the money or takes a cut.

portal / invoices
The client's Invoices view — outstanding balance, paid-to-date, and a line per invoice.
The client's Invoices view — outstanding balance, paid-to-date, and a line per invoice.
  1. 1Outstanding and paid-to-date totals, scoped to this client.
  2. 2Status pills: Paid, Due, Overdue.
  3. 3Pay opens your own payment link in a new tab.
  1. 1
    Create an invoice
    From the client account, set the number, amount, dates, and paste the payment link from your processor.
  2. 2
    The client pays through your link
    They see the amount due in your branded portal and click through to your processor to pay.
  3. 3
    Mark it paid
    Payment happens at your processor, so flip the invoice to Paid in the console once it lands. The client's portal reflects it from then on. Automatic reconciliation is on the roadmap.
Why the link-out
Taking card payments ourselves would put PortalTable between you and your client's money, with a cut and a compliance surface to match. Your processor, your rates, your relationship — this is a deliberate choice, not a gap.

Messages

Messaging is designed but not built — a thread per portal so a question about an invoice sits next to the invoice. Until it ships, the Messages tab is marked Soon on both sides and there is nothing behind it. For now, keep client conversation wherever it already lives.

Next
Security & permissions
Keep client data isolated.
Next
Billing & plans
Invoicing and payments by plan.
On this page