Create the client and issue a portal invite.
A client portal for viewing invoices and reporting payment
Give a client an invite link to view shared invoices and submit a payment notice, while keeping final confirmation with the freelancer.

How it works
The client opens shared invoices from the invite link.
Review any payment notice and confirm only after funds arrive.
What it helps you do
Keep shared invoices in one client view.
Let clients provide amount, method and reference.
Preserve a manual confirmation boundary.
Worked example
A client opens their private invitation, reviews two shared invoices and reports a bank transfer against one invoice with its reference. The notice remains pending. The freelancer checks the bank account, confirms the matching amount and only then updates the invoice payment record.
Before treating a record as ready, compare it with the client agreement and its source evidence. Check the client, service period, quantity, rate, currency, tax treatment and payment terms independently. Resolve missing receipts or unclear descriptions while the work is recent. Preview the final document, confirm the intended recipient and keep the issued version in the account. After sending, record delivery, reminders and confirmed payments against the same invoice rather than rebuilding the history from email or chat. Billoz supports that workflow, but the account owner remains responsible for approval, classification and any professional advice required.
Feature details
Invite tokens are stored as hashes. Portal data is scoped to the invited client, and payment notices remain pending until the account owner confirms or rejects them.
Important conditions
The portal is not a payment processor and a client notice is not proof that cleared funds have arrived.
Treat invite links as private. Revoke or replace an invite if it is sent to the wrong person.
Questions and answers
Can clients pay through Billoz?
No. They can report a payment made elsewhere.
Who confirms payment?
The freelancer confirms after checking that funds arrived.
Are invite tokens stored directly?
No. The database stores a hash of the token.
Can a client see another client?
The portal query is scoped to the invited client.
Can notices be rejected?
Yes. The account owner can reject an incorrect notice.
What can clients see?
Shared invoices and sender payment details intended for that portal.