Story
Oracle
Lloyds Banking GroupLloyds Banking Group Extends NetSuite Across Source to Pay
Lloyds Banking Group, a financials organization in the United Kingdom, uses NetSuite from Oracle to support source to pay for procurement and AP.
Teams at Lloyds Banking Group moved procurement and payables onto Oracle after local tools started to collide.
“Inside Lloyds Banking Group, source to pay used to depend on whoever still had the latest file.”
“Procurement and AP needed a system that would still make sense after the original project team moved on.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Productivity | Fewer stalled items because procurement and payables has a clear owner |
| Productivity | Handoffs in source to pay sit in a shared queue instead of a mailbox trail |
| Risk and compliance | NetSuite is the governed place procurement and AP use for source to pay |
Story
Inside Lloyds Banking Group, source to pay used to depend on whoever still had the latest file. That pattern is common in financials groups working out of the United Kingdom. Procurement and AP needed a system that would still make sense after the original project team moved on.
Lloyds Banking Group uses NetSuite from Oracle as the working layer for procurement and payables. Oracle delivers enterprise applications, databases, and cloud infrastructure, including Fusion Cloud ERP and Oracle Cloud Infrastructure. The practical change is simple: source to pay has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What Lloyds Banking Group gets from Oracle is a durable place to run source to pay and a way for procurement and AP to see the same procurement and payables at the same time.
