Multi-phased proposals with entity-specific rate cards represent one of the more technically demanding configuration scenarios in enterprise PSA. The combination of variable contract types across phases, different billing currencies per entity, and cost rates that differ from billing rates by role and geography creates a financial structure that most platforms handle with some degree of compromise. Understanding how enterprise PSA models this correctly — and where the common failure points are — is what allows a finance or ops leader to evaluate whether a platform will hold the margin discipline of a complex proposal through the full delivery lifecycle.
Why Multi-Phase Proposals Break in Less Capable Platforms
The structural problem with multi-phase proposals is that each phase typically represents a distinct financial commitment: different contract terms, different role mixes, different billing milestones, sometimes different entities delivering the work and different currencies invoicing the client. A platform that models an engagement as a single financial container cannot represent this correctly. When phase two uses a different rate card than phase one — because it involves a different geography or a different seniority mix — the billing logic either flattens to a single rate structure or requires manual overrides that finance has to track outside the system.
The failure usually surfaces at invoicing. Phase one completes on a T&M basis at the rates agreed for that phase. The project transitions to phase two, which was quoted as fixed-fee with a different resource mix. If the PSA cannot carry distinct contract terms per phase while maintaining a unified engagement record for the client, finance ends up building the invoice manually from the contract document rather than from the system. That is the moment the PSA stops being a financial system of record and becomes a time tracking tool with an invoice export.
Engagement Structure as the Financial Foundation
Enterprise PSA separates the engagement — the client-facing commercial relationship — from the projects beneath it, which represent the delivery of that engagement in distinct phases or workstreams. This separation is what makes multi-phase configuration possible without loss of financial continuity. The engagement holds the master contract terms and the client relationship. Each project beneath it inherits from the engagement but can override specific financial parameters: its own rate card, its own contract type, its own billing currency if the entity delivering that phase operates in a different currency.
That inheritance model matters because it preserves the financial chain. When a rate card update propagates from the entity level, it flows through the engagement to the projects beneath it — unless a project has an explicit override in place, in which case the override governs. Finance can see, at the engagement level, which projects are operating on the default rate card and which are on negotiated terms, without auditing each project individually.
How Entity-Specific Rate Cards Work Across Phases
In a multi-entity firm, rate cards are owned at the cost center level — the organizational node that corresponds to a practice, geography, or legal entity. When a project is created under a cost center, it inherits that cost center’s default rate card for both billing rates (what the client pays) and cost rates (what the delivery costs internally). Both matter for margin calculations: a proposal that uses billing rates without grounding them in real cost rates is an estimate, not a financial plan.
For multi-phase proposals where different phases involve resources from different entities — a US-based strategy phase followed by a UK-based implementation phase, for example — each phase lives under a project assigned to the relevant cost center. The US project draws from the US entity’s rate card. The UK project draws from the UK entity’s rate card. The engagement above them consolidates both into a single financial view for the client relationship and for cross-entity reporting.
Overriding the Default at the Project Level
Client negotiations frequently produce rate structures that deviate from the entity default. A long-term client might receive a blended discount across all roles. A specific engagement might carry negotiated rates for senior roles that differ from the standard card. Enterprise PSA handles this through project-level rate overrides, where the default from the cost center is replaced by an explicit rate structure for that project only. The override is visible and auditable — finance can see that a non-standard rate is in effect and trace it back to the engagement terms — rather than a silent exception that only surfaces when someone queries why the margin on that project differs from the norm.
Billing Currency and Cost Currency as Separate Dimensions
When the entity delivering a phase and the entity invoicing the client operate in different currencies, the PSA needs to hold both dimensions simultaneously. The billing currency — the currency on the client invoice — is set at the engagement level and governs how the client sees the commercial relationship. The cost currency — the currency in which delivery costs are recorded — follows the cost center of the project delivering that phase. Enterprise PSA converts between the two at the engagement level using the prevailing FX rate, and the margin calculation reflects the real economic cost of delivery rather than a single-currency approximation.
Contract Types Across Phases of the Same Engagement
A multi-phase proposal commonly mixes contract types: a discovery phase billed on T&M, an implementation phase priced as fixed-fee, and an ongoing support arrangement structured as a retainer with a bucket of contracted hours. Enterprise PSA models each phase as a contract line item within the engagement, each with its own billing terms. T&M lines bill based on approved time at the applicable rates. Fixed-price lines bill against milestones or a revenue schedule. Retainer lines track consumed hours against the contracted bucket and surface overage for billing or write-off depending on contract terms.
Example: A 290-person management consultancy structures a digital transformation engagement across three phases: a six-week discovery billed T&M at senior consultant rates, a twenty-week implementation priced as a fixed fee of $840K with milestone billing, and a twelve-month managed services retainer at $45K per month with a 60-hour-per-month contracted ceiling. Each phase carries a distinct contract line item in the PSA. Finance invoices against each line item independently, with the correct revenue recognition treatment per phase — T&M recognized as delivered, fixed-fee recognized on milestone completion, retainer recognized monthly — without manual adjustment between phases.
Margin Visibility Across the Full Proposal
The operational value of correct multi-phase configuration is that margin becomes visible at the right level of granularity. Phase-level margin shows where the engagement is performing against the proposal. Role-level margin within each phase shows whether the resource mix is consistent with what was priced. Engagement-level margin consolidates both into the view the CFO needs for portfolio profitability reporting.
This visibility depends on the cost rates being as accurate as the billing rates. Enterprise PSA calculates both for every time entry: the billing rate that determines what the client owes, and the internal cost rate that determines what delivering that hour actually cost the firm. The difference is the project margin on that time. When cost rates are maintained at the cost center level and inherited correctly through the engagement-to-project structure, margin calculations at every level of the hierarchy are grounded in the same financial logic rather than derived from approximations.
Handling Scope Amendments During Delivery
Multi-phase engagements rarely execute exactly as proposed. A fixed-fee phase extends. A T&M phase is capped at the client’s request. A new phase is added mid-engagement. Each of these scenarios requires a change to the contract structure without disrupting the financial history already recorded.
- Phase extensions on T&M: additional hours are logged against the existing project and billed at the rate card in effect at the time of delivery. No structural change required unless rates have been renegotiated.
- Fixed-fee scope additions: a new contract line item is added to the engagement for the incremental work, with its own milestone or revenue schedule, leaving the original fixed-fee line intact and auditable.
- New phases mid-engagement: a new project is created under the existing engagement, inheriting the engagement’s client relationship and commercial context while carrying its own rate card, contract type, and budget — consistent with the approach used for the original phases.
