Effective: 09/06/2018
Previous information
- "Auditing
Travel & Expense"
The OSS Service Management team populates the TE QA Operational Accuracy DATE v3.0 workbook with the completed items for the previous business day and the workbook generates a random sample of travel and expense transactions to be reviewed by the QA Auditors. The data from the TE QA Operational Accuracy DATE v3.0 tool is copied into the QA Quality Performance Tracking Worklist on SharePoint.
The audit is conducted by the QA Reviewer comparing data in OAKS FIN to data on the expense report and on receipts and tracking the results on the SharePoint My Worklist Access Datasheet.
Sections in this Topic Hide
![]()
link in the
QA Associate Quick Links.
link beneath QA
Area: Travel & Expense.
![]()
to Assigned.
field.
The QA Associate audits each transaction assigned to them by working from the My Worklist data sheet in SharePoint.
link in the
QA Associate Quick Links.
link beneath QA
Area: Travel & Expense.

Minimize
the window with the My Worklist screen (or place on 2nd monitor).
For instructions on logging in to MyOhio and OAKS Financials, click here.
The Expense Report page displays.

Return to My
Worklist
screen.
Copy
an expense report
number
from My Worklist.
Minimize
the window with the My Worklist
screen or move it to the 2nd monitor.
In
OAKS FIN, paste the expense report number into the begins
with field
.
Click
Search
.

Click the Expense
Date header
to sort by the expense date.
Click the Authorization
ID
and verify the date range matches the
date range on the expense reports.
Click the Expense
Type
header to sort by expense type.
Click the Attachments
link to open all attached receipts to verify against each expense
line (if applicable).
Review each Expense
line
as applicable following the travel and expense
standards listed in "The Source OSS>
Travel & Expense> Working Expense Reports> Auditing Expense
Reports> Review Receipts and Expenses" topic.
To complete the audit transaction, the QA Auditor records the audit results on My Worklist and closes the item. QA errors are assigned to the appropriate processor via SharePoint as they are discovered, until all the samples for the day have been audited. The assigned processor receives tan e-mail notification via SharePoint workflow when an error has been identified by the QA Auditor.
If an error was not identified:
.
to "Closed."
to "Complete."
If an error was identified:
.
field to support the error
identified.
.
field.
to "Complete."
Once items have been marked as "complete" or "completed," edits or updates that do not pertain to error assignment (completion date, QA Associate assigned, etc.) must be approved in writing by supervisor. Edits or updates that pertain to error assignment (specific error fields, comments, etc.) will not be allowed, as QA items will be considered final once QA status is marked as "complete" or "completed.
Press
on the keyboard to refresh the data sheet.