Record the accepted customer order, paying entity, assignment or placement reference and agreed charging basis before operational handoff. Separate permanent placement fees from time-based assignment billing, and preserve any conditions requiring review. Keep employment and candidate decisions under their responsible processes rather than implying that a sales order settles those obligations.
Understand the decision
A customer may request several assignments across locations while using one procurement contact and another invoice recipient. Rates can change by assignment or effective date. The administrative record must identify the actual approved arrangement so recruiters, account managers and finance do not rely on informal messages.
Work through the requirements
- Identify assignment and customer billing references.
- Record the accepted charging basis.
- Separate commercial and employment decision owners.
| Record or decision | Why it matters |
|---|---|
| Customer order | Defines accepted commercial requirements and payer. |
| Assignment reference | Connects operational records to billing scope. |
| Rate approval | Preserves agreed amounts and effective dates. |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
Using one customer-level rate for every assignment can misstate charges and hide approved differences. Preserve the assignment reference and effective commercial terms, and review exceptions before operational information becomes an invoice proposal.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for Staffing agencies in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Odoo 19: sales quotations and invoicing methods ↗Odoo 19: timesheet configuration and recording ↗Odoo 19: project management ↗