1. Recruitment Search PSA
  2. Implementation and migration
Reference

How a Recruitment Search PSA rollout works

Start with a search mandate that can be followed through delivery and fee collection.

  1. Agree the operating scope

    Select a client search with a known lead consultant, fee value, budget hours, milestone and payment terms. Name the partner, delivery reviewer and finance owner.

  2. Map source records

    Import organizations and consultants before clients and mandates. Use stable codes to link delivery, time, expenses, milestones and payments.

  3. Configure a bounded pilot

    Enter one active mandate and a representative delivery line. Submit it, run approval and inspect the review decision and operation receipt.

  4. Rehearse billing and collection

    Approve a milestone with an amount and mandate, run the invoice operation and follow its payment through collection. Test missing amount and missing mandate failures as well.

  5. Reconcile and release

    Compare delivered, approved, invoiced and received amounts with the source records. Review access by role, resolve failed receipts and agree who will handle the first live exceptions.

What the customer provides

  • Client list, partners, billing terms and mandate agreements.
  • Consultant roster, bill and cost rates, capacity and practice ownership.
  • Mandate budgets, delivery dates, milestone amounts and due dates.
  • Opening fee invoices, payments, time, expense and supporting files.
  • Approval owners and the policy for correcting submitted work.

Changing it afterwards

Review changes to fee values, rates, statuses and approval ownership with their business owners. Retain the source reference and earlier outcome when a delivery or invoice operation is retried. Rehearse a failing case alongside a successful one before extending the configuration.

Prepare the pilot.

Set up Recruitment Search PSA your way.

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

How to get started