All applications611

Find your application

611 applications

Open full catalog

Browse applications by category or open the full catalog.

  1. Estimation & Quote Builder
  2. Features
  3. Service delivery
Feature · Service delivery

Service delivery

Capture delivered service lines and show approval results before billing.

OverviewApproved Not Invoiced
Estimation & Quote Builder · Service delivery

Approved Not Invoiced

Service entries

New
Service entry codeService dateService descriptionEngagementHoursAmount
SEC-46404 OctApproved se-499ENG-69787AMN-123
SEC-51920 OctApproved se-671ENG-21062AMN-545
SEC-35816 OctApproved se-503ENG-701810AMN-969
SEC-43718 OctApproved se-733ENG-756011AMN-604
SEC-90413 OctApproved se-623ENG-288713AMN-760
6 of 6 records
SEC-464Service entries · SE-93833
Approved
Service date04 Oct
Service descriptionApproved se-499
EngagementENG-6978
Hours7
AmountAMN-123
Example screen with sample data

What you can do

Record the work that can be reviewed

Consultant creates a service entry for work delivered on a client engagement. The line records a service date, description, hours, rate, billable flag, team member, and engagement. Its calculated amount and delivery cost give the delivery manager a view of the value and cost of the work. A Draft line can be corrected before submission triggers the approval check.

The Service Entry Approval workflow handles submitted lines. It checks that the line is billable, has hours, and has an engagement. A valid submission moves to Approved and records a Review Decisions row and an operation receipt. If a guard fails, the line stays Submitted and the operation receipt records Failed. Service Reviewer follows that exception with the Consultant rather than treating a failed operation as approval.

How the work is organized

  • Delivery line. Service Entries records what was done, when, for which engagement, by whom, and at what rate.
  • Decision trail. Review Decisions records the decision, reviewer reference, date, and notes written by the service approval operation.
  • Operation result. Operation Receipts separates a successful service approval from a failed attempt so the handoff can be checked later.

What to agree during setup

Name the Service Reviewer for each engagement. Agree how that person checks approved lines and failed submissions against the description, hours, rate, billable flag, and agreed scope. Define who corrects a line that fails the guard and how the reviewer sees it again. A Failed receipt should prompt a correction, not an invoice.

Decide when approved service value is ready for billing review. Approved and Invoiced are distinct statuses; approval of delivery alone does not mean money has been collected. Billing Specialist should reconcile approved lines with invoiced service amount and the engagement’s remaining value before taking an invoice action in the team’s billing process.

Check the handoff on an actual case

A Consultant records ten billable hours of design work at $150 per hour against an Active engagement. They submit the line. The approval operation moves it from Submitted to Approved and writes a decision and successful receipt. Service Reviewer checks the resulting line against the client work. Billing Specialist finds it in Approved Not Invoiced and compares the amount with the engagement’s approved and invoiced service totals.

Now repeat the attempt with no engagement. The workflow leaves the line Submitted and writes a Failed receipt. Consultant links the correct engagement before submitting the line again. The team should be able to distinguish the failed attempt from a rejection decision and from a genuinely approved line. For a line that is Rejected, Rejected Service Entries gives the manager and reviewer a separate correction queue.

What your team sees

  • Approved Not Invoiced — Reviewed service value waiting for billing attention.
  • Rejected Service Entries — Lines that need correction or a delivery discussion.

Follow the work through

See delivery review and client work to collection. Review the data model for the linked records.

What it keeps track of

Data model
Service entries
Delivered service lines billed against an engagement.
Review decisions
Approval decisions recorded against service, time and expense subjects.
Operation receipts
Evidence of executed billing, approval and document operations.
Engagements
Billable engagements with contract value, budget and delivery status.
Team members
Consultants and delivery staff with rates and capacity.

Who uses it

Permissions
Consultant
Submits service lines.
Service Reviewer
Checks approval results and exceptions.
Engagement Manager
Owns delivery context.
Billing Specialist
Follows approved value before billing.

Set up Estimation & Quote Builder your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started