Allowances are not tied to hours or effort and are not reported on FTE reports or included in Institutional Base Salary (IBS).<\/p>\n
4. Emoluments<\/p>\n
Emoluments are cash or non-cash gain from position or employment. \u00a0Emoluments are a taxable event to the employee and are therefore recorded in the payroll system.<\/p>\n
The difference between allowances and emoluments within the A&M System are:<\/p>\n
- \n
- Allowances are paid\/disbursed and taxed through the payroll system.<\/li>\n
- 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
5. County Funds<\/p>\n
County funds are special emoluments that are used by the Texas A&M AgriLife Extension Service to document and record payments to County Agents made by the Texas County.\u00a0 Many county agents are paid some of their compensation directly by the counties.<\/p>\n
The A&M System and Workday treat these as a special emoluments.\u00a0 Special handling is in place on these emoluments since the Texas A&M AgriLife Extension Service is responsible to pay retirement and insurance benefits on these emoluments.<\/p>\n
6. One-time Merit Payments<\/p>\n
One-time merit or lump sum merit payments are one-time payments made to employees to recognize employee performance or accomplishments.\u00a0 Merit based salary\/hourly rate increases applied to regular pay will be reported with regular pay.<\/p>\n
7. Awards<\/p>\n
Awards are one-time payments made to employees and not subject to the A&M System policy on merit payments.<\/p>\n
8. Entitlements<\/p>\n
Entitlements are compensation, paid to the employee, based on statutory requirements not directly tied to effort.\u00a0 Currently, longevity is the sole entitlement used by the A&M System.<\/p>\n
9. Lump Sum Payouts<\/p>\n
Lump sum payouts are payments to employees based on some sort of accumulated benefit or unpaid compensation.\u00a0 Examples include:<\/p>\n
- \n
- Lump sum vacation payouts<\/li>\n
- Payment of sick leave to diseased employee\u2019s estate<\/li>\n<\/ul>\n
10. Stipends<\/p>\n
Stipends are a fixed sum of money paid periodically to cover expenses or in recognition of additional job duties.<\/p>\n
11. Uplifts<\/p>\n
Uplifts are increases to the employee\u2019s regular rate of pay in recognition of special circumstances.\u00a0 Examples include:<\/p>\n
- \n
- Shift differential<\/li>\n
- Expatriate work subject to different taxes<\/li>\n
- Hazard Duty Pay<\/li>\n<\/ul>\n
12. Additional Pay<\/p>\n
Additional Pay is compensation for services that are (at least) one of the following: temporary, beyond the scope of the employee’s position restriction, targeted to a specific job profile or position type, or related to a second position.<\/p>\n
Object Codes<\/h2>\n
Earning codes map to FAMIS object codes.\u00a0 Earning codes for regular pay, overtime, and one-time merit payments have a complex mapping based on items such as the employee\u2019s faculty\/non-faculty status and title.\u00a0 Most other earning codes map to a single object code.<\/p>\n
Workday FIT Withholding Rate<\/h2>\n
Earning codes in Workday impact the amount of Federal Income Tax withheld.\u00a0 The possible values are:<\/p>\n
- \n
- Supplemental \u2013 22%: – Federal income tax is withheld at the supplemental rate<\/li>\n
- W-4: Federal income tax is withheld at the employee\u2019s W-4 rate<\/li>\n
- No FIT: No federal income tax is withheld<\/li>\n<\/ul>\n
Workday Assess & Withhold Retirement<\/h2>\n
Earning codes may or may not be subject to retirement contributions.\u00a0 For example, base pay is subject to retirement holdings, but employee relocation allowances are not. \u00a0Each earning code in Workday is configured as specified in this spreadsheet:\u00a0 Possible values are:<\/p>\n
- \n
- Yes<\/li>\n
- No<\/li>\n<\/ul>\n
TRS Creditable<\/h2>\n
Each earning code is marked Yes or No, as to whether the earnings must be reported to TRS.\u00a0 This attribute is used during the A&M System integration to TRS TEAM.<\/p>\n
See the following link for more information:\u00a0 https:\/\/www.trs.texas.gov\/Pages\/re_creditable_compensation.aspx<\/a><\/p>\n
Include on FTE Report<\/h2>\n
Each earning code is marked Yes or No, as to whether the pay and effort is reported on the State Auditor FTE report.\u00a0 At this time, this data element is used exclusively in the enterprise data warehouse application.<\/p>\n
Include for Time and Effort – IBS<\/h2>\n
Each earning code is marked Yes or No, as to whether the payroll expense is part of Institutional Base Pay (IBS) and sent to the Time and Effort system.\u00a0 The definition of IBS follows:<\/p>\n
IBS as defined by the A&M System:<\/h3>\n
Institutional Base Pay (IBS) is the total guaranteed annual compensation an Individual receives from a TAMUS institution or agency, whether the individual\u2019s time is spent on research, teaching, patient care or other activities.<\/p>\n
Other institutions have a more in depth definition of IBS. \u00a0For example IBS defined by the University of Buffalo:<\/h3>\n
Institutional Base Salary (IBS) is the annual salary paid to an individual for performance of 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 his\/her primary UB appointment. IBS excludes any income that an individual is permitted to earn outside of duties performed as part his\/her primary UB appointment.<\/p>\n
IBS is set prospectively either for an indefinite period or for a specified term. IBS may not be increased or decreased based on availability of salary support from sponsored agreements or other revenue sources.<\/p>\n
FAMIS \u2013 Payroll History Compute Hours<\/h2>\n
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
FAMIS \u2013 SGIP (GIP)<\/h2>\n
FAMIS uses this element to control the allocation of the employer group insurance premium (GIP) to the set of appropriate earning codes.\u00a0 GIP is often referred to as SGIP \u2013 since it often funded by the State of Texas. \u00a0Typically, the GIP is charged to earning codes that are in the regular pay earning family.\u00a0 By attaching GIP charges to these earning codes, it also ensures that GIP is allocated to accounts in proportion to the regular pay.<\/p>\n
Possible values are:<\/p>\n
- \n
- Yes \u2013 This earning code (if present) will receive a proportional share of the GIP charge<\/li>\n
- No \u2013 This earning code will not receive a proportional share of the GIP charge<\/li>\n<\/ul>\n
Note: \u00a0Special allocation rules are in place for the allocation of GIP in the summer months<\/p>\n
FAMIS \u2013 Retirement<\/h2>\n
FAMIS uses this element to control the allocation of the retirement expenses (TRS or ORP) to the set of appropriate earning codes.<\/p>\n
Possible values are:<\/p>\n
- \n
- Yes \u2013 This earning code (if present) will receive a proportional share of the employer retirement contribution<\/li>\n
- No \u2013 This earning code will not receive a proportional share of the employer retirement contribution<\/li>\n<\/ul>\n
FAMIS \u2013 FICA<\/h2>\n
FAMIS uses this element to control the allocation of the FICA (OASI\/OAHI) expenses to the set of appropriate earning codes.<\/p>\n
Possible values are:<\/p>\n
- \n
- Yes \u2013 This earning code (if present) will receive a proportional share of FICA<\/li>\n
- No \u2013 This earning code will not receive a proportional share of FICA<\/li>\n<\/ul>\n
FAMIS \u2013 FIT<\/h2>\n
FAMIS uses this element to control the allocation of the Federal Income Tax (FIT) to the set of appropriate earning codes.<\/p>\n
Possible values are:<\/p>\n
- \n
- Yes \u2013 This earning code (if present) will receive a proportional share of FIT<\/li>\n
- No \u2013 This earning code will not receive a proportional share of FIT<\/li>\n<\/ul>\n
Note: \u00a0Since FIT is an employee deduction, the allocation of FIT does not impact accounting<\/p>\n
FAMIS \u2013 Unemployment Compensation Insurance (UCI)<\/h2>\n
A value of Yes indicates the integration with Workday that builds the FAMIS payroll history data, will attempt to allocate and assess UCI to this earning code.<\/p>\n
FAMIS \u2013 Workers Compensation Insurance (WCI)<\/h2>\n
A value of Yes indicates the integration with Workday that builds the FAMIS payroll history data, will attempt to allocate and assess WCI to this earning code.<\/p>\n
FAMIS \u2013 Emolument (EMOL)<\/h2>\n
A value of Yes indicates that special processing occurs.\u00a0 The special processing is as follows:<\/p>\n
- \n
- The emolument will only<\/u><\/strong> be allocated FICA (OASI, OAHI) deductions<\/li>\n
- The emolument will be allocated FIT\/SIT\/LIT\n
- \n
- Note: allocation of deductions does not really change accounting \u2013 it is for reporting only<\/li>\n<\/ul>\n<\/li>\n
- The emolument will be assessed UCI and WCI<\/li>\n
- Covered earnings (for the above) will be set to the amount of the earning itself<\/li>\n
- The earning amount will be zeroed out (Gross Pay will be set to zero) \u2013 as the earning itself does not need to be expensed in accounting<\/strong><\/li>\n<\/ul>\n
A value of No indicates that regular benefit allocation processing occurs.<\/p>\n
Note: \u00a0\u201cregular benefit allocation processing\u201d \u2013 does use other flags\/attributes of the earning code.<\/p>\n
FAMIS – Allowance<\/h2>\n
A value of Yes indicates that special processing occurs.\u00a0 The special processing is as follows:<\/p>\n
- \n
- The allowance will only be allocated FICA (OASI, OAHI) deductions<\/li>\n
- The allowance will be allocated FIT\/SIT\/LIT\n
- \n
- Note: Allocation of deductions does not really change accounting \u2013 it is for reporting only<\/li>\n<\/ul>\n<\/li>\n
- The allowance will be assessed UCI and WCI<\/li>\n
- Covered earnings (for the above) will be set to the amount of the earning itself<\/li>\n
- The earning amount will be expensed in FAMIS<\/li>\n<\/ul>\n
A value of No indicates that regular benefit allocation processing occurs.<\/p>\n
Note: \u00a0\u201cregular benefit allocation processing\u201d \u2013 does use other flags\/attributes of the earning code.<\/p>\n
FAMIS – Task Payment<\/h2>\n
A value of Yes indicates that this earning code is considered a task payment.\u00a0 Task Payment is a legacy reporting attribute only.<\/p>\n
FAMIS – Longevity<\/h2>\n
A value of Yes indicates that this earning code should get an allocation of the longevity payment.<\/p>\n
Group 100%<\/h2>\n
Group 100% is used for the assignment of source percent effort.<\/p>\n
- \n
- A value of No indicates that this earning code will stand alone with no grouping done in the percent effort calculation and therefore will always get 100% of whatever benefits\/deductions are associated with the earning code.<\/li>\n
- A value of Yes groups earning codes together for dispersing benefits and deductions.<\/li>\n
- All value of Incremental was added after several payrolls were run after Workday HCM went live. A new grouping was needed to combine some earning codes together for the proper distribution of their associated benefits\/deductions, but not have them as part of regular pay.<\/li>\n
- All other values will be grouped together with their like values when computing percent effort (i.e. values of Yes and Incremental).<\/li>\n<\/ul>\n
Pay Type<\/h2>\n
FAMIS will assign this pay type to the Payroll History record.\u00a0 Pay Type is a legacy value used in BPP.\u00a0 Use of Pay Type for reporting should be discouraged.\u00a0 The earning code itself should drive reporting.\u00a0 However, the value is assigned to facilitate backwards compatibility.<\/p>\n
Possible values assigned to Pay Type in the Pay History file are:<\/p>\n
- \n
- B: Normal Budgeted Monthly (FAMIS automatically converts to H if hourly biweekly)<\/li>\n
- D: Death Benefits<\/li>\n
- E: Adjustment or Correction Entry<\/li>\n
- F: Work Study<\/li>\n
- H: Normal Hourly Biweekly<\/li>\n
- I: Monthly supplemental Pay<\/li>\n
- J: On-Demand Payment \u2013 Monthly Payroll<\/li>\n
- K: On-Demand Payment \u2013 Biweekly Payroll<\/li>\n
- P: Biweekly Supplemental Pay<\/li>\n
- Q: Biweekly Supplemental Pay<\/li>\n
- U: Emolument<\/li>\n
- V: Vacation Lump Sum Payout<\/li>\n<\/ul>\n
Note:\u00a0 FAMIS Screen 730 does not currently allow for a value of H.\u00a0 For all earning codes with a Pay Type of B, during the pay history generation process FAMIS will automatically change the Pay Type from B to H for biweekly payroll cycles.<\/p>\n
Include in FTE Base Pay<\/h2>\n
A value of Yes indicates that this earning code should be added to base pay (RPH, RPS) for the current FTE salary and FTE monthly salary calculation.<\/p>\n
Note:\u00a0 This was used to calculate FTE monthly Salary Rate \u2013 which becomes the denominator in the FTE calculation, but it is not used anymore.<\/p>\n
Allowance Encumber<\/h2>\n
A value of Yes indicates that this earning code does utilize allowance encumbering in FAMIS.<\/p>\n
HRIS Pay Transaction Type<\/h2>\n
Earning codes map earnings to HRIS payroll transaction types.\u00a0 The following HRIS transaction types are allowed:<\/p>\n
- \n
- LS: Lump Sum Payment \u2013 A lump sum payment of accumulated annual leave upon employee termination, or a lump sum payment for half of accumulated sick leave or for 336 hours, whichever is less, upon the death of an employee.<\/li>\n
- OP: Overtime Payment \u2013 Payment for hours worked in addition to regular work hours for an employee who is subject to the Fair Labor Standards Act (FLSA).<\/li>\n
- RP: Regular Payment \u2013 Payment for regular work hours.<\/li>\n
- SP: Supplemental Payment \u2013 Payment of an amount that was 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
- TP: Task\/Temporary Payment \u2013 Payment for non-reportable employees, college work study and student status employees.<\/li>\n<\/ul>\n
Note: \u00a0HRIS permits other Pay Transaction types, but only the above types are used with earning codes<\/p>\n
HRIS Entitlement Code:<\/h2>\n
Earning codes map earnings to HRIS payroll entitlement codes.\u00a0 The following HRIS entitlement codes are allowed:<\/p>\n
- \n
- 1XM: One-time merit award<\/li>\n
- ALP: Annual Leave Pay<\/li>\n
- AWD: Award Pay<\/li>\n
- BSY: Base Salary<\/li>\n
- CAR: Car Allowance<\/li>\n
- CLO: Clothing Allowance<\/li>\n
- CRT: Certification\/Advanced Degree Pay<\/li>\n
- CSS: Cost of Living Salary Supplement<\/li>\n
- CTP: Compensatory Time Pay<\/li>\n
- ENR: Enrichment<\/li>\n
- EXP: Expense Allowance<\/li>\n
- EXM: Emergency One Time Merit Award<\/li>\n
- HAZ: Hazardous Duty Pay<\/li>\n
- HLY: Hourly (Temporary Hourly only)<\/li>\n
- HOU: Housing Allowance (Including Utilities)<\/li>\n
- LDP: Location Differential Pay<\/li>\n
- LOG: Longevity Pay<\/li>\n
- MLS: Meals<\/li>\n
- MSC: Miscellaneous Entitlement<\/li>\n
- OCP: On Call Pay<\/li>\n
- OTP: Overtime Pay<\/li>\n
- PRB: Performance Bonus<\/li>\n
- SCH: Scholarship Allowance<\/li>\n
- SDP: Specialty Differential Pay<\/li>\n
- SEV: Severance Pay<\/li>\n
- SHD: Shift Hours Differential Pay<\/li>\n
- SLP: Sick Leave Pay<\/li>\n
- SPA: Augmentation\/Special Augmentation<\/li>\n
- SRB: Retention Bonus<\/li>\n
- SSP: Student Status Payments (College Work Study\/Student Status only)<\/li>\n
- STI: Stipend\/Extra Duty Pay<\/li>\n
- SUP: Salary Supplementation<\/li>\n
- TOP: Teaching Overload<\/li>\n<\/ul>\n
HRIS Payroll Type:<\/h2>\n
Earning codes map earnings to HRIS payroll types.\u00a0 The following HRIS payroll types are allowed:<\/p>\n
- \n
- BIW: Biweekly – Regular<\/li>\n
- MON: Monthly \u2013 Regular<\/li>\n
- LUM: Lump-Sum Payments<\/li>\n
- OTP: Overtime Payments<\/li>\n
- SUP: Supplemental<\/li>\n<\/ul>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
The A&M System\u2019s master list of earning codes assigns and documents the values assigned to each earning code from the following taxonomy. Earning Families Each earning code is assigned to an earning family.\u00a0 An earning family is a group of earning codes that have similar characteristics.\u00a0 Following are the A&M System earning families: 1. Regular […]<\/p>\n","protected":false},"author":12,"featured_media":0,"parent":7,"menu_order":30,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":{"0":"post-74","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages\/74","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/comments?post=74"}],"version-history":[{"count":0,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages\/74\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages\/7"}],"wp:attachment":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/media?parent=74"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":60,"date":"2022-03-11T13:58:52","date_gmt":"2022-03-11T19:58:52","guid":{"rendered":"https:\/\/it.tamus.edu\/earningcodes\/?page_id=60"},"modified":"2022-03-11T13:58:52","modified_gmt":"2022-03-11T19:58:52","slug":"how-to-request-a-new-earning-code","status":"publish","type":"page","link":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/home\/request-process\/how-to-request-a-new-earning-code\/","title":{"rendered":"How-To: Request a New Earning Code"},"content":{"rendered":"
To request a new earning code, you must first be an authorized user of the Earning Codes database in the Requester role. See\u00a0User Setup<\/a>\u00a0for more information.<\/p>\n
1. Log in to the Earning Codes application in Quick Base – https:\/\/tamus.quickbase.com\/db\/bqckiccab<\/a><\/p>\n
2. Select \u201cRequest a New Earning Code\u201d on the Earning Code Request Home.<\/p>\n
![\"\"](\"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-content\/uploads\/sites\/37\/2022\/03\/Request-earning-code-1024x570.png\")
<\/p>\n3. Complete each field and select \u201cSave & close\u201d.<\/p>\n
![\"\"](\"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-content\/uploads\/sites\/37\/2022\/03\/Add-earning-code.png\")
<\/p>\n4. Find and select the Earning Code you just created from the list of \u201cMy Pending Earning Codes\u201d.<\/p>\n
![\"\"](\"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-content\/uploads\/sites\/37\/2022\/03\/Pending-earning-codes-1024x588.png\")
<\/p>\n5. Scroll to the very bottom of the page and select \u201cRequest Earning Code Approval\u201d.<\/p>\n
![\"\"](\"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-content\/uploads\/sites\/37\/2022\/03\/Request-approval.png\")
<\/p>\n6. Your earning code request has now been submitted and the approval process has been
\ninitiated. You will receive an email alert from QuickBase that informs you that your request
\nhas been submitted.<\/p>\n![\"\"](\"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-content\/uploads\/sites\/37\/2022\/03\/Earning-code-created-1024x293.png\")
<\/p>\n![\"\"](\"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-content\/uploads\/sites\/37\/2022\/03\/Earning-code-submitted-email-1024x492.png\")
<\/p>\n","protected":false},"excerpt":{"rendered":"To request a new earning code, you must first be an authorized user of the Earning Codes database in the Requester role. See\u00a0User Setup\u00a0for more information. 1. Log in to the Earning Codes application in Quick Base – https:\/\/tamus.quickbase.com\/db\/bqckiccab 2. Select \u201cRequest a New Earning Code\u201d on the Earning Code Request Home. 3. Complete each […]<\/p>\n","protected":false},"author":12,"featured_media":0,"parent":19,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":{"0":"post-60","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages\/60","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/comments?post=60"}],"version-history":[{"count":0,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages\/60\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages\/19"}],"wp:attachment":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/media?parent=60"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":31,"date":"2020-09-30T17:26:07","date_gmt":"2020-09-30T22:26:07","guid":{"rendered":"http:\/\/it.tamus.edu\/earningcodes\/?page_id=31"},"modified":"2021-12-16T12:40:44","modified_gmt":"2021-12-16T18:40:44","slug":"search","status":"publish","type":"page","link":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/search\/","title":{"rendered":"Search Results"},"content":{"rendered":"","protected":false},"excerpt":{"rendered":"","protected":false},"author":37526,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"page-templates\/template-search.php","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":{"0":"post-31","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages\/31","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/users\/37526"}],"replies":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/comments?post=31"}],"version-history":[{"count":0,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages\/31\/revisions"}],"wp:attachment":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/media?parent=31"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":19,"date":"2020-03-27T20:06:57","date_gmt":"2020-03-28T01:06:57","guid":{"rendered":"http:\/\/it.tamus.edu\/earningcodes\/?page_id=19"},"modified":"2022-03-11T14:01:01","modified_gmt":"2022-03-11T20:01:01","slug":"request-process","status":"publish","type":"page","link":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/home\/request-process\/","title":{"rendered":"Request Process"},"content":{"rendered":"
To request a new earning code, you must first be an authorized user of the Earning Codes database in the Requester role. See User Setup<\/a> for more information.<\/p>\n
Requesters can create a new earning code in the Earning Codes database, and submit the new record for approval. If the status is New<\/strong>, click on Request Earning Code Approval<\/em><\/span> link in the Approvals<\/strong> section of the form (screenshot below). This will complete the submission, and update the status to Pending Approval<\/strong>.<\/p>\n
![\"\"](\"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-content\/uploads\/sites\/37\/2022\/02\/Earning-Codes-Approval-Request-300x150.png\")
<\/p>\nMore details about how to request a new earning code<\/a>.<\/p>\n
Once an earning code is submitted for approval, it is reviewed by 3 approval groups:<\/p>\n
- \n
- Workday Services<\/strong>, which adds several payroll-related fields to the request<\/li>\n
- System Budgets and Accounting (SOBA)<\/strong>, which adds the financial systems’ object codes to the request<\/li>\n
- System Enterprise Applications (SEA)<\/strong>, which sets the effective from\/thru dates and performs the final approval<\/li>\n<\/ul>\n
After these groups have reviewed the request and added the needed payroll and accounting detail information, an earning code administrator will activate the new earning code.<\/p>\n
The Earning Codes application will email Workday Services, FAMIS, and the Enterprise Data Warehouse group upon activation and they will update their earning codes data accordingly.<\/p>\n","protected":false},"excerpt":{"rendered":"
To request a new earning code, you must first be an authorized user of the Earning Codes database in the Requester role. See User Setup for more information. Requesters can create a new earning code in the Earning Codes database, and submit the new record for approval. If the status is New, click on Request […]<\/p>\n","protected":false},"author":12,"featured_media":0,"parent":7,"menu_order":20,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":{"0":"post-19","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages\/19","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/comments?post=19"}],"version-history":[{"count":0,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages\/19\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages\/7"}],"wp:attachment":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/media?parent=19"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":7,"date":"2020-03-27T15:01:46","date_gmt":"2020-03-27T15:01:46","guid":{"rendered":"http:\/\/it.tamus.edu\/earningcodes\/?page_id=7"},"modified":"2022-04-26T23:40:27","modified_gmt":"2022-04-27T04:40:27","slug":"home","status":"publish","type":"page","link":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/","title":{"rendered":"Earning Codes"},"content":{"rendered":"
Earning codes are used by many enterprise systems at The Texas A&M University System, including Workday, FAMIS, the Enterprise Data Warehouse, Position Budgeting, and others.<\/p>\n
As such, earning codes are a controlled data element. New earning codes can be requested by authorized financial and payroll personnel within the A&M System.<\/p>\n
To request a new earning code, please contact the Payroll Manager(s) at your member and they will submit a request through the Earning Codes application.\u00a0 To request a change to an existing earning code, please email support@tamus.edu<\/a>.\u00a0 If you are a Payroll Manager at your member and need access to submit requests in the Earning Codes application, please email support@tamus.edu<\/a>.<\/p>\n
To view the master list of earning codes, visit the public Earning Codes website<\/a>.<\/p>\n
Earning codes are closely related to object codes. To view the master list of object codes, visit the public Object Codes website<\/a>.<\/p>\n
To learn more about the attributes that define Earning Codes, see the Earning Codes Attributes<\/a> documentation on this web site.<\/p>\n
History<\/h2>\n
In 2017, as part of the implementation of the Workday HCM and Payroll system, The Texas A&M University System (A&M System) was required to set up and define earning codes<\/u>.<\/p>\n
Earning codes are critical to any Workday Payroll implementation, defining attributes such as tax rates and tax eligibility, and are essential data elements used for multiple business processes and tasks within Workday.<\/p>\n
Earning codes affect many reports, integrations, and other processes outside of Workday and downstream in FAMIS and the Enterprise Data Warehouse.<\/p>\n
Earning codes are used in the following systems:<\/p>\n
- \n
- State of Texas \u2013 integration with USAS<\/li>\n
- State of Texas \u2013 integration with HRIS<\/li>\n
- State of Texas \u2013 integration with TRS TEAM<\/li>\n
- Federal Government \u2013 IPEDs reports<\/li>\n
- Federal Compliance \u2013 Time and Effort reports<\/li>\n
- FAMIS \u2013 Object code assignment and benefit allocations<\/li>\n<\/ul>\n
BPP Background<\/h3>\n
The A&M System\u2019s previous payroll system, BPP, implemented the concept of earning codes differently.\u00a0 BPP used multiple identifiers to attempt to accomplish similar purposes.\u00a0 Being a software system that was created before many of the alternate forms of compensation were used by the A&M System, BPP did a less than perfect job in classifying compensation.\u00a0 The codes used in BPP were:<\/p>\n
- \n
- Object Code<\/li>\n
- Supplemental Pay Code<\/li>\n
- Pay Type<\/li>\n
- Task Payment<\/li>\n<\/ul>\n
Pay Type was a problematic multi-purpose code that usually controlled how taxes were withheld and if the compensation was delivered by check or ACH.<\/p>\n
Starting from these codes, the Workday implementation team built the list of earning codes used in Workday.\u00a0 The Workday model of earning codes simplifies many of the payroll classification issues.<\/p>\n
Supplemental Compensation<\/h3>\n
Supplemental compensation is a term that has been used for many years at the A&M System.\u00a0 However, it is a generic and imprecise term that often was used to refer to allowances, merit or bonus payments, or other non-regular pay.<\/p>\n
The term supplemental was also used in BPP to refer to off-cycle or out-of-cycle payroll runs.<\/p>\n
It is recommended that the A&M System move away from this term and use the more precise terms described in the Earning Codes Attributes<\/a> documentation.<\/p>\n","protected":false},"excerpt":{"rendered":"
Earning codes are used by many enterprise systems at The Texas A&M University System, including Workday, FAMIS, the Enterprise Data Warehouse, Position Budgeting, and others. As such, earning codes are a controlled data element. New earning codes can be requested by authorized financial and payroll personnel within the A&M System. To request a new earning […]<\/p>\n","protected":false},"author":12,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"content-sidebar","footnotes":""},"class_list":{"0":"post-7","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages\/7","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/comments?post=7"}],"version-history":[{"count":0,"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/pages\/7\/revisions"}],"wp:attachment":[{"href":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-json\/wp\/v2\/media?parent=7"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":16,"date":"2020-03-27T11:10:20","date_gmt":"2020-03-27T16:10:20","guid":{"rendered":"http:\/\/it.tamus.edu\/earningcodes\/?page_id=16"},"modified":"2021-05-12T11:40:28","modified_gmt":"2021-05-12T16:40:28","slug":"user-setup","status":"publish","type":"page","link":"https:\/\/tamuserp2.wpengine.com\/earningcodes\/home\/user-setup\/","title":{"rendered":"User Setup"},"content":{"rendered":"
New Users<\/h2>\n
Payroll managers, financial officers, and IT personnel from TAMUS OIT must be set up as users of the Earning Codes database in order to request and approve earning codes.<\/p>\n
Email support@tamus.edu<\/a> to initiate the process. You must provide your UIN and the requested role in this email. Those are:<\/p>\n
- \n
- Requester<\/li>\n
- Workday Services Approver<\/li>\n
- SOBA Approver<\/li>\n
- SEA Approver<\/li>\n<\/ul>\n
When your role is granted, you will receive an invitation to join the QuickBase platform as a user and another to accept your role in the Earning Codes database.<\/p>\n
Administration<\/h2>\n
New users of the Earning Codes app must first be set up in QuickBase. This should be done using the employee’s work email address as displayed in SSO.<\/p>\n
Next, the new user must be granted his\/her role in the application.<\/p>\n
Finally, the new user must be added to the appropriate Google Group for email distribution:<\/p>\n
![\"\"](\"https:\/\/tamuserp2.wpengine.com\/earningcodes\/wp-content\/uploads\/sites\/37\/2020\/03\/Earning-Codes-email-groups.png\")
<\/p>\n
- System Budgets and Accounting (SOBA)<\/strong>, which adds the financial systems’ object codes to the request<\/li>\n
- Workday Services<\/strong>, which adds several payroll-related fields to the request<\/li>\n
- The emolument will be allocated FIT\/SIT\/LIT\n
- The emolument will only<\/u><\/strong> be allocated FICA (OASI, OAHI) deductions<\/li>\n