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.
- IT Services PSA
- Features
- Service delivery
Service delivery
Keep delivered service lines, review outcomes and evidence tied to an engagement.
OverviewApproved Not Invoiced×
IT Services PSA · Service delivery
New
Approved Not Invoiced
Service entries
| Service entry code | Engagement | Team member | Hours | Amount | Status | |
|---|---|---|---|---|---|---|
| SEC-917 | ENG-9731 | 9 | AMN-982 | Approved | ||
| SEC-315 | ENG-8755 | 2 | AMN-258 | Approved | ||
| SEC-424 | ENG-2658 | 13 | AMN-377 | Approved | ||
| SEC-777 | ENG-3130 | 14 | AMN-731 | Approved | ||
| SEC-834 | ENG-5586 | 12 | AMN-531 | Approved |
6 of 6 records
SEC-917Service entries · SE-71533
ApprovedEngagementENG-9731
Hours9
AmountAMN-982
What you can do
Service delivery
Keep delivered service lines, review outcomes and evidence tied to an engagement. A consultant enters the service date, description, hours, rate, billable flag, engagement and team member. The calculated amount and delivery cost help the manager read value alongside effort.
How the work is organized
- Record the work. A consultant enters the service date, description, hours, rate, billable flag, engagement and team member. The calculated amount and delivery cost help the manager read value alongside effort.
- Submit for review. A draft service line moves to submitted. The Service Entry Approval workflow checks that it is billable, has hours and has an engagement. A valid line becomes approved and writes both a review decision and an operation receipt.
- Resolve exceptions. A line that fails the check stays submitted and gets a failed operation receipt. The manager can inspect the record and correct the source before trying again. A rejected list also keeps lines marked rejected visible.
The team can follow each decision through its source record. References connect work to the client engagement, while statuses keep the current queue readable. Review a record before changing its status so the next person can understand why it moved.
What to agree during setup
Agree who submits lines, who corrects incomplete descriptions or engagement links, and how the team distinguishes a failed validation receipt from a recorded rejection decision. Set rate ownership before work starts. Keep record ownership clear when a colleague is away. Use the status lists during a pilot to make sure submitted items are visible to the person expected to act.
Check the handoff on an actual case
An engineer records four billable hours on an active engagement and submits the line. The review workflow validates its hours and engagement and records approval evidence. The manager sees it among approved lines that have not been invoiced. A second line fails validation; it remains submitted with a failed receipt. The manager reads the line and its receipt, corrects the source and reviews it again before billing.
The manager reads the service line beside its review decision and operation receipt. A failed receipt leaves the line submitted; a successful review moves it to approved. Billing Specialist uses Approved Not Invoiced to find accepted lines, then checks the engagement and amount before preparing the billing handoff.
What your team sees
- Approved Not Invoiced — Approved service lines ready for billing review.
- Rejected Service Entries — Rejected lines that need the delivery team’s attention.
Follow the work through
Follow the related process and review the data model when preparing a pilot.
What it keeps track of
Data model- Service entries
- Delivered service lines billed against an engagement.
- Engagements
- Billable engagements with contract value, budget and delivery status.
- Team members
- Consultants and delivery staff with rates and capacity.
- Review decisions
- Approval decisions recorded against service, time and expense subjects.
- Operation receipts
- Evidence of executed billing, approval and document operations.
Who uses it
Permissions- Consultant
- Records service.
- Engagement Manager
- Resolves exceptions.
- Billing Specialist
- Reads accepted lines.
Set up IT Services PSA your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.