A rejected or change-requested professional-services invoice proposal should not appear as open accounts receivable. It remains upstream billing work until approval and posting create a supported customer invoice.

Keep proposal status separate from receivable status

Project invoice proposals can move through approval workflows before posting. Microsoft documents workflow outcomes that include approval, rejection, and requested changes, with posting available only after approval in the configured process. That makes proposal status useful operational evidence, but it is not the same as an issued open receivable.

The professional-services invoice proposal versus AR guide covers the general boundary. A rejection adds a specific action state: determine what must change before billing can proceed.

Create a rejected-proposal queue

Record the proposal ID, customer, project, service period, proposed amount, submitted date, rejected or change-requested date, reason category, requested correction, approver, owner, and next review date.

Keep the reason narrow and supportable. Examples include missing project detail, amount or grouping correction, incomplete evidence, wrong approver, or workflow error. Do not convert a generic rejection into a customer dispute unless the source evidence says the customer has disputed an issued invoice.

If the workflow itself is stuck, preserve the history and investigate the process error. Do not bypass approval simply to place the amount into a cash forecast.

Forecast the right population

Use two separate views:

  • Billing pipeline: rejected, change-requested, approved, and ready-to-post proposals.
  • Collections forecast: issued open invoices with evidence-based timing.

The proposal amount may inform an upstream cash-planning scenario when clearly labeled, but it should not be mixed into the invoice-level AR collections total. Once the proposal is approved and posted, capture the new invoice ID, invoice date, due date, delivery status, and open balance before assigning a collection week.

The unbilled professional-services work guide explains why work and billing backlog stay outside open AR.

Handoff from project operations to finance

Project operations should provide the proposal status, reason, required correction, responsible person, supporting project records, and next approval step. Finance should record whether the amount is excluded from AR, whether a planning scenario includes it separately, and what event will make it eligible for the collections forecast.

Do not assign an expected collection date from the proposal's submission date. First establish an issued invoice. Then use terms, delivery, approvals, customer commitments, and other evidence to set timing.

Decision rule

Rejected proposal equals billing backlog, not open receivables. Keep it actionable in the billing queue and move it into the collections forecast only after approval and posting. Professional-services finance teams can apply for AR Pulse for a ranked invoice action list and four-week collections view.