A manufacturer with five plants has five sets of supplier relationships, five goods receipt workflows, and five local teams who understand the context behind every delivery. It also has one group balance sheet, one working capital position, and one CFO who wants to see the full AP picture without waiting for five separate reports.
The instinct to centralize AP completely makes sense on paper. One team, one system, one process. The reality is that a remote central AP team processing invoices from plant sites they have never visited produces higher exception rates, slower resolution times, and more frustrated plant managers than a decentralized process with all its inefficiencies.
The operating model that actually works separates what genuinely needs to be centralized from what genuinely needs to stay local and uses technology to connect both without forcing either into a structure that does not fit.
What Drives Multi-Plant AP Complexity
- Goods receipt confirmation requires someone physically at the plant to verify what arrived. A central AP team cannot do this without a workflow that connects them to the receiving dock in real time.
- Plant managers have authority over spending at their sites and expect to approve invoices for their operations. Routing all approvals through a central finance team frustrates plant leadership and slows approvals for time-sensitive purchases.
- Supplier relationships for raw materials and MRO supplies are often managed locally. The plant purchasing manager knows the supplier context that drives exceptions and disputes. A central team processing the same invoice without that context takes longer to resolve it.
- Currency and tax compliance at international plants requires local knowledge of jurisdiction-specific requirements that a centralized team in a different country may not have the depth to handle correctly.
What Belongs at the Center
Vendor master management
The vendor master is a fraud and duplicate payment risk that cannot be managed locally. When five plants each maintain their own vendor records, the same supplier appears multiple times under different names, with different banking details, and often with different payment terms negotiated independently. Centralized vendor master management means one canonical record per supplier, one verified set of banking details, and one sanctions screening result that applies across all plants.
New vendor onboarding, bank account changes, and vendor deactivations all require central approval regardless of which plant initiated the request. This is a non-negotiable control, not a convenience preference.
Payment execution
Payments should execute from a single treasury-connected function that can optimize cash across all plant entities simultaneously. A plant that pays its own suppliers from its own bank account cannot participate in group-level cash pooling, cannot contribute to centralized early payment discount optimization, and cannot benefit from bulk payment terms negotiated at the group level.
Central payment execution does not mean slow payment. It means structured payment with consistent controls, FX management at the group level, and treasury visibility into all outflows regardless of which plant originated the invoice.
Approval policy and controls
The approval thresholds, the segregation of duties requirements, and the exception escalation rules should be defined centrally and enforced by the platform configuration. Plants operate within the policy. They do not set the policy.
Consolidated AP reporting
The CFO's view of outstanding payables, upcoming cash outflows, DPO by entity, and early payment discount opportunity should aggregate all plants into a single view. This requires all plants to process invoices on the same platform with the same field definitions so that the consolidation is a true aggregation rather than a manual reconciliation of incompatible reports.
What Belongs at the Plant
Goods receipt confirmation
The plant receiving team confirms delivery against the purchase order. This must happen at the plant. The automation requirement is a digital goods receipt workflow that the plant team completes on a mobile device or plant-level terminal, with the confirmation feeding directly into the AP three-way match without manual re-entry.
First-touch invoice coding and context
Plant-level AP staff who know the suppliers, the cost codes, and the operational context of each invoice produce better first-pass coding than a central team processing the same invoice without context. Coding accuracy at the plant level feeds directly into the quality of the central GL and the reliability of the cost center reporting that plant managers depend on.
Supplier dispute resolution
When a delivered quantity does not match the invoice, when a price has changed unexpectedly, or when a supplier is claiming for goods that were returned, the plant team with knowledge of the delivery resolves the dispute faster than a central team coordinating across time zones and knowledge gaps.
Local regulatory compliance
Plants in jurisdictions with specific e-invoicing mandates, local VAT treatment, or unique invoice format requirements need local capability to manage those requirements. The central AP platform should support the compliance requirement technically, but local knowledge of the specific regulatory environment is a genuine local capability rather than something that can be fully centralized.
The Technology That Makes the Hybrid Work
The hybrid model is only manageable with a platform that allows local processing within centrally defined rules and that provides a consolidated view without requiring manual aggregation. The specific capabilities required:
- Multi-entity processing on a single platform with entity-level separation of invoice queues, approval workflows, and local GL coding
- A single group-level vendor master with entity-specific payment preferences and local contact details that override for specific purposes without compromising the core record
- Mobile goods receipt confirmation that feeds directly into the three-way match without a manual handoff between the plant floor and the AP system
- Consolidated treasury view that aggregates all entity payables in real time without requiring a nightly report extraction
Common Failure Modes in Multi-Plant AP Projects
- Attempting full centralization before the data layer is clean: central processing of plant invoices with fragmented vendor masters and inconsistent cost codes produces worse results than the decentralized process it replaces
- Leaving payment execution at the plant level: plants that maintain their own payment infrastructure cannot participate in group working capital optimization
- Failing to build the goods receipt digital workflow before going live: without a mobile GRN confirmation capability, the three-way match requires manual intervention for every PO-backed invoice at every plant
- Measuring AP performance only at the group level: if the group touchless rate looks good but one plant has a 60% exception rate, the underlying problem is invisible until it surfaces as a supplier relationship issue or an audit finding
