Search within:

FARM Overview

Summary

Financial Approvers and Related Metadata system , also known as FARM, is a system used to streamline the management of financial transaction approvals across the University. FARM enables Planning Unit CFAOS/Financial Leads and their delegates to centrally maintain who can approve transactions in BobcatBUY, Concur, and Individual Compensation Distribution (ICD) based on their university organizational structure. It is also used to track approvers for OHIO Business Service Center requests and planning unit leadership roles such as Current Dean/Director/VP and CFAO (Chief Financial and Administrative Officer) and Signature Sub-delegation.

Key Features

The FARM system has a number of features that allow planning units to maintain their approvers while minimizing the effort required:

  • Can assign approvers based on the organization hierarchy, as new organizations are set-up the approvers are already established based on the hierarchy
  • Can copy an existing employee’s approval levels
  • Can replace one employee’s approval levels by assigning someone else, due to reorganization/turnover
  • Can easily remove/end date an employee’s approval levels

Logging into FARM

You can access FARM from:

Use your OHIO email and password to single-sign on to access FARM.

Access and Roles

  • Fiscal Officer:
    • CFAO or Financial Lead of planning unit
    • Can establish delegates to maintain approvers
    • Can set up and maintain approvers
    • Access to the fiscal officer role is maintained centrally.  Current fiscal officers or CFAOs should email financecustomercare@ohio.edu if a fiscal officer needs to be added/replaced.
  • Delegates:
    • Can set up and maintain approvers
    • Access to the FARM delegate role is maintained by the planning unit’s fiscal officer(s) directly in FARM.
  • Approvers:
    • Roles set up within FARM to approve financial transactions in systems such as BobcatBUY, Concur, and ICD.
    • These approvers do not have access in FARM

Definitions

Organization:The units within Ohio University that have responsibility for sections of the University budget. Organizations range from entire budgets devoted to each vice president’s area of responsibility, down to each individual office or department.

Approval Type:The different systems for which FARM provides approver status. Includes BobcatBUY, Concur, Individual Compensation Distribution (ICD), OHIO BSC, and other planning unit roles.

Approval Level: The range of financial and/or approval levels per approval type. 

BobcatBUY

Approver Levels Limit Amounts
$0 - $1500 $1,500
$1500 - $5k $5,000
$5k - $10k $10,000
$10k - $25k $25,000
$25k - $50k $50,000
$50k+ $50,000+

Concur

Approver Levels Limit Amounts
Approvals for Travel/PCARD expense reports $100,000

Individual Compensation Distribution (ICD)

Approver Levels Limit Amounts
Escalation for Department Head $100,000
Department Head $100,000

Organization Hierarchy

Parent vs. Child Organization Levels

Parent values summarize child values for reporting purposes. Parent organization values begin with a letter followed by five numbers.  For example: C14000 or E14020.

Child values are used for posting transactions and entering budget.  Child organization values consist of six numerical characters.  For example: 140200 or 140210.

Example:

Parent vs Child Hierarchy Chart

For more information about the Organization hierarchy, please review the Organization Segment Quick Reference Guide .

All approvals in FARM will be based on organization and utilize the organization hierarchy. Approvers can be set up at any level in the organization hierarchy (planning unit level, department level or by individual organization value); however, it is recommended to set approvers at the planning unit or department parent levels when possible.

Approvers set at a parent level will trickle down to the individual organizations in the hierarchy. This requires less data entry and is easier to maintain than setting approvers at each individual org child value. Additionally, if new orgs are created, they will inherit the approvals that you have already set at the parent level. If you choose to set an approver at an individual org level, that approver will only apply to that specific org.

When approvers are set at multiple levels in the hierarchy, the logic used to identify which approvers get sent to BobcatBUY, Concur, and ICD varies.  See details below: 

System Approver Selection if Approvers are Set at Multiple Levels in the Hierarchy
BobcatBUY (BCB) Approvers set at all levels in the organization’s hierarchy are sent to BCB, but one of the approvers will need to assign the transaction to themself to approve the transaction.
Concur Approvers set at all levels in the organization’s hierarchy may be selected as the approver.  Concur will randomly select one of the approvers.
Individual Compensation Distribution (ICD) Only the approver set at the lowest level in the organization’s hierarchy will be selected as ICD approvers (for example, if an approver is set for an individual org and a different approver is set at the C-level, the approver at the individual org is selected as the ICD approver and the approver at the C-level is ignored.)

FARM Structure

Planning Unit Setup

The page where a fiscal officer can add or delete delegates for each organization within the University. Find more information about Planning Unit Setup on our Quick Reference Guide .

Example, Planning Unit

Approver Setup

By Organization

The page where a fiscal officer or delegate can add, remove, or edit approvers for specific parent or child orgs. This page displays the full org hierarchy so that the user can maintain approvers at any org level in the hierarchy.  Find more information about Approver Setup on our Quick Reference Guide.

Example of by Organization

By User

The page where a fiscal officer or delegate can view and maintain approver roles for a specific person. On this page, users can:  

  • Add new approval roles to a person
  • Copy approvals from one approver to another
  • Replace an approver with another approver
  • Remove approval roles from a person
Example of by User

FARM Setup Reminders

The Financial Approvers and Related Metadata (FARM) system is used by planning units to maintain their approvers for finance and human resource transactions.  If these approvers are not set up properly, it results in errors that delay the processing of these transactions.  Here are a few FARM setup reminders to help reduce these errors/delays:

Ensure approvers are updated and current– Use the Replace Approver, Copy Approver, and Remove Approver features in FARM to easily maintain the approvers for your unit. More information about these features can be found in the Fiscal Officers quick reference guide:    If an employee is leaving their role or the university, please remember to update their approval roles in FARM.  Inactive employees listed as approvers in FARM will cause your transactions to fail.

Avoid missing approvers– Every organization must have at least one approver in every approval role in FARM.

Avoid duplicate approver issues– Some approval levels allow duplicates, while others will not. The chart below shows which approval roles permit multiple approvers.

Approval Type
Approval Level
Multiple approvers permitted in each approval level?
Can the approver be in more than one approver level for this approval type?
BobcatBUY
  • Req. Approval 0.01-1500.00
  • Req. Approval 1500.01-5000.00
  • Req. Approval 5000.01-10000.00
  • Req. Approval 10000.01-25000.00
  • Req. Approval 25000.01-50000.00
  • Req. Approval >$50K
Yes (one of the approvers will need to assign the transaction to themselves)
Yes
Concur
  • Approvals for Travel/PCARD expense reports
Yes (one approver will be randomly selected)
Yes
ICD
  • Dept Head approval
  • Escalation for DEPT Head (nonresponse)
No, only one person is permitted in each of these roles
No, the same person cannot be in both roles
Planning Unit Roles
  • CFAO
  • Vice President/Pres Council member
No, only one person is permitted in each of these roles
Yes, the same person can be in the VP and CFAO role
Planning Unit Signature Subdelegation
  • COA Segment Values (Signature Subdelegation)
  • Honorarium (Signature Subdelegation)
  • PCard Increases (Signature Subdelegation)
  • Short Form Services Agreement (Signature Subdelegation)
Yes
Yes
View Site in Mobile | Classic
Share by: