Rejected billing / trust walkthrough
The invoice was valid. The portal still said no.
A subcontractor can finish the work, send a correct invoice, and still get stopped by a GC portal over a missing PO number, a file-format rule, or a duplicate submission. Here is what happens when that rejection loses its connection to the books.
A frustrating kind of silence
A portal rule can hide a perfectly ordinary invoice.
The owner remembers the job. The crew finished it. The invoice was prepared from the same scope and documentation used everywhere else. Then a portal sends back a short rejection message and the invoice stops moving.
“Missing PO,” “invalid format,” and “duplicate” can each be accurate without telling the whole story. The books still expect payment. The portal still needs a corrected submission. The person responsible for bridging those facts may be the same person running payroll, scheduling crews, and starting the next job.
Drumtap starts by reconnecting the rejection to its source record. See the evidence flow for the broader reconciliation path.
The four-part handoff
Follow the record, not just the rejection.
The problem is rarely one dramatic failure. It is the space between a legitimate invoice, a portal rule, and the evidence needed to make the next submission stick.
- 01
The invoice was valid in the first place.
Call the subcontractor Harborline Mechanical. The crew finished the scope, the work was approved, and the books carried a real invoice for $18,760 in accounts receivable.
- 02
The GC portal rejected the handoff.
The portal returned a rejection that looked administrative, not substantive: the PO number was missing, the file was in the wrong format, or the invoice appeared to be a duplicate of an earlier submission.
- 03
The record stalled between two systems.
QuickBooks still showed the invoice as open. The portal showed a rejected or duplicate submission. Unless someone connected those two records, the next action lived in a message, a download folder, or somebody’s memory.
- 04
Drumtap refilled the packet with evidence.
The invoice was matched to the job, the rejection reason was named, and the missing PO, corrected file format, or duplicate-resolution note was attached. The resubmission had a clear record to follow.
Where the record stalls
Three records. One invoice. No shared next step.
The books, the portal, and the handoff can all be telling the truth. Reconciliation makes the relationship between them visible before a valid invoice becomes forgotten work.
The books
Invoice: $18,760 open
The work was completed and billed. Nothing in the ledger says the invoice was invalid.
The portal
Submission rejected
Missing PO, wrong format, or duplicate submission. The portal has an answer, but not always the context around it.
The handoff
Valid work without a next step
Without the matching evidence, a rejection can sit untouched until the next payment run—or the next time someone asks why it is still open.
The refile packet
Evidence turns “rejected” into a resubmission.
Drumtap does not guess which portal rule matters. It keeps the rejection reason alongside the invoice and assembles the supporting record for the next attempt.
- The original invoice and job reference
- The portal rejection reason and timestamp
- The correct PO number or a note identifying where it belongs
- The accepted file format or duplicate-resolution explanation
How reconciliation follows it
Fix the handoff without blaming the invoice.
Reconciliation separates the quality of the work from the quality of the submission. A missing PO number is a fixable handoff problem. A wrong format is a portal requirement to satisfy. A duplicate needs a clear explanation so nobody pays—or rejects—the same invoice twice.
That is why Drumtap’s full reconciliation workflow brings the source records and evidence together before someone sends the next message or re-uploads the next file.
The output
A rejection with a reason.
The owner can see whether the next move is to add the PO, convert the file, explain the duplicate, ask the GC a focused question, or escalate a real issue.
The owner’s next move
Refile once, with the full record.
The resubmission carries the invoice, the correction, and the evidence that explains why this is the right record to process.
The point of the exercise
A portal rejection should create a task—not a mystery.
When the invoice, rejection, correction, and evidence stay together, a valid bill has a way back into the payment process.
Have a rejection like this?
Bring us the invoice and the portal’s answer.
Tell us what was billed, what the GC portal rejected, and what evidence was available. We can help you find the missing connection and prepare the next step.