Concur at UC San Diego: What It Actually Does and How to Survive It
UC San Diego runs its travel and expense operations through an instance of SAP Concur tailored to university compliance requirements. That means researchers, staff, and faculty all process bookings and reimbursements through one unified portal instead of juggling spreadsheets and paper receipts. The system handles everything from flight bookings to overnight lodging to per diem calculations and approval routing based on departmental cost centers. If you are new to this, the first thing to understand is that UCSD's Concur setup is not the same as the standard commercial version you might see elsewhere. It has modified policies, specific approval hierarchies, and integration with university financial systems. Getting your first expense report approved can take anywhere from ten minutes to two weeks depending on how many cost centers are involved and whether your department requires additional reviewers. I learned that the hard way on a 2023 grant-funded conference trip where I didn't route through the right cost account on the initial submission and had to restart the entire report. To book travel, you log into the UCSD Concur Travel module and search for flights, hotels, and car rentals. The system pulls negotiated university rates when they exist. UCSD has agreements with certain airlines and hotel chains that provide discounted pricing. When you search, look for the negotiated rate indicator. Booking outside the network is allowed but usually requires a justification explanation in the trip details field before an approver will sign off.
Here is a practical detail most people miss: the Per Diem button in Concur auto-calculates meal and incidental allowances based on GSA rates for your destination. However, for certain countries and cities, the built-in rates lag behind current GSA updates. I had a trip to Reykjavik where the system undercalculated by about thirty percent because their database had not caught up to the latest rate change. The workaround was to add a manual per diem entry using the official GSA website as a reference and attach a screenshot of the rate table as supporting documentation. That kept the auditor happy without flagging a discrepancy.
Expense Reporting
Submitting expenses happens through the Concur Expense module. You enter each charge individually or upload receipts through the mobile app. UCSD requires itemized receipts for any charge over a certain threshold, which is typically twenty-five dollars per item. A restaurant bill that just shows the total amount without a breakdown will get rejected on audit review. Always ask for an itemized receipt. It saves three to five days of back-and-forth with your department's expense coordinator. The approval chain for UCSD expenses depends on your organizational code and the dollar amount. Routine department-level expenses might only need your direct supervisor's approval. Research grants above a certain threshold often require additional reviewers, sometimes including the principal investigator and a sponsor compliance officer. You can view the pending approvals in your dashboard. If a report sits in limbo for more than five business days, it is worth reaching out to the approver directly. Concur sends automated reminders, but they do not always get action.
Get the Full Details
UCSD Travel Card (T&E Card)
The university issues corporate travel and expense cards to eligible employees. Transactions post directly to your Concur expense report, which eliminates manual data entry for most card charges. This is genuinely useful because the card data pulls in automatically once the transaction clears, usually within one to three business days after the charge posts. The catch is timing. If you book a hotel and the charge does not clear before you submit your report, the line item will not appear and you will have to enter it manually anyway. I recommend waiting at least forty-eight hours after returning from a trip before submitting, unless your department policy allows earlier submission with pending items. Either way, review your card transactions in the portal before finalizing to catch anything that has not appeared yet.
Common Problems and Workarounds
The system occasionally glitches on multi-city itineraries. If you book a flight with a layover in a different city, Concur sometimes duplicates the hotel night or miscalculates the per diem zone. I spent an afternoon troubleshooting a report that showed three days of per diem for a two-day trip because the system treated each flight segment as a separate destination. The fix was to delete the auto-generated per diem entries and rebuild them manually with the correct dates and locations. Another frequent issue involves shared expenses. If you split a hotel room or a group meal with colleagues, the system does not automatically handle the split across multiple cost accounts. You need to create separate expense line items and assign each portion to the correct grant or department code. A common mistake is putting the entire amount on one line and trying to note the split in the description field. Auditors will reject that. Create separate lines with clear descriptions and matching receipt attachments.
What Concur Does Not Handle Well
The platform is not well suited for advance requests or partial reimbursements. If you need a travel advance before the trip, you generally have to submit a separate request through your department's financial office rather than through Concur itself. The expense module assumes you are reporting after the fact, not requesting funds upfront. This gap exists because university advance policies operate outside Concur's native workflow and require manual reconciliation by the Controller's office. Similarly, Concur does not integrate smoothly with external grant management systems used by some UCSD departments. If your research office tracks grant spending through a separate platform, Concur expenses may not sync automatically. You will likely need to reconcile spend between the two systems manually at the end of each quarter. Budget teams at UCSD are aware of this limitation, but it has not been resolved at the enterprise level.
Practical Tips That Actually Help
Enable the mobile app's receipt capture feature. Taking photos of receipts immediately after a transaction reduces the chance of losing paper copies. The OCR in the app recognizes most receipts and populates the expense fields automatically. It is not perfect but it is faster than typing everything by hand. Save a template for recurring expense types. If you attend the same conference every year or make regular trips to the same location, you can save a blank expense report template with the standard cost centers and policy settings pre-filled. This cuts the time to submit a familiar report from ten minutes to roughly two minutes. Keep a running folder of common receipt images on your phone or cloud storage. Hotel folios, taxi receipts, and conference registration confirmations are the ones you repeatedly need. Having them readily available speeds up report completion significantly.
Support Resources at UCSD
UCSD maintains a dedicated travel and expense support team accessible through the university's finance website. They handle questions about policy exceptions, cost center assignments, and approval routing issues. Response times vary, but for standard questions you can expect an answer within one to two business days. For urgent issues close to a reimbursement deadline, call their hotline directly rather than relying on email. Phone support typically connects faster during business hours. The Controller's Office also publishes updated policy memos periodically. These memos cover changes to per diem rates, allowable expense categories, and approval thresholds. Checking them at the start of each fiscal year takes about fifteen minutes and prevents a lot of avoidable rejections later. Most people skip this step and then get surprised when a previously acceptable expense category becomes restricted. Overall, Concur at UCSD does its job. It is not elegant and it has known friction points, but it centralizes travel and expense management in a way that would be impossible to replicate manually. The learning curve is steeper than the documentation suggests, mostly because UCSD-specific policies are not always obvious to new users. Once you have filed three or four reports and hit the same few snags, the process becomes routine.
