Systems integrators

How PSA for Software Implementation Partners is set up for you

An integrator coordinating implementation work across practice groups can use organizations to identify the owning practice and consultants to show the people delivering each engagement. Time, expense and configuration lines stay tied to the same customer commitment.

Choose one client and one real implementation. Enter its contract value, budget hours, delivery dates, engagement manager and owning organization. Give each consultant the right practice, role, rate and weekly capacity. This first case should contain a time entry, a project expense, a configuration deliverable and a go-live milestone so the team can follow the same work from delivery into commercial review.

Let the delivery consultant submit a valid billable configuration line. Confirm that the review decision and operation receipt refer to the right source. Then try a line without its engagement and check that it remains Submitted with a Failed receipt. The service reviewer can use that exception to agree who corrects source records and how the team communicates the result.

For billing, ask the billing manager to review an approved milestone with an amount and engagement. Follow its invoice result, then create the milestone billing and mark collection Received only when the team has the payment information. Compare the billing with the milestone's payment totals. Open the Implementation Margin Desk and trace any difference between contracted, delivered and billed values back to the engagement.

Before wider use, agree who owns client terms, who approves a milestone for billing and who follows a failed operation. Review access for consultants and managers using real records from the pilot. Use [implementation planning](/psa-for-software-implementation-partners/implementation) to prepare those decisions and [the data model](/psa-for-software-implementation-partners/data-model) to map existing client and engagement records.