Systems Work Requests

PeopleSoft

Student Financial Services supports a wide range of PeopleSoft-related work requests. Departments and staff can submit requests for updates or changes to existing configurations, feasibility analysis for new or changing business needs, batch processing for groups of students, or data requests via query.

Examples of requests include:

Tuition and fee setup for testing in a test database
Group posts of charges or adjustments on student accounts
Adding or adjusting item types
Adjustments to GL Chartfield values
Altering what a specific financial aid type can or cannot pay
Troubleshooting processing or data errors

Work requests are prioritized based on several factors, including:

Order received
Level of impact
Collaboration with other departments and their availability (if necessary)

SFS PeopleSoft Technical Work Request

Transact (Online Payments)

Need the ability to accept online payments? Are you a department or organization that would like to go cashless? �� utilizes a third-party payment processor, “Transact." Transact is a secure, user-friendly online payment platform that enables departments and organizations to collect payments electronically.

Transact offers the flexibility to accommodate a variety of business needs via “eMarkets.” Student Financial Services supports the build and maintenance of eMarkets that provide a variety of customers (students, staff, public, etc.) the convenience of making digital payments on multiple platforms (computer, phone, tablet).

Common use case scenarios for eMarkets include:

Collecting registration fees for conferences, workshops, or exams
Collecting membership dues
Selling merchandise for student organizations
Selling tickets for events that do not require assigned seating

Through eMarkets, Student Financial Services fosters operational efficiency and enhances the overall financial transaction experience for both students and staff.

Interested in setting up an eMarket? Start here.

The following steps should be followed when considering having an eMarket built for your online payment needs:

Step 1: Determine your online payment need(s)

What products or services do you want to sell?
Do you have a quantity limit for what you are selling?
Do you need the customer to receive a “ticket” or reservation?
Does an eMarket already exist where you can just add a new product (i.e., Student Organizations eMarket)?
Do you have the need to take an online payment in-person?

Step 2: Banking and Transaction Fees

Which business unit does your department or organization fall under (i.e., State, Corporation, Foundation, ASI, Housing, etc.)?
Do your eMarket needs require a new bank account? Note: New bank accounts cost approximately $2,500 (Wells Fargo/Transact costs)
Do you want your customers to have the ability to make ACH (bank account) payments?
Do you want to pass the fees associated with debit/credit card transactions (2.675% per transaction) onto the customer or absorb them?
Note: If the ACH (bank account) payment method is desired, a fee of approximately $0.25 per transaction is charged to the department or organization (no option to pass the fee on to the customer)

Step 3: Data Collection and Reporting

Do you wish to collect any data from each transaction? Samples include:
- Name
- Dietary restrictions
- Company name
- Address, email, etc.
Do you require a scheduled report of transactions and/or customer data? What frequency (weekly, monthly, etc.)?

Step 4: Product/Pricing/Presentation

Does the product or event you are selling have an expiration date (the date you no longer want it available to purchase)?
Do you want to offer discounted rates via a discount/coupon code?
Any “If/Then” scenarios (i.e., if you purchase this item, can you add-on “x” item)?
Do you require tiered pricing (i.e., “early bird” rates, different rates for different types of customers, etc.)?
Note regarding unexpected/on-demand rate changes: Rate changes cannot be scheduled and require SFS staff to adjust. Changes rely on resource availability and only during business hours.
Will you require product images, logos, graphics, etc.?

Step 5: Refunds

Are any of your products/services eligible for a refund?
Who has delegated authority for refunds?
Notes regarding refunds:
- Refunds typically take 6-8 weeks. Duration includes approval, notification to SFS, AP, Transact, and bank processing)
- Transaction fees are non-refundable (whether absorbed or passed on to customers)

eMarkets are not a good fit for:

Point of sale
Donations
Events that require assigned seating

eMARKET Request Form (Coming Soon)

Current estimated turnaround times* for building a new eMarket:

Standard eMarket (existing bank account) 4-6 Weeks

Characteristics:

Typically selling merchandise
No registration or data collection component
No ACH (bank account) payment option
No tiered pricing
No maximum quantity/no price expiration
Standard customer data collection (name, student number)

Standard eMarket (new bank account) 3-6 Months

Includes 4 to 6 weeks of traditional eMarket build, with an additional 4 to 5 months processing time required by Wells Fargo for bank account setup.

Dynamic eMarket (existing bank account) 2-3 Months

Characteristics:

Ability to purchase tickets/registrations
Ability to set up tiered pricing
Products/pricing can expire
Discounted rates/promotion codes are available
Ability to collect non-traditional data elements (i.e., dietary restrictions, company name, addresses, email, etc.)
Add-on purchases option
Product images, logos, and graphics can be used

Dynamic eMarket (new bank account) 4-7 Months

Includes 8-10 weeks of traditional eMarket build, with an additional 4-5 months of processing time required by Wells Fargo and Transact for bank account setup.

Current estimated turnaround times* for changes to existing eMarkets

Traditional eMarket: 1-2 Weeks
Registration/Event eMarket: 4-6 Weeks

*Turnaround times are subject to change and can be impacted by competing priorities and unexpected production issues that must take precedence.

��������