Won engagements, statements of work, staffing plans, hours and invoices move between Salesforce and the delivery and finance systems of a services firm.
In consulting, engineering, accounting and other services firms, integration connects what was sold to what gets delivered and billed. When an opportunity closes, the engagement, budget, rate card and milestones pass to professional services automation or project accounting, and the resourcing team starts staffing from the same record. Hours, utilization, milestones and invoices then return so account leaders see delivery health and revenue beside the pipeline. Signed contracts and statements of work are linked from the contract repository. The design depends on which system owns projects and rates, and on how the firm recognizes revenue.
Every deal a services firm signs consumes named people's calendars, which turns the sales forecast into a hiring and bench question. A large opportunity nearing close should tell resourcing which skills will be needed and when, which means Salesforce data has to reach resource planning before the deal is won, not after. Pricing structures vary widely across time and materials, fixed fee, retainers and milestone billing, and each changes how data flows to finance. Many firms also run a mix of systems acquired over time, so the same client may appear in project accounting under several codes. And because billable hours drive revenue, errors in time data affect invoices directly and damage client trust.
When an opportunity reaches closed-won, the integration creates the project in professional services automation or project accounting with the contract type, budget, rate card, billing schedule and engagement lead. The project code returns to Salesforce, linking delivery data to the account and opportunity. Required fields are validated before the handoff, so projects never start without an approved statement of work or a billing contact.
Opportunities above an agreed probability share role, skill, start date and estimated effort with the resource management system as soft demand. Resourcing leads see upcoming needs before contracts are signed, and can plan hiring, subcontracting or bench allocation. When deals close, lose or slip, demand updates automatically, keeping the capacity forecast aligned with the sales forecast. Resourcing no longer has to chase sellers for start dates by email.
Hours logged, budget consumed, milestones completed and project status from delivery systems summarize on the account and project in Salesforce. Account leaders see at a glance which engagements are running over budget before discussing an extension, and leadership reports on utilization and backlog by practice alongside pipeline. Detailed timesheets stay in the time system, where approvals and audit trails already live.
Invoices, payments and outstanding balances from the billing system appear on the account, and approved change requests in Salesforce update budgets and billing schedules in project accounting. Account leaders know when a client has unpaid invoices before proposing new work, and finance sees scope changes as soon as they are agreed rather than at month end, which shortens the lag between agreed work and billed work.
We involve sales operations, delivery leadership, resourcing, finance and the PSA administrator from the first workshop, and trace one engagement from proposal to final invoice. That trace sets the project key and the moment ownership moves from sales to delivery. Opportunity-to-project creation is built first, since it removes duplicate setup; delivery and billing summaries follow, then resource demand. Testing uses closed engagements with known budgets and invoices. Releases avoid month-end close and annual rate card changes, and delivery managers help validate that status data matches what they see day to day.
Won work creates projects with budgets, rates and billing terms, and hours, budget burn, milestones and status return for account and practice reporting.
Soft demand from late-stage opportunities feeds capacity planning, and consultant skills, availability and roles return to support staffing conversations during the sale.
Signed statements of work and change orders are linked to the opportunity and project, keeping one authoritative contract version for delivery and finance.
Rates may be set by practice, role, region or client contract. Choose one system to master them, most often project accounting, and make Salesforce quote from that source. Two sets of rates lead to proposals that finance cannot bill as written.
Sharing every early opportunity with resourcing creates noise, while sharing only won deals is too late. Agree on the stage or probability at which demand is sent, what fields it includes and how resourcing treats it, so the capacity forecast stays credible.
Fixed-fee, milestone and time-and-materials engagements recognize revenue differently. Make sure project type, billing schedule and contract terms carried from Salesforce match what finance needs under current revenue recognition standards, and let finance control recognition and any adjustments in its own systems.
Client names are anonymized.
Both approaches work. A Salesforce-native PSA shares the data model, which simplifies integration but ties delivery to the CRM. An external PSA or ERP-based project accounting may suit firms with complex finance needs. We assess delivery processes, finance requirements and existing investments before recommending one, then design integration around that choice. Either way, the handoff from sale to delivery should create the project automatically rather than through a manual setup form.
Early enough to act, late enough to be reliable. Many firms share demand when opportunities reach a proposal or verbal commitment stage with a named start date. We work with sales and resourcing leaders to set the threshold, review forecast accuracy after a few cycles, and adjust so demand signals help planning without creating busywork.
They can see summaries such as budget consumed, forecast margin and billing status if leadership agrees. Detailed cost rates and individual compensation should stay in finance and HR systems. We usually bring project-level margin bands or percentages computed in project accounting, restricted to account leaders and practice heads. That gives enough signal to steer renewal and pricing conversations without exposing salary-driven cost detail.
An integration layer can normalize multiple project accounting or time systems into one set of project and client identifiers for Salesforce. Account leaders then see a combined view of delivery across practices. Over time, as acquired practices move onto the firm's standard platform, only their integration adapters change. Client hierarchies are mapped once, so the same enterprise client is not reported as several smaller ones.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.