Waypoint Suites / Claims Portal
The work you did becomes the invoice you send
The administrative side of an adjusting operation: scheduled data exchange with carriers, who is licensed where, which adjusters are deployed to which engagement, and what the client owes for the work.
Thirteen pages, and none of them can cancel anybody’s insurance. Invoicing here bills a client for adjusting work — that is a receivable, not a coverage decision.
Walk a month endProblem 1 — Exchange
Bordereaux that stop eating a week a month
Scheduled
It runs without a reminder
Data exchange with each carrier runs on a schedule in the carrier’s own format. Nobody has a calendar entry that says “build the bordereau”.
Validated
Rejections are visible
A row the carrier will not accept is surfaced with its reason while the context is still fresh, not at quarter end.
Reconciled
Both sides agree
What you reported and what the carrier accepted are compared, so a silent gap does not become a dispute.
Problem 2 — Getting paid
Work performed, work billed, no gap between them
Roster
Who can work where
License state per adjuster per jurisdiction, with expiries visible while there is still time to renew them.
Deployments
Who is on what
Adjusters assigned to an engagement, with the fee structure that engagement pays attached to it.
Invoicing
What the client owes
Generated from recorded work under the deployment. A month end that needs no spreadsheet.
The vocabulary guard
Two things are called billing. Only one can cancel a policy.
Invoicing bills a client for adjusting work. Premium billing bills a policyholder for coverage. Different payers, different portals, different consequences for non-payment — and the distinction is enforced by automated checks rather than by training.
Invoicing
Payer: your client. Unpaid means a receivable you chase.
Premium billing
Payer: the policyholder. Unpaid can end coverage, through a two-desk workflow.
Separate portals
Different screens, different roles, no shared surface where a mistake is possible.
Enforced
Automated checks fail the build if the vocabularies cross.
Role catalog — shared with the Claims Platform
A person handling claims and running the operation holds two roles rather than one broad one, so the administrative surface is not a side effect of being senior.
Clients and agencies are terminated, never deleted — the book, the history and the commission record stay intact and reportable after a relationship ends.
What it solves
Invoicing reads the claims recorded against the deployment and its fee structure, so billable work cannot quietly fall outside the invoice.
Scheduled exchange in the carrier’s format, with rejected rows surfaced and correctable the day they fail.
License state is held per adjuster per jurisdiction and read by both deployments and auto-assignment.
Structurally impossible. Invoicing has no path to a coverage decision — the two systems share no surface.
Termination preserves everything; the audit log holds who changed what, when and why.