What to Centralize Across Portfolio AP vs Keep Company-Specific

1. Centralize the platform: run one AP platform across companies. 2. Centralize controls: apply one approval and audit framework. 3. Centralize standards: standardize coding and vendor onboarding. 4. Centralize reporting: define metrics consistently across companies. 5. Localize the ERP: keep each company's ERP as its system of record. 6. Localize approvers: keep approval ownership with local budget owners. 7. Localize coding dimensions: respect each entity's ERP structure.

The things to centralize are the ones where consistency and control create portfolio value. A common AP platform gives every company the same workflow and gives the portfolio one place to see everything. A consistent control framework, with the same approval authority model and segregation of duties, gives uniform control across companies that often arrived with their own ad hoc processes.

Coding and vendor-onboarding standards, and consistent reporting definitions, complete the centralized layer. Standardized coding lets the portfolio roll up and compare spend, a common vendor-onboarding standard reduces fraud and data inconsistency, and consistent reporting definitions make metrics comparable across companies. These are the framework-level decisions that belong portfolio-wide.

The things to keep company-specific are the ones tied to each company's systems and operations. Each company's ERP stays its system of record, because consolidating ledgers is a separate, major undertaking and is not required to standardize the process layer. Entity-specific coding dimensions stay local too, since each ERP has its own structure that the portfolio standard maps to rather than overrides.

Local approvers and vendor relationships also stay with each company. The approval framework is centralized, but the actual approvers are the local budget owners who hold the context to judge spend. Vendor relationships often have a local dimension that the company manages. Centralizing the framework while keeping these local is what lets standards apply without erasing the context that makes approvals and relationships work.

The unifying principle is to centralize the framework and localize the execution within it. The portfolio sets the platform, the controls, the standards, and the reporting definitions, and each company executes within that framework using its own ERP, approvers, and context. This gives the portfolio consistency and control without imposing a uniformity that ignores each company's reality.

This balance avoids the two failure modes. Over-centralizing, by pulling approvals away from local owners or forcing identical ERP structures, breaks the context that makes AP work. Under-centralizing, by letting each company keep its own platform, controls, and standards, forfeits the consistency and control a portfolio needs. The framework-versus-execution split threads between them.

Stampli supports this split by running as one AP platform across companies while integrating with each company's ERP and keeping it as the system of record. The portfolio gets a common workflow, control framework, and standards, while each company's ledger, dimensions, and structure stay its own.

Because Stampli enforces segregation of duties by design, supports standardized coding mapped to each ERP, and offers a common vendor-onboarding portal, the centralized framework applies consistently. Role-based access and multi-entity support let central standards coexist with local approvers and local execution, so budget owners in each company still approve their own spend.

Centralized visibility across entities gives portfolio leadership one view, while each ERP remains authoritative and every action is captured in an immutable audit trail. The framework is centralized in Stampli, and the execution stays local within it, which is exactly the split portfolio AP design calls for.