Companies considering SAP-integrated invoice verification workflows will at some point be confronted with the question of whether to use a system with SAP parking or whether to use the system vendor's own documents. In this article, we distinguish between documents that are parked in SAP, that are posted in SAP, and that qualify as your own "technical" documents. The essential difference between these types of documents becomes apparent when real-time reporting is important. Let's take a look at the differences:

As companies begin to automate their invoice approval processes, it is important for them to make an essential decision in advance: Is an integrated workflow system required? Or would it be better to opt for something that places fewer limitations on company and users?

SAP S/4HANA is on everyone's lips. The new technology, which is intended to support the user in all aspects, has flooded the business world, at least as far as advertising goes. In addition, businesses are under pressure as a result of the termination of mainstream maintenance for SAP ERP 6.0 and SAP Business Suite 7, set to take place at the end of 2025. For many users, it has become clear that the old SAP environment must be migrated to S/4HANA, and that this change must not long be postponed. But what is the best way to migrate the legacy data? What options does a company have for migration from the existing SAP environment? What is the difference between the "greenfield" approach and the "brownfield" approach, and are there any other options? In this article, we will discuss the most common migration procedures and the challenges they present.

The skills shortage is a huge concern in the IT sector. Needless to say, for me as a recruiter, it is a particularly pressing problem. A true paradigm shift has taken place, as at present, potential candidates* can very often pick and choose from employers.