Reroute invoice approval after a cost-center reorganization

Freeze the current workflow and organization facts

A cost-center reorganization can strand invoices with inactive approvers or create pressure to code everything to the new structure. Preserve the invoice, current coding, workflow status, original requester, approvers, timestamps, rejection or delegation notes, purchase order, service period, amount, currency, and due date. Record the old and new cost-center identifiers and the reorganization effective date from a controlled source. Do not cancel the workflow or overwrite the old owner until the transition rule and invoice population are understood.

Determine what changed: manager ownership, cost-center code, legal entity, department hierarchy, budget responsibility, approval threshold, or all of them. These changes have different control effects. A new manager may approve an old code, while a retired code may require finance mapping. A legal-entity move cannot be treated as a simple routing update. Capture the approved organization map, effective dates, delegation records, and system configuration owner. AP prepares the evidence; finance and business owners decide coding and authority.

Map economic ownership across the effective date

Compare the invoice’s delivery or service period, order date, invoice date, receipt date, and posting period with the reorganization date. A service spanning the change may need allocation, but AP should not invent a proration rule. Show the amounts and periods available from the supplier or contract and ask finance for the approved basis. For goods, receipt site and purchasing entity may control different questions from budget ownership. Keep commercial acceptance, coding, and approval authority distinct in the packet.

Review purchase-order and non-PO paths separately. A purchase order may retain its original cost center until formally amended, even when the manager changed. A non-PO invoice may rely on an effective-dated coding matrix. Identify open commitments, receipts, accruals, and prior invoices under the same agreement. Do not change an order reference to force new routing. Purchasing owns amendments; the service or goods owner confirms acceptance; finance owns accounting mapping. Record the answer for this invoice without assuming it applies to every transition item.

Reroute approval without rewriting history

Map the authorized approval route using the current matrix and any documented transition rule. If the former approver is inactive, use approved delegation or reassignment rather than forwarding the task informally. Preserve completed approvals when policy allows; do not make the history appear as if the new owner approved earlier events. If thresholds changed, identify which rule applies to the invoice and cite the owner decision. A backup approver’s authority should include scope and dates, not merely a manager’s name in chat.

Keep the aging clock factual. Record invoice receipt, first complete packet, each owner handoff, response, and current blocker. A reorganization may explain delay but should not reset the invoice’s age. Send one structured request containing the document, affected period, proposed mapping, prior approvals, and decision needed. Avoid parallel requests to several managers that can produce conflicting approvals. Escalate through the defined ownership chain, and tell the supplier only the supported status through an approved contact channel.

Verify the final coding, approval, and aging record

After rerouting, compare the final ERP coding and workflow with the approved mapping. Confirm buyer entity, cost center, account, tax, order, service period, approval threshold, approvers, and posting date. Check for duplicate workflow instances or an abandoned parked document created during reassignment. If the invoice was split, the parts must sum to the source and retain the allocation authority. Preserve the original route and the reason for change so the audit trail shows a transition, not unexplained editing.

Close with the organization source, effective-date analysis, coding decision, delegation or reassignment, approval record, posting, and remaining transition issue. Review cases by old cost center, new owner, exception type, and time to decision. Repeated stranded invoices may reveal incomplete workflow maintenance or supplier routing instructions. Outsourced AP can manage the queue and evidence, while company owners retain budget authority, coding policy, organizational design, and payment release. The result should show why this invoice reached this approver and this cost object.

Test the route across the transition date

Use two invoices from the same supplier to test the boundary: one covers service completed before the reorganization, while the other covers the first full period after it. Add a third invoice that spans the effective date. The procedure should preserve the old owner and code where the transition rule requires them, use the new route where appropriate, and send the spanning case to finance for an approved allocation. If all three automatically follow the current manager, the process is ignoring economic period and effective-dated authority.

Review the first close after reorganization for stranded work. Compare old and new cost-center queues, parked documents, open purchase orders, receipts, accruals, and approval tasks. Link each exception to an owner and do not reset age when it moves. Confirm that supplier communications use the same case reference after rerouting. This wider check proves that the organization update changed responsibility without losing obligations, duplicating workflow, or rewriting approvals that were valid under the former structure.

Update durable routing references after the first cases prove the transition rule. Supplier instructions, non-PO coding aids, approval matrices, and queue ownership should point to controlled sources with effective dates. Do not paste temporary manager lists into invoice notes. A maintained source reduces inconsistent routing while preserving the ability to explain which organization rule applied to an older invoice.

When the hierarchy is stable, retire temporary delegations through controlled access review and verify that no broad approval role remains from the transition. Sample later invoices to confirm that normal routing now reaches the intended owners without manual forwarding. Record any persistent exception in the workflow backlog rather than extending emergency access indefinitely.