Great field operations start with clear guidance

What this guide covers

This guide explains how to run consistent billing operations for Use Invoice Reporting Views. It is written for the current JobsiteOn implementation and avoids assumptions about unshipped behavior.

Before you begin

• Confirm you can access the relevant route(s) for this workflow.
• Use sandbox first when testing a new process or policy update.
• Keep this article open while you execute each step so your team can follow one consistent path.

Workflow overview

1. Open the correct route and confirm workspace context.
2. Complete the core workflow action in order.
3. Validate downstream impact before handoff.
4. Document exceptions and close the loop with your team.

Step 1: Open the correct route and confirm context

Start from /reporting and confirm you are operating in the intended workspace and environment. The older /invoices/reporting root route now redirects to /reporting, while the individual invoice drilldown routes remain available under /invoices/reporting/*.

Route checklist

• /reporting
• /invoices/reporting
• /invoices/reporting/invoices-sent
• /invoices/reporting/jobs-completed
• /invoices/reporting/proposals-sent
• /invoices/reporting/tasks-assigned

Step 2: Complete the core workflow action

Follow the route sequence above from first screen to final save/submit point. Use the top-right date-range picker on /reporting to switch presets or choose an exact custom range. The old standalone Export CSV button is no longer part of the reporting header.

Step 3: Validate downstream impact

After the main action completes, verify that related modules reflect the update. The expected downstream impact for this area is clean payment workflows and reporting confidence.

Step 4: Handle exceptions quickly

If the expected result does not appear:

1. Refresh the current page and confirm the record status.
2. Verify required linked entities (contact/property/team/job/invoice context as applicable).
3. Re-run the action in sandbox if live-state confidence is low.

Step 5: Keep the process repeatable

Capture the final operating sequence for your team and reuse this article as the reference runbook. When behavior changes, update this article in the same change set as the product update.

Validation checklist

• Primary route opened successfully.
• Core action completed without blocking errors.
• Downstream module behavior matches expected workflow.
• Team handoff information is complete.
• The /reporting date-range picker appears in the header action area and updates the selected reporting window.

Troubleshooting

I cannot access one of the listed routes

Confirm account permissions and environment selection. If access is still blocked, route the issue to your admin/support path with the exact URL.

I saved changes but I do not see the result

Reload the route, confirm linked records, and validate whether this workflow is beta-gated in your workspace.

My screen layout looks different

Layout can vary by feature flags or viewport size. Keep following route names and workflow checkpoints from this guide.

FAQ

Is this available in every workspace?

Not always. This guide includes beta-dependent behavior and may require feature-flag visibility.

Should we run this in sandbox first?

Yes. Sandbox-first execution is recommended for process changes and first-time team rollout.

How often should this process be reviewed?

Review whenever related auth/onboarding/module/release behavior changes.

Notes

The canonical analytics workspace is /reporting. Use the invoice drilldown routes under /invoices/reporting/* when you need the focused per-metric views linked from that workspace.

Related Articles

• Create and Manage Invoices
• Read Dashboard Cards and Filters