Work Is Finished, but Cash Hasn’t Arrived: How a Fractional Controller Strengthens Accounts Receivable 

The project is finished, employees and suppliers have been paid, and leadership expects the customer’s payment to follow. Yet accounting is still waiting for an approved change order, a completion record, or the purchase order reference needed to submit the invoice.  A Fractional Controller can help leadership identify where the process has stalled and why completed work has not yet turned into cash. The business has delivered the work, but the steps that move it toward payment remain unfinished.

That gap matters because the business is still funding the work after the work itself is complete. Payroll continues, supplier payments come due, and new projects require cash while the timing of the last project’s collection remains uncertain. Before treating the problem as slow customer payment, leadership needs to understand where the transaction actually stopped moving and whether the delay is something the business can control. 

Our view is that Accounts Receivable should not begin with the question, “Which customers are late?” It should begin earlier: “What happened between completing the work and getting the cash?” A Fractional Controller can help leadership answer that question by looking across the handoffs between operations, billing, customer submission, collections, and cash application rather than treating AR as an isolated accounting function. 

When Does the Cash Collection Process Actually Start? 

Finishing a project does not necessarily start the customer’s contractual payment period. The starting point depends on the agreement and applicable requirements, which may refer to the invoice date, receipt of a proper invoice, acceptance of the work, or another specified event. 

Consider a hypothetical project completed on September 1, with payment due 30 calendar days after a compliant invoice is received and all billing conditions are met. Accounting receives the supporting documentation on September 8 and successfully submits the invoice on September 10. If the customer pays on October 10, the customer has paid within the assumed terms, but 39 days have passed since completion. 

Those nine days before submission still matter to leadership. They are separate from the customer’s agreed payment period, and if the same delay occurs across multiple projects, the business can carry a meaningful amount of completed work without a corresponding cash receipt. 

The contractual due date and the customer’s internal processing status should also remain distinct. A portal rejection or an internal approval delay may affect when payment actually arrives, but it does not automatically rewrite the contractual payment terms. For example, U.S. federal procurement rules can tie payment due dates to the later of proper invoice receipt and government acceptance in certain federal contracts; those rules are specific to that contracting environment and should not be treated as a general rule for commercial customers.  

That distinction is important because leadership needs to know which part of the timeline is contractual and which part reflects the company’s own process. If an invoice could have been submitted five days earlier because the required completion record was sitting in an operations inbox, that is a different problem from a customer legitimately taking 30 days to pay under the contract. 

Where the Delay Actually Begins 

Accounts Receivable can look like the problem even when the delay started somewhere else. The invoice may be overdue today, but the business may have lost days or weeks before an invoice was ever created.

When Operations and Billing Lose Alignment

The first issue is often the handoff from operations to billing. Operations may consider a job complete while accounting is still missing signed completion documents, approved timesheets, delivery confirmation, milestone acceptance, or change-order information. When those records remain in a project folder or email thread, the billing team may not know that the work is ready to move forward. 

The second issue is invoice quality. An invoice can be prepared quickly and still require correction because the quantities do not match the purchase order, an approved change has not been reflected, or required supporting documents are missing. A genuine commercial dispute is different from an administrative billing error, and the distinction matters because the two problems require different decisions. 

One point we would emphasize here is simple: if the same invoice issue keeps recurring, correcting the invoice should not replace correcting the process that caused it. Repeated corrections are evidence that something upstream may need attention, whether that is the information collected during project setup, the communication between sales and operations, or the way billing requirements are captured.

Why Invoice Submission Can Still Delay Payment

The third issue is submission. “Invoice sent” does not necessarily mean “invoice entered the customer’s payment process.” An invoice may have been emailed to a project manager instead of Accounts Payable, or a customer portal may have rejected it because a required field or attachment was missing. A dependable process therefore needs evidence that the invoice was actually submitted through the required channel and that any rejection has an owner. 

Finally, the customer may have the invoice but still be unable to pay it. The balance could be waiting for approval, caught in a legitimate dispute, missed by a payment run, or affected by the customer’s own financial circumstances. Those situations should not all sit in the same “collections” bucket because the appropriate response depends on what is actually preventing payment. 

The practical takeaway is that leadership should not ask accounting to collect harder until it knows what kind of delay it is dealing with. A collection call cannot resolve a missing completion record, an incorrect purchase order, or a customer portal rejection. 

What a Fractional Controller Should Be Looking For 

A Fractional Controller adds value when the business needs more than transaction processing. The useful question is not simply whether AR is high, but where time is accumulating and whether the business understands why. 

A focused review can trace a sample of completed but unbilled work, rejected invoices, disputed balances, and significant overdue accounts through the records that exist today. 

The value of this exercise is not the table itself. It is what the evidence tells leadership about responsibility. When operations routinely supplies documentation late, the issue belongs partly outside accounting. Customer-specific billing requirements agreed to by sales can create an earlier problem if they never reach the billing team. Meanwhile, invoices that are submitted correctly but remain disputed for weeks may require leadership to address ownership or commercial decision-making rather than simply ask for more collection activity.

This is where tFG’s Controller Services can be relevant. The role is not simply to review whether transactions were processed. Controller-level oversight can help management challenge recurring exceptions, understand unusual balances, strengthen accountability, and determine whether the accounting information is giving leadership a reliable picture of what is actually happening. 

What the AR Aging Report Does Not Tell You 

An invoice-based aging report is useful, but it cannot show every point where completed work may be waiting. Completed work that has not yet reached an invoice may not appear in the aging report at all, which means leadership can see a manageable overdue balance while a significant amount of economic activity is still sitting upstream. 

Understanding Unbilled Work and Contract Assets

There is also an accounting distinction that matters for businesses applying IFRS. Under IFRS 15, a receivable represents an unconditional right to consideration, while a contract asset reflects a right to consideration that remains conditional on something other than the passage of time. The operational fact that a project is complete does not, by itself, determine which accounting balance should be recorded. 

That distinction should prevent leadership from treating every dollar of completed work as immediately collectible. A hypothetical $50,000 completed project may require additional acceptance, documentation, or billing conditions before it becomes an invoice and ultimately a cash receipt. 

The better management view connects the accounting records to the operational pipeline. Leadership should be able to see not only overdue invoices, but also material completed work that has not yet moved into billing, why it has not moved, and what evidence supports the expected collection date. 

The same principle applies to cash that has already arrived. Unapplied receipts are not a collections problem in the same sense as an unpaid invoice. The cash is in the bank, but it may not yet be matched to the relevant customer account and outstanding invoice or invoices. That can distort customer balances and create unnecessary collection activity. Oracle’s guidance on unapplied receipts provides additional technical context on how these receipts are handled. 

The metrics worth watching therefore extend beyond an overdue balance. Leadership may want visibility into completed unbilled work, completion-to-invoice time, invoice rejection and dispute levels, dispute resolution time, overdue receivables, Days Sales Outstanding, and unresolved cash application. The purpose is not to create another dashboard for its own sake. It is to show where the process is slowing down and whether the same exceptions are continuing. 

Why Billing Delays Become a Cash-Flow Problem 

The financial pressure becomes clearer when the timing of delivery is separated from the timing of collection. Employees may already have been paid. Subcontractors may have submitted invoices. Materials, equipment, travel, and other project costs may already have left the bank account. The business has therefore funded the work before the related customer cash has completed the billing and collection cycle. 

Consider a hypothetical business with 20 completed jobs valued at $10,000 each. The $200,000 total represents completed work waiting somewhere in the process; it is not an immediate $200,000 cash receipt. Contractual billing eligibility, submission requirements, customer acceptance, and actual payment behavior still determine when the money can reasonably be expected. 

How Delayed Billing Affects Working Capital

The important issue is what the cash forecast assumes. If management forecasts those receipts as though all 20 invoices are already moving through the customer’s payment process when several are still waiting for documentation or submission, the forecast may be giving leadership more confidence than the underlying evidence supports. 

That matters beyond collections. Hiring dates, supplier commitments, financing decisions, and other operating choices can all depend on expected customer receipts. BDC’s guidance on the cash conversion cycle and collection period reinforces the broader working-capital impact of money remaining tied up in receivables.  

Our point of view is that the quality of a cash forecast depends partly on whether the assumptions behind expected collections reflect what is actually happening in the billing process. A customer payment date supported by a properly submitted invoice and established payment history is different from a date based only on the fact that a project has been completed. 

This is also where fractional CFO support can become relevant. The CFO-level question is not simply whether the company has receivables. It is whether the timing and reliability of those receivables are being reflected appropriately in the decisions leadership is making about cash. 

Fix the Cause, Not Just the Balance 

A lower overdue balance can look like progress without necessarily telling leadership why it fell. Customers may have paid, but balances can also decline because of credits, write-offs, or other adjustments. The explanation matters because each outcome says something different about the health of the receivables process. 

The same principle applies to operational improvements. If eligible work is reaching billing faster, invoice rejection rates are declining, disputes are being resolved more consistently, and expected collections are increasingly matching actual receipts, the business has stronger evidence that the process is improving. 

If those measures are not improving, adding more collection activity may not be the answer. 

For example, if accounting spends every week reconstructing completion records before invoices can be issued, additional accounting capacity may reduce the immediate backlog without fixing the underlying handoff. A clearer requirement for what operations must provide, when it must be provided, and who owns the exception addresses the source of the delay. 

Similarly, customer-specific billing requirements should be captured before the first invoice rather than discovered after a rejection. Purchase order details, required attachments, submission channels, and customer contacts all affect whether an invoice can move through the process without unnecessary rework. 

This is where bookkeeping and accounting support can provide the transaction-level consistency needed to keep invoicing, reconciliations, receipt application, and follow-up current. Controller oversight becomes useful when management needs someone to look across those activities and determine whether recurring exceptions require a change in ownership, process, controls, or decision-making. 

Technology can support that work, but software will not create discipline by itself. A workflow is only dependable when someone owns the handoff, the required information is clear, and exceptions are acted on rather than carried forward from one reporting period to the next. 

Where a Fractional Controller Becomes Useful 

Not every receivables problem requires a Fractional Controller. A business with a temporary processing backlog may simply need additional accounting capacity. A business with unclear responsibilities may need to clarify ownership. A specific customer dispute may require a commercial decision rather than a finance project. 

The case for Controller-level support becomes stronger when the problem crosses those boundaries. If leadership cannot tell whether the issue is billing, operations, customer compliance, collections, cash application, or forecasting, the business may need someone who can look across the entire process rather than optimize one part of it in isolation. 

The objective is not to make Accounts Receivable more complicated. It is to make the path from completed work to cash easier for leadership to understand and manage. 

A useful starting point is to take one recently completed job and one significant overdue invoice and trace each from completion to its current status. If the review shows that the same type of delay is recurring, the next question should not simply be how to clear the current balance. It should be what needs to change so the next transaction does not follow the same path. 

Find Where the Last Completed Job Stopped Moving Toward Cash 

A Fractional Controller strengthens Accounts Receivable by helping leadership see the entire path from completed work to billing, customer processing, collection, and cash application. The value is not in producing another report. It is in making the reason for the delay clear enough that someone can act on it. 

Before relying on the next expected collection, trace one completed job and one significant overdue invoice. Identify where time accumulated, what evidence supports the current status, and who has the authority to move the transaction forward. That exercise can reveal whether the obstacle is a contractual condition, an internal process failure, an unresolved dispute, or customer credit risk. 

If the same gaps are appearing across multiple transactions, connect with the Finance Group to discuss what level of Controller or Accounting Support makes sense for your business. The right answer may be additional capacity, clearer ownership, or more senior financial oversight. The important thing is to understand the problem before adding another layer of process around it. 

Key Takeaways 

• Completed work does not necessarily mean the customer payment timeline has started. 

• A high AR balance can be the result of delays that began before an invoice became overdue. 

• Repeated billing corrections are often a reason to examine the process upstream, not simply correct the next invoice. 

• Cash forecasts are more reliable when expected collections reflect the actual status of billing and customer processing. 

• Controller-level support is most useful when receivables problems cross accounting, operations, customer requirements, and cash-flow decisions.