Ucsd Concur The Ultimate Guide To Streamlining Your University Operations

Ucsd Concur The Ultimate Guide To Streamlining Your University Operations

I spent three years managing procurement and travel workflows for a mid-sized university research department before we migrated everything to Concur, so I have some opinions about what works and what just creates more paperwork than the old system. Concur is SAP's travel and expense management platform. Universities adopted it aggressively around 2015 to consolidate manual processes. The short version is that it routes purchase requests, travel bookings, and expense reports through a single system instead of having five different forms across five different departments. Here is how it actually functions on a UC San Diego campus. You log into the Concur portal, which for UCSD routes through the MyUCSD single sign-on. From there you initiate a Purchase Requisition by selecting your cost center, the GL account, the vendor, and the dollar amount. The system checks spending authority limits and routes the request to your supervisor and the appropriate budget holder for approval. Once approved, it generates a commitment against your department's budget. This is the procurement piece. The travel piece works similarly but pulls from a different workflow template. An expense report submission triggers automated receipt matching and policy compliance checks before routing to your approver.

The configuration at UCSD is not a vanilla Concur install. It has custom approval matrices tied to campus organizational units, mandatory field validations for sponsored research accounts, and integration with PeopleSoft for general ledger posting. This means certain business processes behave differently than they would at a standard corporate Concur deployment. If you came from a non-education background and expect the system to work the same way everywhere, you will run into friction quickly. I remember one specific edge case that took me two weeks to resolve. A faculty member was trying to book travel using an NIH grant as the funding source for a conference abroad. Concur blocked the booking because the per diem rates it pulled from the GSA tables did not match the actual costs in that city, and the system's policy engine flagged it as a violation. The problem was not the software logic. It was that the grant had a supplemental per diem clause that allowed actual costs, but Concur's approval workflow had no field to capture that exception. The workaround was filing a manual override through the Campus Travel Office and attaching the grant terms to the approval packet. After that incident, our department added a custom note field to the travel request form that references the specific award clause allowing the variance. It is not a perfect fix but it prevents the same blocker from recurring.

Setting Up and Using Concur for University Operations

Getting started requires you to have an active MyUCSD account and your department's chartstring information. You will find the chartstring lookup tool under the Resources menu inside Concur. Having your cost center, project code, and fund number ready before you start a request saves you from the reload-and-retry cycle that slows down most first-time users. The system defaults to showing only the cost centers you are authorized to access, which is a feature, not a bug, but it does mean you cannot borrow another department's budget without proper delegation paperwork filed first. For purchase requisitions, the critical step is selecting the right commodity code. The Commodity Classification system maps to the General Ledger accounts, and an incorrect selection here will cause the requisition to route to the wrong approver or fail policy validation entirely. I have watched valid requests sit in pending approval for days because someone selected a general goods code when the purchase was actually services. The fix is always the same: cancel the pending requisition and recreate it with the correct code. There is no bulk edit function for commodity codes once a request is in workflow. Expense reporting follows a similar pattern of small decisions that compound into big problems. The automatic credit card feed from Citi is reliable for most transactions but it does not always categorize correctly for university-specific purchases. Lab supplies show up as general merchandise. Equipment rentals appear as services. You need to review every line item before submitting, and the policy is strict about late submissions. Reports submitted more than 30 days after the expense occur get routed to the Finance Business Partner desk for manual review, which adds roughly three to five business days to your reimbursement timeline.

Travel bookings through the integrated travel portal let you search flights and hotels in real time. The rate negotiation contracts that UCSD has with specific vendors show up as preferred options during the search, but they are not always the cheapest option available. I have found cases where a non-contracted hotel was $40 per night cheaper than the contracted property, and the policy allows you to book non-contracted when it is demonstrably less expensive, provided you document the price difference in the request notes. That documentation step is where most people skip and then get questioned later.

Common Pitfalls and What the Documentation Leaves Out

The official Concur training materials are written for corporate users, not university researchers or departmental admins. They do not cover sponsored account restrictions, federal compliance flags, or the way UCSD's delegation of authority matrix works. The gap between what the help docs assume and what actually happens on campus is where most errors originate. One counter-intuitive thing about Concur at UCSD is that delegation settings do not inherit across fiscal years. If you set up a delegated approver in June for next year's budget cycle, that delegation expires on June 30 and you have to reauthorize it after the new fiscal year starts in July. Departments that forget this find themselves with incomplete approval chains during the busy fall semester. Setting a calendar reminder for early July to verify all delegation assignments prevents this entire category of delay. Another thing nobody warns you about is the behavior of the budget check engine during year-end close. In May and June, Concur's real-time budget checking can slow down or return false insufficient funds messages as PeopleSoft is running its close cycles. I had a requisition for essential lab equipment sit in a "budget unavailable" state for four business days in late May because the backend reconciliation was still processing. The workaround was contacting the Budget Office directly rather than waiting for the system to clear itself. They confirmed the funds were there and manually triggered a budget refresh, which resolved the issue within a couple hours.

Concur also has a hard limitation with split-funding requests. If a single purchase needs to draw from two different grants or accounts, the system does not support splitting one requisition across multiple chartstrings in a single workflow. You have to create two separate requisitions for the same vendor with different cost centers. This doubles the approval work and increases the chance of duplicate ordering if two people are managing the split without coordination. Our department solved this by having the procurement assistant submit both requisitions as a paired set with cross-references in the notes, but it is an informal workaround that is not documented in any official procedure. The system also struggles with micro-purchases under $5000 that repeat monthly. Recurring library database subscriptions, software licenses, and journal renewals all look identical in Concur because there is no recurring purchase template. Each month someone has to manually enter the same vendor, same amount, same GL account, and resubmit the approval workflow. It is administratively wasteful. Some universities have built custom purchase order agreements that auto-generate monthly requisitions, but the UCSD Concur instance does not currently support that automation for most departments. The closest alternative is setting up a standing blanket purchase order through Procurement Services, which generates the requisition automatically each cycle and only requires a one-time approval.

Navigation and Daily Workflow

The home screen layout changed in the latest update, so if you watched a tutorial from last year the buttons may be in different places. The main actions are in the top navigation bar: Expenses, Trip, Reports, and My Profile. The Reports section is where you manage approval queues. If you are an approver for multiple departments, filtering by your organization unit is essential because the default view shows every request across all units you have access to, which can be dozens of items on a busy day. Receipt capture through the mobile app has improved but it still fails on certain types of documents. Institutional receipts that are printed on thick paper, receipts with thermal ink that faded, or scanned PDFs older than six months all require manual entry. The app's OCR engine is not reliable for these. The fastest workaround is taking a clear photo in good lighting, cropping to just the receipt, and letting the system extract the data. Then verify the merchant, date, and amount before saving. Skipping verification here creates discrepancy flags that bounce the report back to you later. When you submit an expense report, the system runs a real-time policy check. It will flag per diem overages, missing receipts for amounts above $75, and alcohol expenses in unsupported categories. You can add a business purpose explanation for flagged items, and most policy exceptions approve within the same workflow without needing escalation. The one exception that never auto-approves is any expense exceeding your delegation authority threshold, which routes to the next level of approval in the org chart regardless of your explanation.

Processing times vary significantly depending on who is in the approval chain. A straightforward domestic travel request with a single approver typically moves through in one to two business days. A multi-cost-center research purchase requiring three approvals and a sponsorship compliance check can take five to seven business days. Budget holders tend to be slower approvers than departmental admins because they receive far fewer requests and may be managing approvals across multiple departments. Sending a polite email when a request has been pending for more than 48 hours is standard practice and usually results in same-day action.

Limitations and When Concur Is Not the Right Tool

Concur is not suitable for every transaction type at a university. Emergency equipment purchases under $500 that need to happen the same day do not flow well through its approval process. The turnaround time for emergency requisitions is measured in hours, not minutes, and most departments find it faster to use the emergency purchase card program and file a retroactive report afterward. This is an accepted workaround that is explicitly recommended by Campus Financial Services for genuine emergencies where delay would risk safety or research continuity. International vendor payments through Concur are another area where the system falls short. The platform is designed for domestic travel and domestic vendor purchases. If you are paying a foreign supplier, ordering equipment from an overseas manufacturer, or reimbursing a researcher for international expenses incurred in non-dollar currencies, the system's automatic currency conversion is decent but the compliance review process adds significant time. These transactions often require manual intervention from International Accounting, and the total processing time can extend to two or three weeks depending on the destination country's sanctions screening requirements. Large equipment purchases over $25,000 should bypass Concur and go through Procurement Services directly. The system is not configured for capital asset tracking, and tagging the purchase with the fixed asset workflow after the fact creates reconciliation issues during annual audits. Procurement Services handles capital acquisitions with the proper serialization, depreciation scheduling, and physical inventory tagging that Concur does not support.

The reporting module in Concur is functional but limited. You can generate basic spend-by-vendor and spend-by-category reports, but cross-referencing spending against grant performance metrics or departmental headcount requires exporting data and rebuilding the analysis in Excel or a BI tool. The UCSD Business Intelligence platform has a Concur data extract, but the latency is typically 24 to 48 hours, so real-time financial visibility is not available. Training gaps are the most persistent operational problem. New staff members who have never used Concur before require approximately 15 to 20 hours of self-guided practice to reach proficiency with purchase requisitions and expense reports. The online training modules are mandatory but they do not account for UCSD-specific workflows. Junior staff in departments that process high volumes of requests often learn the system through osmosis from senior colleagues rather than through formal training. This creates inconsistency in how requests are categorized and documented across different parts of the same department, which makes reconciliation harder for the finance team. System outages are rare but when they occur they stop all activity. There is no offline mode. During the brief outage in March 2024 that lasted roughly six hours, several departments reported that time-sensitive travel approvals for visiting speakers could not be processed. The workaround was faxing signed approval documents to the travel office and submitting the records retroactively once the system came back online. This is not ideal but it is the only contingency most departments have on file.