Story
SAP
Phillips 66Phillips 66 Uses SAP SuccessFactors for Financial Close
Phillips 66, an energy organization in the United States, uses SAP SuccessFactors from SAP to support record to report for controllers and shared services.
Phillips 66 folded SAP SuccessFactors into record to report so controllers and shared services share one view of financial close.
“Controllers and shared services needed a system that would still make sense after the original project team moved on.”
“SAP is the global leader in enterprise resource planning software, with S/4HANA, business technology platform services, and industry cloud applications.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Capability | Controllers and shared services work from the same SAP SuccessFactors record for financial close |
| Capability | Financial close can be reviewed without waiting on a personal export |
| Capability | Named workflow replaces ad hoc routing for financial close |
Story
Inside Phillips 66, record to report used to depend on whoever still had the latest file. That pattern is common in energy groups working out of the United States. Controllers and shared services needed a system that would still make sense after the original project team moved on.
Phillips 66 uses SAP SuccessFactors from SAP as the working layer for financial close. SAP is the global leader in enterprise resource planning software, with S/4HANA, business technology platform services, and industry cloud applications. The practical change is simple: record to report has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What Phillips 66 gets from SAP is a durable place to run record to report and a way for controllers and shared services to see the same financial close at the same time.
