Standard Operating Procedure: Audit Form Submission and Compliance (UT Austin)

This Standard Operating Procedure (SOP) outlines the mandatory protocols for completing, reviewing, and submitting audit documentation within the University of Texas at Austin framework. Adherence to these procedures ensures fiscal responsibility, institutional compliance with UT System policies, and seamless coordination with the Office of Internal Audits or relevant departmental oversight committees. Accuracy in these filings is critical to maintaining audit readiness and institutional transparency.

Phase 1: Pre-Audit Preparation and Documentation Gathering

• Define Scope: Identify the specific audit type (e.g., Fiscal Year-End, Grant-Specific, or Departmental Inventory) and the associated UT Austin Audit Form version.
• Access Portal: Ensure you are logged into the UT Austin Internal Audit Portal or the specific departmental administrative interface using your UT EID and multi-factor authentication (Duo).
• Compile Supporting Evidence: Gather all relevant source documents, including:
  • Definitive ledger reports from DEFINE or Workday.
  • Proof of transaction authorization (e.g., electronic signatures on VP forms).
  • Reconciliation summaries for the audit period.
  • Inventory logs, if applicable to the form requirements.

Phase 2: Form Completion and Data Integrity

• Field Validation: Complete all required fields marked with an asterisk (*). Ensure that "N/A" is used for non-applicable fields rather than leaving them blank.
• Financial Accuracy: Cross-reference all numerical entries against official UT financial statements. Discrepancies exceeding the department's materiality threshold must be noted in the "Comments/Discrepancies" section.
• Standardized Coding: Utilize the correct UT Account numbers, Object Codes, and Cost Center identifiers as dictated by the Handbook of Business Procedures (HBP).
• Attestation: Verify that the "Preparer" and "Approver/Delegate" signatures align with the official UT Austin Authorization Hierarchy for your specific unit.

Phase 3: Review, Submission, and Record Retention

• Final Quality Control: Perform a "Double-Blind" review. Have a peer who did not prepare the form verify the data against the source documents.
• Submission Protocol: Upload the final document in the required file format (typically PDF/A) to the secure audit repository.
• Confirmation: Retain the automated submission receipt and the unique Transaction ID number for your internal records.
• Archiving: Store a copy of the submission packet according to the UT Austin Records Retention Schedule (RRS), ensuring PII (Personally Identifiable Information) is redacted if applicable.

Pro Tips & Pitfalls

• Pitfall - Browser Compatibility: Many UT Austin audit portals perform best on updated versions of Chrome or Firefox. Avoid using Safari or outdated browser versions, as they may cause script errors during form submission.
• Pitfall - Timeout Errors: These systems are security-intensive. If your session takes too long, you will be logged out and unsaved data will be lost. Draft long comments in a local text editor first, then paste them into the portal.
• Pro Tip - Version Control: Always download the "Fresh Form" from the official UT website every quarter. Using an old, cached version of a PDF form often leads to submission rejections due to outdated validation logic.
• Pro Tip - The "Evidence Map": Create a table of contents or an "Evidence Map" as your first page if you are submitting a multi-document audit packet. This dramatically reduces the time reviewers spend seeking clarity on specific line items.

FAQ: Audit Compliance

Q: What should I do if I discover a discrepancy after the audit form has been submitted? A: Do not attempt to re-submit a duplicate form. Contact the Internal Audit liaison for your department immediately, disclose the discrepancy in writing, and request the appropriate "Correction Request" procedure.

Q: Is there a specific format for file naming conventions when uploading to the audit portal? A: Yes. Unless otherwise specified by your department, use the format: YYYYMMDD_AuditType_DepartmentCode_PreparerInitials. Example: 20231015_GrantAudit_COLA_JD.pdf.

Q: How long must I keep the supporting documentation for these audit forms? A: Per UT Austin records policy, most financial audit documentation must be retained for the current fiscal year plus three additional fiscal years. Always check the specific retention category for your department’s unique records in the Records Management Services database.

<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "How do I access the UT Austin Internal Audit Portal?", "acceptedAnswer": { "@type": "Answer", "text": "Access the UT Austin Internal Audit Portal by logging in with your UT EID and completing multi-factor authentication (Duo) at audit.utexas.edu." } }, { "@type": "Question", "name": "What supporting documents are required for UT Austin audits?", "acceptedAnswer": { "@type": "Answer", "text": "You must compile ledger reports from DEFINE or Workday, proof of transaction authorization (VP forms), reconciliation summaries, and relevant inventory logs." } }, { "@type": "Question", "name": "How should discrepancies be handled on audit forms?", "acceptedAnswer": { "@type": "Answer", "text": "Any numerical discrepancies exceeding the department's materiality threshold must be explicitly documented in the 'Comments/Discrepancies' section of the form." } } ] } </script> <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "SoftwareApplication", "name": "UT Austin Internal Audit Portal", "applicationCategory": "EducationalApplication", "operatingSystem": "Web-based", "provider": { "@type": "EducationalOrganization", "name": "University of Texas at Austin" }, "description": "The official UT Austin portal for managing audit documentation, fiscal compliance, and internal audit form submissions." } </script>