Invoice Run Warnings in Sparks Provider: Why an Invoice Won't Issue, and How to Delete One Safely

An invoice run warning is Sparks Provider telling you exactly why a piece of work isn't ready to bill, not a glitch to click past. The fix is almost always in the linked shift or the participant's price settings, not in the invoice itself.

1. Read the warning next to the client, not just the total

When you run invoices for a period, any client that can't be billed shows a warning beside their name. That warning links straight to the shift or participant setting causing the hold up. Open it before you do anything else. Guessing which shift is the problem wastes more time than reading the one line Sparks Provider gives you.

2. Fix the cause, then run the period again

• Unapproved hours: approve the shift so it's ready to invoice.
• Missing pricebook item: add the support item to that participant's pricebook, then re-run.
• Unclear or incomplete shift details: open the shift, correct it, and come back to the run.

Once the underlying shift or pricing is sorted, run the invoice period again rather than trying to patch the warning from inside the invoice screen. The run checks the business's current price book and the participant's approved hours each time, so a clean re-run picks up the fix automatically.

3. Editing an invoice: what counts as eligible

Sometimes the invoice did issue, but something on it needs correcting. Open an eligible invoice and choose Edit invoice. Sparks Provider asks for a reason, saves a new version, and keeps the previous version available in History so nothing is lost. Not every invoice can be edited this way. An invoice already sitting in Xero, one with a send in progress, or one where delivery is uncertain, cannot be edited. In those cases the safer move is to resolve the Xero or email side first.

4. Deleting an invoice: when it's the right call

Delete an invoice only when it genuinely needs to be rebuilt from scratch, not as a quick way to tidy up a small error that Edit invoice could handle. Only eligible invoices can be deleted. When you delete one, its shifts become billable again so they're ready for the next run, and any saved versions stay in Invoice history for reference. If the invoice has already gone to Xero or been emailed, sort that out first. Deleting and reissuing on top of an unresolved delivery is how providers end up with two versions of the same invoice floating around.

A fictional, anonymous example

Picture a small fictional provider we'll call Provider A, with no real business or participant behind it. Provider A runs invoices on a Friday and sees a warning next to one client: a support item used that week isn't in that participant's price book. Instead of forcing the run, the admin opens the participant's pricebook, adds the item from the business's current price book, and re-runs the period. The invoice issues cleanly. A week later they notice a shift was billed at the wrong quantity. Because the invoice hasn't been sent to Xero yet, they open it, choose Edit invoice, add a short reason, and save the corrected version. The original stays in History in case anyone needs to check what changed.

The habit worth keeping

Treat invoice run warnings as a checklist, not noise. Fix the shift or the price, re-run the period, and only reach for Edit invoice or delete once you know whether the invoice has already left the building. That one habit avoids most of the duplicate-invoice headaches small teams run into.

For a wider view of how approved hours flow into invoices and Xero, see our related reading below.