In this article
Reconcile a staffing invoice against the agreed billing basis, approved time and assignment history. Do not use a worker’s pay rate as if it were the client’s bill rate, and do not alter worked hours to solve a commercial dispute. Identify the kind of mismatch before asking anyone to correct it.
Confirm who is invoicing whom
Ascen’s invoicing guide distinguishes funded arrangements, where Ascen invoices clients, from self-funded arrangements where use of its invoicing can be optional. Its billing-settings guide describes separate pay and bill rates and configurable invoice grouping. These are setup-dependent features. Confirm your actual arrangement and current schedule rather than assuming every invoice follows the same path.
Draw a small flow showing the service provider, invoice issuer, invoice recipient and party responsible for resolving a dispute. A client invoice, an agency-facing statement and a payroll output are not interchangeable records. Put the document type at the top of the review note. That simple label prevents a surprisingly common mistake: two people discussing different totals while believing they are reconciling the same transaction.
Compare a matched set of records
Begin with the invoice number and version, service period, client entity, assignment reference and applicable purchase-order or department reference. Then locate the authorized billing instruction and time records for that same scope. Matching the period first is more useful than comparing a total copied from last month.
| Check | Question | Possible issue class |
|---|---|---|
| Identity | Is this the correct entity and assignment? | Mapping or recipient |
| Period | Are the work dates and invoice period aligned? | Timing or grouping |
| Quantity | Does each billed quantity have the expected source? | Time or expense mapping |
| Rate | Is the correct billing instruction applied? | Commercial setup |
| Adjustments | Are credits, fees or separate items explained? | Missing reference or duplicate |
Keep a discrepancy in one category until evidence supports moving it. “Total too high” is an observation, not a cause. A wrong period, duplicated line and incorrect rate can produce the same symptom but require different fixes. Record the amount or quantity needed for the authorized review without distributing unrelated worker information.
A small fictional arithmetic example
Thirty hours, two different rates
In a fictional simplified example, thirty ordinary hours have an agreed worker pay rate of $28 and a client bill rate of $44. The corresponding base amounts are $840 and $1,320. The $480 difference is not a calculation of profit: this example excludes employer costs, service fees, insurance, taxes, funding costs and other items that may apply.
The example only demonstrates why comparing a client invoice with base worker earnings can create a false discrepancy. It is not an Ascen quote, a pricing recommendation or a payroll calculation. Actual billing and earnings may include other categories, and their treatment must come from the relevant agreement, settings and qualified review.
Use a similarly small test case during implementation to check that the team understands which rate belongs in which output. Label every example as fictional and keep it out of production records. A simple example is useful because its arithmetic is easy to inspect; it is dangerous if someone later mistakes it for a live instruction.
Keep no-bill questions separate from missing pay
Ascen documents a no-bill treatment for certain hours that are paid to a worker but not charged to the client. The existence of such a treatment illustrates a general distinction: recorded work, worker pay and client billing are related but not identical. Follow the official process for an actual case rather than deleting or moving time to make an invoice fit.
If a client disputes a charge, ask whether the dispute concerns work performed, the agreed commercial rate, a purchase-order limit or the presentation of the invoice. A budget shortfall does not by itself establish that the worker’s recorded time is wrong. Keep the factual record intact while the responsible teams resolve the commercial question. This publication cannot determine wage entitlement or whether a particular cost is legally billable.
Build a correction request that can be acted on
A useful request identifies the invoice and line, describes the observed mismatch, states the expected treatment with its authority and asks for a specific review. Include the related assignment and period through the approved channel. Avoid sending an entire payroll export when one line reference and a contract citation are sufficient.
Ask how the correction will be represented: revised invoice, credit, later adjustment or another supported mechanism. Do not independently net amounts, withhold a payment or issue a replacement document on behalf of another party without authorization. Those are financial actions, not harmless bookkeeping conveniences. Obtain the responsible team’s instruction and keep the result tied to the original exception.
Close only when the records agree
“Credit promised” and “credit applied” are different states. Mark the exception complete when the agreed correction is visible in the appropriate record and the relevant recipient has the information needed to continue. If the issue also affects worker pay, track that as a separate linked outcome; a corrected invoice does not prove a payroll correction occurred.
For recurring discrepancies, look upstream. A repeated wrong rate belongs in the change-control handoff. Missing quantities may point to the time-approval cycle. Unclear ownership belongs in the operating model. Reconciliation becomes valuable when it improves the next cycle rather than merely explaining the last one.
Preserve the authorized evidence and correction reference according to the organization’s retention requirements. Do not keep every export indefinitely “just in case.” The useful record is the one that explains the decision to a permitted reviewer, with access limited to the people who need it.
Sources & scope
Public sources checked October 25, 2026. Product descriptions are attributed to their publisher. The planning methods and fictional examples are original editorial analysis, not official Ascen procedures or legal, tax, safety or financial advice. Your contract, configuration, work location and current official instructions govern actual operations.