SAP Concur Expense Management: Policy, Receipt, and the Close That Waits on T&E

SAP Concur is not a travel website bolted onto SAP. Expense, Invoice, Request, and Intelligence sit on a policy engine: spend categories, audit rules, receipt capture, VAT/GST reclaim, mileage, per diems, card feeds, and a posting to FI that Record to Report has to close. Fortune 500 T&E programs fail when Concur is staffed as “the travel admin tool” and FI never owns the tax and accrual.

The unique challenge is exception volume. 80% of reports are boring. The 20% — split receipts, attendees, alcohol, personal time on a mixed trip, missing VAT invoices, card transactions that never become reports — decide whether close waits on T&E. Audit rules that fire on everything train users to click through. Rules that fire on nothing train fraud. SR Soft staffs Concur configuration, T&E process, and FICO together.

The challenges that actually break the program

• Policy that legal signed and Concur never modeled — attendees, gifts, per diem vs actuals
• Card feed timing that leaves unsubmitted charges sitting outside the accrual
• VAT reclaim that needs a tax invoice, not a photo of a dinner
• Employee vs cost-center vs WBS vs internal order — the account assignment fight
• S/4 posting failures that Concur shows as “success” to the traveler

How SR Soft LLC staffs and delivers it

We put a Concur solution consultant with a T&E process owner and a FICO resource who has posted company-pay and employee-pay. We design audit rules from the exception report, not from a template. We name who owns unsubmitted card spend at month-end. That is how T&E stops holding RTR hostage.