These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- PSA for Software Implementation Partners
- Features
- Client accounts
Client accounts
Keep client ownership and billing terms connected to the work.
OverviewActive Clients×
PSA for Software Implementation Partners · Client accounts
New
Active Clients
Completion waits for the practice lead
| Client code | Client name | Account owner | Owning practice | Billing terms | Status | |
|---|---|---|---|---|---|---|
| CC-944 | Client 148 | CNS-4029 | ORG-9155 | Net 15 | Active | |
| CC-897 | Client 459 | CNS-9717 | ORG-1841 | Net 30 | Active | |
| CC-653 | Client 516 | CNS-2159 | ORG-3193 | Net 45 | Active | |
| CC-221 | Client 747 | CNS-2429 | ORG-8394 | Net 60 | Active | |
| CC-377 | Client 497 | CNS-2919 | ORG-4257 | Due on Receipt | Active |
6 of 6 records
CC-944Clients · CLN-73614
Net 15Client nameClient 148
Account ownerCNS-4029
Owning practiceORG-9155
StatusActive
What you can do
Client accounts in daily work
A practice lead starts with the client record. The client name, industry, primary contact and billing terms give the delivery team an agreed commercial starting point. The account owner points to a consultant and the owning practice points to an organization. When a prospect becomes an active client, the team can distinguish a live account from one still being qualified.
An implementation engagement then links back to that client. The engagement carries its own manager, owning organization, dates and budget, so the client record does not have to stand in for a project plan. A practice can serve the same client through several engagements while keeping each engagement’s contract value and delivery result separate. The client count rolls up from those engagements for a useful account overview.
How the work is organized
- Account context. Keep the primary contact, industry and billing terms on the client record.
- Practice owner. Link the account owner to a consultant and the owning practice to an organization.
- Separate engagements. Open each implementation from the client while retaining its own manager, dates and contract value.
What to agree during setup
- Account ownership. Decide who maintains the client record and who can change billing terms.
- Practice mapping. Link each client to the organization responsible for delivery.
- Status policy. Agree when a prospect becomes Active or moves on hold.
Agree a representative implementation for rehearsal. Use the same client and engagement across delivery, service review and billing. Keep the person who enters a record distinct from the person who makes the business decision when the team requires that separation. Make the ownership rule clear before a busy billing period, because a status alone does not explain who should take the next action.
Check the handoff on an actual case
Use a client with an agreed software rollout and a named account owner. Check that the active client opens the intended engagement and that the engagement points back to the same client. Change the billing terms only through the person who owns that decision. Then open another engagement for the same client and confirm its scope and contract value remain independent. A manager reviewing the second engagement should see the right practice and contact without copying client details into free text.
The reviewer should open the source record behind each amount and compare it with the engagement. If a correction is needed, keep the earlier outcome visible and explain the new one in the appropriate decision or operation record. A manager should be able to identify the client, the responsible person and the next action without reconstructing the history from messages.
What your team sees
- Active Clients — Check ownership and billing terms for clients receiving delivery work.
- Client Prospects — Review prospective accounts before opening a contracted implementation.
Follow the work through
Start with Establish engagement and use implementation planning to rehearse the handoff with your team.
What it keeps track of
Data model- Clients
- Client master records with ownership and billing terms.
- Organizations
- Firm business units, practice groups and regional offices.
- Consultants
- Consultants and delivery staff with rates and capacity.
Who uses it
Permissions- Practice Lead
- , Engagement Manager use these records for their assigned decisions and follow-up.
- Admin
- Maintains access and record configuration.
Set up PSA for Software Implementation Partners your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.