Documenting Financial/Accounting Transactions

Responsible Officer
Sue Paulson
Controller
Owner
Mollie Viola
Director of Accounting Services
Primary Contact
Mollie Viola
Director of Accounting Services
Last Revised
Effective Date

Policy Statement

Justification standards help ensure that the benefit to the institution and compliance with regulatory requirements is clearly documented and can be understood by both internal and external reviewers (e.g., managers, auditors, IRS, the public) for all financial and accounting transactions.

University faculty and staff initiating, preparing, completing or approving any sponsored or non-sponsored financial transactions must comply with the justification and documentation standards established by this policy, all other associated policies, procedures and job aids.

Units must ensure that the transaction justification and supporting documentation includes complete and transparent information about the transaction, to include:

  • WHO initiated the transaction and who are the affected individuals or units?
  • WHAT is the transaction for?
  • WHERE did/will the activity take place (if applicable)?
  • WHEN did/will the activity take place (if applicable)?
  • WHY the transaction is being completed and how does the transaction relate to or benefit the account affected or charged?

Units need not repeat information in the justification that is already included in the transaction or supporting documentation. Rather to comply with policy, the justification must provide an explanation about the allowability, allocability, reasonableness and benefit to the project/University not already apparent within the transaction or supporting documentation.

Units must record transactions accurately, in a timely manner, and completely within financial system guidelines and applicable external agency rules (including federal agencies funding University programs, the Internal Revenue Service, and the Minnesota Department of Revenue). Accurate recording includes adequate descriptions of transactions, as well as the correct use of chart of account codes and all other chart fields.

Reason for Policy

University financial transaction documentation for sponsored and non-sponsored activity must consistently meet and comply with legal, governmental and auditing requirements. Providing thorough and complete transaction justifications and supporting documentation protects and benefits the University in the following ways:

  • Minimizes the risk of penalties and fines due to unsubstantiated business expenses.
  • Ensures compliance with legal and regulatory requirements.
  • Establishes adequate and consistent documentation standards for all financial transactions.
  • Provides an independent and efficient source for obtaining transactional information.
  • Complies with tax regulations that specify requirements for nontaxable reimbursements under an accountable plan versus reimbursements taxable to employees.
  • Minimizes reputational risks and adverse public perception.

Contacts

SubjectContactPhoneEmail
General Document Instructions University Financial Helpline 612-624-1617 [email protected]
Policy Questions Mollie Viola 612-625-0126 [email protected]

Definitions

Accountable Plan
An accountable plan requires that reimbursements and/or other expense allowance arrangements meet certain IRS requirements related to business-connection and substantiation, and requires that amounts in excess of substantiated expenses be returned in a timely manner. Amounts paid under an accountable plan are excluded from the individual's income. Reimbursements made that do not meet the requirements of the accountable plan are taxable.
Allocable Costs
Expenses for goods or services which can be charged to (or allocated to) a particular unit, activity or function because the goods or services provide a commensurate benefit to that unit, activity or function.
Allowable Costs
Expenses for goods or services which can be charged to a particular source of funds. Expenses may be deemed allowable by law or regulation; by external parties such as donors or sponsors; or by the University, based on the institution’s risk management profile.
Documentation Standards
Common rules and guidelines that establish the form, type and amount of documentation that is reasonable and appropriate to establish the justification for a transaction. Documentation requirements may include (but are not limited to) the following, depending on the type of transaction:
  • Written explanations containing relevant financial data elements (such as emails) Detailed receipts, or confirmation of payment;
  • Bill of sale, invoice, etc.
Non-Sponsored Funds (NS)
Includes general operations and maintenance, miscellaneous unrestricted, auxiliaries, internal service organizations, federal appropriations, state specials, and miscellaneous restricted. See funds included in this fund type.
Sponsored Project
An externally funded activity that is governed by specific terms and conditions. Sponsored projects must be separately budgeted and accounted for subject to terms of the sponsoring organization. Sponsored projects may include grants, contracts, and cooperative agreements, as well as other public service activities.
Substantiation
The IRS requires that records be provided on a timely basis that show details of the Who, What, Where, When and Why to substantiate all expenses reimbursed under an accountable plan. For hospitality expenses, including entertainment and meals with non-university attendees, the nature, timing and duration of the business discussion and the names of the persons who took part in the entertainment activity must also be part of the substantiation.
Transaction Justification
Explanations that delineate a transaction’s legitimate business purpose or benefit to the University regardless of funding source, May be supplied by supporting documentation and/or written explanation when documentation does not provide adequate clarity or transparency.

Responsibilities

Approver/Certified Approver
Ensures all documents submitted for approval contain adequate justification and supporting documentation as required by this policy, job aids, and related procedures.
Controller's Office
Ensures accuracy and appropriateness of policy. Responsible for timely updates, policy maintenance and related communications; compliance oversight.
Department Manager
Communicates policy requirements and ensures compliance for their area(s). Oversees and monitors all transaction activity in their area.
RRC
Oversees and monitors all transaction activity in their units.
Transaction Initiator
Requests the purchase of goods, services or travel; initiates process of procurement. Provides supporting documentation and clear and complete business justification for the transaction preparer.
Transaction Preparer
Prepares transaction in the financial system in accordance with policies and procedures. Obtains appropriate approvals.

Related Information

History

Amended:
November 2014 - Comprehensive Review, Minor Revision. Comprehensive review. New appendices to assist in determining what additional information should be added to a transaction to satisfy the 5 Ws. Minor changes to language to improve clarity.
Amended:
July 2008: Job Aid and Responsibilities updated to reflect EFS changes.
Amended:
June 2004 - Transaction Justification Job Aid was published in December 2003. The job aid has been updated to reflect that "How" justifications only required when the account relationship is unclear. Notes were added or enhanced for Budgeting; and Entertainment, Hospitality & Recruiting sections. Examples were added to several sections. Justification requirements changed for Payment to External Vendors & Individuals and Sponsored Accounts (Purchases from Internal Vendors, External Vendors & External Vendors and Individuals) only section.
Effective:
July 2004

Document Feedback

Notification: Please be aware that while we rarely receive these data requests, any information submitted through this comment form is public, including your name, email address and comment/question, unless you are a student.

Add new comment

The content of this field is kept private and will not be shown publicly.
About text formats

Plain text

  • No HTML tags allowed.
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.