Reconcile a group training booking with a customer purchase order by comparing the agreed booking scope and customer identity against the current PO record. Show differences for staff review rather than changing the booking to make the figures agree. The handoff should explain what has been checked and which decisions remain open.
Start with the order-reference, invoicing, and booking features in the existing training platform and CRM. A consistent PO field and approved customer mapping may resolve the problem without custom software. A separate review tool should focus on a specific gap between the booking evidence and finance handoff.
Compare the booking scope explicitly
Fictional Alder Learning books course TR-72 for customer Brookfield Ltd. The booking confirms twelve attendees (delegates) on 20 October, while PO-441 states ten places and names Brookfield Services Ltd. The course title is abbreviated on the PO. These differences should not be treated as one generic mismatch.
| Field | Approved booking | Purchase order | Review question |
|---|---|---|---|
| Customer entity | Brookfield Ltd | Brookfield Services Ltd | Which entity placed the order? |
| Course | Supervisory Skills, TR-72 | Supervisor workshop | Is the scope equivalent? |
| Delegate places | 12 | 10 | Has an amendment been approved? |
| Date | 20 October | Not stated | Is a date reference required? |
The abbreviated course title may be an approved alias. The entity and quantity differences need separate evidence. A staff member should confirm the intended agreement before the finance team treats the records as aligned.
Preserve the distinction between places and people
A booking may reserve twelve places while only nine attendee names have been supplied. That does not necessarily mean the booking quantity should become nine. Keep reserved capacity, confirmed attendees, attendance, and billed scope as separate concepts.
If a delegate substitution occurs, the number of places may remain unchanged. If two places are cancelled, the effect on the booking and billing depends on the agreed process. The checker should record the change and route the commercial question to staff, rather than infer a credit or revised charge.
Use stable customer and course identifiers
Customer names can be abbreviated or shared across related entities. Use the booking system's approved account ID and a reviewed mapping to the PO's named entity. For Alder Learning, carry the account identifier through the booking export and preserve the reviewed relationship to the customer entity named on the PO.
For courses, preserve the course ID, scheduled event ID, and any approved title alias. A reusable course and a specific delivery date are different records. Matching the course title alone can attach a PO to the wrong cohort when the customer books the same programme several times.
Check the integration path itself
Pipedrive documents that required fields do not stop deal progression when fields are updated through imports or third-party integrations. If a CRM is part of the booking handoff, test the actual path used rather than assuming that a required field on a screen guarantees complete imported records.
- Keep the PO document and extracted fields linked.
- Record amendments and their approval evidence.
- Flag missing or ambiguous customer mappings.
- Distinguish unsupported balance checks from completed comparisons.
- Show the finance reviewer which booking version was checked.
If prior billing or remaining PO allocation is in scope, use current authoritative history and avoid counting the same booking twice. Without that history, the tool should not claim to know the available balance.
Pilot the finance handoff
Use fictional cases with an entity mismatch, extra places, an approved amendment, the same course booked for different delivery dates, and a delegate substitution. Ask booking and finance staff to label the expected outcome together. This reveals disagreements in the process before they are embedded in software.
Measure incorrect matches, unresolved questions, and time spent reconstructing the agreement. Clear Anvil's workflow approach can help define a bounded administrative review. Staff retain authority over booking terms, charges, invoicing, and any customer communication; a matched record is not evidence that a payment has been authorized or received.
Sources and further reading
AI-assisted research and writing, checked against the linked sources. Worked examples are fictional. Product features can change; confirm the details in your own account.