IT Glossary
Software procurement covers sourcing, evaluating, approving, contracting and onboarding software. The steps, the GDPR check and why SaaS bypasses it.
November 2, 2026
Software procurement is a business process that covers how a company sources, evaluates, approves, contracts and onboards the software it uses. It decides which tools enter the stack, on what terms and with which data protection guarantees. For SaaS, software procurement also has to catch the tools that arrive through free trials, company cards and self-service sign-ups, before purchasing sees them.
The classic process assumed that software arrived through a purchase order: a request, a quote, a signature, then an installation. SaaS reversed the order. A user signs up with a work email, invites colleagues and upgrades with a company card, and the first document procurement sees is an invoice or an expense line. By then, company data is already in the tool, under the vendor's standard terms.
A working process accepts that some tools will arrive this way and adds a second entry point: discovery of the applications already in use, followed by the same review, so that shadow IT is pulled into procurement instead of ignored. Article 28 of the GDPR requires a contract or other legal act binding a processor when it processes personal data on behalf of a controller, which applies to a SaaS vendor as soon as it stores customer or employee data on the company's behalf.
A 220-person company has a purchasing policy for anything above a set amount, yet its marketing team runs a webinar tool, an AI writing assistant and a survey tool bought on cards, each below the threshold. A discovery pass finds them, with customer email addresses stored in two of them and no data processing agreement on file. Procurement runs the standard review: it keeps the survey tool, moves webinars to the video platform the company already pays for, and signs the vendor's agreement for the AI assistant after checking where the data is hosted.
Corma supports both entry points: it discovers the SaaS applications already in use, records contracts and renewals in one inventory, and routes access requests through self-service approval workflows.
Request, check against the existing stack, security and data protection review, negotiation, approval, contract record, provisioning and a renewal calendar.
Usually purchasing or finance, with IT and security as reviewers. In mid-sized companies without a purchasing team, IT often runs the process and finance approves the budget.
Yes, as soon as the trial holds company data. Signing up accepts the vendor's terms, so a light review before use keeps an unvetted tool from becoming a paid contract.
Software procurement is the process; a procurement policy is the written rule set behind it, with thresholds, approvers and mandatory checks. The policy says who decides, the process is how each purchase runs.