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
- Data model
The tables behind PSA for Software Implementation Partners
PSA for Software Implementation Partners ships with 13 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 13
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Accounts and practice
Clients, Organizations and Consultants establish account ownership, delivery practice and staff rates.
Delivery
Implementation engagements connect client commitments to consultant hours, project expenses and configuration deliverables.
Billing
Go live milestones connect the engagement to milestone billings and payment outcomes.
Evidence
Review decisions, operation receipts and record attachments preserve decisions, operation results and linked files. Users carries account access information.
Every table, by feature
- Client accounts3
- Implementation engagements4
- Consultant work4
- Configuration delivery4
- Milestone billing4
- Review and evidence4
- Shared and settings1
- Clients
Client master records with ownership and billing terms.
Linked to Consultants, Organizations - Organizations
Firm business units, practice groups and regional offices.
- Consultants
Consultants and delivery staff with rates and capacity.
Linked to Organizations
- Implementation engagements
Billable engagements with contract value, budget and delivery status.
Linked to Clients, Consultants, Organizations - Clients
Client master records with ownership and billing terms.
Linked to Consultants, Organizations - Consultants
Consultants and delivery staff with rates and capacity.
Linked to Organizations - Organizations
Firm business units, practice groups and regional offices.
- Consultants
Consultants and delivery staff with rates and capacity.
Linked to Organizations - Consultant hours
Logged consultant time by client and engagement.
Linked to Consultants, Clients, Implementation engagements - Project expenses
Reimbursable and billable engagement expenses.
Linked to Implementation engagements, Consultants - Implementation engagements
Billable engagements with contract value, budget and delivery status.
Linked to Clients, Consultants, Organizations
- Configuration deliverables
Delivered service lines billed against an engagement.
Linked to Implementation engagements, Consultants - Implementation engagements
Billable engagements with contract value, budget and delivery status.
Linked to Clients, Consultants, Organizations - Review decisions
Approval decisions recorded against service, time and expense subjects.
Linked to Consultants - Operation receipts
Evidence of executed billing, approval and document operations.
Linked to Consultants
- Go live milestones
Contractual milestones that trigger billing.
Linked to Implementation engagements, Consultants - Milestone billings
Invoices and receipts raised against milestones.
Linked to Go live milestones - Implementation engagements
Billable engagements with contract value, budget and delivery status.
Linked to Clients, Consultants, Organizations - Operation receipts
Evidence of executed billing, approval and document operations.
Linked to Consultants
- Review decisions
Approval decisions recorded against service, time and expense subjects.
Linked to Consultants - Operation receipts
Evidence of executed billing, approval and document operations.
Linked to Consultants - Record attachments
Files linked to records across the app.
Linked to Consultants - Configuration deliverables
Delivered service lines billed against an engagement.
Linked to Implementation engagements, Consultants
Keys and references
Keep each source identifier stable when importing. Client code identifies a client; engagement code identifies a contracted implementation. The engagement references its client, manager and organization. A configuration line, time entry or expense references its engagement. A milestone references an engagement and a billing references a milestone. Record attachments uses parent table name and parent record id for its parent; confirm those values against the intended record before loading files.
Migration order
- Account foundations. Load Organizations, Consultants, Clients and Users.
- Engagement commitments. Load implementation engagements with client, manager, practice, dates and budget.
- Delivery activity. Load consultant hours, project expenses and configuration deliverables with their references.
- Billing commitments. Load go live milestones, then milestone billings.
- Evidence. Load review decisions, operation receipts and record attachments after their subjects are present.
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.