SAP Procure-to-Pay for Utilities: Mapping the Handoffs
A procure-to-pay map should explain who passes what information to whom. Start with a real utility purchase and follow it from the request through receipt, invoice review and final resolution.
SAP Procure-to-Pay for Utilities
Separate process ownership from document entry. The person entering a receipt may not be the person who can confirm that a service was performed satisfactorily.
Follow a purchasing item across the whole process before blaming one stage. The requisition, purchase order, receipt, invoice and payment can each contain a different part of the explanation. Keep their references connected in the review. A discrepancy that appears in finance may have started with an unclear description or an incorrect quantity much earlier.
A practical first pass
- Choose one material purchase and one service purchase.
- Identify the evidence required at each handoff.
- Record the owner of each exception route.
Evaluate a proposed improvement using both routine and awkward purchases. A stocked item, a non-stock item and a service can create different handoffs. Include partial delivery, cancellation and a returned item in the test set. A process that handles only the cleanest purchase is not ready to be treated as the standard for all utility work.
A hypothetical example
A contractor invoice can be entered correctly but remain unresolved because nobody knows who approves the service evidence. The process map should make that responsibility explicit.
Distinguish the physical event from the accounting record of that event. Goods may have arrived without a complete receipt record, or a document may have been entered before the receiving team has resolved a discrepancy. Ask the operational owner to confirm what actually happened. A matched set of system references is useful evidence, but it should not replace the underlying receiving or service confirmation.
Avoid the common shortcut
Do not draw a workflow containing only successful steps. Cancellations, disputes and partial deliveries are part of the actual process.
Give exceptions a specific route rather than a general instruction to contact purchasing. Quantity differences, price questions, missing approvals and supplier-master changes need different owners. Include enough context for the next person to act without repeating the investigation. This reduces the temptation to bypass a control simply because the queue is difficult to understand.
Keep the wider process connected
Plan the exception route as carefully as the normal route. Emergency work, missing material identifiers and late confirmations are predictable situations even when their timing is uncertain. Staff need to know how to record the facts without inventing details. A controlled follow-up process is better than making the initial screen appear complete with information that nobody can verify.
Use examples of acceptable and unacceptable entries in the guidance. Abstract definitions can leave users uncertain about a real request. Show a complete ordinary record, an ambiguous request and an exception that must be escalated. Review the examples with the people who actually submit and approve changes.
Separate preparation, review and resolution in the status record. A task can be prepared but not reviewed, or reviewed with open questions. Calling all of those states complete removes useful information. Define the evidence required for final acceptance and keep unresolved items assigned to someone who can actually make the next decision.
What to take away
Keep a handoff map showing documents, responsibilities, controls and exception paths.
Related reading
Utility Purchase Order Account Assignments; Service Entry Evidence for Utility Contractors; Utility Materials Master Data: Avoiding Duplicate Items.