What this solves
Employer billing questions should stay attached to the organization, job, shift, invoice, and approval owner so support can separate finance review from worker support.
Route billing by record
Start with the invoice, shift, worker closeout, or membership record that triggered the question. A support case without those identifiers becomes a finance research task instead of a billing correction.
If a charge is tied to a disputed shift, keep the dispute and billing conversation connected. Do not ask the worker to resolve billing outside the platform.
Who should open the case
Use an account that belongs to the employer organization and has billing or admin authority. This protects worker privacy and keeps invoices away from unauthorized team members.
If the billing owner has left the company, open an account-access case first so support can validate the organization before discussing billing details.
What support can and cannot do
Support can help identify invoice status, shift closeout state, membership context, and missing record details shown in the product. Payment movement, refunds, credits, pricing commitments, and production account changes require approval through the right internal route.
For enterprise contracts, include the contract owner and rollout context. That prevents a public support message from becoming an unauthorized commercial change request.
Before you open support
Case is opened by an authorized employer account.
Invoice, shift, membership, or organization record is named.
Worker dispute and billing issue remain linked when both are involved.
No refund, credit, or pricing commitment is assumed from a help article.