Rejected and short-paid invoices, matched to the reason and ready to fix.

Rejections land in portal notices and emails; short payments show up when cash is applied. Today someone on the billing team reads the reason, pulls the work order and paperwork, works out the fix, rebuilds the invoice or finds the proof, and resubmits. The ones nobody reaches sit in aging.

In the proof of concept, AI works from copies of rejections and short payments your team has already dealt with. For each one it names the cause and drafts the fix: a corrected invoice, the photo or sign-off that was missing, a tax change, or a note asking the site a question. Your reviewer, the billing lead who knows each customer's quirks best, compares every draft with what your team actually did.

Every portal has its own words for no. In ServiceChannel an invoice can sit On Hold, meaning the client needs more review before it acts; show as Disputed, which there means the tax you entered didn't match the client's tax validation; or come back Rejected, meaning the client doesn't agree with the costs or details. CorrigoPro marks an invoice Disputed when the customer turns it down, the customer's reason travels with it, and the provider fixes the invoice and submits it again. Reading the status right is the first step, because a held invoice needs patience and a disputed one needs a tax answer.

A fix is usually a new invoice. ServiceChannel doesn't let you edit an invoice once it's submitted, and you can't void one after it has been rejected or put on hold. The correction goes in as a new invoice under another unique number, unless the client has turned on reuse of rejected invoice numbers. Your own books have to agree, so the rejected one gets credited or voided on your side and the replacement carries the same work order. The draft proposes the new invoice and lists the entry your team would post, and your billing lead does both.

Plenty of rejections are about format, not the work. A client can require line item invoices for certain trades, with labor, travel and materials on their own lines, and resolution text saying what was done. In CorrigoPro, invoices for work orders that need the customer's verification wait in a pending verification status, and some customers refuse any invoice on a work order rated not completed. So the draft reads the reason first and sorts the fix: a missing photo or sign-off, lines to split, a tax change, or a question for the site.

Short payments rarely explain themselves. A customer pays the contract amount and drops the extras, pays some of a storm's sites and not the rest, or pays without the tax. Tax rules shift by service and by state. The Texas Comptroller, for example, treats mowing, pruning and other landscaping as taxable services but handles installing an underground sprinkler system under the rules for construction and repair work, and tells providers to state nontaxable charges separately from taxable ones. The draft ties each short payment to the invoice line it came from and the likely reason, and says so when it can't tell.

Your billing lead makes the call. Some cases need a resubmission, some a credit, some a call to the site manager first. The draft sorts each one and attaches the proof it found; your billing lead chooses what goes back and sends it.

If your reviewer says yes, new rejections and short payments get the same treatment for about 30 days.

A person checks every corrected invoice before it goes back to a customer, and your team does all the resubmitting in the portals. Credits and write-offs are still decided by your billing lead. The reviewer keeps comparing drafts with what the billing team would have done.

Through the 30 days the scope stays on rejections and short payments.