PeopleSoft Reviews

We use this for HR management.

This solution integrates very well with other products which is helpful.

I would like for the initial rollout process to be completed faster so that it can be implemented in a more efficient manner.

I have been using PeopleSoft for two years.

It is a stable product. Even though it is a cloud-based product, it still has good availability and we do not face any downtime.

This solution is scalable.

The initial setup takes a long time, as does any cloud-based solution.

I would consider this to be an expensive product, but the quality justifies it.

I would recommend this product to many potential customers; however, I do not believe that the price is justifiable for smaller companies.

I would rate this an eight out of ten.

My primary use case is for global HR and payroll.

PeopleSoft is well integrated and has excellent tools to enhance or amend according to business practices. You are also provided with professional help, which means everything can be done without too much consulting. The product includes effective dating, numerous data analysis tools, even for big data, and self-service to handle pages, screens, development, and so on.

The most valuable features are the functionality to take care of HR and payroll needs, SQR and SQL tools, and good security.

An area for improvement would be PeopleSoft's global payroll capabilities, which could be easier to use. In the next release, I'd like to see multifactor authentication for self-service be added as an inbuilt feature.

I've worked with PeopleSoft for twenty years.

PeopleSoft is a solid product - no other HR package gives the same flexibility.

PeopleSoft scales up very well.

The initial setup is straightforward and can be completed quickly, though a totally new implementation may take a little longer.

This is one of the cheapest solutions available, and it's also one of the best.

PeopleSoft is easy to develop and maintain. I would rate this solution as nine out of ten.

We primarily use the solution for our payroll needs and in human resources. These are the areas in which I have expertise. 

I am acquainted with versions 8.8 and 9.2.

The solution allows us to explore the databases and enables people to properly develop their work. 

The main issue we have with the solution is that it is very expensive. This presents an issue when it comes to tabulating the many tariffs which exist in Mexico. 

We find the technical support to be very difficult, as it is not local, and we tend to receive a response only the following morning. Response time takes very long and requires a person to be awake night and day to benefit from it. 

I have been working with PeopleSoft for the past 14 years. 

We have encountered no bugs or glitches with the solution. 

The solution is easy to scale, expand and make bigger. 

We find the technical support to be very difficult, as it is not local, and we tend to receive a response only the following morning. Response time takes very long and requires a person to be awake night and day to benefit from it.

Deployment takes a minimum of six months and I speak from the vantage point of someone who has a year-and-a-half of experience with my company, primarily in the area of implementation. 

The main issue we have with the solution is that it is very expensive. This is an issue when it comes to tabulating the many tariffs which exist in Mexico.

The calculating of the taxes in Mexico is an issue which many companies face, as this must be done every two weeks. 

I would recommend the solution to others. 

I rate PeopleSoft as an eight out of ten. 

PeopleSoft is used for human capital management in my organization. It can manage a lot of business areas, such as payroll, time and labor, and absences.

The solution is very good and we have been using it for a very long time keeping us organized.

PeopleSoft is a good core system. It has a lot of functionality. They frequently update the solution and recently they have added some good enhancement features for higher education. We just switched to the new fluid interface and that is working very well for us. It is very good.

Employees can use PeopleSoft to input their time and their own absences. Additionally, they can look at their paychecks and configure their direct deposits.

PeopleSoft should be more flexible with the configuration. There should be less coding and more configuration.

I have been using PeopleSoft for approximately 30 years.

The solution is very stable, it is a senior or mature solution.

PeopleSoft is scalable. We are decreasing employees versus increasing right now, but it has worked well for us. We are using the solution extensively in our organization. We plan to increase usage.

We have approximately 9,000 employees using the solution in my organization.

The product strategist from PeopleSoft is very good. I have not contacted the support myself but I have heard they are good.

We have used other systems in the past. The organization is a University and we have been here for a long time.

The initial implementation is complex. Everything is complex when you first start using a new system. If someone tells you it is not complex, they can not be telling the truth. However, the most recent upgrade from 9.1 to 9.2 was pretty good.

When we first implemented the solution we used consultants but recently we did the upgrade of the solution in-house. We saved a lot of money.

We have an IT team of four who do the maintenance, checkups, updates and patching. Additionally, they answer user help requests. We have an additional three or four developers and administrators that help out during projects.

We are a University and the cost and license are negotiated privately.

We did a complete evaluation of other solutions, such as cost and customer responses, and we determined PeopleSoft was best suited for us as a University.

PeopleSoft is a stable solution and it has a lot of functionality. Additionally, it has good product strategist and user input support.

I rate PeopleSoft a nine out of ten.

We're a consulting company, therefore, we get involved in all kinds of use cases.

PeopleSoft is used for usually larger organizations and some middle tier. However, usually, organizations that are maybe 2000 employees or two and a half billion dollars or more tend to be users. They use it primarily for back-office systems, finance supply chain, human resources, payroll benefits, that kind of stuff. That includes recruiting and everything associated with HCM. It's one of the primary ERP systems.

The most valuable feature is that it's wide and broad and it does about everything anybody needs in a major organization from a back-office systems point of view. 

It's a mature product. I've been using it since 1994. It came out maybe a few years before that. It's matured over the years to where, from a back-office system point of view in those primary areas, if you want an all-inclusive system, you can do almost anything you need to do with PeopleSoft without having to buy other third party systems to bolt on to it.

They continue to improve and support the product. The latest announcement was that they're going to continue to support it through 2032. However, every year they add a year or two to that. They confirm their outgoing support for 10 years almost every year.

It's a real contrast between things like Workday and Oracle cloud. The biggest challenge we see as consultants from an Oracle cloud and Workday point of view is that you cannot customize those systems to better fit your business processes. Companies that are smaller and that are less complex tend to go with Oracle and Workday. The big advantage there is they don't have to do any upgrades. However, they're almost forced into the changes if there are new versions for these cloud systems. The good news is you don't have to upgrade them. The bad news is it may not support all your business processes as you want. Therefore, you have to change your business processes to fit the software.

The biggest disadvantage with things like PeopleSoft is that they do continuous support and fixes and upgrades. You get to choose when you want to implement that upgrade. However, in order to keep up, you have to upgrade. The biggest challenge with PeopleSoft is it's a trade-off between feature functionality and the pain of going through those upgrades. And when you upgrade, you've got to do some work. You have to look at what's available in the new version, figure out whether we're going to use that or not, and turn it on or not. On top of that, it's got to go through an implementation process.

Most people do about one upgrade per year. Some people do two, and some people get way behind. However, in order to take advantage of what they buy and pay for, they need to really do probably at least one upgrade a year. And it's a minor upgrade. It's not the kind of upgrade we used to think of that people did once every five years that was almost a reimplementation. In upgrade terms, it's a minor upgrade, however, it is an upgrade.

The difference in PeopleSoft and cloud version is the trade-off between not being able to do any customization and being forced into upgrades almost monthly. You don't have a chance to take your time. You don't have a choice when you do it. It just happens.

Within the company, we've been dealing with PeopleSoft for 15 years. I personally have been dealing with PeopleSoft going back to 1994. I have many, many years of experience working with it.

I would say their tech support is good. I don't have a problem there. They've been doing this a long time, so they know how to do it.

I've also used SAP - and have about five years of experience with it.

The software comes with a fee, with a license fee. The upgrade software comes with a license fee. However, it takes their staff time and resources to go through that. Sometimes customers will hire a consultant firm like us to help them get through it. That would be an extra cost, technically speaking.

The cost varies by license and license type. Many times, it's so much per user, and depending on which software modules you're using. It depends on the modules you're using and how many users you have using that module.

Some people buy what may be called an enterprise-wide license, where it's not really based on the number of users. You get more of a flat cost for that and the users may not be impacted. I haven't gotten involved in that in a while, therefore, I'm not sure how it works.

We're a PeopleSoft partner. We're primarily an Oracle and are a PeopleSoft consultancy where we implement and help people use the PeopleSoft systems. Now we're combining that with UiPath, and so most of the things we do are going to be PeopleSoft system related.

Having been in this business for 25 years or so, my biggest advice for PeopleSoft clients would be the same for any software client - that whenever they implement it, that they do it right and not try to do it cheaply.

Once they do it right, they will realize the benefit from doing it right forever, from then on. If they do it on the cheap to take shortcuts, they will pay the price for taking those shortcuts until they get around to making the investment to fix it. Customers are often a victim of themselves by trying to do it too cheap.

For example, I had one large enterprise client that asked their consulting firm how long it was going to take to put in PeopleSoft. They were putting in about everything PeopleSoft offers. It was a major implementation for the financial supply chain, human resources, payroll benefits, all that stuff. They had something like 130,000 people. It was a big, big corporation.

The consultant company came back and said, "Probably two years, maybe as soon as 18 months, but probably two years to get it implemented and into production from the time we actually start." The company came back and gave them six months, and the implementation was a disaster. The company tried to blame it on the consulting firm. However, they said, "Hey, man, you gave us six months and we should have taken two years for an organization of your size and complexity."

That's a little more than typical. Lots of times people will, instead of 18 months, take 12 months or 15 months. The more they try to shortcut the implementation, the more problems they create for themselves.

The biggest advantage - whether they're doing PeopleSoft, SAP - et cetera - for software companies and the clients, if they're going to put in a major software system, don't try to do it the cheapest you can. Do it the best you can. If you do that, it will pay off in spades. If you don't, it will screw you. That's the biggest advice I would have.

I'd rate the solution at a ten out of ten.

We are not deploying PeopleSoft for our internal process, but we are implementing PeopleSoft to other organizations. Clients primarily use it for their financials, for the HCM, and some of them do use it for their supply chain.

The financial capabilities are great.

We really like the HCM.

It's great for helping users deal with their supply chain.

The stability is quite good.

The solution has the potential to scale. 

It's very easy to integrate with other solutions.

I'm not a direct user. I'm more of an implementor. Therefore, I can't speak to what may be missing. If we do need to add something, we can do so for the client via extensions. I'm not sure what a client would like in future releases.

There can occasionally be complexity in the initial setup.

The pricing could be lower.

We have been working with this solution for almost six or seven years. It's been a while. 

The stability of the solution is excellent. There are no bugs or glitches. It does not crash or freeze. It's reliable. 

The scalability is fine. We don't have any issues if we need to expand. That said, we haven't had any situations where people wanted to expand anything. Of course, if it also happens it's fine.

We have about 15 clients on the solution so far.

Technical support has been fine. They are helpful and responsive. We're happy with the level of support we get. 

The initial setup can be straightforward or complex. We've dealt with both types of implementations. It really depends on the client and their requirements. 

We tend to implement this solution for our clients. 

This solution offers a perpetual license.

While I cannot compare the solution directly to others on the market, I can say that it would be ideal if the pricing was a bit less.

We are an implementor and a partner of Oracle.

In our client's environment, we are using the latest version of the solution. I can't speak to the exact version number.

I'd recommend the solution to other companies, however, it all depends upon the maturity of the customer, and its ability to adapt to this Tier 1 ERP's expertise.

I'd rate the solution at an eight out of ten.

We use it for financial books. It is used for bookkeeping, accounting, and reporting.

It is on-premise, and the next logical step in the journey is to either take it to a public cloud such as GCP or go for SaaS.

It is a customizable product. We can customize it based on our needs, which is one of the features that I like about PeopleSoft. 

As far as financial accounting is concerned, the user interface is very good. You can also configure Chart of Accounts for all performance insights. 

Scalability is not there in PeopleSoft. Its performance and resilience are also very bad. When you're trying to stretch it, it breaks. It is not resilient. 

It is also not stable. It is stable as far as data is concerned, but the infrastructure is not stable.

I have been using this solution for more than 13 years.

It is not stable. It is stable in terms of data, but it is not stable in terms of infrastructure. This is because PeopleSoft has to rely on Oracle and Microsoft for the underlying infrastructure stack, so it boils down to how reliable these components are. From what I have seen, Windows is not reliable, and therefore, the time it takes for transaction processing is not good. It takes a long time.

It is not scalable. When you're trying to stretch it, it breaks.

Their technical support is not that good. Because we've done so much customization, they don't support us. They support only out-of-the-box features.

It was complex. It was done 15 years ago. I wasn't there when the installation was done, but it was quite complex.

I am not satisfied with this solution because its performance is not good. Everything Oracle promises is under-delivered. For example, version 12c of Oracle Database promises an in-memory capability feature, and they say that in-memory makes your workload super fast, but we haven't seen that improvement. It is a case of overpromising and under-delivering. It is also very difficult to adopt the features that Oracle keeps releasing. PeopleSoft is certainly very flexible, but we cannot use the new features.

I wouldn't recommend this solution because PeopleSoft is now the end of life. There are no new customers for PeopleSoft. I wouldn't suggest anyone to go for it. It is a dying product. Even though Oracle says that it will be supporting PeopleSoft until 2030, you shouldn't go for PeopleSoft.

I would rate PeopleSoft a six out of ten.

I basically deal with order management, purchasing order, inventory and accounts receivable.

In general, this solution is user-friendly and also performs well. There are two types of forms. One is a standardized form, which you can define things into. The other, you can customize so more repetition can be done in an even manner. That way, it can be designed for what the public or user actually wants. It's not very tough for any person, or layman to understand exactly what the screen requires one to do.

I believe this software is quite easy to work with, because I have used other software, such as SAP. I find Oracle and SAP are both easier to work with than other apps.

The other reason I use this solution is because I have only worked for one and a half years with SAP, whereas I have been working with Oracle for nine years, so I have more experience in Oracle and I find it more user-friendly.

I think the inventory part it should be simplified. There is the GR, or Good Receipt note, which is the time that the materials come in, and the workdays, etc. There is a lot of shuffling through pages, which creates a lot of problems for our users. They don't know which page to go to, where to create a GR, or where to create a stock entry. In other words, all the information is very daunting. It's very easy for people to understand and get better clarity over it.

I would like to see order management or purchase order screens, with all of the information there on a single line, so you just have to scroll the page to the right side to view all of the information. If you work in inventory, however, you have to keep on changing the screen, one after another. I think that is not perfect, so improvement can be done here.

In terms of additional features, I would like to see a list of employees entered into the organization, their attendance, payroll, and other things that are more linked to Oracle. Only the name of the employee which is entered into the Oracle Master is there, but the in and out system of an employee and other things like payroll, salary, etc., are not included in Oracle. For those things, we have to use another software or ERP.

For human resources, we have one ERP and for daily transactions, we have another ERP. I think Oracle can take this part of the detailed system and attendance into Oracle so that it is right there in one ERP. Oracle could handle all of the transactions, whether they are in human resources, accounting, supply chain, or any other department.

I've been working with Oracle PeopleSoft for more than nine years.

Sometimes when a month is closing, there is a huge number of invoices that are being generated and many orders being placed by customers. At that time, there is a huge invoice created and the server cannot handle the capacity. Then the invoice gets stuck up in between. The time-lapse is due to this and due to the fact that the order cannot be generated during this time, may mean that two percent of your opportunity is lost. 

Apart from that, stability is good. If you take a calendar month of 30 days, from the 4th to the 25th, all is well and good. After getting to the 30th, which is the peak time of sale, I think the software hangs up too much.

There is too much demand from customers at that time, so you have to handle it very well so that none of the other invoices are getting stuck. You also need to make sure pickup and delivery are on the spot and on time.

This solution can be expanded at any time. Initially, we started in one department and then another department got used to it. Later on, other departments began to use it. In our entire company, we have 27 branch offices and four factories. Initially, it was only implemented in the head office to get people used to it. Now, the entire company has been using it, including branches and our department center, all of the 10,000 employees have been using it. It's scalable. Everybody is used to it now.

It's used by 10,000 people. We have 10,000 employees here.

I've always been in touch with technical support because I love to actually see the coding they do behind the bug releases. I don't understand that much, but my curiosity makes me just want to know what they write there and how they put the command in it to clear the invoices, etc. When I see at the end of the month that it gets stuck, they clear the errors from the back end. There are also many times when there is a load on the servers, so they jointly come up to the other end and they write some of the other code.

I really don't understand the technical part, but I enjoy seeing it and I think that they do a great job. There is a functional coordinator and there are technician coordinators, though we as the users are not supposed to interfere with the technical people. Functionality has to coordinate with technical, but there are some people who can directly talk to the technical guys. For instance, when you are stuck, there is a problem with the server, or the invoices are getting stuck, I am one of the people that can go and ask them.

In terms of technical support, I can approach them directly and ask them for assistance. Instead of going through the functional team, I ask them directly. It's a direct communication, so it goes faster.

The initial setup is straightforward. It is not complex.

Initially, we needed help to implement this solution because I was an SAP user, so getting into Oracle, I needed consultants to understand it. Obviously, if you're moving from one ERP to another ERP, you need to get help from somebody to get educated. There was a data consultancy which was reappointed here to train each and every one of them.

We were trained at first until they trained the trainer. You get your first training and then you can train other people.

Based on my experience, if your company is expanding on a very high level and already has good growth in it, you could do very well with Oracle. If you want to develop your own project as well, which involves standardized as well as customized forms, that would be another reason to go with Oracle.

SAP has their own advantages as well, so I would not say that Oracle is the best platform. You could go with SAP also. It depends which company asks for which ERP software.

I would rate this solution as seven out of ten.