Project margin and cash availability answer different questions. Learn how timing, unbilled work, cost recognition, recorded transactions, and uncertain payment expectations can create a cash gap—and how to review it without mixing forecasts with facts.
A project can look healthy and still put the business under cash pressure.
The budget may show a positive margin. Delivery may be progressing. Revenue may have been recognized, or the period may contain more recorded income than expense. Yet the bank balance can still be tighter than expected.
Follow a hypothetical service visit through customer booking, staffing, equipment, delivery, and follow up. See how named owners keep changes consistent across the work.
That is not necessarily a contradiction. “Profitable” and “cash-generating now” use different inputs, recognize events at different times, and answer different questions.
Confusion begins when one number stands in for all of them: forecast margin becomes “profit,” recognized revenue becomes “money due,” or an expected payment becomes “cash next week.”
The remedy is a clear bridge among delivery, project economics, revenue treatment, expected customer payments, and recorded cash movement.
Before diagnosing a cash problem, identify which question each number answers.
| View | Core question | Typical inputs | What it does not prove |
|---|---|---|---|
| Project period net | What recorded project-linked income and expense appears in this date range? | Actual-status finance transactions, plus supported project costs such as qualifying mileage | Audited profit, invoice status, or bank cash |
| Project forecast margin | What margin does the current delivery plan imply? | Budgets, progress, linked transactions, and available time rates | A guaranteed final margin or collection outcome |
| Revenue recognition | What amount is eligible to be recognized and posted under the selected policy? | Contract amount, method, period, delivery or time evidence, approval | That an invoice was issued or paid |
| Expected customer payment | What cash does the team currently expect and when? | External invoice, agreement, communication, or planning commitment | That cash has arrived |
| Cash position and movement | What balances and recorded income or expense are visible now? | Account balances with source/as-of context and actual-status transactions | That every balance is live, reconciled, or complete |
These views can move in different directions. A project forecast can improve while cash declines because costs have already been paid. Revenue can be recognized while collection remains in the future. A large customer payment can arrive while the project margin deteriorates because the remaining cost estimate increased.
The operating task is to explain the bridge, not force the values to agree.
Many projects consume labor before the next billing event. The team completes hours, milestones, or deliverables, but the commercial process may require approval, a billing date, supporting evidence, or a customer purchase-order step before an invoice can be issued.
Figena’s project control center can calculate billable time value from paid minutes and the available billable rate. It can also calculate estimated unbilled time as the positive difference between billable time value and recorded project income. That is useful as an investigation signal: project work may be economically accumulating faster than income is being recorded.
It is not an invoice balance. The calculation does not prove that every hour is billable under the agreement, that delivery has been accepted, that an invoice exists, or that payment is due. A project owner still needs to check the contract, completion evidence, and the authoritative billing source.
The practical questions are:
Revenue recognition and customer collection are separate processes.
Figena supports a governed project revenue flow: a user with the required access defines a revenue policy, creates a recognition draft for an eligible period, approves the draft, and explicitly posts the journal to an active asset account and an income account. The service prevents the recognition total from exceeding the contract amount and retains the calculation basis used for the proposal.
That workflow can support a disciplined accounting record. It does not create a complete customer invoice ledger. It does not establish invoice due dates, aging buckets, DSO, collection history, or automated follow-up. Posting recognized revenue therefore must not be interpreted as recording cash receipt.
The project can therefore show recognized economic activity while the customer invoice or collection process remains external and the operating account remains unchanged.
A project may require payroll, contractor work, inventory, travel, software, deposits, or other costs before a billing milestone or payment date. Even when the total commercial value exceeds the total expected cost, the timing creates a financing requirement.
The team may pay or incur delivery costs while work progresses and the estimate at completion remains within budget. If customer payment belongs to a later milestone, current cash absorbs the gap.
Positive forecast margin does not eliminate that gap. It only suggests that forecast revenue exceeds forecast cost under the current inputs.
This is why project reviews need both an economic view and a cash-timing view. The first asks whether the work is expected to create value. The second asks whether the business can fund the path to collection.
A date-range total is useful, but totals compress timing. Two projects can show the same income, expense, and net result for a month while creating very different cash pressure inside that month.
One may receive a deposit before work begins. Another may pay suppliers early and collect after acceptance. A third may have income and expenses recorded in the same reporting period even though the underlying account movements happened on different days.
When reviewing the transaction management view, open the entries behind a material project total. Check the dates, accounts, currency context, status, and project linkage. A project tag helps attribution; it does not turn the project total into a bank statement.
A project forecast is only as reliable as its inputs. Several gaps can make a healthy-looking margin misleading:
The appropriate response is not to discard the forecast. Label its confidence, correct the inputs, and avoid using it as a cash promise.
Figena provides two complementary project views. Understanding their construction helps a team use the right one.
The project summary aggregates project-linked, non-deleted, actual-status income and expense transactions for the selected date range. It calculates income, expense, and net by project and across the workspace. Supported approved mileage costs can also be included when they represent project cost not already carried by an authoritative project-linked reimbursement transaction.
This makes the summary useful for finding the largest recorded project results, checking attribution, comparing the income-and-expense mix, and choosing which totals to inspect at transaction level.
The summary is not a complete cost-accounting statement. It depends on transaction status, date range, project links, and the supported cost sources included in the calculation. Call the output a project period net or project profit summary as presented in the product; do not call it audited profit.
The project control center goes beyond a date-range total by connecting delivery and economics. When the member has the necessary access, it can use project budget lines, linked actual-status finance transactions, and time entries.
The core calculations are explicit:
| Metric | Calculation basis | Important dependency |
|---|---|---|
| Budget revenue | Sum of project budget lines marked as revenue | Current budget structure |
| Budget cost | Sum of project budget lines marked as cost | Current budget structure |
| Committed cost | Sum of committed amounts on cost lines | Updated commitments |
| Labor cost | Paid minutes × cost rate | Time access, submitted time, valid cost rates |
| Billable time value | Billable paid minutes × billable rate | Billable flags and rates |
| Actual cost | Linked external expense + calculated labor cost | Complete links and no duplicate labor posting |
| Estimate at completion | Actual cost ÷ weighted progress when progress is sufficiently established; otherwise the greater of actual cost or budget cost | Credible progress and cost inputs |
| Forecast revenue | Budget revenue when present; otherwise the greater of recorded income or billable time value | Current budget or time/income data |
| Forecast margin | Forecast revenue − estimate at completion cost | All upstream assumptions |
| Estimated unbilled time | Positive portion of billable time value − recorded project income | Time value is not invoice evidence |
The control center also surfaces overdue and blocked work and can flag when estimate-at-completion cost exceeds budget cost. Those signals help the team ask why the forecast changed.
The application explicitly separates external expense and calculated labor cost and warns organizations to avoid posting the same labor cost twice. It also indicates whether time cost was included. If a member cannot read time data, or the project lacks time and rate information, the displayed economics should be interpreted accordingly.
Once the team has separated the views, connect them with a short bridge. Do this for projects that materially affect the next operating period rather than for every active record.
| Bridge step | Question | Evidence to inspect | Result |
|---|---|---|---|
| Delivery | What work is complete, blocked, or overdue? | Project work items, milestones, progress | Credible delivery status |
| Economics | What changed in cost, EAC, revenue, or forecast margin? | Project budget, linked transactions, available time data | Updated economic forecast |
| Billing readiness | What completed work can be billed under the agreement? | Contract and delivery evidence outside or linked to Figena | Billing action or documented blocker |
| Expected payment | What amount and date does the authoritative customer-payment source support? | Invoice system, agreement, communication, planning commitment | Dated expectation with confidence |
| Cash confirmation | Has the movement been recorded and reconciled in the relevant account? | Account source/as-of, transaction, statement review | Confirmed position or exception |
This reveals whether the issue is delivery, billing readiness, collection timing, transaction recording, or a genuine need for working capital.
Use the accounts view to review account type, balance source, update time, imported activity, and reconciliation context. Do not flatten a credit-card liability, physical cash count, manually entered balance, and connected bank balance into one unquestioned number.
The standard workspace cash-flow series uses recorded actual-status income and expense transactions for the selected period. It supports common and custom periods, filters, and previous-period comparison. That makes it valuable for explaining what happened. It does not, by itself, predict future customer collection.
When a balance matters, ask what produced it, when it was current, whether native-currency facts are complete, whether statement lines remain unmatched, and whether a recent reconciliation supports it.
If the answer is uncertain, follow the account reconciliation guide before treating the balance as decision-ready.
Figena also has a separate planning forecast. It can project one to 730 days using expected or draft recurring occurrences and proposed or approved finance commitments. Expected recurring amounts are weighted by their confidence; commitments are weighted by probability. Dated events contribute to projected income, expense, net movement, and—when associated with an account—projected account balances.
This is useful for testing questions such as:
The forecast is only as complete as its recurring occurrences and commitments. It is not a bank guarantee, an invoice-aging report, or a prediction that a particular customer will pay. Keep the source, confidence, and scenario visible whenever a forecast supports a decision.
Use the following sequence for any project that looks profitable but creates cash pressure.
Confirm source, freshness, native currency, imported activity, and reconciliation status. Do not begin with a home-currency total that nobody can trace.
Open the income and expense entries behind the project period net. Correct missing or incorrect project links at the source. The guide to recording transactions with useful context explains why account, date, currency, category, client, vendor, project, and supporting evidence matter.
Update work-item status and weighted progress. Submit relevant time. Confirm cost and billable rates. Update budget or committed cost only when the underlying plan actually changed.
Check whether calculated labor and external expense contain the same cost. Keep the project calculation basis visible when explaining actual cost or forecast margin.
If customer invoices live outside Figena, keep invoice identifier, amount, due date, status, dispute context, latest contact, and next owner in that system or a controlled collection list. Bring only the material expectations into the operating review.
Use dated recurring items and finance commitments for supported planning scenarios. Set confidence or probability honestly. Do not enter a hopeful collection date merely to make projected cash look comfortable.
Finish a milestone, obtain acceptance, prepare an invoice externally, confirm a payment date, link a transaction, reconcile an account, update an input, or change the plan. Give the action one owner, one due date, and one completion condition.
Forecast margin compares forecast revenue with estimate-at-completion cost. It does not describe the day on which costs are paid or customers pay.
A posted revenue-recognition journal records approved accounting treatment. Without a complete customer AR subledger, it should not be presented as an invoice or aging fact.
Estimated unbilled time highlights billable time value not yet reflected in recorded project income. Contract rules, acceptance, billing, dispute, and collection still intervene.
The standard cash-flow series summarizes recorded actual-status transactions. Use the separate planning forecast for dated expectations, and label uncertainty.
Yes. A positive period net or forecast margin can coexist with cash pressure when costs occur before collection, work remains unbilled, revenue is recognized before payment, or customer payment timing changes. The labels and evidence behind “profitable” determine the precise explanation.
In the control center and project summary, actual income refers to qualifying recorded finance transactions linked to the project. Review the transaction account, date, status, and source before drawing a cash conclusion. It is not a substitute for account reconciliation.
Figena calculates period net and operational forecasts from supported inputs. Forecast margin depends on budgets, progress, linked transactions, and available time and rate data. It is not a guaranteed final result or an audited accounting conclusion.
No. It is calculated from billable time value and recorded project income. Accounts receivable requires customer invoice, due-date, payment, credit, and aging facts that the current product does not provide as a complete subledger.
No. It projects dated recurring items and commitments using the recorded confidence or probability. It can represent a team’s expectation, but it does not predict customer behavior or guarantee bank receipt.
Fix the fact that changes the immediate decision: an unreliable account balance, missing project cost, stale progress value, unlinked transaction, unsupported billing assumption, or unowned customer follow-up. Then refresh the bridge rather than adjusting an unrelated number.
A healthy margin is important, but a small business also has to fund the route from work to collection. That route crosses delivery, cost, billing readiness, expected payment, and confirmed account movement. No single metric can safely replace the others.
Use Figena’s budget management and project views to keep plans and operational economics visible. Use account and transaction records to explain recorded movement. Use planning forecasts for dated, uncertainty-labeled expectations. Keep invoice and collection facts in their authoritative source until a complete receivables workflow exists.
When the team can explain each bridge step, “profitable but short on cash” stops being a mystery. It becomes a timing problem with visible assumptions, evidence, owners, and actions.
Separate decisions, actions, and open questions in meeting notes. Use a practical handoff template to confirm owners, define completion, manage dependencies, and review the result.
Decide which inquiries deserve the next sales step using evidence of need, fit, timing, and decision process. With a decision matrix, two hypothetical examples, and a reusable lead review.