When one professional-services project is billed across multiple customers, divisions, grants, or other funding sources, forecast the resulting receivables by issued invoice and responsible payer. Keep the project total as management context, but do not assign one collection date or confidence level to the full project merely because the work shares a contract or delivery team.

Project value is not one receivable

Microsoft's project-contract documentation describes projects with multiple funding sources and funding rules that allocate charges among those sources. Its project-invoicing documentation notes that separate invoice proposals can be created for different funding sources before customer invoices are posted.

That structure matters after billing. Two invoices tied to the same engagement can have different customers, acceptance evidence, due dates, currencies, disputes, and payment paths. Rolling them into one expected-cash line hides which payer supports the timing assumption and makes reconciliation harder when only one portion is collected.

Use the invoice-proposal boundary guide to keep preliminary billing outside open receivables. The unbilled-sales comparison separates project work from issued invoices.

Build a funding-source bridge

For each project, preserve:

  • project and contract identifiers;
  • funding-source or responsible-customer identifier;
  • allocation rule and evidence date;
  • invoice proposal, posted invoice, and open-balance identifiers;
  • payer-specific invoice amount, due date, and currency;
  • customer acceptance, dispute, or portal status;
  • payment terms and current timing evidence;
  • amount collected, credited, retained, or still open; and
  • owner and next action for each payer.

Reconcile the sum of payer-level posted invoices to the project's billed total. Keep committed, unbilled, or proposed amounts in separate lanes. If the funding allocation changes before posting, update the upstream record. If an issued invoice is corrected, preserve the old-to-new lineage instead of silently changing the project forecast.

A shared project milestone can support invoice readiness without proving simultaneous payment. Assign a collection week only to the invoice whose payer and current evidence support it. If one payer is blocked, keep that portion visible without delaying or accelerating the other payer's separate receivable.

The professional-services retainage guide applies when a payer withholds a defined portion. The billing-backlog comparison helps keep work awaiting billing out of the open-invoice population.

Decision rule

Forecast the invoice, payer, and evidence path—not a blended project total. Use the project rollup to reconcile completeness, then retain payer-level owners, dates, and exceptions so collected cash can be traced without double counting.

AR Pulse analyzes an authorized QuickBooks receivables export and produces a ranked action list and four-week range. It does not administer project contracts or guarantee collections. Professional-services finance teams can apply for AR Pulse.