Revenue That Arrives Too Early

The controller's rationale confuses cash with performance. Non-refundability and cost incurrence are not, by themselves, criteria for recognizing revenue.

The analysis proceeds in steps.

Is the fee a separate performance obligation? A mobilization fee typically does not transfer a distinct service to the customer on its own; it is an advance payment for the service that follows. If it does not transfer a distinct good or service, it is not a separate performance obligation and should not be recognized as a standalone item at a point in time.

If not distinct, it is part of the transaction price allocated to the service obligation and recognized as the service is delivered - typically over the 12-month service period. Recognizing 150K in month one would front-load revenue ahead of the work.

If it is distinct (for example, it funds a genuinely separable transition or setup deliverable the customer controls and can benefit from independently), then it may be recognized when that obligation is satisfied. The determination should be documented with the specific facts, not asserted from non-refundability.

Cost is a separate question. Costs incurred in mobilization are capitalized or expensed per the applicable cost guidance, and recovery is assessed against the contract. Incurring cost does not create revenue.

What to document: the contract terms, the conclusion on distinctness, the allocation of transaction price, the recognition pattern, and the rationale for rejecting the month-one treatment. A non-refundable fee with a 12-month no-termination commitment is strong evidence the customer is paying for service continuity, which points to recognition over time.

An invoice issued ahead of the service period is a billing event, not a revenue event. Booking it as revenue would recognize consideration for performance not yet delivered, which is exactly the error revenue recognition rules exist to prevent. The correct entry is a contract liability (deferred revenue) that unwinds as the service is delivered.

Handling. Decline the request, document it, and explain the distinction between billing, cash collection, and revenue. Confirm the deferred balance and the scheduled release. If the quarter gap is real, it is closed by delivering work or by better forecasting - not by reclassifying a liability.

The control issue is more serious than the one request. A PM with the ability to influence revenue postings and a quarter-gap motive is a fraud-risk pattern, not just a training gap. Actions:

1. Segregation. Revenue postings should be system-generated from the recognition schedule, not manually entered by delivery staff. Manual overrides require controller approval with a reason code.
2. Cut-off review. At each period end, review invoices raised in the last week of the period against delivery dates; flag any invoice where the service period begins after period end.
3. Exception reporting. Produce a report of manual revenue journals and deferred-revenue releases that deviate from schedule, reviewed by finance.
4. Tone at the top. The request came from a PM under pressure to close a gap. If the pressure originates above, the control will be tested again. Raise it with the controller and, if needed, through the appropriate escalation channel.

Document the refusal contemporaneously. If the entry is later made by someone else, the record matters.