Managing institutional travel, employee reimbursements, and procurement card transactions requires tight controls and clean accounting links. At the University of California, San Diego, the deployment of UCSD Concur serves as the primary gateway for handling these financial logistics. Navigating the platform efficiently prevents reimbursement delays and ensures compliance with institutional accounting standards.
Understanding how requests, expense reports, and chart strings interact within the system helps faculty, staff, and department administrators clear internal reviews without friction. Whether you're managing a travel advance, reconciling a procurement card, or mapping chart of accounts (CoA) strings, mastering the backend mechanics of this platform saves hours of administrative overhead.
Core Architecture of the UCSD Concur Platform
The integration ties together several distinct financial functions into a centralized portal managed by Integrated Procure-to-Pay Solutions (IPPS). Rather than treating travel booking, out-of-pocket reimbursements, and card reconciliations as isolated silos, the platform bridges them through structured routing.
The ecosystem relies on two major transactional pillars: For additional information on this issue, in-depth coverage can be read at Kiplinger.
- Concur Request: Used primarily for pre-approval of official business travel and specific high-value or entertainment events before financial commitments are made.
- Concur Expense: Used post-transaction to reconcile corporate cards, process travel reimbursements, and clear out-of-pocket expenses.
These modules share delegate permissions natively. Assigning a departmental preparer or financial coordinator as a delegate in one area automatically grants permissions for both requests and expense reports, though final submission responsibilities remain strictly with the cardholder or traveler.
Streamlining Chart of Accounts and Allocations
A historical pain point in university expense reporting involved redundant data entry, particularly regarding how expenditure types mapped to accounting codes. With platform iterations like Concur 2.0, the layout minimizes manual coding errors through streamlined structural alignments.
Dynamic Chart String Mapping
Expense types are directly linked to specific account codes, removing the redundant requirement to manually select an independent expenditure type every time a project code is updated. When processing reports, users only need to provide the relevant project or General Ledger (GL) elements rather than managing conflicting combinations.
Mandatory Allocation Usage
To ensure postings flow cleanly into core financial systems like Oracle, transactions require proper allocation inputs. Users must utilize the allocation feature to assign financial units, funds, functions, or project-task identifiers.
- Financial Unit & Approver: Required baseline routing parameters for departmental account owners.
- Project/Task vs. Fund/Function: Select either the project and task string or the fund and function string depending on whether the expense draws from sponsored research or institutional ledger funds.
Failing to use the allocation window properly causes review bottlenecks, often routing reports into extended exception queues before central office clearance.
Managing Travel and Event Pre-Approvals
Travel arrangements require strict adherence to pre-trip authorization workflows. Faculty and staff must initiate a Concur Request before booking flights, lodging, or registering for conferences where expenses will be reimbursed.
[Create Concur Request] --> [Attach Estimated Expenses] --> [Department Review & Approval] --> [Book via Concur Travel / T&E Card]
Prepayments and Conference Registrations
Handling conference fees and hotel deposits requires careful selection of payment mechanisms to avoid compliance flags:
- Conference Fees with No Travel: If no incidental travel costs are incurred, use a departmental Procurement Card or personal Travel & Entertainment (T&E) card directly.
- Travel-Incidental Conferences: Use personal T&E cards or explore temporary virtual card solutions.
- Sponsored Projects: Never use sponsored research funds for advance prepayments ahead of a trip unless explicitly allowable under the award terms; use non-sponsored departmental project codes for initial deposits.
Receipt Management and Mobile Integration
Paper receipts create administrative backlog. The platform integrates with the Concur Mobile App and the ExpenseIt service to digitize documentation at the point of purchase.
1. Snap a photo of the receipt using the mobile app or forward digital invoices to verified email addresses (receipts@expenseit.com).
2. The system automatically reads vendor data, dates, and amounts, matching them with corporate card feeds.
3. Attach the verified digital receipt directly to the line-item expense before report generation.
Delegates managing receipts on behalf of faculty members must ensure the primary user's verified email address is included in the subject line of forwarded documentation to prevent unassigned items from sitting indefinitely in the receipt bank.
Common Mistakes to Avoid
Efficiency drops when users repeat common configuration errors during report generation. Avoiding these pitfalls speeds up reimbursement timelines:
- Skipping Allocations: Submitting a GL or project value without completing the explicit allocation step causes mapping failures during Oracle synchronization.
- Mixing Legacy and Non-Legacy Reports: Attempting to modify old, unsubmitted draft reports created under obsolete form templates often triggers validation errors. Delete legacy drafts and recreate them using current non-legacy request types.
- Improper Delegate Submission: While delegates can build, edit, and organize complete packets, clicking the final submit button on a travel reimbursement or card report violates policy if performed by anyone other than the traveler or cardholder.
Frequently Asked Questions
How long does expense approval typically take within the system?
Once a clean report is submitted with all required allocations and attached receipts, initial department-level approval usually clears within 24 to 48 hours. Final reviews by central campus teams depend on volume, but accurate chart strings prevent escalation to "Pending IPPS Review" hold queues.
Can personal travel be booked through the university portal?
Yes, employees can utilize the booking engine for personal itineraries, but payment must be settled using personal credit cards rather than institutional funds or university-issued T&E cards.
What happens if a corporate card transaction is missing from my account?
If a transaction fails to feed automatically into the active expense profile within a few business days, check whether the card is properly linked in the profile settings, or manually add the out-of-pocket expense item with an explanatory note and receipt attached.
How do I handle split funding across multiple departments?
Use the Allocation feature within the line-item details to distribute percentages or specific dollar amounts across different financial units, fund codes, or project strings before final submission.
