Why IT Procurement Is Harder Than It Should Be
In a perfect world, you identify what you need, you buy it, it arrives. In a Fortune 500 company, the reality is a multi-step approval chain, procurement policy compliance checks, preferred vendor constraints, and a PO process that can take days if you don't know how to navigate it.
I was the device approval manager for a regional IT team — processing hundreds of thousands of dollars worth of IT hardware per year through SAP Ariba. Here's what I learned.
How SAP Ariba Works (For IT People Who Aren't Procurement Experts)
SAP Ariba is SAP's cloud procurement platform. For IT, the flow looks like this:
Ariba IT Procurement Flow
1. Need Identified
IT creates request
2. PR in Ariba
Purchase Requisition
3. Manager Approval
IT Manager + Budget owner
4. PO Created
Purchase Order issued
5. Vendor Delivers
Equipment received
6. Goods Receipt (GR)
Confirm in Ariba, invoice paid
▲ The GR step is critical — the vendor doesn't get paid until you confirm receipt. Many IT teams forget this and create payment disputes.
The 5 Mistakes That Delay IT Procurement
Mistake 1: Missing the Cost Centre or GL Account
Every PR needs a valid cost centre and general ledger account. If you get these wrong, the PR goes into a budget exception hold and waits for the Finance team to manually correct it.
Fix: Get the correct cost centre and GL account codes from your Finance business partner before you need them. Save them somewhere. Use them every time.
Mistake 2: No Vendor Catalogue Item
Ariba works best when you select items from the approved vendor catalogue. When you type a free-text description instead, it triggers manual review by procurement, which adds 2–3 days.
Fix: Always search the catalogue first. If your item isn't in the catalogue, raise a vendor onboarding request before you need the item urgently.
Mistake 3: Raising the PR After You Need It
I have seen IT engineers raise a PR for a laptop that was needed "last week." Ariba has approval chains — with manager approval, budget check, and PO issuance, you're looking at 3–5 business days minimum.
Fix: Plan ahead. If a laptop refresh is coming in 3 months, raise the PR in 2.5 months.
Mistake 4: Not Following Up on Approvals
PRs sit in managers' inboxes and get forgotten. It's not bad intent — it's email overload.
Fix: After 24 hours with no action, a gentle message: "Hi [Name], I raised PR [number] yesterday for [item]. Could you approve when you get a chance? It's needed for [user/date]." One follow-up message. Not five.
Mistake 5: Forgetting Goods Receipt
After equipment arrives, you must post the Goods Receipt in Ariba. Until you do this, the vendor invoice sits unpaid, the vendor gets frustrated, and your relationship with them (and future delivery speed) suffers.
Fix: Post GR the same day equipment arrives. Make it a habit.
Procurement Cycle Time Improvement
Building Your IT Procurement Efficiency
A simple tracking process used across procurement cycles:
| Date | Item | PR Number | Status | Expected Delivery |
|---|---|---|---|---|
| Jan 5 | Lenovo ThinkPad T14 x5 | PR-2024-00123 | PO Issued | Jan 18 |
| Jan 8 | iPhone 15 Pro x2 | PR-2024-00127 | Manager Approval | Jan 22 |
This took 15 minutes per week to maintain and saved hours of "where is my PR?" conversations.
Working With IT Vendors
Relationship management with technology distribution partners matters enormously in enterprise IT:
What builds vendor trust:
- Paying invoices promptly (post GR on time)
- Giving advance notice of large orders
- Consistent point of contact
- Paying for what you ordered (no last-minute cancellations)
What damages it:
- Rushing emergency orders regularly
- Disputing invoices over minor differences
- Multiple contacts sending conflicting messages
The vendors who trust you will prioritise your orders, hold stock for you, and call you when they see relevant products. That goodwill has real operational value.
The Numbers Behind 3 Years of IT Procurement
After managing regional device procurement for 3 years:
- Average PR to PO time: 3.2 business days (reduced from 6.1 days)
- GR posting rate within 24hrs: 96% (up from 71%)
- Vendor dispute incidents: 3 total (down from ~15/year)
The biggest driver of improvement was simple: education. Once every person who could raise a PR understood the full process — including why cost centres matter and why GR posting is critical — compliance improved dramatically.
Procurement is not just an admin task. Done well, it's a competitive advantage: faster equipment availability, better vendor relationships, and clean financial records that pass audit.
◆ Pro Tips
- ▸ Get your cost centre and GL account codes from Finance before you ever need to raise a PR — wrong codes send orders into a budget hold that can delay delivery by a week.
- ▸ Always search the approved vendor catalogue before using free text — catalogue items skip manual procurement review and can cut 2–3 days from your cycle time.
- ▸ Post the Goods Receipt the same day equipment arrives — the vendor's invoice is unpaid until you do, and late GR posting is the fastest way to damage a vendor relationship.
- ▸ Raise PRs at least 3–4 weeks before equipment is needed — even a smooth Ariba cycle takes 3–5 business days, and any approval delay will push past your deadline.
- ▸ Maintain a simple procurement tracker (date, item, PR number, status, ETA) — 15 minutes per week of tracking saves hours of "where is my order?" follow-up conversations.