Multi-level approvals for Payment Requests
Set the sign-off levels your business needs for every Payment Request
Payment Requests now support multi-level approvals, using the same approval flows already available for Contracts and Spend Requests. Organizations can route each request through multiple stages of sign-off, either for every request or based on its value, giving Finance and Procurement teams greater control over contractor payments at any scale.
Payment Requests are often used for high-value spend, including influencer and content creator campaigns where a single request can be significant. At that level, many organizations need more than one person to review and approve a payment before it is released, in line with their internal financial controls.
Multi-level approvals bring Payment Requests in line with Contracts and Spend Requests, so clients can apply consistent approval policies across their contingent workforce program. Teams can define exactly who needs to sign off and when, while keeping everyday requests moving quickly.
What's new
- Flexible approval flows: Approval flows can be level-based, where every Payment Request passes through every stage, or limit-based, where requests escalate to the next stage depending on the amount. Each stage can include both on-platform and off-platform approvers.
- Default routes on contracts: Hirers can set a default approval route when drafting or editing a contract. If your organization has only one active route, it is applied automatically. If no default is set, the hirer selects a route on each Payment Request and can save it as the contract default.
- Route changes when you need them: Contract owners and collaborators can change the route on an individual Payment Request and, if they choose, make it the contract's new default. Approval then restarts from the first stage, and approvers who were waiting are notified by email that their approval has been withdrawn.
- Clear visibility of progress: Contract owners, admins, and collaborators can see which route applies to each Payment Request and which stage it has reached. Contract approvers can also see the billing type and default Payment Request route when approving a contract.
- Payment Request approver access level: Contract owners can give a team member the new Payment Request approver access level, so the right people can take part in sign-off.
How it works
Payment Request approval flows are set up for your organization by the YunoJuno team. Speak to your account or delivery manager to define your approval stages, approvers, and any spending limits. Once a flow is active, it can be used as an approval route on your contracts.
When drafting or editing a contract, hirers can choose a default approval route for Payment Requests. Every request raised against that contract then follows the route automatically. Contract owners and collaborators can switch to a different route on an individual request if needed.
The first stage of every route is always the contract owner and collaborators. If a contract has no active default route, Payment Requests go to them as a single-stage approval, so requests continue to move through the process.
Approvers receive an email when a request is waiting for them and can action it from the Payment Requests tab in the Approvals dashboard. If a request is rejected, the approver must give a reason, which the contractor can see, and the request's approval progress resets.
Notifications keep everyone informed throughout:
- Approvers are notified when a Payment Request is waiting for their approval.
- Contract owners and collaborators are notified when a request moves to the next stage, is rejected, or is fully approved.
- Contractors are notified when their request is fully approved or rejected.
For limit-based flows, the final stage of each route has no limit, so every request has a clear path to full approval regardless of its value.
Benefits for teams
Multi-level approvals give Finance, Procurement, and contingent workforce program teams confidence that high-value contractor payments receive the right level of scrutiny. Limit-based routes mean larger requests are escalated to senior approvers, while smaller ones stay with the people closest to the work, so control does not come at the cost of speed.
For hiring managers, setting a default route once on the contract removes repeated decisions on every request. Shared visibility of each request's route and stage reduces follow-up messages, and including off-platform approvers means stakeholders outside the platform can still be part of the sign-off process.
Contractors and freelancers also benefit from clearer communication. They are told when a payment is fully approved, and when a request is rejected they receive the reason, so they know exactly what to address.
Check out multi-level approvals for Payment Requests today
Contact your account or deliver manager to set up Payment Request approval flows that match your organization's sign-off requirements.
