PSU SAP Concur Guide 2026: Navigating Penn State Travel, Expense, And BZYV Voucher Workflows

Penn State University utilizes SAP Concur as its primary cloud-based engine for institutional travel bookings, expense reporting, and corporate Purchasing Card (pCard) reconciliations. When users encounter alphanumeric batch codes or voucher tracking strings such as BZYV within system notifications, accounts payable disbursements, or general ledger extracts, these characters designate automated routing sequences generated during transaction posting between SAP Concur and the university enterprise resource planning backbone, SIMBA (System for Integrated Management, Budgeting, and Accounting).

Mastering the mechanics of this financial ecosystem ensures rapid reimbursements, strict adherence to institutional travel policies, and compliant allocation of sponsored research awards. The operational guidelines below detail the technical architecture, expense lifecycles, audit mandates, and troubleshooting protocols governing PSU SAP Concur operations in 2026.

Architectural Framework: How PSU Integrates SAP Concur with SIMBA

At Penn State, travel logistics and non-travel employee reimbursements do not operate in a vacuum. SAP Concur functions as the front-end intake and policy-compliance platform, while SIMBA—powered by SAP S/4HANA—serves as the system of record for accounting, budget checking, and fund disbursement.

When an employee or student submits an expense report, Concur cross-references user profile attributes against the university Master Data Directory. Each expense entry ties directly to a specialized funding account structure within SIMBA:

• Cost Centers: Used for general departmental operating budgets, administrative units, and operational travel.
• WBS Elements (Work Breakdown Structure): Applied to internally funded capital projects, non-sponsored specialized accounts, and construction initiatives.
• Internal Orders: Deployed to track specific events, departmental conferences, or specialized internal programs requiring localized budget tracking.
• Grants and Sponsored Program Accounts: Heavily regulated funding profiles governed by federal uniform guidance, state terms, or private foundation agreements.

Demystifying BZYV and Financial Posting Identifiers

The identifier "BZYV" represents a specific system-level clearing batch or document header sequence assigned when an approved SAP Concur expense report transitions into the SIMBA payments queue.

During the nightly interface transfer, batches of approved expense reports are grouped and converted into SAP financial accounting documents. The automated script assigns distinct alphanumeric document identifiers (such as prefix runs beginning with BZYV) to track:

1. Accounts Payable clearing items for employee out-of-pocket reimbursements disbursed through direct deposit (ACH).
2. Credit card liability clearing items offsetting internal university pCard holding accounts against designated departmental cost objects.
3. Third-party vendor disbursements routed for direct travel agent bookings processed via the institutional travel management company (Anthony Travel).

Understanding these strings allows business managers and financial delegates to pinpoint exact clearing entries within SIMBA transaction reports, eliminating reconciliations bottlenecks across campus departments.

Step-by-Step Protocol for Expense Report Submission and Reconciliation

Submitting travel reports and pCard charges through PSU SAP Concur requires following a standardized operational pathway. Incomplete entries, missing electronic receipts, or improper account coding lead directly to administrative delays or report rejections.

Step 1: User Profile Configuration and Delegate Assignment

Before initiating any bookings or reports, personnel must verify their profile settings. Employees can assign Expense Delegates to build reports on their behalf, though policy strictly dictates that only the traveler/cardholder can provide final digital submission.

Profile Accuracy Requirement

All travelers must confirm that their legal first, middle, and last names in Concur perfectly match their official government-issued photo identification (REAL ID or Passport). Discrepancies can lead to ticketing rejections and transportation security failures.

Step 2: Travel Request Creation and Pre-Trip Authorization

Certain travel categories require pre-trip authorizations before incurring non-refundable costs:

• International Travel: Mandatory submission of a Concur Travel Request. Requires clearance through the Penn State Global Office of Global Programs and integration with international emergency assistance services.
• High-Risk Travel Destinations: Involves additional institutional safety review protocols before travel approval can be issued.
• Sponsored Project Travel: Grant agreements often require pre-approval from the principal investigator (PI) or sponsor agency to guarantee funding eligibility.

Step 3: Expense Capture and Mobile Receipts (ExpenseIt)

Penn State strongly advises the use of the SAP Concur mobile application. Through the integrated ExpenseIt optical character recognition (OCR) tool, receipts photographed with a mobile device automatically parse vendor names, dates, currencies, and total amounts.

The software pairs receipt images directly with incoming corporate pCard charges through automated smart-matching algorithms, significantly reducing manual data entry.

Step 4: Allocating Funding Strings and Cost Distributions

Every line item must reflect proper accounting:

• Choose the primary Cost Center or Grant WBS Element at the report header level.
• Use line-item splitting when single expenses (such as combined airfare and lodging) cross multiple funding streams or distinct grant awards.
• Identify and segregate unallowable expenses (e.g., alcohol, personal room charges, non-approved upgrades) using the institutional "Unallowable Expense" itemization category to prevent improper charges against university or research budgets.

Step 5: Submission and Multi-Tier Approval Workflow

Once submitted, the expense report enters an automated workflow engine:

1. Expense Delegate/Preparer: (Optional step if prepared by an administrative assistant).
2. Cardholder/Traveler Signature: Mandatory legal certification by the claimant.
3. Financial Reviewer (Business Area Approval): Departmental budget verification to confirm availability of funds and operational legitimacy.
4. Research Accounting Review: Triggered automatically if the report charges a sponsored grant project.
5. SIMBA ERP Processing: Financial document generation and automated payment dispatch.

PSU Policy Compliance: Purchasing Card vs. Out-of-Pocket Reimbursements

Penn State encourages the use of the university Purchasing Card (pCard) for approved business and travel transactions to minimize employee out-of-pocket spending. However, the documentation guidelines and financial reconciliation workflows differ markedly between the two payment mechanisms.

Critical Pitfalls, Rejection Triggers, and Troubleshooting Batch Errors

The majority of report rejections within PSU SAP Concur trace back to administrative oversight or failure to maintain adequate substantiating records. The following issues trigger immediate report hold states:

Missing Itemized Hotel Folios

A credit card summary receipt showing only the total lodging fee does not satisfy internal audit protocols. Travelers must upload an itemized hotel folio documenting room rates, local hospitality taxes, parking fees, and room-service charges on a daily basis. Any personal streaming, minibar, or spa services must be itemized as non-reimbursable personal expenses.

Missing Itemized Meal Documentation

Restaurant charge slips showing only the final authorized charge and tip amount are insufficient for actual-expense claims. Receipts must detail all food and beverages purchased. Under university financial policy, alcoholic beverages cannot be submitted under standard meal allowances and must be separated into unallowable categories funded exclusively by discretionary general accounts, never sponsored grants.

Non-Compliant Airfare Classes

Penn State policy requires booking the lowest available commercial economy/coach fare. First-class, business-class, or premium economy seating enhancements are disallowed unless justified by a certified medical accommodation filed with the Affirmative Action Office, or under documented flight-duration thresholds established in current travel policies.

Federal Uniform Guidance Violations (2 CFR 200)

When charging travel expenses to federal grants, expenses must be necessary, reasonable, and directly allocable to the research project. Furthermore, travelers must strictly comply with the Fly America Act, ensuring that travel supported by federal funds uses U.S. flag air carriers unless qualified exceptions are officially documented via the Open Skies Agreement.

Resolving BZYV and Clearing Interface Failures

Common ERP Batch Error Handling

If an expense report indicates an approved status within SAP Concur but does not clear payment within three to five business days, the automated SIMBA batch transfer has likely encountered an interface hold.

Most batch transfer holds result from expired WBS elements on research grants, overdraft status on departmental cost centers, or inactive user bank information in the SIMBA vendor master.

Financial delegates should reference the batch or voucher ID (e.g., BZYV clearing sequences) when submitting support inquiries directly to the SIMBA Financial Support Center or the Central Travel Services Help Desk.

Frequently Asked Questions

What does the string "BZYV" indicate in a PSU SAP Concur transaction?

The string identifies an internal clearing run or automated accounts payable voucher prefix produced during batch integration between SAP Concur and the university SIMBA accounting database.

It is used by central financial services and departmental accountants to track the distribution of payments, monitor cleared liability items, and correlate credit card reconciliations against specific general ledger postings.

How long does it take to receive reimbursement from PSU SAP Concur?

Reimbursements typically post to the employee's bank account via direct deposit within three to seven business days following final institutional approval.

The exact timing depends on how rapidly departmental approvers, business area managers, and sponsored research accounting sign off on the report. Once the status shows Approved and In Accounting Review, the SIMBA automated batch payment release generally disburses the funds during the subsequent scheduled payment cycle.

What is the deadline for reconciling pCard charges in SAP Concur?

Penn State policy mandates that all pCard transactions must be fully reconciled and submitted within 30 days of the transaction date.

Allowing pCard charges to remain unreconciled beyond 30 days risks formal notification from Central Finance, potential temporary suspension of card charging privileges, and eventual escalation to departmental leadership. Transactions older than 60 days are considered delinquent.

Can an employee claim both standard per diem and actual meal receipts on the same trip?

No, travelers must select either the standard GSA Per Diem rate method or the actual expenses method for the duration of a single business journey.

Blending per diem allowances with actual expense reimbursements within the same trip itinerary is prohibited under university travel guidelines. If per diem is claimed, travelers must remember to deduct any meals that were provided by a conference, seminar, or host.

Are receipts required for every expense item in an expense report?

Itemized receipts are strictly mandatory for all lodging, airfare, car rental, and individual purchases of twenty-five dollars or higher.

While purchases under twenty-five dollars may be exempted under general receipt threshold guidelines for incidental out-of-pocket costs, utilizing the university pCard requires receipts for all expenses regardless of dollar amount in accordance with departmental audit standards.

Streamlining Institutional Expense Governance

Maintaining an efficient, audit-ready expense pipeline requires ongoing diligence from travelers, faculty, and administrative staff across Penn State. By maintaining accurate profile setups, leveraging mobile receipt technology, reconciling pCard expenses within prescribed timeframes, and understanding the financial clearing links between SAP Concur and SIMBA, departments ensure rapid reimbursement cycles and complete adherence to university fiscal standards.