[{"id":6514,"date":"2025-08-25T11:14:57","date_gmt":"2025-08-25T16:14:57","guid":{"rendered":"https:\/\/it.tamus.edu\/famis\/?post_type=white_papers&#038;p=6514"},"modified":"2025-08-25T11:14:57","modified_gmt":"2025-08-25T16:14:57","slug":"september-gip-lng-biweekly-payrolls","status":"publish","type":"white_papers","link":"https:\/\/it.tamus.edu\/famis\/white-papers\/september-gip-lng-biweekly-payrolls\/","title":{"rendered":"Funding for September GIP and Longevity on the September Biweekly Payrolls"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Overview_and_Background\"><\/span>Overview and Background<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>This paper describes the assignment of employer Group Insurance Premium (GIP) and Longevity (LNG) contributions to the appropriate FAMIS bank and Uniform Statewide Accounting System (USAS) appropriation year, specifically when biweekly payroll crosses the fiscal year boundary of September 1 of each year.<\/p>\n\n\n\n<p>With the state general revenue (GR) fund (state fund 0001), the State of Texas appropriates funds for the employer contribution of the GIP in a separate appropriation number for each appropriation year. Longevity may also be funded from a separate appropriation, and other state funds may also use separate appropriations.<\/p>\n\n\n\n<p>For salaried \/ monthly paid employees who are funded (either fully or partially) from state funds, the process is straightforward. When their earnings for the September pay period (September 1\u201330) are processed, their earnings are funded from the new state appropriation, and the GIP and LNG funding follows using the new appropriation number and appropriation year as well. This is done through the FAMIS accounting analysis (AA) table.<\/p>\n\n\n\n<p>For biweekly paid employees, the process is more complex. The full monthly employer GIP contribution is assessed and taken on the first biweekly payroll paid in a month, a practice utilized for the last 30 to 40 years. Longevity is assessed and taken on the biweekly pay period that contains the first day of the month.<\/p>\n\n\n\n<p>With the implementation of Workday, special coding was implemented to ensure that the September GIP and LNG employer contributions were funded from the new year\u2019s appropriation. Due to the timing of pay periods in September 2024, the special coding was no longer effective, and funding for these employer charges from state funds was redirected to the previous year\u2019s appropriation.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Additional Details<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Biweekly pay periods end on Saturday. The actual pay date is always the following Friday, six days after the end of the pay period.<\/li>\n\n\n\n<li>The State of Texas funds and appropriates a monthly amount for the employer\u2019s share of GIP based on employee counts and the budget process. The funding is often provided in a separate appropriation.<\/li>\n\n\n\n<li>The Texas A&amp;M University System members plan on spending this GIP appropriation over 12 months.<\/li>\n\n\n\n<li>Historically (going back to the Budget Payroll Personnel [BPP] application), for biweekly paid employees, the employer contribution for GIP as an employer-paid benefit was charged on the first biweekly pay in any given month. Note that for employees, the deduction amount is split across the first two biweekly periods in a month.<\/li>\n\n\n\n<li>The process for LNG closely follows that of GIP, but longevity is paid on the biweekly period that contains the first day of the month.<\/li>\n\n\n\n<li>Before the A&amp;M System Workday implementation, pay periods were cut short and manipulated so that no payroll crossed the August 31 boundary. With the implementation of Workday, this practice was modified to include biweekly periods that cross the August 31 boundary.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Funding_for_Pay_Periods_Crossing_the_Fiscal_Year_Boundary\"><\/span>Funding for Pay Periods Crossing the Fiscal Year Boundary<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>State guidance indicates that for employees funded from state funds, earnings should be charged to the appropriation year corresponding to the period during which the work is performed. For example, if six working days of the two-week period occurred in August, 60% of the funding for the earnings should come from the old year\u2019s appropriation, with the remaining 40% coming from the new year.<\/p>\n\n\n\n<p>While this may be true for earnings, the A&amp;M System\u2019s practice for GIP funded 100% of the employer GIP and LNG contributions from the new year\u2019s appropriation. This creates a complex situation for biweekly employees paid from state funds for the first payroll in September, where the GIP and LNG appropriation years may differ from the earning appropriation year.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Understanding Workday Subperiods<\/h3>\n\n\n\n<p>The Workday assignment and handling of subperiods are relevant to understanding the funding of employer-paid GIP and LNG and the related challenges.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>In normal circumstances, Workday assigns subperiods for each week of the biweekly period.<\/li>\n\n\n\n<li>Normally, when the FAMIS integration creates a payroll detail record, it combines those subperiods into a single record showing the pay period as two weeks. Note that there are exceptions throughout the entire fiscal year in which the FAMIS payroll integration keeps payroll details separate by subperiod. &nbsp;An example of this is a change in pay rate. This process of creating multiple pay detail records does no harm, more payroll detail records are simply passed into FAMIS.<\/li>\n\n\n\n<li>However, when pay periods cross the August 31 \/ September 1 boundary at fiscal-year end, subperiods received from Workday are preserved in the payroll integration. This is achieved through specialized processing in the Workday-FAMIS integration. Note that Workday can also assign a subperiod if the employee\u2019s compensation rate changes during the regular pay period.<\/li>\n<\/ul>\n\n\n\n<p>This process in Workday results in employee earnings being separated, or at least closely separated, by fiscal year.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">End of FY 2024 and the Problem with the GIP Appropriation Year<\/h3>\n\n\n\n<p>At fiscal-year end in August of 2024 and due to the way the pay-period dates fell, a problem occurred for the first time:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The biweekly pay period was entirely in August, and<\/li>\n\n\n\n<li>The pay date was in September.<\/li>\n<\/ul>\n\n\n\n<p>Biweekly payrolls processed in previous years (since the implementation of Workday) always had at least one day of the pay period in the new fiscal year. The existing coding in the Workday-FAMIS integration incorrectly assumed that a certain number of days in the pay period would be in September.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Previous Solution<\/h3>\n\n\n\n<p>The coding that was in place attempted to direct GIP and LNG funding to the near-year appropriation in the following manner:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The incorrect assumption was that some of the pay period would be in the new fiscal year and that there would be earnings in the new fiscal year.<\/li>\n\n\n\n<li>GIP is normally allocated across all earnings that are GIP eligible. However, the previous coding had an exception for September. This coding would force all the GIP to the earnings in the pay period that was part of the new year.<\/li>\n\n\n\n<li>In September of 2024, since there were no earnings in the new fiscal year, all the GIP was allocated to the old year&#8217;s earnings, and in turn, no GIP was allocated to the new year&#8217;s appropriation.<\/li>\n<\/ul>\n\n\n\n<p>Note that this primarily caused pain and problems for A&amp;M System members when:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The A&amp;M System member had many biweekly employees who received the GIP benefit.<\/li>\n\n\n\n<li>Many of these employees were funded from the state funds.<\/li>\n<\/ul>\n\n\n\n<p>Note that state payroll funded from non-GR funds usually do not have separate GIP appropriations and are also likely able to carry those funds forward. Using the correct appropriation year is less of a significant issue with these non-GR funds.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">New Solution for FY 2025<\/h3>\n\n\n\n<p>For several reasons, the existing coding to force GIP and LNG to the new year payroll detail records was unsustainable. Separating or forcing GIP and LNG to a separate payroll detail record for just the September 1 biweekly was a significant challenge when no earnings belonged in the new year.<\/p>\n\n\n\n<p>The following solution was developed:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The GIP and LNG allocation to payroll detail records are simplified and return to the standard approach.\u00a0GIP and LNG will be spread across all eligible earning records (by UIN and pay period) regardless of the fiscal year.<\/li>\n\n\n\n<li>The Workday subperiods will continue to be respected for the pay period and pay date that crosses the August 31 boundary.<\/li>\n<\/ul>\n\n\n\n<p>When state funds are involved, the requirement remains to fund the earnings from the correct appropriation year, which in FAMIS is the correct new appropriation year bank. This is accomplished by using the AA code from the relevant fiscal year, which directs the payroll to be funded from the correct bank account.<\/p>\n\n\n\n<p>The following steps outline the process for determining the AA code for the September biweekly pay period:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>As described above, the payroll records are split according to the Workday subperiod.<\/li>\n\n\n\n<li>The fiscal year, now also known as the <strong>Appropriation Fiscal Year<\/strong> (AFY), of the pay period is determined.\n<ul class=\"wp-block-list\">\n<li>If the period or subperiod crosses the September 1 boundary, the payroll detail record is assigned to the AFY that contains the most working days.\n<ul class=\"wp-block-list\">\n<li>If most of the working days for the period or subperiod are in the old year, the payroll detail record will be considered a prior-year AFY record.<\/li>\n\n\n\n<li>If most of the working days in the period \/ subperiod are in the new year, this is treated as a new AFY record.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>For other biweekly periods, the payroll detail record is assigned to a fiscal year based on the actual pay date.<\/li>\n\n\n\n<li>For monthly periods, the payroll detail record is assigned to an AFY based on the pay-period end date (i.e., the last day of the month). This aligns with the accounting effective date of the payroll expense.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>The Subsidiary Ledger-Support Account (SL-SA) attributes are looked up in the <strong>current fiscal year<\/strong> to determine the relevant AA code.<\/li>\n\n\n\n<li>AA overrides are applied. If this is a prior-year pay period, the prior-year AA override table is used.<\/li>\n\n\n\n<li>The AA table lookup will be done. \n<ul class=\"wp-block-list\">\n<li>If this record is a prior-year record, the <strong><em>PRIOR year&#8217;s AA table is used for the earnings.<\/em><\/strong><\/li>\n\n\n\n<li>The <strong><em>NEW (current) year&#8217;s AA table is used for GIP and LNG.<\/em><\/strong><\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<p>This process will drive the GIP and LNG (if any) to the new appropriation year.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Screen_Image_Examples\"><\/span>Screen Image Examples<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The following screen images contain highlights of relevant data elements.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/08\/WP_SummerGIP-AAMaint-724-2.png\"><img loading=\"lazy\" decoding=\"async\" width=\"714\" height=\"436\" src=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/08\/WP_SummerGIP-AAMaint-724-2.png\" alt=\"Screen capture of FAMIS Screen 724 Accounting Analysis Maintenance with fiscal year and Pay Kind fields highlighted\" class=\"wp-image-6511\" srcset=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/08\/WP_SummerGIP-AAMaint-724-2.png 714w, https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/08\/WP_SummerGIP-AAMaint-724-2-300x183.png 300w\" sizes=\"auto, (max-width: 714px) 100vw, 714px\" \/><\/a><\/figure>\n\n\n\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/07\/WP_SummerGIP-AAMaint-GIPLNG-724.png\"><img loading=\"lazy\" decoding=\"async\" width=\"723\" height=\"446\" src=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/07\/WP_SummerGIP-AAMaint-GIPLNG-724.png\" alt=\"Screen capture of FAMIS Screen 724 Accounting Analysis Maintenance with fiscal year and GIP and LNG benefit fields highlighted. Added note reads &quot;When using the new year table, the new year Appropriation banks will be used for salary, GIP, and LNG&quot;\" class=\"wp-image-6512\" srcset=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/07\/WP_SummerGIP-AAMaint-GIPLNG-724.png 723w, https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/07\/WP_SummerGIP-AAMaint-GIPLNG-724-300x185.png 300w\" sizes=\"auto, (max-width: 723px) 100vw, 723px\" \/><\/a><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Notes_on_PCTs_and_the_Accounting_Analysis_Table\"><\/span>Notes on PCTs and the Accounting Analysis Table<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The described solution for GIP and LNG allocations impacts payroll cost transfer (PCT) processing and the AA table in the following ways:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>If the PCT is for a period that crosses the fiscal year boundary, the same logic is applied to the AA table lookup and the determination of the GIP and LNG charge codes and banks.<\/li>\n\n\n\n<li>PCTs for prior-year pay periods use the prior-year AA table.<\/li>\n\n\n\n<li>PCTs for two previous fiscal years (currently, only the Texas Division of Emergency Management [TDEM]) only use the prior-year AA table.\u00a0A change is being considered.\u00a0Note the technical problem in routine FBPR061.<\/li>\n\n\n\n<li>PCTs for prior years DO NOT interrogate the AA override table.<\/li>\n\n\n\n<li>AA table lookups are handled in routine FNSPPHAA.\u00a0This applies to batch and PCTs.<\/li>\n<\/ul>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Overview and Background This paper describes the assignment of employer Group Insurance Premium (GIP) and Longevity (LNG) contributions to the appropriate FAMIS bank and Uniform Statewide Accounting System (USAS) appropriation [&hellip;]<\/p>\n","protected":false},"author":37507,"template":"","categories":[49],"tags":[],"class_list":["post-6514","white_papers","type-white_papers","status-publish","category-white-papers","entry"],"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/6514","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers"}],"about":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/types\/white_papers"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/users\/37507"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/6514\/revisions"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/media?parent=6514"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/categories?post=6514"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/tags?post=6514"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":6302,"date":"2025-07-10T10:47:52","date_gmt":"2025-07-10T15:47:52","guid":{"rendered":"https:\/\/it.tamus.edu\/famis\/?post_type=white_papers&#038;p=6302"},"modified":"2025-07-10T11:13:26","modified_gmt":"2025-07-10T16:13:26","slug":"oeec-charges","status":"publish","type":"white_papers","link":"https:\/\/it.tamus.edu\/famis\/white-papers\/oeec-charges\/","title":{"rendered":"OEEC Charges and the FAMIS Accounting Analysis Table"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Overview_and_Background\"><\/span>Overview and Background<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>In 2024, through the Workday application, The Texas A&amp;M University System was made aware of new payroll taxes to be assessed on employees working in other states. The first tax \/ assessment was for the state of Vermont, but recently, notifications have been received from Colorado and Oregon. Massachusetts also has an employer tax, but it has not yet been activated for the A&amp;M System because the minimum employee threshold has not been met.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Employer_Contribution\"><\/span>Employer Contribution<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The new taxes are levied on both the employee and the employer. This is different from the state income tax, which Workday has handled since its implementation. State income tax is a withholding levy on employees, deducted from their gross earnings.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Creation_of_New_OEEC_Benefit_Type_and_Object_Code_1986\"><\/span>Creation of New OEEC Benefit Type and Object Code 1986<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The A&amp;M System uses the term \u201cbenefits\u201d or \u201cemployer contribution\u201d to describe additional charges paid by the employer for the benefit of the employee.<\/p>\n\n\n\n<p>Since these new taxes \/ assessments are levied on the employer, the code \u201cOEEC\u201d (Other Employer and Employee Charges) was created. These charges must be expensed in the financial system; therefore, an additional A&amp;M System expense object code (1986) was created.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"FAMIS_Accounting_Analysis_Table_Impact\"><\/span>FAMIS Accounting Analysis Table Impact<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>FAMIS depends on the accounting analysis table to direct employer-funded benefits to the proper funding source. See the <a href=\"https:\/\/it.tamus.edu\/famis\/white-papers\/accounting-analysis-and-payroll-charge-codes\/\">Accounting Analysis and Payroll Charge Codes<\/a> white paper for a description of that process.<\/p>\n\n\n\n<p>Since the OEEC was a new employer charge, a new entry in the table would have been ideal. However, changing this table is a complex and involved process. The A&amp;M System team decided to leverage an existing, though rarely used, table entry.<\/p>\n\n\n\n<p>The Federal Insurance Regular (FIR) employer benefit was created for the AgriLife Extension as an employer contribution for employees with federal civil service appointments. Only a few of these employees remain active and employed by the A&amp;M System. Since the FIR benefit was never utilized outside of these few AgriLife Extension employees, the decision was made to have OEEC and FIR use the same accounting analysis table entries.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"System_Member_Requirement\"><\/span>System Member Requirement<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The merging of FIR \/ OEEC entries in the accounting analysis table now means that A&amp;M System members can no longer specify zero on the accounting analysis table for FIR \/ OEEC. A valid charge code must now be specified.<\/p>\n\n\n\n<p>Note that if an employee receiving Federal Insurance has FIR charges allocated to any other A&amp;M System member, other than AgriLife Extension, the charge code will be changed to zero for those entries, and the amount will not be charged through Workday to the FAMIS payroll integration.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Equity_Transfers\"><\/span>Equity Transfers<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Employees who are subject to these new taxes \/ assessments can be jointly funded. Therefore, OEEC charges may result in equity transfer requirements. The A&amp;M System member employing the person is responsible for paying these taxes. This is true regardless of the employee\u2019s costing allocations and is comparable to the payment of Federal Insurance Contributions Act (FICA) taxes (Social Security and Medicare).<\/p>\n\n\n\n<p>The FAMIS integration process has been modified to include OEEC in the equity transfer process.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Example_Accounting_Analysis_Table\"><\/span><strong>Example Accounting Analysis Table<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<figure class=\"wp-block-image size-full is-resized\"><a href=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/07\/WP_OEEC-AAMaintenance-724.png\"><img loading=\"lazy\" decoding=\"async\" width=\"671\" height=\"403\" src=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/07\/WP_OEEC-AAMaintenance-724.png\" alt=\"Screen capture of FAMIS Screen 724 Accounting Analysis Maintenance with FIR benefit item highlighted\" class=\"wp-image-6298\" style=\"width:997px;height:auto\" srcset=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/07\/WP_OEEC-AAMaintenance-724.png 671w, https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/07\/WP_OEEC-AAMaintenance-724-300x180.png 300w\" sizes=\"auto, (max-width: 671px) 100vw, 671px\" \/><\/a><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>Overview and Background In 2024, through the Workday application, The Texas A&amp;M University System was made aware of new payroll taxes to be assessed on employees working in other states. [&hellip;]<\/p>\n","protected":false},"author":37507,"template":"","categories":[49],"tags":[],"class_list":["post-6302","white_papers","type-white_papers","status-publish","category-white-papers","entry"],"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/6302","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers"}],"about":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/types\/white_papers"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/users\/37507"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/6302\/revisions"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/media?parent=6302"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/categories?post=6302"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/tags?post=6302"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":6270,"date":"2025-06-26T08:48:05","date_gmt":"2025-06-26T13:48:05","guid":{"rendered":"https:\/\/it.tamus.edu\/famis\/?post_type=white_papers&#038;p=6270"},"modified":"2025-06-26T09:25:15","modified_gmt":"2025-06-26T14:25:15","slug":"accounting-analysis-and-payroll-charge-codes","status":"publish","type":"white_papers","link":"https:\/\/it.tamus.edu\/famis\/white-papers\/accounting-analysis-and-payroll-charge-codes\/","title":{"rendered":"Accounting Analysis and Payroll Charge Codes"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Overview_and_Background\"><\/span>Overview and Background<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The accounting analysis (AA) table contains configuration and coding information that serves two primary purposes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Directing payroll expenses to the appropriation funding source, including specific Uniform Statewide Accounting System (USAS) information for state-funded payroll<\/li>\n\n\n\n<li>Directing employer-paid benefits to the correct funding source and FAMIS cost center (i.e., the FAMIS Subsidiary Ledger [SL] account)<\/li>\n<\/ul>\n\n\n\n<p>The table can be either very simple or very detailed, depending on the business requirements.<\/p>\n\n\n\n<p>FAMIS uses cost centers (SL accounts and support accounts [SAs]) and object codes to properly classify payroll expenses. Here, the FAMIS SLs and SAs will be referred to as the FAMIS SL-SA. Additionally, FAMIS utilizes the bank account attribute to manage and link accounting activities to state funds and state appropriations. Directing payroll to the proper bank account is critical to the payroll-to-accounting process.<\/p>\n\n\n\n<p>The AA table was originally the domain of the previous A&amp;M System payroll system (Budget Payroll Personnel [BPP]) that was retired in 2017. At that time, ownership and responsibility for the table were transferred to the FAMIS domain. The concepts and functionality of the table remained relevant because the Workday implementation did not address the benefit allocation or USAS state integration requirements.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Timing_Application_and_Building_Payroll_History\"><\/span>Timing, Application and Building Payroll History<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>In the A&amp;M System, payroll calculation is the responsibility of Workday.&nbsp;This includes managing positions, base pay compensation, allowances and other additional compensation, as well as deductions and benefits.&nbsp;&nbsp;Workday also manages the allocation of payroll expenses to FAMIS SL-SA and the actual payment of employee net pay (whether by Automated Clearing House [ACH] or check).<\/p>\n\n\n\n<p>Once payroll is calculated and allocated, the data is transferred to the FAMIS application for posting to accounting, as well as for the allocation and distribution of employee deductions and employer-funded benefits (e.g., Teacher Retirement System [TRS], Optional Retirement Program [ORP], Social Security, Medicare). During the FAMIS process, the rules and guidance provided by the FAMIS AA table are applied to the Workday payroll results. This process is referred to as building payroll history. Payroll history contains all payroll details, from the allocation and costing of benefits to the employee and cost allocation level. The accounting analysis charge codes are critical to this process.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Benefits Not Calculated by Workday<\/h3>\n\n\n\n<p>During the implementation of Workday, the developers identified selected benefits that could not be calculated in Workday to meet A&amp;M System requirements because the benefit rates were based on A&amp;M System member costing allocations. Workday calculates payroll before it calculates the costing allocation split; therefore, it cannot accurately calculate the benefit rates to meet A&amp;M System requirements. This was true for the following benefits:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Unemployment Compensation Insurance (UCI)<\/li>\n\n\n\n<li>Workers&#8217; Compensation Insurance (WCI)<\/li>\n\n\n\n<li>Leave pool (LEAVE)<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Assignment_of_the_Accounting_Analysis_Code\"><\/span>Assignment of the Accounting Analysis Code<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>AA codes are assigned to each payroll detail item based on the FAMIS SL-SA provided from the Workday pay results. The AA is specified as an attribute on each FAMIS SL-SA.<\/p>\n\n\n\n<p>Additionally, FAMIS enables business administrators to modify and override AA codes throughout the fiscal year. &nbsp;Currently, this is done on FAMIS Screen 725  (Accounting Analysis Override).<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Benefit_Types\"><\/span>Benefit Types<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The AA table provides funding instructions for the following benefit types:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>GIP \u2013 Group Insurance Premium<\/li>\n\n\n\n<li>FICA &#8211; OASI (Social Security) and OAHI (Medicare)<\/li>\n\n\n\n<li>LNG \u2013 Longevity<\/li>\n\n\n\n<li>TRS \u2013 Teacher retirement contribution<\/li>\n\n\n\n<li>TRS 90 \u2013 Teacher retirement contribution during the employee&#8217;s first 90 days<\/li>\n\n\n\n<li>TRS CARE \u2013 Additional TRS medical coverage for some employees<\/li>\n\n\n\n<li>TRS SURC \u2013 TRS surcharge for TRS retirees working at more than 50% effort<\/li>\n\n\n\n<li>UCI \u2013 Unemployment Compensation Insurance assessment<\/li>\n\n\n\n<li>WCI \u2013 Workers&#8217; Compensation Insurance assessment<\/li>\n\n\n\n<li>ORP BASE \u2013 Optional Retirement Base account<\/li>\n\n\n\n<li>ORP SUPL \u2013 ORP supplemental amount (grandfathered ORP participants only)<\/li>\n\n\n\n<li>ORP SSUP \u2013 ORP System supplement amount (grandfathered ORP participants only)<\/li>\n\n\n\n<li>FIR &#8211; Federal Insurance Regular (for employees with Civil Service appointments)<\/li>\n\n\n\n<li>OEEC \u2013 Other Employee and Employer Charges (current taxes assessed by another state for employees that do not live in Texas)<\/li>\n\n\n\n<li>CSRS \u2013 Civil Service Retirement System<\/li>\n\n\n\n<li>LEAVE \u2013 Accrued leave assessment<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Charge_Codes\"><\/span>Charge Codes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The purpose of the benefit charge codes is to direct benefit expenses to the correct FAMIS SL-SA and bank.&nbsp;Based on business requirements and statutory requirements (both state and federal), funding for various benefits may need to come from a different source than the funding of the actual payroll earnings.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Charge Code 1<\/h3>\n\n\n\n<p>Charge Code 1 is the most straightforward charge code.&nbsp;It simply directs the benefit to the same FAMIS SL-SA and bank that funded the employee earnings.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Charge Code 2<\/h3>\n\n\n\n<p>Charge Code 2 is used when the benefit expense is to be assigned to a different FAMIS SL-SA account and also requires the specification of a FAMIS bank. Simply defined, Charge Code 2 means paid by the bank and account specified on the BPP AA table. This code is typically used when benefits are centrally funded (and not charged to departmental FAMIS SL-SA accounts) or when other restrictions are in effect.<\/p>\n\n\n\n<p>Note that for SAs, the AA table does not allow for the specification of an SA as part of its configuration and process.&nbsp;However, special coding is in place for both AgriLife Research (06) and AgriLife Extension (07) to facilitate the assignment of the SA. For AgriLife Research, the SA is the same as the one used for the earnings; for AgriLife Extension, the support account is derived from the bank and the fiscal year.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Charge Code 3<\/h3>\n\n\n\n<p>Charge Code 3 indicates that the benefit is to be charged to the same FAMIS SL-SA as the earning but is assigned to a different FAMIS bank account.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Charge Codes 4 through 7<\/h3>\n\n\n\n<p>Charge Codes 4 through 7 are specifically created for the allocation of <em>retirement<\/em> benefits when federal funds are used to fund the earnings.&nbsp;These codes are only allowed to be specified on TRS and ORP benefits for the following system members:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>06 \u2013 AgriLife Research<\/li>\n\n\n\n<li>07 &#8211; AgriLife Extension<\/li>\n\n\n\n<li>05 \u2013 Prairie View A&amp;M University<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Charge Codes 4 and 5<\/h4>\n\n\n\n<p>Charge Codes 4 and 5 have special processing that splits the retirement benefit amount into two parts:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Up to 5% of the covered earnings is considered the \u201ccharged\u201d amount.<\/li>\n\n\n\n<li>Retirement benefit amounts beyond the 5% are considered \u201cuncharged.\u201d<\/li>\n<\/ul>\n\n\n\n<p>Note that the payroll integration process does not handle these uncharged amounts.&nbsp;The state general revenue appropriation actually pays the uncharged benefits for TRS or ORP through special processes.<\/p>\n\n\n\n<p>With <em>Charge Code 4<\/em>, the charged amount is assigned to the same FAMIS SL-SA and bank as the earning.<\/p>\n\n\n\n<p>With <em>Charge Code 5<\/em>, the charged amount is assigned to the specified FAMIS SL-SA and to the specified bank. The same special logic for SAs as applied in Charge Code 2 is also applied to the SA.<\/p>\n\n\n\n<p><em>Note that Charge Codes 4 and 5 are for TRS and ORP <strong>only<\/strong> and cannot be used on the other TRS benefits or the ORP supplemental benefits.<\/em><\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Charge Codes 6 and 7<\/h4>\n\n\n\n<p>Charge Codes 6 and 7 are new in Fiscal Year 2025 and replace special hard-coding and exception logic, placing control of the retirement split in the hands of the person maintaining the AA table.<\/p>\n\n\n\n<p>These codes have special processing that splits the retirement benefit amount into two parts, which differs from the split used for Charge Codes 4 and 5:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>One-half of the employee\u2019s retirement benefit, with a maximum of 5% of the covered earnings<\/li>\n\n\n\n<li>The remaining amount (nearly always the other half) is uncharged.<\/li>\n<\/ul>\n\n\n\n<p>With <em>Charge Code 6<\/em>, the charged amount is assigned to the same FAMIS SL-SA and bank as the earnings.<\/p>\n\n\n\n<p>With <em>Charge Code 7<\/em>, the charged amount is assigned to a specified FAMIS SL-SA and to the specified bank. The same special logic for SAs as applied in Charge Code 2 is also applied to the SA.<\/p>\n\n\n\n<p>As with charge Codes 4 and 5, these uncharged amounts are not handled by the payroll integration process. The state general revenue appropriation actually pays the uncharged benefits for TRS or ORP through special processes.<\/p>\n\n\n\n<p>With Charge Codes 6 and 7, the charged contribution is calculated as the employer ORP-covered earnings multiplied by .033 (half of 6.6%) for most employees and employer ORP-covered earnings multiplied by .0425 (half of 8.5%) for \u201cgrandfathered\u201d employees. See <a href=\"#grandfather\">Grandfathered ORP Employees and ORP Supplements<\/a> for more information.<\/p>\n\n\n\n<p><em>Note that Charge Codes 6 and 7 are for TRS and ORP <strong>only<\/strong> and cannot be used on the other TRS benefits or the ORP supplemental benefits.<\/em><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Charge Code 0<\/h3>\n\n\n\n<p>Charge Code 0 is a special charge code applicable only to certain benefits. Note that specifying Charge Code 0 does not eliminate any obligation the system member may have in paying or funding benefits.<\/p>\n\n\n\n<p>This code indicates that the benefit amount retrieved by Workday should be ignored or not charged.&nbsp;This is best understood by examining the appropriate use of Charge Code 0 for each relevant benefit.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Workers&#8217; Compensation Insurance<\/h4>\n\n\n\n<p>The WCI benefit is an assessment to allow the A&amp;M System to build up a reserve pool for future WCI claims. Note that the A&amp;M System runs a self-insured workers&#8217; compensation plan. Currently, certain types of funds do not now allow an assessment of this nature. For example, WCI cannot be charged on state funds because it would allow funds to be moved from USAS and the state treasury to be held locally for potential future expense.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Unemployment Compensation Insurance<\/h4>\n\n\n\n<p>Like WCI, the UCI benefit is an assessment that allows the A&amp;M System to build a reserve pool for future unemployment claims. Also like WCI, the A&amp;M System runs a self-insured plan for unemployment claims. Certain types of funds allow an assessment of this nature.&nbsp;Note that if an employee is funded from state general revenue, the state (not the A&amp;M System) is proportionally responsible for any unemployment claims, and the proportions are reported to the Texas Workforce Commission through a quarterly integration between FAMIS and the commission.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Leave Assessment<\/h4>\n\n\n\n<p>The A&amp;M System also assesses an amount of payroll to fund vacation balance payouts when employees terminate. This is the LEAVE assessment. As with WCI and UCI, certain funding sources do not permit this type of assessment.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">TRS when Funded by General Revenue (State of Texas Fund 0001)<\/h4>\n\n\n\n<p>When TRS is funded (or partially funded) by state general revenue appropriations, most system members assign Charge Code 0 to the TRS contribution. A special process at the state transfers funds to TRS from the general revenue fund, and the dollars do not flow through the system members&#8217; treasury accounts. System members later manually book these expenses.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Civil Service Retirement<\/h4>\n\n\n\n<p>Texas AgriLife Extension is fully responsible for Civil Service Retirement System (CSRS) contributions. Other system members do not share these contributions and are not charged; therefore, Charge Code 0 is used by all other A&amp;M System members for CSRS.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Optional Retirement Program<\/strong><\/h4>\n\n\n\n<p>Although it is not recommended, some members use Charge Code 0 for the ORP base amount and manually handle the state general revenue portion of ORP.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">FIR and OEEC<\/h4>\n\n\n\n<p>When the new OEEC benefit became active in Workday, a decision was made to share the FIR AA directives with OEEC. This decision was made due to the limitations of the FAMIS AA table and the complexities of adding another set of codes to the AA table.  The sharing of AA directives was possible because FIR charges are very rare and are being phased out.<\/p>\n\n\n\n<p>Therefore, the FIR charge code is now shared with the OEEC benefit.&nbsp;System members have traditionally used Charge Code 0, but in the future, Charge Code 0 should no longer be permitted.<\/p>\n\n\n\n<p id=\"grandfather\">Note that the charge codes on the table under the OEEC \/ FIR label are now primarily for OEEC.&nbsp;If FIR changes are allocated to any system member other than Agrilife Extension (07), the charge code will be changed to 0, and no FIR charges will be applied.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Grandfather_ORP_Employees_and_ORP_Supplements\"><\/span>Grandfather ORP Employees and ORP Supplements<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>In the mid-1990s, the State of Texas limited its contribution to ORP retirement to 6.6%, which was the TRS employer contribution amount at that time. Employees already enrolled in ORP at that time retained the previous ORP rate of 8.5% and are referred to as \u201cgrandfathered.\u201d&nbsp; The A&amp;M System set up a process to fund the additional 1.9% (the difference between 6.6% and 8.5%).&nbsp;<\/p>\n\n\n\n<p>This change occurred in two steps, and the 1.9% was split into two components:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ORPL \u2013 1.19% of the employee\u2019s covered earnings<\/li>\n\n\n\n<li>ORPS \u2013 0.71% of the employee\u2019s covered earnings<\/li>\n<\/ul>\n\n\n\n<p>The ORP base amount is 6.6% of the employee\u2019s covered earnings. Note that Workday is responsible for identifying grandfathered ORP employees and applying the correct employer contribution rate for the ORP contribution. The FAMIS payroll history process is responsible for splitting the ORP contribution for grandfathered employees into the base and supplemental components.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Employees_with_Federal_Appointments\"><\/span>Employees with Federal Appointments<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>In addition to the charge code logic, special logic for AgriLife Extension employees with federal appointments remains in place during the payroll history build process. This is true even though only a handful of employees with federal appointments exist. Employees are identified as federal appointments if they are both AgriLife Extension employees and have a CSRS deduction. When an employee has a federal appointment, the charge code for ORP or TRS is set to zero (Charge Code 0), in accordance with federal guidance.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Screen_724_Accounting_Analysis_Maintenance\"><\/span>Screen 724 (Accounting Analysis Maintenance)<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/06\/724_AcctAnalysisMaint.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"535\" src=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/06\/724_AcctAnalysisMaint-1024x535.png\" alt=\"Screen capture of FAMIS Screen 724 Accounting Analysis Maintenance\" class=\"wp-image-6274\" srcset=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/06\/724_AcctAnalysisMaint-1024x535.png 1024w, https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/06\/724_AcctAnalysisMaint-300x157.png 300w, https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/06\/724_AcctAnalysisMaint-768x401.png 768w, https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/06\/724_AcctAnalysisMaint-800x418.png 800w, https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2025\/06\/724_AcctAnalysisMaint.png 1280w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>Overview and Background The accounting analysis (AA) table contains configuration and coding information that serves two primary purposes: The table can be either very simple or very detailed, depending on [&hellip;]<\/p>\n","protected":false},"author":37507,"template":"","categories":[49],"tags":[],"class_list":["post-6270","white_papers","type-white_papers","status-publish","category-white-papers","entry"],"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/6270","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers"}],"about":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/types\/white_papers"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/users\/37507"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/6270\/revisions"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/media?parent=6270"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/categories?post=6270"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/tags?post=6270"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":6128,"date":"2025-01-30T08:27:37","date_gmt":"2025-01-30T14:27:37","guid":{"rendered":"https:\/\/it.tamus.edu\/famis\/?post_type=white_papers&#038;p=6128"},"modified":"2025-01-30T08:48:17","modified_gmt":"2025-01-30T14:48:17","slug":"understanding-earning-codes","status":"publish","type":"white_papers","link":"https:\/\/it.tamus.edu\/famis\/white-papers\/understanding-earning-codes\/","title":{"rendered":"Understanding Earning Codes"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Introduction\"><\/span>Introduction<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The Texas A&amp;M University System set up and defined earning codes as part of implementing the Workday human capital management (HCM) and payroll system. Earning codes are a controlled data element critical to any Workday Payroll implementation. The Workday implementation team at the Texas A&amp;M University System defined all earnings based on business requirements.<\/p>\n\n\n\n<p>Earning definitions and their assigned codes are available to authorized Workday users via a report called \u201cAll Earnings.\u201d These earning codes are available for selection in Workday on payroll inputs, compensation plans and allowances depending on the type of earning.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Impact_in_Workday\"><\/span>Impact in Workday<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Earning codes direct the Workday payroll calculation\u2019s behavior and impact the gross-to-net calculation. Earning codes are also used by benefits that control additional employer contributions and employee deductions.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Impact_Downstream_from_Workday\"><\/span>Impact Downstream from Workday<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>In addition to the impact inside of Workday, earning codes and their related attributes are critical to many integrations, including FAMIS, the Uniform Statewide Accounting System (USAS), Time and Effort, the Teacher Retirement System (TRS), and the Human Resources Information System (HRIS). Earning codes are also critical to downstream reporting.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Governing_Earning_Codes_and_Attributes\"><\/span>Governing Earning Codes and Attributes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Earning code attributes further define and direct processes to report and handle each usage of an earning code appropriately.&nbsp; To properly govern and control these codes and tables, the A&amp;M System built an earning code database available to all employees and staff. The A&amp;M System\u2019s master list of earning codes assigns and documents the attributes attached to each earning code. To view the master list of earning codes, see the <a href=\"https:\/\/tamus.quickbase.com\/db\/bqckiccab\" target=\"_blank\" rel=\"noreferrer noopener\">public TAMU Earning Codes website<\/a>.<\/p>\n\n\n\n<p>The remainder of this document describes the attributes assigned to each earning code found in the Master earning code database.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Earning Code Usage<\/h3>\n\n\n\n<p>Workday creates a corresponding compensation plan if the earning code is used as a one-time payment or allowance. The compensation plan is then added to the employee after the necessary approvals are completed per the business process configuration.&nbsp; Once the compensation plan is in place, it will impact current and future payrolls as defined in the plan.<\/p>\n\n\n\n<p>A compensation plan will designate the earning code and flow to Workday Payroll based on the effective date added.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Earning Families<\/h3>\n\n\n\n<p>An earning family is a group of earning codes that have similar characteristics. Earning families are primarily used for reporting, but grouping earning codes into families improves the overall understanding of the earning code concept. Each earning code is assigned to one of the following earning families:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Regular Pay<\/strong>: Compensation for normal job duties paid hourly or salaried monthly.<\/li>\n\n\n\n<li><strong>Overtime Pay<\/strong>: Compensation for normal job duties for employees classified as nonexempt and paid hourly.<\/li>\n\n\n\n<li><strong>Allowance:<\/strong> Funds paid, one time or at regular intervals, for a specific purpose. Allowances are usually part of a total compensation package and are disbursed to the employee through the payroll system.<br><br>These payments are not directly proportional to hours worked or an employee\u2019s monthly percent effort. Examples include allowances for:\n<ul class=\"wp-block-list\">\n<li>Cell phone<\/li>\n\n\n\n<li>Housing<\/li>\n\n\n\n<li>Relocation<br><br>Allowances are not tied to hours or effort and are not reported on full-time employee (FTE) reports or included in institutional base salary (IBS).<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<ol start=\"4\" class=\"wp-block-list\">\n<li><strong>Emolument<\/strong>: Cash or noncash gains from position or employment. Emoluments are paid directly to the employee outside of Workday but are a taxable event to the employee and are therefore recorded in the payroll system.<br><br>The difference between allowances and emoluments within the A&amp;M System are:\n<ul class=\"wp-block-list\">\n<li>Allowances are paid\/disbursed and taxed through the payroll system.<\/li>\n\n\n\n<li>Emoluments are paid outside of the payroll system, but the payroll system is used to assess and collect taxes on the compensation.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<ol start=\"5\" class=\"wp-block-list\">\n<li><strong>County Funds<\/strong>: Special emoluments used by the Texas A&amp;M AgriLife Extension Service to document and record payments to County Agents made by each Texas county. Most county agents are paid some of their compensation directly by the counties.<br><br>The A&amp;M System and Workday treat County Funds as special emoluments. Special handling is in place on these emoluments since the Texas A&amp;M AgriLife Extension Service is responsible for paying retirement and insurance benefits on them.<br><br>See the <a href=\"https:\/\/it.tamus.edu\/famis\/white-papers\/understanding-county-earnings\/\"><strong>Understanding County Earnings<\/strong><\/a> white paper for more information.<\/li>\n<\/ol>\n\n\n\n<ol start=\"6\" class=\"wp-block-list\">\n<li><strong>Lump Sum Merit<\/strong>: One-time merit or lump sum payments made to employees to recognize their performance or accomplishments. Merit-based salary\/hourly rate increases applied to regular pay are reported with regular pay.<\/li>\n\n\n\n<li><strong>Award<\/strong>: One-time payments made to employees and not subject to the A&amp;M System policy on merit payments.<\/li>\n\n\n\n<li><strong>Entitlement<\/strong>: Compensation paid to the employee based on statutory requirements not directly tied to effort. Currently, longevity is the only entitlement used by the A&amp;M System.<\/li>\n\n\n\n<li><strong>Lump Sum Payment<\/strong>: Payments to employees based on accumulated benefits or unpaid compensation. Examples include:\n<ul class=\"wp-block-list\">\n<li>Lump sum vacation payouts<\/li>\n\n\n\n<li>Payment of sick leave to diseased employee\u2019s estate<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Stipend<\/strong>: Fixed sum paid periodically to cover expenses or in recognition of additional job duties.<\/li>\n\n\n\n<li><strong>Uplift<\/strong>: An increase to the employee\u2019s regular pay rate in recognition of special circumstances. Examples include:\n<ul class=\"wp-block-list\">\n<li>Shift differential<\/li>\n\n\n\n<li>Expatriate work subject to different taxes<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Additional Pay<\/strong>: Compensation for services that are (at least) one of the following types:\n<ul class=\"wp-block-list\">\n<li>Temporary<\/li>\n\n\n\n<li>Beyond the scope of the employee\u2019s position restriction<\/li>\n\n\n\n<li>Targeted to a specific job profile or position type<\/li>\n\n\n\n<li>Related to a second position<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Object Codes<\/h3>\n\n\n\n<p>Earning codes map to FAMIS object codes. Earning codes for regular pay, overtime and one-time merit payments have a complex mapping based on the employee\u2019s faculty\/nonfaculty status and title. Most other earning codes map to a single object code.<\/p>\n\n\n\n<p>See the <a href=\"https:\/\/apps1.system.tamus.edu\/objcodes\" target=\"_blank\" rel=\"noreferrer noopener\">public Object Codes website<\/a> for the master list of object codes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Workday FIT Withholding Rate<\/h3>\n\n\n\n<p>Earning codes in Workday impact the amount of Federal Income Tax (FIT) withheld. The possible attribute values are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Supplemental \u2013 22%<\/strong>: FIT is withheld at the supplemental rate.<\/li>\n\n\n\n<li><strong>W-4<\/strong>: FIT is withheld at the employee\u2019s W-4 rate.<\/li>\n\n\n\n<li><strong>No FIT<\/strong>: No FIT is withheld.<\/li>\n<\/ul>\n\n\n\n<p>Based on the FIT Withholding Rate, earning codes in Workday will be added to the appropriate Pay Component Group, which groups all earnings together based on how they are taxed.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Workday Assess and Withhold Retirement<\/h3>\n\n\n\n<p>Earning codes may or may not be subject to retirement contributions. For example, base pay is subject to retirement holdings, but employee relocation allowances are not. The earnings code database reflects the Workday configuration.<\/p>\n\n\n\n<p>Possible attribute values are Yes or No.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">TRS Creditable<\/h3>\n\n\n\n<p>Each earning code is marked Yes or No, depending on whether the earnings must be reported to the Texas Retirement System (TRS). This attribute is used during the A&amp;M System integration to TRS TEAM.<\/p>\n\n\n\n<p>See the <a href=\"https:\/\/www.trs.texas.gov\/Pages\/re_creditable_compensation.aspx\">Creditable Compensation<\/a> page on the <a href=\"https:\/\/www.trs.texas.gov\/Pages\/Homepage.aspx\">TRS website<\/a> for more information.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Include on FTE Report<\/h3>\n\n\n\n<p>Each earning code is marked Yes or No, depending on whether the pay and effort are reported on the State Auditor FTE report. This data element is used exclusively in the Electronic Data Warehouse (EDW) application.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Include for Time and Effort \u2013 IBS<\/h3>\n\n\n\n<p>Each earning code is marked Yes or No depending on whether the payroll expense is part of the IBS and sent to the Time and Effort system.<\/p>\n\n\n\n<p>As defined by the A&amp;M System, IBS is the total guaranteed annual compensation an Individual receives from an A&amp;M System institution or agency, whether the individual\u2019s time is spent on research, teaching, patient care or other activities.<\/p>\n\n\n\n<p>Other institutions have a more in-depth definition of IBS. For example, IBS is defined by the University of Buffalo (UB) as the annual salary paid to an individual to perform all professional obligations required by the individual\u2019s primary UB appointment. These professional obligations may include research, teaching, administrative functions and\/or other service activities and are generally identified in the individual\u2019s appointment or reappointment letter. Unless otherwise specified, the annual salary stated in the appointment or reappointment letter fully compensates the individual for all professional obligations required by their primary UB appointment. IBS excludes any income that an individual is permitted to earn outside of duties performed as part of their primary UB appointment.<\/p>\n\n\n\n<p>IBS is set prospectively for an indefinite period or a specified term. It may not be increased or decreased based on the availability of salary support from sponsored agreements or other revenue sources.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">FAMIS \u2013 Payroll History Compute Hours<\/h3>\n\n\n\n<p>If marked Yes, the integration with Workday that builds the FAMIS payroll history data set will attempt to allocate hours worked to this earning code (if hours are available).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">FAMIS \u2013 SGIP (GIP)<\/h3>\n\n\n\n<p>FAMIS uses this attribute to control the allocation of the employer group insurance premium (GIP) to the set of appropriate earning codes. GIP is often called state GIP (SGIP) since the State of Texas often funds it. Typically, the GIP is charged to earning codes in the Regular Pay earning family. By attaching GIP charges to these earning codes, FAMIS also ensures that GIP is allocated to accounts in proportion to regular pay.<\/p>\n\n\n\n<p>Possible values are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Yes<\/strong>: Earning code (if present) will receive a proportional share of the GIP charge.<\/li>\n\n\n\n<li><strong>No<\/strong>: Earning code will not receive a proportional share of the GIP charge. Special allocation rules are in place for the allocation of GIP in the summer months.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">FAMIS \u2013 Retirement<\/h3>\n\n\n\n<p>FAMIS uses this attribute to control the allocation of retirement expenses (TRS or optional retirement program [ORP]) to the set of appropriate earning codes.<\/p>\n\n\n\n<p>Possible values are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Yes<\/strong>: Earning code (if present) will receive a proportional share of the employer retirement contribution.<\/li>\n\n\n\n<li><strong>No<\/strong>: Earning code will not receive a proportional share of the employer retirement contribution.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">FAMIS \u2013 FICA<\/h3>\n\n\n\n<p>FAMIS uses this element to control the allocation of the Federal Insurance Contributions Act (FICA; &nbsp;Old-Age and Survivors Insurance [OASI]\/OAHI [Medicare]) expenses to the set of appropriate earning codes.<\/p>\n\n\n\n<p>Possible values are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Yes<\/strong>: Earning code (if present) will receive a proportional share of FICA.<\/li>\n\n\n\n<li><strong>No<\/strong>: Earning code will not receive a proportional share of FICA.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">FAMIS \u2013 FIT<\/h3>\n\n\n\n<p>FAMIS uses this attribute to control the FIT allocation to the set of appropriate earning codes.<\/p>\n\n\n\n<p>Possible values are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Yes<\/strong>: Earning code (if present) will receive a proportional share of FIT.<\/li>\n\n\n\n<li><strong>No<\/strong>: Earning code will not receive a proportional share of FIT.<\/li>\n<\/ul>\n\n\n\n<p>Since FIT is an employee deduction, the allocation of FIT does not impact accounting.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">FAMIS \u2013 Unemployment Compensation Insurance (UCI)<\/h3>\n\n\n\n<p>A value of Yes indicates that the integration with Workday that builds the FAMIS payroll history data will attempt to allocate and assess UCI to this earning code.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">FAMIS \u2013 Workers Compensation Insurance (WCI)<\/h3>\n\n\n\n<p>A value of Yes indicates that the integration with Workday that builds the FAMIS payroll history data will attempt to allocate and assess WCI to this earning code.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">FAMIS \u2013 Emolument (EMOL)<\/h3>\n\n\n\n<p>A value of Yes indicates that special processing occurs. The special processing is as follows:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The emolument will <em>only<\/em>be allocated FICA (OASI, OAHI) deductions.<\/li>\n\n\n\n<li>The emolument will be allocated FIT\/state income tax (SIT)\/local income tax (LIT).\u00a0 Note that the allocation of deductions does not change accounting; it is only for reporting.<\/li>\n\n\n\n<li>Emoluments are no longer assessed UCI and WCI.\u00a0 Note that before FY 2025, most emoluments were assessed UCI and WCI.<\/li>\n\n\n\n<li>Covered earnings for the above are set to the earned amount itself.<\/li>\n\n\n\n<li><strong>The earned amount will be zeroed out (gross pay set to zero) because the earned amount does not need to be expensed in accounting.<\/strong><\/li>\n<\/ul>\n\n\n\n<p>A value of No indicates that regular benefit allocation processing occurs. Such processing uses other flags\/attributes of the earning code.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">FAMIS \u2013 Allowance<\/h3>\n\n\n\n<p>A value of Yes indicates that special processing occurs. The special processing is as follows:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The allowance will <em>only<\/em>be allocated FICA (OASI, OAHI) deductions.<\/li>\n\n\n\n<li>The allowance will be allocated FIT\/SIT\/LIT.\u00a0 The allocation of deductions does not change accounting; it is only for reporting.<\/li>\n\n\n\n<li>The allowance will be assessed UCI and WCI.<\/li>\n\n\n\n<li>Covered earnings for the above are set to the earned amount itself.<\/li>\n\n\n\n<li>The earning amount will be expensed in FAMIS<\/li>\n<\/ul>\n\n\n\n<p>A value of No indicates that regular benefit allocation processing occurs. Such processing uses other flags\/attributes of the earning code.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">FAMIS \u2013 Task Payment<\/h3>\n\n\n\n<p>A value of Yes indicates that this earning code is considered a task payment. Task Payment is a legacy reporting attribute only.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">FAMIS \u2013 Longevity<\/h3>\n\n\n\n<p>A value of Yes indicates that this earning code should get an allocation of the longevity payment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Group 100%<\/h3>\n\n\n\n<p>This attribute is used to assign source percent effort. Possible values are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>No<\/strong>: The earning code will stand alone with no grouping in the percent effort calculation and, therefore, will always get 100% of whatever benefits\/deductions are associated with the earning code.<\/li>\n\n\n\n<li><strong>Yes<\/strong>: Groups earning codes together for dispersing benefits and deductions.<\/li>\n\n\n\n<li><strong>Incremental<\/strong>: This value was added after several payrolls were run following the release of Workday HCM. A new grouping was needed to combine some earning codes to distribute their associated benefits\/deductions properly but not include them in regular pay.<\/li>\n\n\n\n<li>All other values are grouped with like values when computing percent effort (i.e., Yes and Incremental).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Pay Type<\/h3>\n\n\n\n<p>FAMIS assigns this pay type to the Payroll History record. Pay Type is a legacy value used in the previous Budget Payroll Personnel (BPP) system. The Pay Type value should not be used for reporting; the earning code itself should drive reporting. However, the value is assigned to facilitate backward compatibility.<\/p>\n\n\n\n<p>Possible values for Pay Type in the Pay History file are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>B<\/strong>: Normal Budgeted Monthly (FAMIS automatically converts to H if hourly biweekly)<\/li>\n\n\n\n<li><strong>D<\/strong>: Death Benefits<\/li>\n\n\n\n<li><strong>E<\/strong>: Adjustment or Correction Entry<\/li>\n\n\n\n<li><strong>F<\/strong>: Work Study<\/li>\n\n\n\n<li><strong>H<\/strong>: Normal Hourly Biweekly<\/li>\n\n\n\n<li><strong>I<\/strong>: Monthly supplemental Pay<\/li>\n\n\n\n<li><strong>J<\/strong>: On-Demand Payment \u2013 Monthly Payroll<\/li>\n\n\n\n<li><strong>K<\/strong>: On-Demand Payment \u2013 Biweekly Payroll<\/li>\n\n\n\n<li><strong>P<\/strong>: Biweekly Supplemental Pay<\/li>\n\n\n\n<li><strong>Q<\/strong>: Biweekly Supplemental Pay<\/li>\n\n\n\n<li><strong>U<\/strong>: Emolument<\/li>\n\n\n\n<li><strong>V<\/strong>: Vacation Lump Sum Payout<\/li>\n<\/ul>\n\n\n\n<p>FAMIS Screen 730 (Earning Code \/ Object Code Table) does not currently allow for a value of H. FAMIS will automatically change the Pay Type from B to H during the pay history generation process for biweekly payroll cycles for all earning codes with a Pay Type of B.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Include in FTE Base Pay<\/h3>\n\n\n\n<p>A value of Yes indicates that this earning code should be added to base pay (regular pay hourly [RPH], regular pay salary [RPS]) for the current FTE salary and FTE monthly salary calculation.<\/p>\n\n\n\n<p>This attribute was used to calculate FTE monthly salary rate, which becomes the denominator in the FTE calculation, but it is no longer used.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Allowance Encumbrance<\/h3>\n\n\n\n<p>A value of Yes indicates that this earning code does utilize allowance encumbering in FAMIS.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">HRIS Pay Transaction Type<\/h3>\n\n\n\n<p>Earning codes map earnings to Human Resources Information System (HRIS) payroll transaction types. The following HRIS transaction types are allowed:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>LS<\/strong>: A lump sum payment of accumulated annual leave upon employee termination or a lump sum payment for half of the accumulated sick leave or 336 hours, whichever is less, upon the death of an employee.<\/li>\n\n\n\n<li><strong>OP<\/strong>: Overtime payment for hours worked and regular work hours for an employee subject to the Fair Labor Standards Act (FLSA).<\/li>\n\n\n\n<li><strong>RP<\/strong>: Regular payment for regular work hours.<\/li>\n\n\n\n<li><strong>SP<\/strong>: Supplemental payment for an amount not included in the regular monthly payroll, a one-time payment for work performed in addition to an employee\u2019s regular job or a one-time merit payment (1XM entitlement).<\/li>\n\n\n\n<li><strong>TP<\/strong>: Task\/temporary payment for nonreportable, college work-study and student-status employees.<\/li>\n<\/ul>\n\n\n\n<p>HRIS permits other Pay Transaction types, but only the above types are used with earning codes<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">HRIS Entitlement Code<\/h3>\n\n\n\n<p>Earning codes map earnings to HRIS payroll entitlement codes. The following HRIS entitlement codes are allowed:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>1XM<\/strong>: One-time merit award<\/li>\n\n\n\n<li><strong>ALP<\/strong>: Annual Leave Pay<\/li>\n\n\n\n<li><strong>AWD<\/strong>: Award Pay<\/li>\n\n\n\n<li><strong>BSY<\/strong>: Base Salary<\/li>\n\n\n\n<li><strong>CAR<\/strong>: Car Allowance<\/li>\n\n\n\n<li><strong>CLO<\/strong>: Clothing Allowance<\/li>\n\n\n\n<li><strong>CRT<\/strong>: Certification\/Advanced Degree Pay<\/li>\n\n\n\n<li><strong>CSS<\/strong>: Cost of Living Salary Supplement<\/li>\n\n\n\n<li><strong>CTP<\/strong>: Compensatory Time Pay<\/li>\n\n\n\n<li><strong>ENR<\/strong>: Enrichment<\/li>\n\n\n\n<li><strong>EXP<\/strong>: Expense Allowance<\/li>\n\n\n\n<li><strong>EXM<\/strong>: Emergency One-Time Merit Award<\/li>\n\n\n\n<li><strong>HAZ<\/strong>: Hazardous Duty Pay<\/li>\n\n\n\n<li><strong>HLY<\/strong>: Hourly (Temporary Hourly only)<\/li>\n\n\n\n<li><strong>HOU<\/strong>: Housing Allowance (Including Utilities)<\/li>\n\n\n\n<li><strong>LDP<\/strong>: Location Differential Pay<\/li>\n\n\n\n<li><strong>LOG<\/strong>: Longevity Pay<\/li>\n\n\n\n<li><strong>MLS<\/strong>: Meals<\/li>\n\n\n\n<li><strong>MSC<\/strong>: Miscellaneous Entitlement<\/li>\n\n\n\n<li><strong>OCP<\/strong>: On-Call Pay<\/li>\n\n\n\n<li><strong>OTP<\/strong>: Overtime Pay<\/li>\n\n\n\n<li><strong>SCH<\/strong>: Scholarship Allowance<\/li>\n\n\n\n<li><strong>SDP<\/strong>: Specialty Differential Pay<\/li>\n\n\n\n<li><strong>SEV<\/strong>: Severance Pay<\/li>\n\n\n\n<li><strong>SHD<\/strong>: Shift Hours Differential Pay<\/li>\n\n\n\n<li><strong>SLP<\/strong>: Sick Leave Pay<\/li>\n\n\n\n<li><strong>SPA<\/strong>: Augmentation\/Special Augmentation<\/li>\n\n\n\n<li><strong>SRB<\/strong>: Retention Bonus<\/li>\n\n\n\n<li><strong>SSP<\/strong>: Student Status Payments (College Work Study\/Student Status only)<\/li>\n\n\n\n<li><strong>STI<\/strong>: Stipend\/Extra Duty Pay<\/li>\n\n\n\n<li><strong>SUP<\/strong>: Salary Supplementation<\/li>\n\n\n\n<li><strong>TOP<\/strong>: Teaching Overload<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">HRIS Payroll Type<\/h3>\n\n\n\n<p>Earning codes map earnings to HRIS payroll types. The following HRIS payroll types are allowed:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>BIW<\/strong>: Biweekly \u2013 Regular<\/li>\n\n\n\n<li><strong>MON<\/strong>: Monthly \u2013 Regular<\/li>\n\n\n\n<li><strong>LUM<\/strong>: Lump Sum Payments<\/li>\n\n\n\n<li><strong>OTP<\/strong>: Overtime Payments<\/li>\n\n\n\n<li><strong>SUP<\/strong>: Supplemental<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Introduction The Texas A&amp;M University System set up and defined earning codes as part of implementing the Workday human capital management (HCM) and payroll system. Earning codes are a controlled [&hellip;]<\/p>\n","protected":false},"author":37507,"template":"","categories":[49],"tags":[],"class_list":["post-6128","white_papers","type-white_papers","status-publish","category-white-papers","entry"],"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/6128","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers"}],"about":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/types\/white_papers"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/users\/37507"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/6128\/revisions"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/media?parent=6128"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/categories?post=6128"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/tags?post=6128"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":6036,"date":"2024-11-12T08:06:58","date_gmt":"2024-11-12T14:06:58","guid":{"rendered":"https:\/\/it.tamus.edu\/famis\/?post_type=white_papers&#038;p=6036"},"modified":"2024-11-13T07:27:14","modified_gmt":"2024-11-13T13:27:14","slug":"sl-budgets-gl-fund-balance","status":"publish","type":"white_papers","link":"https:\/\/it.tamus.edu\/famis\/white-papers\/sl-budgets-gl-fund-balance\/","title":{"rendered":"DRAFT &#8211; Understanding Subsidiary Ledger Budgets versus General Ledger Fund Balance"},"content":{"rendered":"\n<p><em><strong>NOTE<\/strong><\/em>:<br><em>November 2024: This FAMIS white paper was written in 1991 yet remains relevant today.&nbsp; It has been edited and updated but is by and large presented in its original form.<\/em><\/p>\n\n\n\n<p>In FAMIS, budget authority is given to cost centers by budget entries in the subsidiary ledger (SL) accounts.&nbsp;These budget entries do not affect fund balance, cash or anything else in the general ledger (GL) balance sheet accounts. <em>Note, however, that the budget amounts from SL accounts are recorded in the GL summary account controls.<\/em><\/p>\n\n\n\n<p>Technically, budget authorization can be created without a supporting basis.&nbsp;This is not desirable, so the question remains: how can the GLs and the SLs be managed so that budget authority is given only when funds are available or expected? The answer is in enforcing, on a <em>procedural<\/em> basis, the following formula for every GL that has SLs:<\/p>\n\n\n\n<p>+ Fund balance<br>=<br>+ Expense budget balance available (Expense BBA)<br>+ Encumbrances<br>+ Revenue budget balance available (Revenue BBA)<\/p>\n\n\n\n<p>Note that encumbrances are added back to the Expense BBA because they have not been deducted from the fund balance.<\/p>\n\n\n\n<p>What the formula says is essentially that the Expense BBA in the SL should be &#8220;covered&#8221; by (1) the fund balance in the corresponding GL or (2) a corresponding revenue budget (i.e., estimated income). As expenditures are incurred or as revenue is received, both sides of the equation will be impacted equally. If the equation is out of  balance, there are two possible explanations:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>The budget has been inappropriately allocated to an SL account, or<\/li>\n\n\n\n<li>The difference is intentional, and the amount represents unallocated fund balance (i.e., unbudgeted fund balance reserve).<\/li>\n<\/ol>\n\n\n\n<p>Therefore, it is more correct to represent the above equation as:<\/p>\n\n\n\n<p>+ Fund Balance<br>\u2013 Fund Balance to be held in reserve<br>=<br>+ Expense BBA<br>+ Encumbrances<br>+ Revenue BBA<\/p>\n\n\n\n<p>By management decision, the reserve balance for some GL accounts may be kept at zero (0), in which case, any unobligated reserves can be held as fund balance in a separate standalone GL or as Expense BBA in another SL.&nbsp;However, keeping reserve balances in a GL account with or without SL accounts is perfectly acceptable. Keeping reserve balances as budget balances in SL accounts is possible, but with no intent to spend.<\/p>\n\n\n\n<p>The best ways to manage the reserve balance in GL accounts are:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>For a <strong>cost-reimbursable grant<\/strong>, set up the entire expense budget for the grant amount.&nbsp; Then, set up a revenue budget for the same amount as the expense budget.<\/li>\n\n\n\n<li>For a restricted account on a <strong>cash basis<\/strong> (i.e., allow expenses only to the extent revenue has been received; often done with gift accounts), do NOT set up a budget for the account, but set the generated expense budget (GEB) flag to Y.&nbsp;The budget generator program will adjust both the revenue and expense budgets, thus keeping the reserve amount constant.<\/li>\n\n\n\n<li>If budget authority for an SL account is <strong>transferred<\/strong> from another SL account, the corresponding cash from the first GL account must be transferred into the new GL.&nbsp;This is routinely done by doing budget transfers with the cash transfer field set to Y. Note that if both SLs are mapped to the same GL, no cash transfer will be done.<\/li>\n\n\n\n<li>If the budget authority for an SL account must come from the <strong>fund balance in another GL<\/strong>, the cash should be transferred into the mapped GL for the SL receiving the budget authority.&nbsp;For this, two things are needed:\n<ul class=\"wp-block-list\">\n<li>A journal entry with a fund addition account control (thus increasing the fund balance) for the new GL and<\/li>\n\n\n\n<li>A fund deduction account control with the old GL.&nbsp;<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n<!-- wp:paragraph&gt;-->\n<p>The expense budget can then be entered in the SL as the original or revised budget.<\/p>\n<!-- \/wp:post-content -->\n\n<!-- wp:heading -->\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"FAMIS_Classic_Report_FBAR530\"><\/span>FAMIS Classic Report: FBAR530<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>In 1991, FAMIS Report FBAR530 was developed to provide insight into GL balances, SL budgets and fund balances held in reserve. This report is a management tool that produces a year-to-date report comparing GL fund balances to SL budget balances. The report prints one line per GL showing the fund balance and the summary of the SL encumbrance, expense and revenue figures. The final column shows the unbudgeted fund balance reserve.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>FBAR530 can be run with Option2 set to Y. This version prints each SL&#8217;s balances within the GL, identifying the portion of the GL fund balance contained in each SL.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:heading -->\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"BusinessObjects_Universe_FAMIS_GLSL_Balances\"><\/span>BusinessObjects Universe: FAMIS GL\/SL Balances<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>A BusinessObjects universe was developed to provide the same functionality as the report FBAR530. The universe has additional features and capabilities and is highly recommended. Fund balances can be analyzed using multiple combinations of attributes.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:heading -->\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"FAMIS_Screen_702\"><\/span>FAMIS Screen 702<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>The reserve balance can also be observed on FAMIS Screen 702 (GL 6 Digit Reserve Balance).<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:acf\/accessible-screenshot {\"name\":\"acf\/accessible-screenshot\",\"data\":{\"screenshot_heading\":\"FAMIS Screen 702 GL 6 Digit Reserve Balance\",\"_screenshot_heading\":\"field_5ec598982e785\",\"screenshot_heading_level\":\"h3\",\"_screenshot_heading_level\":\"field_5ec598da2e786\",\"screenshot_image\":6038,\"_screenshot_image\":\"field_5ec5954a5bb67\",\"screenshot_text\":\"702 GL 6 Digit Reserve Balance                                 11\/10\/24 10:56\\r\\n                                                                  FY 2025 CC 01\\r\\n  Screen: ___  Account: 029500 ____         JOURNEY 2024 TEST ACCOUNT\\r\\n               Thru Month: 11  November\\r\\n    Department: INRE    Resp Person: SCHULZ, MARK A        Flags: D F\\r\\n                                                                  N N\\r\\n                                           Year to Date Balance\\r\\n                                              Thru November\\r\\n                                         \\u002d\\u002d\\u002d\\u002d\\u002d\\u002d\\u002d\\u002d\\u002d\\u002d\\u002d\\u002d\\u002d\\u002d\\u002d\\u002d\\u002d\\u002d\\u002d\\u002d\\u002d\\u002d\\r\\n Special Reserves                                         0.00\\r\\n Fund Balance                                         8,500.00\\r\\n Reserve for Encumbrances                                 0.00\\r\\n   Accrued Cash Balance                               8,500.00\\r\\n\\r\\n Fund Balance                                         8,500.00\\r\\n Revenue Budget - Unrealized                        100,000.00\\r\\n Unobligated Remaining Budget                        98,500.00\\r\\n Reserve for Encumbrances                                 0.00\\r\\n   Estimated Uncommitted Fund Balance                10,000.00  *\\r\\n\\r\\n            * If negative - corrective action may be necessary\\r\\nEnter-PF1\\u002d\\u002d-PF2\\u002d\\u002d-PF3\\u002d\\u002d-PF4\\u002d\\u002d-PF5\\u002d\\u002d-PF6\\u002d\\u002d-PF7\\u002d\\u002d-PF8\\u002d\\u002d-PF9\\u002d\\u002d-PF10\\u002d\\u002dPF11\\u002d\\u002dPF12\\u002d\\u002d-\\r\\n      Hmenu Help  EHelp\",\"_screenshot_text\":\"field_5ec595dd5bb68\"},\"mode\":\"auto\"} \/-->","protected":false},"excerpt":{"rendered":"<p>NOTE:November 2024: This FAMIS white paper was written in 1991 yet remains relevant today.&nbsp; It has been edited and updated but is by and large presented in its original form. [&hellip;]<\/p>\n","protected":false},"author":37507,"template":"","categories":[49],"tags":[],"class_list":["post-6036","white_papers","type-white_papers","status-publish","category-white-papers","entry"],"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/6036","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers"}],"about":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/types\/white_papers"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/users\/37507"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/6036\/revisions"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/media?parent=6036"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/categories?post=6036"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/tags?post=6036"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":5793,"date":"2024-07-19T10:30:14","date_gmt":"2024-07-19T15:30:14","guid":{"rendered":"https:\/\/it.tamus.edu\/famis\/?post_type=white_papers&#038;p=5793"},"modified":"2024-07-19T10:33:02","modified_gmt":"2024-07-19T15:33:02","slug":"understanding-emoluments","status":"publish","type":"white_papers","link":"https:\/\/it.tamus.edu\/famis\/white-papers\/understanding-emoluments\/","title":{"rendered":"Understanding Emoluments"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Introduction\"><\/span>Introduction<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>This whitepaper addresses processing emoluments by the Texas A&amp;M University System and integration with Workday and FAMIS.<\/p>\n\n\n\n<p>Emoluments are compensations recorded in Workday that occur outside the regular payroll process. These payments can be either cash or noncash. For example, noncash emoluments might include company cars or housing provided to employees, whereas cash emoluments could be gift cards paid outside the payroll system. Recording these payments in Workday ensures they are properly taxed and reported on employees\u2019 W2 forms.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Emoluments_in_Workday\"><\/span>Emoluments in Workday<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Entry as one-time payment or allowance<\/strong>: Emoluments are entered into Workday as one-time payments (payroll inputs) or allowances or recorded as recurring allowances (e.g., Housing, Employer-Provided Vehicle, etc.).<\/li>\n\n\n\n<li><strong>Employee tax<\/strong>: Both cash and noncash emoluments are subject to federal taxes, and Workday calculates taxes (Federal Insurance Contributions Act [FICA] and Federal Income Tax) on these payments. This tax is usually deducted from other earnings the employee may have. If no earnings are present, the deductions will go into arrears.<\/li>\n\n\n\n<li><strong>No impact on retirement or GIP<\/strong>: Group Insurance Premium (GIP; sometimes referred to as State GIP [SGIP]) is the employer contribution made to cover an employee\u2019s health insurance). Emoluments do not affect retirement calculations or GIP.<\/li>\n\n\n\n<li><strong>Employer contributions<\/strong>: The employer is also taxed for the employer FICA. It is applied and paid based on the current cost allocations for that employee. The costing allocation account can be specified as part of the emolument data entry.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"FAMIS_Integration\"><\/span>FAMIS Integration<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Allocation to FAMIS SL accounts<\/strong>: The FAMIS SL account to bear the employer tax (FICA) on the emoluments is usually derived from the payroll input or the allowance.<\/li>\n\n\n\n<li><strong>Zero gross pay<\/strong>: Emoluments are a zero gross pay payroll item.<\/li>\n\n\n\n<li><strong>FICA application<\/strong>: Workday calculates the FICA to these payments.<\/li>\n\n\n\n<li><strong>No GIP allocation<\/strong>: GIP is not allocated to emoluments. Beginning with July 2024 payrolls, Unemployment Compensation Insurance (UCI) and Workers\u2019 Compensation Insurance (WCI) are not assessed on emoluments.<\/li>\n\n\n\n<li><strong>FTE report exclusion<\/strong>: Emoluments are not on the full-time equivalent (FTE) report.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>This whitepaper addresses processing emoluments by the Texas A&amp;M University System and integration with Workday and FAMIS.<\/p>\n","protected":false},"author":37507,"template":"","categories":[49],"tags":[],"class_list":["post-5793","white_papers","type-white_papers","status-publish","category-white-papers","entry"],"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/5793","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers"}],"about":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/types\/white_papers"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/users\/37507"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/5793\/revisions"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/media?parent=5793"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/categories?post=5793"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/tags?post=5793"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":5788,"date":"2024-07-19T10:24:03","date_gmt":"2024-07-19T15:24:03","guid":{"rendered":"https:\/\/it.tamus.edu\/famis\/?post_type=white_papers&#038;p=5788"},"modified":"2024-07-22T08:14:42","modified_gmt":"2024-07-22T13:14:42","slug":"understanding-county-earnings","status":"publish","type":"white_papers","link":"https:\/\/it.tamus.edu\/famis\/white-papers\/understanding-county-earnings\/","title":{"rendered":"Understanding County Earnings"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Introduction\"><\/span>Introduction<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>This whitepaper addresses the unique funding structure and payroll processing for Texas County Extension agents by the Texas A&amp;M University System and Workday. County Extension agents receive funding from the Texas A&amp;M AgriLife Extension Service and the local county government. This dual-source funding arrangement is unique within the A&amp;M System. It came about because Texas counties preferred a direct payment model establishing an employer-employee relationship instead of a contractual agreement between the Extension Service and each county.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Purpose\"><\/span>Purpose<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The purpose of this white paper is to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Explain the shared funding model for Texas County Extension agents.<\/li>\n\n\n\n<li>Clarify why TAMUS needs to account for the county portion in Workday and FAMIS.<\/li>\n\n\n\n<li>Describe the mechanics of tracking and processing these earnings.<\/li>\n\n\n\n<li>Detail the integration of county earnings within FAMIS.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Funding_Structure\"><\/span>Funding Structure<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Shared Funding<\/h3>\n\n\n\n<p>Texas County Extension agents receive compensation from two sources:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Texas A&amp;M AgriLife Extension Service<\/strong>: The Extension Service provides funding for agents, most often from state funds, but funds could also come from other or multiple sources, such as federal appropriations or grants.<\/li>\n\n\n\n<li><strong>Local county<\/strong>: The local county directly pays the agents, creating a local employer-employee relationship. However, the county does not contribute to an agent\u2019s Group Insurance Premium (GIP) or retirement program. See <strong>Insurance and Retirement Allocations<\/strong> in <strong>FAMIS Integration<\/strong> below.<\/li>\n<\/ul>\n\n\n\n<p>The local counties prefer direct payment over a reimbursement model for several reasons:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Establishes a direct employer-employee relationship.<\/li>\n\n\n\n<li>Simplifies the administrative process for counties.<\/li>\n\n\n\n<li>Ensures timely compensation for the agents.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Workday_Integration\"><\/span>Workday Integration<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">System and State Funding<\/h3>\n\n\n\n<p>The A&amp;M System and state funding cover full group insurance (medical) and retirement benefits as if the extension agent were a full-time employee of the system. Consequently, the accurate accounting of the county portion is essential for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Employee benefits<\/strong>: Ensures agents receive the correct benefits, including medical insurance and retirement contributions.<\/li>\n\n\n\n<li><strong>Compliance and reporting<\/strong>: Maintains compliance with state and federal regulations regarding employee compensation and benefits.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Mechanics of County Earnings in Workday<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">Tracking and Calculations<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Earning codes<\/strong>: County earnings are tracked with earning Codes 153 and 155 and are assigned as allowances in Workday.<\/li>\n\n\n\n<li><strong>Retirement calculation<\/strong>: This allowance is included in the retirement calculations, impacting both Teacher Retirement System (TRS) and Optional Retirement Program (ORP) benefits.<\/li>\n\n\n\n<li><strong>FTE monthly salary rate<\/strong>: For payroll cost transfer (PCT) processing, full-time equivalent (FTE) reporting and payroll expense reporting as seen in FAMIS and Canopy payroll expense screens, county earnings are included in the FTE monthly salary rate. This is done in the FAMIS\/Workday integration of payroll results. However, the FTE monthly salary rate in Workday will not include county earnings.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Tax and Benefit Considerations<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Tax withholding<\/strong>: Workday does not withhold Federal Income Tax (FIT) or apply Federal Insurance Contributions Act (FICA) taxes (OASI, OAHI) to county earnings; the county withholds and manages these taxes.<\/li>\n\n\n\n<li><strong>Benefits<\/strong>: The county earnings are included in the calculation in Workday, so in most cases, the county agent is recognized as a full-time employee.<\/li>\n\n\n\n<li><strong>Journal entries<\/strong>: Workday does not create journal entries for county earnings since they do not create a payment to the employee. Special processing occurs in the Workday to FAMIS integration to account for these earnings in FAMIS.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"FAMIS_Integration\"><\/span>FAMIS Integration<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Integration Details<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>FTE monthly salary rate<\/strong>: FAMIS includes the county earnings allowance in the FTE monthly salary rate.<\/li>\n\n\n\n<li><strong>Earning codes<\/strong>: County earnings are provided to FAMIS as specific earning codes (see Earning Code Attributes).<\/li>\n\n\n\n<li><strong>Assigning the SL account<\/strong>: FAMIS operations maintain a table (COUNTY-FUNDING-ACCOUNT) on FAMIS FRS Screen 863 to associate county earnings with a FAMIS SL account (e.g., 199999). While no gross pay is charged to this account, it assists in allocating benefits for these earnings.<\/li>\n\n\n\n<li><strong>Determining the AA code<\/strong>: The FAMIS SL account from the COUNTY-FUNDING-ACCOUNT table is linked to an accounting analysis (AA) code on FAMIS Screen 008. This AA code and the SL account are used to identify the accounts, charge codes, and banks assigned to the benefit charges (FAMIS Screen 724).<\/li>\n\n\n\n<li><strong>Insurance and Retirement allocations<\/strong>: Group Insurance Premium (GIP; sometimes referred to as State GIP [SGIP]) is the employer contribution made to cover an employee\u2019s health insurance and must be funded by a cost center (FAMIS SL account). The cost of GIP is spread over the various regular (e.g., regular salary, hourly salary, some stipends) earnings. The GIP and retirement and longevity benefits are proportionally allocated to county earnings based on the percentage of county earnings to the agent\u2019s overall monthly earnings.<\/li>\n\n\n\n<li><strong>FTE reporting<\/strong>: County earnings are included in FTE reports, with special coding recognizing these earnings as payments despite zero gross pay. This is done through integration with the TAMUS Enterprise Data Warehouse.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>This whitepaper addresses the unique funding structure and payroll processing for Texas County Extension agents by the Texas A&amp;M University System and Workday. County Extension agents receive funding from the Texas A&amp;M AgriLife Extension Service and the local county government. <\/p>\n","protected":false},"author":37507,"template":"","categories":[49],"tags":[],"class_list":["post-5788","white_papers","type-white_papers","status-publish","category-white-papers","entry"],"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/5788","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers"}],"about":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/types\/white_papers"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/users\/37507"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/5788\/revisions"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/media?parent=5788"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/categories?post=5788"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/tags?post=5788"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":5004,"date":"2023-07-21T10:54:49","date_gmt":"2023-07-21T15:54:49","guid":{"rendered":"https:\/\/it.tamus.edu\/famis\/?post_type=white_papers&#038;p=5004"},"modified":"2023-07-27T10:23:14","modified_gmt":"2023-07-27T15:23:14","slug":"budget-module-update","status":"publish","type":"white_papers","link":"https:\/\/it.tamus.edu\/famis\/white-papers\/budget-module-update\/","title":{"rendered":"Budget Module Update &#8211; Spring 2023"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Background\"><\/span>Background<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>In FAMIS, the budget module is a collection of screens, processes, and functions that allow the A&amp;M System and its member institutions and agencies to develop the operating budget for the upcoming fiscal year. &nbsp;The outputs of the budget module are official reports and financial plans that are approved by the Board of Regents, as well as data and accounting entries that are loaded to FAMIS to support the operations for the upcoming year. A budget account is a Subsidiary Ledger (SL) account (see <a href=\"https:\/\/it.tamus.edu\/famis\/core-concepts\/core-concept-subsidiary-ledger-sl-account\/\">Core Concept: Subsidiary Ledger (SL) Account<\/a>) activated in the budget module and ready to connect dollars, patterns and categories to build up a system member\u2019s annual budget.<\/p>\n\n\n\n<p>During the Financial System Modernization project in which The Texas A&amp;M University System IT staff took FAMIS through code conversion from a mainframe platform to a Windows platform, the budget module surfaced several times with challenges related to manual processes dependent on outdated and obsolete tools. Elements of the budget module\u2019s design passed these challenges on to the stakeholders.&nbsp;&nbsp;<\/p>\n\n\n\n<p id=\"block-44f1462c-665e-4e90-ab4f-2c2f794c8dfa\">For budget fiscal years (FY) 2022 and 2023, some changes were made to the budget module to address and mitigate some of these challenges. Going into FY 2024, the project team decided to finish updating the module and take it through some significant rework and refactoring to help better serve the needs of the A&amp;M System.&nbsp;&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"block-2cee0d96-6cfb-48cf-9b1c-a4053c3aa04f\"><span class=\"ez-toc-section\" id=\"Update_Objectives\"><\/span>Update Objectives&nbsp;<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"block-b8f6b304-43d4-439d-91b3-74183d1fc0e3\">Simplify Budget Account Creation&nbsp;<\/h3>\n\n\n\n<p id=\"block-d5617442-475b-4b45-b2b4-420ad5c57173\">A significant objective for updating the budget module is to simplify the process of budget account creation and reduce the complicated request process.&nbsp;&nbsp;<\/p>\n\n\n\n<p id=\"block-f38ead0a-e39f-41aa-9548-4cf250b480ba\">In the past, as system members entered into the budget cycle each year, budget accounts are established and patterns are connected to each budget account by several batch processes used in different ways by each system member. Large numbers of complicated requests had to be submitted to the FAMIS production services team. The updated budget module will consolidate all account setup processes into a single process, FBAU588, controlled by a table. Once the table is set up, it will be effective and usable year after year with minimal changes. The FBAU588 table will allow a system member to define all desired budgeted accounts, assign patterns to each account, and prepare them for entry with Canopy or FAMIS.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"block-09a637cd-1dcd-4e9f-acef-523dde6c3687\">Simplify Pattern Creation and Management&nbsp;<\/h3>\n\n\n\n<p>Another significant objective of the budget module update was to simplify the creation and management of patterns so that a standard pattern could be created and used with any automatic budgeted reallocation (ABR) rule. An ABR is a way of budgeting in the operation and ongoing part of FAMIS that defines categories and budget controls. See the&nbsp;<a href=\"https:\/\/it.tamus.edu\/famis\/core-concepts\/core-concept-automatic-budget-reallocation\/\" target=\"_blank\" rel=\"noreferrer noopener\"><strong>Core Concept: Automatic Budget Reallocation<\/strong><\/a>&nbsp;page for more information on ABRs.&nbsp;<\/p>\n\n\n\n<p>The initial design of the budget module required the creation of a pattern for every ABR rule, which is a category set. With the updated module, system members will be encouraged to establish a standard pattern for use across any ABR rule. The standard patterns will be defined with an ABR rule of ***. Regardless of the ABR rule, these standard patterns will allow any account to use the same pattern.\u00a0<\/p>\n\n\n\n<p>To further simplify budget pattern management and because they were never used, the updated budget module no longer supports departmental budget patterns.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Eliminate Orphaned Accounts&nbsp;<\/h3>\n\n\n\n<p>An issue with the budget module prior to these updates, was that budgeted versions could be lost or \u201corphaned\u201d if updates were made to account flags. A full discussion of these changes is beyond the scope of this paper, but changes made to the budget module eliminate the possibility of orphaned accounts. Any data entered into the budget module will be reported (and passed to the data warehouse for Business Objects reporting) until it is removed in the budget module.<\/p>\n\n\n\n<p>See <a href=\"https:\/\/it.tamus.edu\/famis\/glossary\/budget-pattern\/\">Budget Pattern<\/a>, <a href=\"https:\/\/it.tamus.edu\/famis\/glossary\/budget-category\/\">Budget Category<\/a> and <a href=\"https:\/\/it.tamus.edu\/famis\/core-concepts\/core-concept-budget-versions\/\">Core Concept: Budget Versions<\/a> for information on related subjects.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Background In FAMIS, the budget module is a collection of screens, processes, and functions that allow the A&amp;M System and its member institutions and agencies to develop the operating budget [&hellip;]<\/p>\n","protected":false},"author":37507,"template":"","categories":[49],"tags":[],"class_list":["post-5004","white_papers","type-white_papers","status-publish","category-white-papers","entry"],"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/5004","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers"}],"about":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/types\/white_papers"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/users\/37507"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/5004\/revisions"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/media?parent=5004"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/categories?post=5004"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/tags?post=5004"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":1089,"date":"2020-07-29T10:33:19","date_gmt":"2020-07-29T16:33:19","guid":{"rendered":"http:\/\/it.tamus.edu\/famis\/?post_type=white_papers&#038;p=1089"},"modified":"2025-06-20T08:54:30","modified_gmt":"2025-06-20T13:54:30","slug":"understanding-the-famis-chart-of-accounts-structure","status":"publish","type":"white_papers","link":"https:\/\/it.tamus.edu\/famis\/white-papers\/understanding-the-famis-chart-of-accounts-structure\/","title":{"rendered":"Understanding the FAMIS Chart of Accounts Structure"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Introduction\"><\/span>Introduction<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The Texas A&amp;M University System utilizes the Financial Accounting Management Information System (FAMIS) as its fund accounting financial software.\u00a0<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Chart_of_Accounts_Account_String\"><\/span>Chart of Accounts \/ Account String<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The format of the FAMIS \u201caccount string\u201d or \u201cchart string\u201d is:<\/p>\n\n\n\n<p>CC-GGGGGG-SSSSSS-AAAAA-9999 and BBBBB,<\/p>\n\n\n\n<p>where<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>CC is the campus code<\/li>\n\n\n\n<li>GGGGGG is the General Ledger (GL) account<\/li>\n\n\n\n<li>SSSSSS is the Subsidiary Ledger (SL) account<\/li>\n\n\n\n<li>AAAAA is the Support Account (SA)<\/li>\n\n\n\n<li>9999 is the subcode<\/li>\n\n\n\n<li>BBBBB is the bank (sometimes referred to as a memo bank)<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Campus_Code\"><\/span>Campus Code<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The campus code, also known as the member ID, is the unique primary company or A&amp;M System member separator. <\/p>\n\n\n\n<p>Campus codes hold a balanced set of ledgers.&nbsp;Natively, FAMIS does not support entries across campus codes; however, newer developments (e.g., Payroll Cost Transfers [PCTs]) manage inter-campus due to \/ due from processing by posting offsetting entries on each campus code.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"GL_Accounts\"><\/span>GL Accounts<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>GL accounts should be thought of as funds.&nbsp;The GL account number itself is not unique within FAMIS; it must be coupled with the campus code to be unique.<\/p>\n\n\n\n<p>GL accounts have fully balanced sets of assets, liabilities, fund balances, income and expense accounts (subcodes).<\/p>\n\n\n\n<p>Since each SL account is mapped to a single GL account, all SL revenues and expenses are connected and recorded in the appropriate GL account (i.e., fund).<\/p>\n\n\n\n<p>Each GL account has the core attribute of the Annual Financial Report (AFR) fund group.\u00a0All GL accounts with the same AFR fund group comprise the overall fund group for AFR reporting.\u00a0Some members of the A&amp;M System have several hundred distinct GL accounts, but most have between 50 and 75 GL accounts.\u00a0Each member of the A&amp;M System assigns their own GL account numbers.<\/p>\n\n\n\n<p>GL accounts may or may not have subordinate SL accounts. For example, loan funds do not require budgets; therefore, they are managed with GL accounts only.<\/p>\n\n\n\n<p>GL accounts always begin with a zero, and the second digit represents the major fund group.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"SL_Accounts_and_Mapping\"><\/span>SL Accounts and Mapping<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>SL accounts should be viewed as cost centers or budgetary units. They are referred to as subledger accounts because they are subsidiary to a GL account.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>All operational budgeting in FAMIS is done with SL accounts (and related SAs).<\/li>\n\n\n\n<li>Revenues and expenses are recorded in the SL accounts (see the exception for GL Subcode fund additions and fund deductions).<\/li>\n\n\n\n<li>SL accounts are budgetary units.\u00a0Individual employees are responsible for managing and controlling the &#8220;budget to actual&#8221; in the SL accounts.<\/li>\n\n\n\n<li>The first digit in the SL account is always a number between 1 and 9.\u00a0The first digit of the SL will always match the second digit of the parent GL account.<\/li>\n<\/ul>\n\n\n\n<p>Each SL account is mapped to a single GL account.&nbsp;This effectively links all revenues and expenses back to a balanced GL account.&nbsp; Many SL accounts can map back to a single GL account.<\/p>\n\n\n\n<p>Each member of the A&amp;M System assigns its own SL account numbers.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Support_Accounts\"><\/span>Support Accounts<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>SAs are extensions of SL accounts and were added to FAMIS to enable departments to allocate budgets within their department or a grant.\u00a0 They can also be used to segregate revenue or expenses only \u2013 budgeting at the SA level is optional.<\/p>\n\n\n\n<p>By default, every SL account has a default SA of \u201c00000\u201d.&nbsp; The use of additional SAs is optional.&nbsp; The sum of all expenses in all SAs for a single SL account will be the same as the sum of expenses for the SL account.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Subcodes\"><\/span>Subcodes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Subcodes are used in FAMIS as the traditional \u201caccounts\u201d that identify assets, liabilities, income (revenue), expenses, and equity (or fund balance).&nbsp; Subcodes in FAMIS fall into three main categories.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Subcode_Types\"><\/span>Subcode Types<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Revenue subcodes are only used with SL accounts and range from 0001 to 0999.<\/li>\n\n\n\n<li>Expenditure subcodes are also only used with SL accounts and range from 1000 to 9999.\n<ul class=\"wp-block-list\">\n<li>Note:\u00a0Some expenditure subcodes are designated as \u201cbudget only\u201d and are used to create budgets in various categories (salaries, benefits, travel, supplies etc.)<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Account controls are used only with GL accounts.\u00a0They are broken down into five subcategories:\n<ul class=\"wp-block-list\">\n<li>Asset subcodes range from 1000 to 1999<\/li>\n\n\n\n<li>Liability subcodes range from 2000 to 2999<\/li>\n\n\n\n<li>Fund Balance subcodes range from 3000 to 3999<\/li>\n\n\n\n<li>Fund additions range from 4000 to 4999.\u00a0Fund additions record revenue \/ income when the GL account does not require an SL account.<\/li>\n\n\n\n<li>Fund deductions range from 5000 to 5999. Fund deductions record expenses and transfers out when the GL account does not require an SL account.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p>GL subcodes in the range of 9000 to 9999 are used for summary memo entries that summarize the activity from all Sub Ledger accounts that are mapped to this GL account. These subcodes should not be viewed as part of the balance sheet or operating statement, particularly because they contain encumbrance and budget activity.<\/p>\n\n\n\n<p>Thinking of GL account controls as prefixed with a \u201cG\u201d and SL account expense codes as prefixed with an \u201cS\u201d is helpful.&nbsp;FAMIS permits the same number to be both an account control and expenditure code.&nbsp;For example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Code 1215 when used with an SL account means \u201cSalary &#8211; Extension &#8211; County Agents\u201d.\n<ul class=\"wp-block-list\">\n<li>The A&amp;M System Data Warehouse uses subcode types and treats this subcode as \u201cS1215\u201d.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Code 1215 when used with a GL account means \u201cInvestments &#8211; NonCurrent\u201d.\n<ul class=\"wp-block-list\">\n<li>The A&amp;M System Data Warehouse uses subcode types and treats this subcode as \u201cG1215\u201d.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p>All members of the A&amp;M System share the same set of subcodes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Banks\"><\/span>Banks<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Banks are an independent dimension in FAMIS. Banks do not belong to a GL or SL account, nor do they have any particular connection to subcodes.<\/p>\n\n\n\n<p>Banks represent funds held in an actual bank account, or banks can represent appropriations held in the Texas State Treasury.&nbsp;Texas State banks, in particular, have their own characteristics used for reporting.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The A&amp;M System has about 1,000 banks across all members of the A&amp;M System.<\/li>\n\n\n\n<li>Each year, the A&amp;M System creates a new set of banks for the new-year appropriations.\u00a0 Local banks tend to remain the same year after year.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Transaction_Posting\"><\/span>Transaction Posting<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Data entry in FAMIS generally involves using a 17-digit account string plus a bank.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Member ID: Member ID is usually not required with FAMIS since the operators work within a single campus code, but the member ID is required for data integrations. Posting to another member ID requires a change to another campus (or tenant).<\/li>\n\n\n\n<li>Six-digit account number:\u00a0This number can be an SL or GL account.\u00a0If an SL account is used, the related GL account is implied. If a GL account is used, an SL account is not required.<\/li>\n\n\n\n<li>Five-digit SA: If the six-digit number is a GL account, the support account must be 00000.<\/li>\n\n\n\n<li>Subcode: A subcode is required on all FAMIS transactions. If the account is a GL account, the subcode must be from the GL account control list. If the account is an SL account, the subcode must be a revenue or expense subcode.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Special_Reporting_Mapping_%E2%80%93_USAS_Strategy_and_PCA\"><\/span>Special Reporting Mapping &#8211; USAS, Strategy and PCA<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The State of Texas runs the Uniform Statewide Account System (USAS).&nbsp;Each member of the A&amp;M System must integrate with USAS to receive reimbursements for state appropriations spent by the member.&nbsp;A&amp;M System members can also request that the State of Texas directly pay the vendor.<\/p>\n\n\n\n<p>USAS requires several key elements in its integration:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An agency number, state fund number, and appropriation number<\/li>\n\n\n\n<li>An appropriation year<\/li>\n\n\n\n<li>Program Cost Account (PCA) code. The PCA is a short, five-character code that implies:\n<ul class=\"wp-block-list\">\n<li>State goal<\/li>\n\n\n\n<li>State objective (rolls up to goal)<\/li>\n\n\n\n<li>State strategy (rolls up to objective)<\/li>\n\n\n\n<li>NACUBO fund group<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p>When integrating with the State of Texas, the first and second items are derived from the FAMIS bank account number.&nbsp; The PCA code is derived based on a combination of the FAMIS SL account and the related Subcode.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"FAMIS_Account_and_Subcode_Attributes\"><\/span>FAMIS Account and Subcode Attributes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>While some intelligence is embedded in the FAMIS SL and GL account numbers, FAMIS was carefully designed not to make the account number a \u201csmart\u201d code.\u00a0Except for the first digit of the SL account, FAMIS does not mandate a particular structure for the remaining digits.\u00a0Some A&amp;M System members have implemented additional smart digits, but these implementations are not critical for State of Texas reporting or other required reporting.<\/p>\n\n\n\n<p>Instead, FAMIS uses an extensive set of attributes related to the SL accounts, GL accounts, SAs, and subcodes to facilitate reporting.<\/p>\n\n\n\n<p>Note: In FAMIS, attributes are connected to the account on a fiscal year basis. For example, SL account 02-271220 can be mapped to the Biology Department in fiscal year (FY) 2018, but it can be changed and mapped to the Biochemistry Department in FY 2019.<\/p>\n\n\n\n<p>The following screenshot provides an example of accounts held in FAMIS at an SL account level.<strong><br><\/strong><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"SL_Account_FAMIS_Screen_006\"><\/span>SL Account (FAMIS Screen 006)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Campus code \/ company \/ system member: \u00a002 (TAMU)<\/li>\n\n\n\n<li>SL account:\u00a0221323<\/li>\n\n\n\n<li>Notable attributes:\n<ul class=\"wp-block-list\">\n<li>Responsible person:\u00a0account owner<\/li>\n\n\n\n<li>Automatic budget reallocation (ABR) rule: the budget profile of categories used<\/li>\n\n\n\n<li>Annual financial report (AFR) fund group:\u00a0where the revenues \/ expenses are reported <\/li>\n\n\n\n<li>Primary department and subdepartment (and related hierarchy)<\/li>\n\n\n\n<li>Does this account also belong to a Board-recognized center?<\/li>\n\n\n\n<li>Secondary department and subdepartment (and related hierarchy)<\/li>\n\n\n\n<li>NACUBO function and subfunction<\/li>\n\n\n\n<li>Default (primary) bank for expenditures<\/li>\n\n\n\n<li>Various control flags\n<ul class=\"wp-block-list\">\n<li>Are SAs used?<\/li>\n\n\n\n<li>For revenue, for expense?<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Primary funding source<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n<h3><span class=\"ez-toc-section\" id=\"Screen_006_%E2%80%93_SL_6_Digit_Account\"><\/span>Screen 006 &#8211; SL 6 Digit Account<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<div id=\"screenshot-274e\" class=\"screenshot\" style=\"min-height: 350px\">\n  <div class=\"tabs\">\n      <div role=\"tablist\" aria-label=\"Screenshot image and text\">\n          <button role=\"tab\"\n                  aria-selected=\"true\"\n                  aria-controls=\"screenshot-image-panel-274e\"\n                  id=\"screenshot-image-tab-274e\">\n                  Image\n          <\/button>\n          <button role=\"tab\"\n                  aria-selected=\"false\"\n                  aria-controls=\"screenshot-text-panel-274e\"\n                  id=\"screenshot-text-tab-274e\"\n                  tabindex=\"-1\">\n                  Text\n          <\/button>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-image-panel-274e\"\n          aria-labelledby=\"screenshot-image-tab-274e\">\n          <img decoding=\"async\" src=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2020\/07\/FAMIS_CHART_006.png\" height=\"628\" alt=\"Screen 006\" \/>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-text-panel-274e\"\n          aria-labelledby=\"screenshot-text-tab-274e\"\n          hidden=\"\">\n          <pre>  006 SL 6 Digit Account (FSA)                                   10\/28\/20 09:56\r\n                                                                  FY 2021 CC 02\r\n  Screen: ___  Account: 221323 ____ PETE - COLLEGE ADVANCEMENT FEE\r\n\r\nAccount Title: PETE - COLLEGE ADVANCEMENT FEE_____ SA create enable: Y  SRS: N\r\n  Resp Person: 904001796 SPATH, JEFFREY B            Old Acct: _______________\r\n        ABR Rule: 001        Map Code: 22131  Reporting Group: __\r\nBottom Line Cntl: Y    Deflt Cat Cntl: R   Deflt  Cat Tol Pct: _______\r\n  AFR Fund Group: 20       Fund Group: DS      Sub Fund Group: DF  Sub-Sub: __\r\nYear-End Process: F     Year-End Acct: __________    Function: 10  Sub-Fun: __\r\n    Default Bank: 06000      Override: Y     Proj FYTD End Mo: 08 Aux Code: ___\r\n Alternate Banks: *****  _____  _____  _____  _____  Security: ______\r\n     P-Card Bank: _____   State Funds: _  Appropriated: _   --SA Transactions--\r\n             CC Dept  S-Dept Exec Div Coll Mail Cd Stmt           Budget Actual\r\n    Primary:    PETE_ _____   AA   CD  EN   C3116    Y      Expense: B      B\r\n  Secondary:    _____ _____                 _____    _      Revenue: B      B\r\n  Admin For: __ _____ _____\r\n     Center: __ _____ _____                                   TRS\/ORP Exempt: _\r\nFund Source: 03 221311__________________________________      Account Letter: _\r\n Long Title: PETE - COLLEGE ADVANCEMENT FEE__________      Setup Dt: 09\/26\/2014\r\n             ________________________________________  Iteration Dt: 09\/26\/2014\r\nEnter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---\r\n      Hmenu Help  EHelp       Next  CAcct CProj AResp Cmnt  Left  Right<\/pre>\n      <\/div>\n  <\/div>\n<\/div>\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"SL_Account_%E2%80%93_Sample_Additional_Attributes_FAMIS_Screen_008\"><\/span>SL Account &#8211; Sample Additional Attributes (FAMIS Screen 008)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Campus Code\/Company\/System Member: \u00a002 (TAMU)<\/li>\n\n\n\n<li>SL Account:\u00a0 221323<\/li>\n\n\n\n<li>Notable Attributes:\n<ul class=\"wp-block-list\">\n<li>Element of Cost (State reporting)<\/li>\n\n\n\n<li>Various Allowable Expense Type Control Flags\n<ul class=\"wp-block-list\">\n<li>Is Foreign Travel permitted?<\/li>\n\n\n\n<li>Is the Revenue Pledged?<\/li>\n\n\n\n<li>Who is the Responsible Accountant?<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Rules for Salary Savings Processing\n<ul class=\"wp-block-list\">\n<li>If Workday positions funded on this account are vacant, does the department get to keep the savings?\u00a0 If other accounts are specified, the end of month salary savings process initiates budget transfers.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Fringe Benefit posting rules (Pyrl Acct Anal)<\/li>\n\n\n\n<li>Does this account pay its own E-Travel fees?<\/li>\n\n\n\n<li>What restrictions are there on Subcodes (type of expenses)?<\/li>\n\n\n\n<li>What construction project number does this map to (if any)?<\/li>\n<\/ul>\n\n\n<h3><span class=\"ez-toc-section\" id=\"Screen_008_%E2%80%93_SL_Attributes\"><\/span>Screen 008 &#8211; SL Attributes<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<div id=\"screenshot-6f42\" class=\"screenshot\" style=\"min-height: 350px\">\n  <div class=\"tabs\">\n      <div role=\"tablist\" aria-label=\"Screenshot image and text\">\n          <button role=\"tab\"\n                  aria-selected=\"true\"\n                  aria-controls=\"screenshot-image-panel-6f42\"\n                  id=\"screenshot-image-tab-6f42\">\n                  Image\n          <\/button>\n          <button role=\"tab\"\n                  aria-selected=\"false\"\n                  aria-controls=\"screenshot-text-panel-6f42\"\n                  id=\"screenshot-text-tab-6f42\"\n                  tabindex=\"-1\">\n                  Text\n          <\/button>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-image-panel-6f42\"\n          aria-labelledby=\"screenshot-image-tab-6f42\">\n          <img decoding=\"async\" src=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2020\/07\/FAMIS_CHART_008.png\" height=\"628\" alt=\"Screen 008\" \/>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-text-panel-6f42\"\n          aria-labelledby=\"screenshot-text-tab-6f42\"\n          hidden=\"\">\n          <pre>  008 SL Attributes 2                                            10\/28\/20 09:58\r\n                                                                  FY 2021 CC 02\r\n  Screen: ___  Account: 221323 ____ PETE - COLLEGE ADVANCEMENT FEE       SRS: N\r\n\r\n      Element of Cost: ___  Sub-El: __       Foreign Tvl: 2    Gen Exp Bud: _\r\n      Effort Category: DINS_                 Foreign Per: _ Admin\/Clerical: _\r\n     Salary Sav. Dist: ______ _____ ____     Rev Pledged: _     Restricted: _\r\n Fac Salary Sav. Dist: ______ _____ ____  Pyrl Acct Anal: 5012   Delg Type: _\r\n Fac Savings Form 500: ______ _____ ____      Int Exempt: _ Int Exe Reason: __\r\nGrad Savings Form 500: ______ _____ ____   Interest Acct: ______ _____\r\n                                             ETravel Fee: ______ _____\r\n              USAS Cd: __                     Obj Trans   --- Subcode Edits ---\r\n           Bond Issue: ________               Cat Type     Low     High   Match\r\n          Budget Sort: ______     Cost Ref 1:  _    _      ____    ____     _\r\n      Gift Fee Exempt: _          Cost Ref 2:  _    _      ____    ____     _\r\n        A\/R  Clerk Cd: __      Cap. Campaign:  _           ____    ____     _\r\nGCP\/Constr.Proj: __________                                ____    ____     _\r\nAccountant Resp: 105007715  WINKLER, JOHN A                ____    ____     _\r\n Title to Equip: ________________________________________\r\nComments: TO COLLECT FEES THAT WILL SUPPORT ACADEMIC ACTIVITIES FOR___\r\n          GRADUATE STUDIES. SALARIES, FRINGE, TRAVEL, OPERATING EQUIP_\r\nEnter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---\r\n      Hmenu Help  EHelp       Next  CAcct             Cmnt<\/pre>\n      <\/div>\n  <\/div>\n<\/div>\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"SL_Account_%E2%80%93_Sample_Additional_Attributes_FAMIS_Screen_009\"><\/span>SL Account \u2013 Sample Additional Attributes (FAMIS Screen 009)<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Connect this account to a Sponsored Project<\/li>\n\n\n\n<li>To what Subcode do we post the Billing Revenue?<\/li>\n\n\n\n<li>Addition Responsible Persons (role assignments)<\/li>\n\n\n\n<li>If research, it may not be sponsored, but we want to track the NSF and State coding for research initiatives.<\/li>\n<\/ul>\n\n\n<h3><span class=\"ez-toc-section\" id=\"Screen_009_%E2%80%93_SL_Grant_Contract_Attributes\"><\/span>Screen 009 &#8211; SL Grant \/ Contract Attributes<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<div id=\"screenshot-d95e\" class=\"screenshot\" style=\"min-height: 350px\">\n  <div class=\"tabs\">\n      <div role=\"tablist\" aria-label=\"Screenshot image and text\">\n          <button role=\"tab\"\n                  aria-selected=\"true\"\n                  aria-controls=\"screenshot-image-panel-d95e\"\n                  id=\"screenshot-image-tab-d95e\">\n                  Image\n          <\/button>\n          <button role=\"tab\"\n                  aria-selected=\"false\"\n                  aria-controls=\"screenshot-text-panel-d95e\"\n                  id=\"screenshot-text-tab-d95e\"\n                  tabindex=\"-1\">\n                  Text\n          <\/button>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-image-panel-d95e\"\n          aria-labelledby=\"screenshot-image-tab-d95e\">\n          <img decoding=\"async\" src=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2020\/07\/FAMIS_CHART_009.png\" height=\"628\" alt=\"Screen 009\" \/>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-text-panel-d95e\"\n          aria-labelledby=\"screenshot-text-tab-d95e\"\n          hidden=\"\">\n          <pre>  009 SL Grant\/Contract Attributes                               10\/28\/20 10:00\r\n                                                                  FY 2021 CC 02\r\n  Screen: ___  Account: 221323 ____ PETE - COLLEGE ADVANCEMENT FEE       SRS: N\r\n\r\n  Sponsored Project: __________\r\n            Sponsor: 0007398    STUDENT FEES                      Total Awarded\r\n          Award Nbr:\r\n         90 Day Pre: _             Billing Revenue Object: ____      Funding\r\n         Start Date: __________   Indirect Expense Object: ____\r\n           End Date: __________   Indirect Revenue Object: ____\r\nTAMRF Acct\/Proj Nbr: ___________            System Member: __\r\n       CS Acct Link: __ ______   TE Certify: _   E-Verify: _\r\n    ----- Indirect Cost ----                 ------- Responsible Persons ------\r\n            Base: ________                 1: __ 904001796 SPATH, JEFFREY\r\n            Rate: ______                   2: __ _________\r\n    Distribution: __________               3: __ _________\r\nCFDA Nbr: _______  NSF Category: ________  4: __ _________\r\n                       Activity: 1A_\r\n      Science\/Engineering Field: 2A7    ----- Special Areas of Interest ------\r\n              Character of Work: 4A_    ___  ___  ___  ___  ___  ___  ___  ___\r\n              Selection Process: 5B_         ___  ___  ___  ___  ___  ___  ___\r\nEnter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---\r\n      Hmenu Help  EHelp       Next        CProj AResp<\/pre>\n      <\/div>\n  <\/div>\n<\/div>\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"List_of_Accounts_FAMIS_Screen_068\"><\/span>List of Accounts (FAMIS Screen 068)<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Some SL accounts have SAs, some do not.<\/li>\n<\/ul>\n\n\n<h3><span class=\"ez-toc-section\" id=\"Screen_068_%E2%80%93_Support_Account_Search\"><\/span>Screen 068 &#8211; Support Account Search<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<div id=\"screenshot-2fcd\" class=\"screenshot\" style=\"min-height: 350px\">\n  <div class=\"tabs\">\n      <div role=\"tablist\" aria-label=\"Screenshot image and text\">\n          <button role=\"tab\"\n                  aria-selected=\"true\"\n                  aria-controls=\"screenshot-image-panel-2fcd\"\n                  id=\"screenshot-image-tab-2fcd\">\n                  Image\n          <\/button>\n          <button role=\"tab\"\n                  aria-selected=\"false\"\n                  aria-controls=\"screenshot-text-panel-2fcd\"\n                  id=\"screenshot-text-tab-2fcd\"\n                  tabindex=\"-1\">\n                  Text\n          <\/button>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-image-panel-2fcd\"\n          aria-labelledby=\"screenshot-image-tab-2fcd\">\n          <img decoding=\"async\" src=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2020\/07\/FAMIS_CHART_068.png\" height=\"628\" alt=\"Screen 068\" \/>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-text-panel-2fcd\"\n          aria-labelledby=\"screenshot-text-tab-2fcd\"\n          hidden=\"\">\n          <pre>  068 Support Account Search                                     10\/28\/20 10:18\r\n                                                                  FY 2021 CC 02\r\n  Screen: ___  Account: 221323 _____ ____   Title Search: ____________________\r\n     Dept\/SDept Search: _____ _____   Resp Person Search: ____________________\r\n                                   Include Deleted Accts: N\r\nSel          Description              Account    Dept  SDept   Resp. Person   R\r\n _  PETE - COLLEGE ADVANCEMENT FEE  221323-00000 PETE        SPATH, JEFFREY   N\r\n _  JOHN LEE PROVOST START-UP       221323-01002 PETE        SPATH, JEFFREY   N\r\n _  EAPO - COLLEGE ADVANCEMENT FEE  221324-00000 EAPO        WEICHOLD, MARK   N\r\n _  GAT'S-MANNANS                   221324-10000 EAPO        WEICHOLD, MARK   N\r\n _  ITDE                            221324-19000 EAPO        WEICHOLD, MARK   N\r\n _  GRADUATE                        221324-41000 EAPO        MORREL, TANDILY  N\r\n _  GTF                             221324-43000 EAPO        KINRA, VIKRAM K  N\r\n _  MSEN - COLLEGE ADVANCMENT FEE   221325-00000 MSEN        KARAMAN, IBRAHI  N\r\n _  OCEN GRADUATE STUDENT TRAVEL    221326-00000 OCEN        GIRIMAJI, SHARA  N\r\n _  DEAN STARTUP 2 - MORTAZAVI      221327-00000 CPSC        MORTAZAVI, JACK  N\r\n _  CLGE - COLLEGE ADVANCEMENT FEE  221400-00000 CLGE        THOMAS, DEBORAH  N\r\n _  CLGE - COLLEGE ADVANCEMENT FEE  221411-00000 CLGE        THOMAS, DEBORAH  N\r\n _  CLGE - PROGRAM FEE MS OF GEOSCI 221412-00000 CLGE        BABER, SARA F    N\r\n _  DE-SUMMER FACULTY SUPPORT       221412-00001 CLGE        BABER, SARA F    N\r\n                 *** Press ENTER to View More Accounts ***\r\nEnter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---\r\n      Hmenu Help  EHelp                               Dload<\/pre>\n      <\/div>\n  <\/div>\n<\/div>\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Support_Accounts_Attributes_FAMIS_Screens_051_and_052\"><\/span>Support Accounts Attributes (FAMIS Screens 051 and 052)<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Similar to primary accounts.<\/li>\n\n\n\n<li>Most attributes are repeated.\u00a0 If specified here, they override the SL account attributes.<\/li>\n<\/ul>\n\n\n<h3><span class=\"ez-toc-section\" id=\"Screen_051_%E2%80%93_Support_Account_Attributes\"><\/span>Screen 051 &#8211; Support Account Attributes<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<div id=\"screenshot-525a\" class=\"screenshot\" style=\"min-height: 350px\">\n  <div class=\"tabs\">\n      <div role=\"tablist\" aria-label=\"Screenshot image and text\">\n          <button role=\"tab\"\n                  aria-selected=\"true\"\n                  aria-controls=\"screenshot-image-panel-525a\"\n                  id=\"screenshot-image-tab-525a\">\n                  Image\n          <\/button>\n          <button role=\"tab\"\n                  aria-selected=\"false\"\n                  aria-controls=\"screenshot-text-panel-525a\"\n                  id=\"screenshot-text-tab-525a\"\n                  tabindex=\"-1\">\n                  Text\n          <\/button>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-image-panel-525a\"\n          aria-labelledby=\"screenshot-image-tab-525a\">\n          <img decoding=\"async\" src=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2020\/07\/FAMIS_CHART_051.png\" height=\"628\" alt=\"Screen 051\" \/>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-text-panel-525a\"\n          aria-labelledby=\"screenshot-text-tab-525a\"\n          hidden=\"\">\n          <pre>   051 Support Account Attributes                                 10\/28\/20 10:21\r\n                                                                   FY 2021 CC 02\r\n   Screen: ___ Account: 221324 10000         GAT'S-MANNANS\r\n                                                                          SRS: N\r\n Account Title: GAT'S-MANNANS______________________    Security: ______\r\n   Resp Person: 102005166  WEICHOLD, MARK H            SA Group: ______\r\n   Bot Ln Cntl: N  Deflt Cat Cntl: N  Deflt Cat Tol Pct: _______\r\n  Default Bank: _____  Override: _  Delg Type: _       Old Acct: _______________\r\n    Alt. Banks: _____  _____  _____  _____  _____      Roll BBA To Base: _\r\n   P-Card Bank: _____      SL Function: 10  SA Function: 60  Effort Cat: _____\r\n               CC Dept  S-Dept Exec Div Coll Mail Cd Stmt\r\n      Primary:    EAPO_ _____   AA  CD   EN   C3127   Y   Sys Member: __\r\n    Secondary:    _____ _____                 _____   _   Off Campus: _\r\n    Admin For: __ _____ _____                           ---- Indirect Cost -----\r\n       Center: __ _____ _____                                   Base: ________\r\n   90 Day Pre: _      Classing Cd: _       USAS Cd: __          Rate: ______\r\n   Start Date: __________       TAMRF Nbr: ___________  Distribution: __________\r\n     End Date: __________    CS Acct Link: __ ______     Expense Obj: ____\r\n   Long Title: GAT'S-MANNANS___________________________  Revenue Obj: ____\r\n               ________________________________________\r\n  *** All fields entered on this screen override fields on the Parent SL ***\r\n Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---\r\n       Hmenu Help  EHelp<\/pre>\n      <\/div>\n  <\/div>\n<\/div>\n\n<h3><span class=\"ez-toc-section\" id=\"Screen_052_%E2%80%93_Support_Account_Attributes_2\"><\/span>Screen 052 &#8211; Support Account Attributes 2<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<div id=\"screenshot-e0db\" class=\"screenshot\" style=\"min-height: 350px\">\n  <div class=\"tabs\">\n      <div role=\"tablist\" aria-label=\"Screenshot image and text\">\n          <button role=\"tab\"\n                  aria-selected=\"true\"\n                  aria-controls=\"screenshot-image-panel-e0db\"\n                  id=\"screenshot-image-tab-e0db\">\n                  Image\n          <\/button>\n          <button role=\"tab\"\n                  aria-selected=\"false\"\n                  aria-controls=\"screenshot-text-panel-e0db\"\n                  id=\"screenshot-text-tab-e0db\"\n                  tabindex=\"-1\">\n                  Text\n          <\/button>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-image-panel-e0db\"\n          aria-labelledby=\"screenshot-image-tab-e0db\">\n          <img decoding=\"async\" src=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2020\/07\/FAMIS_CHART_052.png\" height=\"628\" alt=\"Screen 052\" \/>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-text-panel-e0db\"\n          aria-labelledby=\"screenshot-text-tab-e0db\"\n          hidden=\"\">\n          <pre>  052 Support Account Attributes 2                               10\/28\/20 10:23\r\n                                                                  FY 2021 CC 02\r\n  Screen: ___ Account: 221324 10000         GAT'S-MANNANS\r\n                                                                         SRS: N\r\n      Accountant Resp: _________                         Funding:\r\n                                             Foreign Per: _ Admin\/Clerical: _\r\n     Salary Sav. Dist: ______ _____ ____\r\n Fac Salary Sav. Dist: ______ _____ ____  Pyrl Acct Anal: ____  TE Certify: _\r\n Fac Savings Form 500: ______ _____ ____      Int Exempt: _ Int Exe Reason: __\r\nGrad Savings Form 500: ______ _____ ____   Interest Acct: ______ _____\r\n                                             ETravel Fee: ______ _____\r\n                                              Obj Trans   --- Subcode Edits ---\r\n                                              Cat Type     Low     High   Match\r\n                                  Cost Ref 1:  _    _      ____    ____     _\r\n                                  Cost Ref 2:  _    _      ____    ____     _\r\n--------- Responsible Persons --------                     ____    ____     _\r\n1: __  102005166  WEICHOLD, MARK H                         ____    ____     _\r\n2: __  _________                                           ____    ____     _\r\n3: __  _________\r\n4: __  _________\r\n *** All fields entered on this screen override fields on the Parent SL ***\r\nEnter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---\r\n      Hmenu Help  EHelp                         AResp<\/pre>\n      <\/div>\n  <\/div>\n<\/div>\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"List_of_Banks_FAMIS_Screen_029\"><\/span>List of Banks (FAMIS Screen 029)<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Note the Account (i.e. Bank Codes).<\/li>\n<\/ul>\n\n\n<h3><span class=\"ez-toc-section\" id=\"Screen_029_%E2%80%93_Account_Search\"><\/span>Screen 029  &#8211; Account Search<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<div id=\"screenshot-e23e\" class=\"screenshot\" style=\"min-height: 350px\">\n  <div class=\"tabs\">\n      <div role=\"tablist\" aria-label=\"Screenshot image and text\">\n          <button role=\"tab\"\n                  aria-selected=\"true\"\n                  aria-controls=\"screenshot-image-panel-e23e\"\n                  id=\"screenshot-image-tab-e23e\">\n                  Image\n          <\/button>\n          <button role=\"tab\"\n                  aria-selected=\"false\"\n                  aria-controls=\"screenshot-text-panel-e23e\"\n                  id=\"screenshot-text-tab-e23e\"\n                  tabindex=\"-1\">\n                  Text\n          <\/button>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-image-panel-e23e\"\n          aria-labelledby=\"screenshot-image-tab-e23e\">\n          <img decoding=\"async\" src=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2020\/07\/FAMIS_CHART_029.png\" height=\"628\" alt=\"Screen 029\" \/>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-text-panel-e23e\"\n          aria-labelledby=\"screenshot-text-tab-e23e\"\n          hidden=\"\">\n          <pre>  029 Account Search                                             10\/28\/20 10:30\r\n                        EAPO - COLLEGE ADVANCEMENT FEE            FY 2021 CC 02\r\n  Screen: ___  Account: B_____ ____         Title Search: ____________________\r\n     Dept\/SDept Search: _____ _____   Resp Person Search: ____________________\r\n                                   Include Deleted Accts: N\r\nSel        Description                 Account Dept  SDept    Resp. Person    R\r\n _  TAMU - CONCENTRATION ACCOUNT        B00601\r\n _  WELLS FARGO-TAMU PRESS              B00665\r\n _  CCA-REC SPORTS                      B01103\r\n _  CCA - COLLEGE OF ARCHITECTURE       B01119\r\n _  CCA-SHORT COURSE                    B01124\r\n _  CCA-TUITION &amp; FEES                  B01134\r\n _  CCA-APPLICATION FEES INTERNET       B01212\r\n _  CCA - TAMU PRESS - IPT              B01234\r\n _  TAMU - FED AGCY CONTRACT &amp; GRANTS   B01606\r\n _  TAMU - CREDIT CARD ACCOUNT          B01650\r\n _  TAMU - DIRECT DEPOSIT ACCOUNT       B01665\r\n _  BANK OF AMERICA LOCAL FUNDS DEMAND  B03000\r\n _  BANK OF AMERICA ON DEMAND           B03002\r\n _  FEDERAL FUNDS-PERKINS LOANS FUNDS-M B04028\r\n                 *** Press ENTER To View More Accounts ***\r\nEnter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---\r\n      Hmenu Help  EHelp                               Dload Left  Right<\/pre>\n      <\/div>\n  <\/div>\n<\/div>\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Bank_Account_Attributes_FAMIS_Screen_028\"><\/span>Bank Account Attributes (FAMIS Screen 028)<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A Bank is either a local bank or a State appropriation.<\/li>\n\n\n\n<li>State attributes tie to specific appropriations.\n<ul class=\"wp-block-list\">\n<li>Appropriations are line items in the overall State of Texas budget.<\/li>\n\n\n\n<li>State funds are not held by the A&amp;M System, they are held in the State treasury.\u00a0 They have their own coding structure.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n<h3><span class=\"ez-toc-section\" id=\"Screen_028_%E2%80%93_Create_Maintain_Bank_Accounts\"><\/span>Screen 028 &#8211; Create \/ Maintain Bank Accounts<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<div id=\"screenshot-3414\" class=\"screenshot\" style=\"min-height: 350px\">\n  <div class=\"tabs\">\n      <div role=\"tablist\" aria-label=\"Screenshot image and text\">\n          <button role=\"tab\"\n                  aria-selected=\"true\"\n                  aria-controls=\"screenshot-image-panel-3414\"\n                  id=\"screenshot-image-tab-3414\">\n                  Image\n          <\/button>\n          <button role=\"tab\"\n                  aria-selected=\"false\"\n                  aria-controls=\"screenshot-text-panel-3414\"\n                  id=\"screenshot-text-tab-3414\"\n                  tabindex=\"-1\">\n                  Text\n          <\/button>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-image-panel-3414\"\n          aria-labelledby=\"screenshot-image-tab-3414\">\n          <img decoding=\"async\" src=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2020\/07\/FAMIS_CHART_028.png\" height=\"628\" alt=\"Screen 028\" \/>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-text-panel-3414\"\n          aria-labelledby=\"screenshot-text-tab-3414\"\n          hidden=\"\">\n          <pre>   028 Create\/Maintain Bank Accounts                              10\/28\/20 11:20\r\n                                                                   FY 2021 CC 02\r\n   Screen: ___  Account: B10010 ____         STATE PAID FICA AY2020\r\n\r\n            Account Title: STATE PAID FICA AY2020_____________\r\n         Long Description: ________________________________________\r\n                           ________________________________________\r\n    Local Bank Information                  State Appropriation Information\r\n  --------------------------                -------------------------------\r\n    Account No: ____________                  Appropriation Year: 2020\r\n       Contact: ____________________                        Fund: 0001\r\n Contact Phone: ___ ___ ____  Ext: ____     Appropriation Number: 91142\r\n    ABA Number: __________  LType: ____              Agency Code: 711\r\n  AFR Fund Grp: 10                                   Cost Center: _____\r\n     Bank Name: ________________________________________   SType: 0004\r\n                      Old Account: _______________\r\n Comments: ____________________________________________________________\r\n           ____________________________________________________________\r\n           ____________________________________________________________\r\n           ____________________________________________________________\r\n\r\n Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---\r\n       Hmenu Help  EHelp<\/pre>\n      <\/div>\n  <\/div>\n<\/div>\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Subcode_Attributes_FAMIS_Screen_806\"><\/span>Subcode Attributes (FAMIS Screen 806)<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Subcodes also have their own mapping and roll-up to State Codes.<\/li>\n<\/ul>\n\n\n<h3><span class=\"ez-toc-section\" id=\"Screen_806_%E2%80%93_Maintain_SL_Subcode_Descriptions\"><\/span>Screen 806 &#8211; Maintain SL Subcode Descriptions<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<div id=\"screenshot-0c1c\" class=\"screenshot\" style=\"min-height: 350px\">\n  <div class=\"tabs\">\n      <div role=\"tablist\" aria-label=\"Screenshot image and text\">\n          <button role=\"tab\"\n                  aria-selected=\"true\"\n                  aria-controls=\"screenshot-image-panel-0c1c\"\n                  id=\"screenshot-image-tab-0c1c\">\n                  Image\n          <\/button>\n          <button role=\"tab\"\n                  aria-selected=\"false\"\n                  aria-controls=\"screenshot-text-panel-0c1c\"\n                  id=\"screenshot-text-tab-0c1c\"\n                  tabindex=\"-1\">\n                  Text\n          <\/button>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-image-panel-0c1c\"\n          aria-labelledby=\"screenshot-image-tab-0c1c\">\n          <img decoding=\"async\" src=\"https:\/\/it.tamus.edu\/famis\/wp-content\/uploads\/sites\/6\/2020\/07\/FAMIS_CHART_806.png\" height=\"628\" alt=\"Screen 806\" \/>\n      <\/div>\n      <div tabindex=\"0\"\n          role=\"tabpanel\"\n          id=\"screenshot-text-panel-0c1c\"\n          aria-labelledby=\"screenshot-text-tab-0c1c\"\n          hidden=\"\">\n          <pre>  806  Maintain SL Subcode Descriptions                           10\/28\/20 11:24\r\n                                                                   FY 2021 CC 02\r\n   Screen:      Subcode: 14__  View Master Campus: _        PANEL: 01MORE&gt;&gt;\r\n                                            State LBB  LAR  Bud   IDC\r\n  F Sbcd             Description             Code Code Code Pool Exmpt HUB\r\n  _ 1410 Salary-Faculty-Teaching____________ 7008 1005 1005   _\r\n  _ 1411 Unallocated Salaries - Teaching____ ____ 1005 1005   Y\r\n  _ 1412 Unalloc Merit Increases - Teaching_ ____ 1005 1005   Y\r\n  _ 1413 Summer Teaching Salaries___________ ____ 1005 1005   Y\r\n  _ 1415 Sal-GAT - Fac\/Academ_______________ 7014 1001 1001   _\r\n  _ 1416 Sal - Grad Asst Lecturer___________ 7014 1001 1001   _\r\n  _ 1420 Salary - Library - Faculty_________ 7009 1010 1010   _\r\n  _ 1425 Salary-Summer Teaching-Faculty_____ 7008 1005 1005   _\r\n  _ 1480 One Time Merit - Faculty___________ 7017 1002 1002   _\r\n  _ 1505 Salary - Resident Physician________ 7010 1001 1001   _\r\n  _ 1510 Salary-Professional-Administrative_ 7010 1001 1001   _\r\n  _ 1511 Unallctd Salaries Pool-Non-Teachg__ ____ 1001 1001   Y\r\n  _ 1512 Unallctd Merit Incr Pool-Non-Teachg ____ 1001 1001   Y\r\n  _ 1515 Salary-Classified__________________ 7015 1001 1001   _\r\n  _ 1516 Sal-TAMUQ Local Professional_______ 7010 ____ ____   _\r\n   ********** More Data -- Press  to View ********\r\n Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---\r\n       Hmenu Help  EHelp                   Comp        DLoad Left  Right<\/pre>\n      <\/div>\n  <\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Introduction The Texas A&amp;M University System utilizes the Financial Accounting Management Information System (FAMIS) as its fund accounting financial software.\u00a0 Chart of Accounts \/ Account String The format of the [&hellip;]<\/p>\n","protected":false},"author":37526,"template":"","categories":[49],"tags":[],"class_list":["post-1089","white_papers","type-white_papers","status-publish","category-white-papers","entry"],"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/1089","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers"}],"about":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/types\/white_papers"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/users\/37526"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/1089\/revisions"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/media?parent=1089"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/categories?post=1089"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/tags?post=1089"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":1087,"date":"2020-07-29T10:20:56","date_gmt":"2020-07-29T16:20:56","guid":{"rendered":"http:\/\/it.tamus.edu\/famis\/?post_type=white_papers&#038;p=1087"},"modified":"2024-07-24T09:17:20","modified_gmt":"2024-07-24T14:17:20","slug":"summer-group-insurance-premium-gip-allocation-process","status":"publish","type":"white_papers","link":"https:\/\/it.tamus.edu\/famis\/white-papers\/summer-group-insurance-premium-gip-allocation-process\/","title":{"rendered":"Summer Group Insurance Premium (GIP) Allocation Process"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Background_and_overview\"><\/span>Background and overview<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>With the Texas A&amp;M University System\u2019s implementation of Workday HCM, the responsibility of the cost allocation of benefits moved to the process that integrates Workday HCM with the A&amp;M System financial systems (FAMIS, TEEX-Masterpiece, WTAMU-Colleague).<\/p>\n\n\n\n<p>Prior to the implementation of Workday HCM, benefit costs could be allocated in BPP to specified funding payroll source lines.&nbsp; These allocations were performed by well-known processes and could also be changed and overridden by payroll operators using the BPP payroll screens.&nbsp; These allocation changes could be made during the permission to pay period.<\/p>\n\n\n\n<p>Workday HCM could not be appropriately configured to meet A&amp;M System business requirements regarding allocation and costing of benefits, and no screens exist in Workday HCM to override the costing allocations for benefits.&nbsp; Specifically, the group insurance premiums (GIP) allocation was the most problematic with the Workday HCM costing allocation process.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Current_process\"><\/span>Current process<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The current process occurs during the Workday HCM\/FAMIS integration.&nbsp; This is Workday integration INT103, and the FAMIS process has several steps but is generally referred to as \u201cpayroll history creation.\u201d<\/p>\n\n\n\n<p>GIP is proportionally allocated across any earning code marked in the earning code table as subject to GIP.&nbsp; Earning codes are defined in Workday HCM, and FAMIS maintains a copy of the earning codes and uses code attributes to control the benefit allocation process.&nbsp; Earning codes can be viewed in FAMIS on screen 730, and allocation attributes can be viewed by pressing the F6 key.<\/p>\n\n\n\n<p>The GIP allocation process is completed in the following steps:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>All payroll result line items for a person are grouped together for each Workday payroll result.\u00a0 Note: different pay periods and positions can create multiple Workday payroll results for a person on the same payroll.<\/li>\n\n\n\n<li>The total amount of employer paid GIP is totaled for a person by pay period.<\/li>\n\n\n\n<li>A table is created for each position, eligible earning code, funding account, and pay period for a person.\u00a0 For most employees, that table contains a single row for regular pay on a single position and a single pay period on a single account.\u00a0 If the employee is funded from multiple accounts or has multiple types of earnings, there will be multiple rows.<\/li>\n\n\n\n<li>Total earnings for these eligible earning codes is computed, and each row in the table is assigned a percent of the total earnings.<\/li>\n\n\n\n<li>GIP is allocated to the earning and account based on the percentage of its eligible earnings over the total eligible earnings for that person and pay period.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Problems_and_issues\"><\/span>Problems and issues<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The summers of 2018 and 2019 revealed the following problems:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>During the summer of 2018, issues were seen when GIP expenses occurred and there were no eligible earnings.\u00a0 This occurred most frequently for employees with nine-month appointments.<\/li>\n<\/ol>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In 2018, when no eligible earnings were present, the GIP costing fell to the default account for each system member.<\/li>\n\n\n\n<li>Later in the summer of 2018, the process was modified to allocate GIP expenses according to the previous May costing allocations in cases where no eligible earnings were present.<\/li>\n<\/ol>\n\n\n\n<ul class=\"wp-block-list\">\n<li>During the summer of 2019, issues were encountered when eligible earnings were present but at a fraction of the employee\u2019s regular monthly earnings.<\/li>\n<\/ul>\n\n\n\n<ol class=\"wp-block-list\" start=\"2\">\n<li>In many of these cases, the accounts funding the employee\u2019s summer earnings received a disproportionate share of GIP employer-paid benefits.<\/li>\n\n\n\n<li>The solution for this issue is described below.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Proposed_changes_for_FY_2020\"><\/span>Proposed changes for FY 2020<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Note: these proposed changes will only apply to employees under the following conditions:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The pay period is for the summer months (June, July and August).<\/li>\n\n\n\n<li>The employee is in a position with an annual work period of less than 11.5 months.<\/li>\n<\/ul>\n\n\n\n<p>The new process will work as follows:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The employee\u2019s FTE monthly salary will be obtained from Workday HCM.\u00a0 It is provided with the Workday pay result integration.<\/li>\n\n\n\n<li>If no summer earnings are present for the pay period, any GIP expenses for the summer will be allocated using the costing allocations of the preceding May period (the same as FY 2019).<\/li>\n\n\n\n<li>For a given pay period, all base pay earnings will be added together.\u00a0 Multiple earning codes can make up base pay, and the earnings may be allocated across multiple account numbers.<\/li>\n\n\n\n<li>The total of base pay earnings will be divided by the employee\u2019s FTE monthly salary to determine the employee\u2019s FTE percent for the period.<\/li>\n\n\n\n<li>If the employee\u2019s FTE percentage is greater than or equal to 75%, then all (100%) of the GIP expense for the period will be allocated to the accounts used for the summer earnings.<\/li>\n\n\n\n<li>If the employee\u2019s FTE percentage is less than 75%, the summer GIP expenses for the period will be allocated as follows:\n<ul class=\"wp-block-list\">\n<li>GIP expense will be allocated to the summer earnings based on each funding line\u2019s FTE percentage.\u00a0 For example, a funding line with 25% of the position\u2019s FTE monthly salary will be allocated 25% of the GIP expense.<\/li>\n\n\n\n<li>Any remaining GIP expense will be allocated to the accounts used in the preceding May.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Payroll_cost_transfer_impact\"><\/span>Payroll cost transfer impact<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>When GIP expenses are connected and allocated to summer earnings, the GIP will remain with the summer earnings, and PCTs will move the GIP along with the regular earnings if the summer earnings are moved with a PCT.<\/p>\n\n\n\n<p>Any GIP expense allocated to the May accounts will be placed on payroll history lines that only contain the GIP expense.&nbsp; In these cases, the GIP alone can be moved and reallocated to any funding source via the PCT process.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Other_benefit_expenses\"><\/span>Other benefit expenses<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Other Benefit expenses (i.e. TRS, ORP, OAHI, etc.) are not impacted by this change.&nbsp;&nbsp; Those benefits are all applied using standard percentages of earnings.&nbsp; Each employee earning and costing will be assigned its percentage share of those benefit expenses.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Notes_on_the_employee_FTE_calculation\"><\/span>Notes on the employee FTE calculation<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>As part of this change, a review of the Workday earning codes was conducted.&nbsp; It is proposed that the following earning codes be removed from the list of earnings that are considered base pay and could be allocated to GIP Expense.<\/p>\n\n\n\n<p>For an employee receiving these earnings, removing these earning codes will reduce the employee\u2019s FTE monthly salary because the Workday\/FAMIS integration recomputes the FTE monthly salary based on earning code.&nbsp; To keep the FTE reports consistent, these earnings will no longer be included in the FTE reports. This will also bring the monthly FTE salary in line with what is reported in Workday.<\/p>\n\n\n\n<figure class=\"wp-block-table is-style-stripes\"><table><tbody><tr><td><strong>&nbsp;<\/strong><\/td><td><strong>Earning codes removed from GIP allocation and FTE reports<\/strong><\/td><\/tr><tr><td><strong>056<\/strong><\/td><td>Qatar &#8211; Salary Incentive<\/td><\/tr><tr><td><strong>070<\/strong><\/td><td>Distinguished Chair Stipend<\/td><\/tr><tr><td><strong>DHS<\/strong><\/td><td>Department Head Stipend<\/td><\/tr><tr><td><strong>OTF<\/strong><\/td><td>Overtime &#8211; FLSA<\/td><\/tr><tr><td><strong>OTS<\/strong><\/td><td>Overtime &#8211; Straight\/State<\/td><\/tr><tr><td><strong>PTOB<\/strong><\/td><td>Paid Time Off for Banked Overtime Hours<\/td><\/tr><tr><td><strong>TII<\/strong><\/td><td>Temporary \/ Interim Increase<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>The following earning codes will be the new list of earning codes eligible to receive a GIP allocation and will be the earning codes reported on the FTE reports.<\/p>\n\n\n\n<figure class=\"wp-block-table is-style-stripes\"><table><tbody><tr><td><strong>&nbsp;<\/strong><\/td><td><strong>Earning codes eligible to receive GIP allocation<\/strong><\/td><\/tr><tr><td><strong>004<\/strong><\/td><td>Study Abroad<\/td><\/tr><tr><td><strong>005<\/strong><\/td><td>Summer Teaching<\/td><\/tr><tr><td><strong>006<\/strong><\/td><td>Summer Research<\/td><\/tr><tr><td><strong>152<\/strong><\/td><td>County Funding (Tax on Total)<\/td><\/tr><tr><td><strong>153<\/strong><\/td><td>County Funding &#8211; Extension Agent<\/td><\/tr><tr><td><strong>155<\/strong><\/td><td>County Funding CSRS<\/td><\/tr><tr><td><strong>156<\/strong><\/td><td>County Funding CSRS (Tax on Total)<\/td><\/tr><tr><td><strong>DBCY<\/strong><\/td><td>Death Occurred &#8211; Final Regular Salary\/Regular Hours (Current Calendar Year)<\/td><\/tr><tr><td><strong>DBPY<\/strong><\/td><td>Death Occurred &#8211; Final Regular Salary\/Regular Hours (Prior Calendar Year)<\/td><\/tr><tr><td><strong>PTO<\/strong><\/td><td>Paid Time Off<\/td><\/tr><tr><td><strong>RPH<\/strong><\/td><td>Regular Hours<\/td><\/tr><tr><td><strong>RPS<\/strong><\/td><td>Regular Salary<\/td><\/tr><tr><td><strong>SEP<\/strong><\/td><td>Salary Enhancement Pay<\/td><\/tr><tr><td><strong>WSH<\/strong><\/td><td>Work Study Hours<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Examples\"><\/span>Examples<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. Employee is a nine-month employee and is given a summer research position for all three months of the summer:<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Employee\u2019s regular FTE monthly salary is $10,000 per month.<br><\/li>\n\n\n\n<li>The summer appointment is for an 80% FTE.<\/li>\n\n\n\n<li>Employee\u2019s GIP expense is employee and family: $992.40 per month.<\/li>\n\n\n\n<li>Employee\u2019s summer research is funded at 50% FTE from Grant A and 30% from Grant B.<\/li>\n\n\n\n<li>Employee is only paid one earning code: RPS (regular salary).<\/li>\n<\/ul>\n\n\n\n<p>Since the summer FTE is greater than 75%, the employee\u2019s summer funding will cover the full cost of the GIP insurance.&nbsp; These allocations will be used for June, July, and August:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Grant A will fund 62.5% (\u215d) of the GIP:\u00a0 $620.25.<\/li>\n\n\n\n<li>Grant B will fund 37.5% (\u215c) of the GIP:\u00a0 $372.15.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2. Employee is a nine-month employee and receives a one-time payment in June for a summer study abroad trip:<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Employee\u2019s regular FTE monthly salary is $10,000 per month.<\/li>\n\n\n\n<li>The summer study abroad payment is $4,000 (40% FTE).<\/li>\n\n\n\n<li>Employee\u2019s GIP expense is employee and family: $992.40 per month.<\/li>\n\n\n\n<li>The summer aboard trip is funded from designated account X.<\/li>\n<\/ul>\n\n\n\n<p>Since the summer FTE is less than 75%, the summer funding will cover only a proportional amount of the summer GIP:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Designated account X will fund 40% of the GIP:\u00a0 $396.90.\n<ul class=\"wp-block-list\">\n<li>The remaining GIP expense for June will be allocated to the employee\u2019s May costing accounts.<\/li>\n\n\n\n<li>GIP expense for July and August will be 100% allocated to the employee\u2019s May costing accounts.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3. Employee is a nine-month employee and is given a summer research position for all three months of the summer:<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Employee\u2019s regular FTE monthly salary is $10,000 per month.<\/li>\n\n\n\n<li>The summer appointment is for 25% FTE.<\/li>\n\n\n\n<li>Employee\u2019s GIP expense is employee and family: $992.40 per month.<\/li>\n\n\n\n<li>Employee\u2019s summer appointment is for teaching: all funded on account C.<\/li>\n<\/ul>\n\n\n\n<p>Since the summer FTE is less than 75%, the summer funding will cover only a proportional amount of the summer GIP:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Account C will fund 25% of the GIP:\u00a0 $248.10.\n<ul class=\"wp-block-list\">\n<li>Remaining GIP expense for summer will be allocated to the employee\u2019s May costing accounts.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4. Employee is a nine-month employee and does not work in the summer:<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Employee\u2019s regular FTE monthly salary is $10,000 per month.<\/li>\n\n\n\n<li>Remaining GIP expense for summer will be allocated to the employee\u2019s May costing accounts.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Background and overview With the Texas A&amp;M University System\u2019s implementation of Workday HCM, the responsibility of the cost allocation of benefits moved to the process that integrates Workday HCM with [&hellip;]<\/p>\n","protected":false},"author":37526,"template":"","categories":[49],"tags":[],"class_list":["post-1087","white_papers","type-white_papers","status-publish","category-white-papers","entry"],"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/1087","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers"}],"about":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/types\/white_papers"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/users\/37526"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/white_papers\/1087\/revisions"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/media?parent=1087"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/categories?post=1087"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/it.tamus.edu\/famis\/wp-json\/wp\/v2\/tags?post=1087"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}]