Colorado Paid Family and Medical Leave Insurance (FAMLI) Program Wage Reporting

Colorado voters approved Proposition 118 in November of 2020, paving the way for a state-run Paid Family and Medical Leave Insurance (FAMLI) program. The FAMLI program is a social insurance program with both employers and employees contributing to the fund that will eventually pay out benefits.

Colorado FAMLI program facts:

• While FAMLI benefits will not be available to employees until 2024, businesses must begin collecting premiums starting on January 1, 2023, through a simple payroll deduction. Most Colorado businesses will need to begin deducting FAMLI premiums from all employees on their payroll, including full-time, part-time, and seasonal employees.

• The premiums are set at 0.9% (through 2024) of the employee's wage, with 0.45% paid by the employer and 0.45% paid by the employee. Premiums are paid on wages up to the Federal Social Security Wage cap.

• Businesses with nine or fewer employees do not have to contribute to the program but do need to remit their employees' share (0.45%) of the premium on behalf of employees each quarter.

• Employees and employers are never required to pay more than 50% of the total premium. Employers may choose to cover their employees' portion and pay the full premium amount as an added benefit.

• Benefits will become available to workers starting in January 2024.

• Employers are required to remit the whole 0.9% premium to the Division once a quarter. Employers can choose to deduct up to 0.45% of that from employees and remit those deductions on behalf of their employees. Ultimately, employers will need to remit 0.9% of wages to the Division, whether they choose to cover the 0.45% for their employees or not.

Attention: For more information, refer to: https://famli.colorado.gov/EMPLOYERS.

Warning: Depending on your requirements, you can set up FAMLI deductions through either the Manage Deductions screen or on the Manage Local Taxes screen. You cannot set up FAMLI deductions on both screens even if the premiums are calculated using different pay periods. Otherwise, Costpoint will not be able to correctly calculate the premiums/contributions if the wages have already reached the annual ceiling. To set up the Colorado FAMLI deductions, refer to the setup instructions in the online help for the Create Quarterly Family and Medical Leave File screen.

 

Create Quarterly Family and Medical Leave File (LDPPFML)

The Create Quarterly Family and Medical Leave File screen features the following updates:

• From the State drop-down list, you can now select Colorado.

• A new File Data group box provides fields that are required for the Colorado FAMLI quarterly wage report.

Field	Description
Employer FAMLI ID	Enter the FAMLI system-generated ID for the employer. This will be used only if an employer does not have FEIN or Tax Payer ID. This field will be enabled and required if the State is Colorado and the Tax ID of the entered Taxable Entity is blank.
Settlement Date and Time	Enter the submission date and time in these fields. If you use Form View, the fields are unlabeled. Settlement Date: Enter, or click Calendar Lookup to select, the submission date of the file. This must be unique from any other submission by this taxable entity. This field is required and enabled for Colorado. Settlement Time: Enter the time of submission of the file. This must be unique from any other submission by this taxable entity. This field is required and enabled for Colorado. Note: The application will use 00:00:00 for the time part of Settlement Date in the wage file if you do not specify a time in the Settlement Date and Time fields.
Total Payment Amount	Enter the total amount paid for the contributions. On a full payment, contributions due is equal to payment amount. This field will be enabled only for Colorado.
Is this the final return?	Select this checkbox to indicate in the report that this is the final return for this taxable entity due to business closure. This field will be enabled only for Colorado.

• The application adds a wage report titled “State Paid Family & Medical Leave Report.”

• The application will generate the wage file in CSV format for Colorado.

Note: You must enter a file name with an extension of .CSV if you are creating a report for Colorado.

 

Manage Local Taxes (PRMLTI)

The Tax Based On field adds a new SUTA Subject Wages option. You can select this option to compute the local tax withholding based on the employee's SUTA subject wages.

The SUTA Wages option in the Tax Based On field was renamed to SUTA Taxable Wages. This option is not based on the SUTA subject wages because it is capped at the SUTA limit.

 

Compute Payroll (PRPCPR)

The Compute Payroll process adds the ability to calculate local tax based on SUTA Subject Wages.

 

Manage Payroll Records (PRMPTF)

The Manage Payroll Records screen adds the ability to calculate local tax based on SUTA Subject Wages.

West Virginia Q1 2023 SUTA Electronic Filing

According to the WorkForce West Virginia Magnetic Media Wage Reporting Specifications Manual, employers must report the SOC Code (or Employee Job Title) and County Name in the Quarterly Unemployment Insurance Wage Report.

Attention: For more information, refer to the Magnetic Media Wage Reporting Specifications Manual.

To support the state requirements, this release updates the Export Payroll Taxes screen. For the SUTA Tax reporting for West Virginia, the application adds the county name in Field 87 of the SUTA Tax record.

Costpoint now provides you with the ability to group contributions together when calculating a contribution matching limit. If you have two contributions, for example, 401K and 403B, where the contribution calculation method is PCTDED, each contribution matching rate will be calculated individually and not together. This feature will allow you to combine the contributions together to determine the rate.

To support this enhancement, the Manage Deduction Group Limits screen (PRMDGL) adds a new Contribution Matching subtask, where you can specify a range of rates and the corresponding percentage contribution for those rates. For combining different contribution rates, Costpoint will use only PCTDED as a calculation method to calculate a matching percent.

Note: This feature requires patch dbc_810_11082.

 

Manage Deduction Group Limits (PRMDGL)

The Effective Dates subtask adds a new Contribution Matching Limit Method field:

Field	Description
Contribution Matching Limit Method	From the drop-down list, select the method that will be used in calculating the contribution limits. The employee's contribution amount will still be calculated with the employee's original calculation method, but the matching amount will use this method. Options are: PCTDED Not Available

A new Contribution Matching subtask provides the following fields:

Field	Description
Rates Over	Enter the starting wages or rates for the contribution matching percent.
Up to and Including	Enter the ending wages or rates for the contribution matching percent.
Matching Percent	Enter the matching percent for the wages specified in the row.

 

Compute Payroll (PRPCPR)

The Compute Payroll contribution calculation was updated to consider the deduction group’s contribution matching rates when calculating contribution matching amounts.

• If any deduction in the deduction group has a contribution with a matching rate, it will be included in the contribution matching calculation for that deduction group.

• If contributions are not included in the contribution matching limit, the application will not use the values in the deduction/contribution’s Contribution Matching subtask on the Manage Deductions screen.

 

Print Data Dictionary Report (SYRDD)

The report now provides information on the following:

• Deduction Group Limits Contribution Matching (DED_LMT_CNTRB_MATCH_RT) table

• S_CNTRB_MTHD_CD column on the Deduction Group Limits date ranges (DED_LMT_DATES) table

Defect 1876299: This application has been updated to increase the length of the STATION_ID database column to allow more simultaneous sessions for the application.

Defect 1871211: When you entered a multicurrency cash receipt, the Amt Recvd was updated to 0. This occurred when:

1. You initially left the Fiscal Year, Period, and Subperiod fields blank.

2. You entered a miscellaneous line which contains a non-existent Invoice and no Customer Account.

3. You entered a cash line.

4. You entered a different Pay Currency and exchange rate info on the Exchange Rates subtask and clicked Apply.

5. You clicked Save and encountered an error.

6. You entered the Fiscal Year, Period, and Subperiod, and clicked Save again.

You were also able to enter a cash receipt for an inactive project/account/organization.

Defect 1732526: When you created bank transactions history for an Accounts Payable voucher check payment that has a bank account currency that is different from your functional currency, the message "No Exchange Rates Exists for Rate Group: From Currency (Functional Currency): USD To Currency (Bank Currency)" displayed, and the transaction amount was saved as 0. This occurred even when exchange rates were set up for those currencies.

Defect 1849938: You encountered a system error when you imported a template that contains data on the Other Books Info subtask. As a workaround, import a template that has no other books information, and manually enter other books information if necessary.

Defect 1876028: When you selected Range as the Users selection range, entered the beginning value in the Start field, left the End field blank, and posted the journal entries using Batch Mode, Costpoint still proceeded with the posting process after the error "This Range's Option's Starting and Ending value combination is invalid" displayed.

Defect 1703894: You encountered an error when you queried daily exchange rate records.

Defect 1880815: On the Submit Job to Queue screen, the Notify When Job is Completed checkbox needed to be renamed to Notify When All Job Steps Are Completed.

Defect 1890819: The following error occurred when you tried to delete a completed record on the Manage Approval Workflow Case Status screen: "Error: Primary key column A.ACTIVITY_KEY is null IPr Key: A.ACTIVITY_KEY = null".

Defect 1650006: A system error occurred when you queried records with Sort Records by set to Statement of Work on the Sort tab of the Query dialog box.

As a workaround, you can sort records on the main screen's Table view using the Sort Ascending or Sort Descending option in the Statement of Work column.

Defect 1742672: You were unable to save a record with a Long Name value having a comma, a single quote, or double quotes.

As a workaround, remove these special characters before saving the record.

Defect 1871706: In mobile view, when you drilled down one or more levels that showed a branch and charges, and you rotated the phone to a horizontal display, the view refreshed back to the top level and showed all branches instead of the level you were viewing.

Defect 1877451: Some complex saved layouts in autoposition mode caused errors when you tried to reopen an application.

Defect 1884843: The Process lookup field returned multiple identical rows for PJPCOMPR (Compute Revenue) when you tried to set up process jobs via Web Services or Manage Jobs.

Defect 1891239: In Table view, the first column did not display when you scrolled back to the left-most part of the screen.

Defect 1896310: There was an issue with Cross-Site Scripting (XSS). When using a URL, Costpoint returned a popup window with the server name instead of the error message you expected to see.

Defect 1744468: A "RequestBroker is busy" system error occurred when you selected a charge while the Find & Replace window was open.

Defect 1862834: When the Notify when Batch Job is completed checkbox was not selected in Configure User Preferences and the Notify When Job Is Completed checkbox was selected for the Batch Mode (Calculate Billings) process with the Submit to Job Queue Now option, you did not receive an email notification for job completion.

 

New Default Setting

 

Notify When Job is Completed is now the default setting in the Submit Batch Job window and takes precedence over the Notify When Batch Job is Completed checkbox in Configure User Preferences and Manage Users.

Defect 1891909: The timestamp in JOB_SCHEDULE_HIST did not update with the Date/Time after job completion.

Defect 1875954: Going forward, the Costpoint MR installer will support both case-sensitive and case-insensitive users (default for Oracle) and FQDN suffixed to your hostname. The user referred to in this defect is the privileged Oracle user entered in one of the MR dialog boxes before execution and not the Costpoint Oracle users.

The Costpoint MR installer requires an Oracle privileged user to execute database reversal scripts and Link views. This Oracle privileged user can be the built-in SYSTEM user or any other custom user with the necessary privileges. If this user is created as case-sensitive, then the user must be entered with the correct case in the MR dialog box or else the MR execution will fail.

If you suffix FQDN to your hostname and your database for all Costpoint schemas is the same, all connections in the Costpoint Web Config Utility for your Costpoint system must have the same hostname entry.

Defect 1876302: The precision and scale of the STATION_ID has been changed to avoid a related system error.

Defect 1874582: When you accessed a record, the net available quantity was incorrect on the Inv Abbrev subtask. This happened when Shelf Life was selected and inventory existed for the record.

Defect 1891761: When you ran Firm Planned Orders, you encountered an error where the process reached a certain percentage and the application stopped responding.

Defect 1871140: When you queried a part with a purchase order (PO) delivery schedule, Costpoint returned an incorrect number of records. This happened when the Inventory Project Selection Option was all other available options except All Projects.

Defect 1871687: When you filtered the record based on warehouses, Costpoint displayed an incorrect result.

Defect 1884740: When a part had a conversion between order and inventory, the detailed part schedule displayed the order quantity and not the inventory quantity. Costpoint displayed the yield as inventory, but when you recalculated the quantity, it went to order.

Defect 1869242: The application has been modified to optimize performance.

Defect 1876267: Material Requirements Planning (MRP) generated planned orders for a product even though there were plenty in stock.

Defect 1883816: Costpoint generated unnecessary planned orders for the reservation when Plan Substitute Part was selected on the Configure Materials Requirements Planning Settings screen.

Defect 1876300: The precision and scale of the STATION_ID has been changed to avoid a related system error.

Defect 1876301: The precision and scale of the STATION_ID has been changed to avoid a related system error.

Defect 1887472: You were unable to create a negative issue to manufacturing order (MO) parts with any or no cost amount tendered, and you encountered the following error: "This negative issue would reduce the MO cost, or one or more of the MO cost elements below zero."

Defect 1741066: When you created a manufacturing order (MO) with the Apply Operationalized BOM to Requirements on Autoload checkbox selected, all items from the routing line components were added to the requirements table even though the part was out of effectivity date on the bill of materials (BOM).

Defect 1876298: The precision and scale of the STATION_ID has been changed to avoid a related system error.

Defect 1876007: When you selected a quote record and you accessed the RFQ Lines subtask, you encountered an error.

Defect 1870963: The Coverage Limit should default to 999,999,999,999,999.00 instead of 999,999,999.99 on new records and when the Calculation Method is set to Amount. This fix updates existing records that have a Calculation Method of Amount.

Defect 1893051: The Import Employee Data application required performance tuning for processing large volumes of employees.

Defect 1884922: When a Costpoint Payroll license user imported an employee from Deltek Talent Management, the application did not create the employee tax record if:

• The employee record had no State information (NULL value).

• The employee record had a State that did not exist in the STATE_TAX_TBL table in Costpoint.

In these scenarios, the employee tax record should be created since the Withholding State field is not required in Costpoint when you have a Costpoint Payroll license. This applies to states with no withholding tax (for example, AK, NH, TN, TX). These states will not exist in the STATE_TAX_TBL table.

Defect 1878885: A system error occurred when you updated a State Withholding record if:

• The employee's withholding state was Guam or Virgin Islands.

• The Form W-4 revision year was 2020 or later.

Defect 1887439: You encountered the following error when you posted timesheets: “text not found for the resource id: LDPLDJ_LV_YR_NOT_CLOSED.” This error displayed when there was no beginning balance record for the leave type that is assigned to the employee.

Defect 1875090: Costpoint should set the UNION_FRNG_FL column on the PR_SETTINGS table to N if it does not have a value set.

Defect 1879118: The 32% federal income tax bracket for Married, Step 2 Unchecked, was 379,099.99 instead of 378,999.99. This affects all Costpoint Payroll users, including those with employees in Guam and Virgin Islands.

As a workaround for this issue, you can manually enter/update the record on the Manage Federal Taxes screen. The record for Married, Step 2 Unchecked, effective 01/01/2023, should be:

Effective Date: 01/01/2023

Filing Status: Married (S_FED_FIL_STAT_CD = M)

Step 2 of W-4: Unchecked

For Taxable Income Over	Base Tax	Percent of Excess
0.00	0.00	0.00%
14,799.99	0.00	10.00%
36,799.99	2,200.00	12.00%
104,249.99	10,294.00	22.00%
205,549.99	32,580.00	24.00%
379,099.99 378,999.99	74,208.00	32.00%
477,299.99	105,664.00	35.00%
708,549.99	186,601.50	37.00%

For companies with Guam and Virgin Islands employees, you can manually update the tax tables for these states on the Manage State Tax Tables screen to mirror the federal tax tables.

Defect 1878070: The tax tables for the following counties had the corresponding issues:

• Frederick County: The second row was missing in each tax table. If a married employee has an annual taxable income of over 100,000, then the tax is calculated as the amount over 100,000 times 7.75 percent. The initial 100,000 is not taxed at all because the base tax amount is missing.

• Anne Arundel County: The second row was missing in each tax table. To address this, the tables have been revised (recalculated) so that the lower income tax rate of 2.70% (using 2.75% tables) will be used on the first $50,000 of taxable income for every taxpayer. The base tax has been recalculated starting from the second row.

As a workaround for these issues, you can manually enter/update the records for Anne Arundel County and Frederick County on the Manage State Tax Tables screen.

• Anne Arundel County

State: MD

Effective Date: 01/01/2023

Filing Status: Anne Arundel - Married/Head of Household (ANNE ARUNDEL-MARRIED)

For Taxable Income Over	Base Tax	Percent of Excess
0.00	0.00	7.5000%
50,000.00	3,750.00	7.6000%
150,000.00	11,350.00	7.8500%
175,000.00	13,312.50	8.1000%
225,000.00	17,362.50	8.3500%
300,000.00	23,625.00	8.6000%

 

State: MD

Effective Date: 01/01/2023

Filing Status: Anne Arundel - Single or Married w/h at Single rate (ANNE ARUNDEL-SINGLE)

For Taxable Income Over	Base Tax	Percent of Excess
0.00	0.00	7.5000%
50,000.00	3,750.00	7.6000%
100,000.00	7,550.00	7.8500%
125,000.00	9,512.50	8.1000%
150,000.00	11,537.50	8.3500%
250,000.00	19,887.50	8.6000%

 

• Frederick County

State: MD

Effective Date: 01/01/2023

Filing Status: Frederick - Married/Head of Household (FREDERICK-MARRIED)

For Taxable Income Over	Base Tax	Percent of Excess
0.00	0.00	7.5000%
100,000.00	0.00 7,750.00	7.7500%
150,000.00	11,625.00	8.0000%
175,000.00	13,625.00	8.2500%
225,000.00	17,750.00	8.5000%
300,000.00	24,125.00	8.7500%

 

State: MD

Effective Date: 01/01/2023

Filing Status: Frederick - Single or Married w/h at Single rate (FREDERICK-SINGLE)

For Taxable Income Over	Base Tax	Percent of Excess
0.00	0.00	7.5000%
50,000.00	0.00 3,875.00	7.7500%
100,000.00	7,750.00	8.0000%
125,000.00	9,750.00	8.2500%
150,000.00	11,812.50	8.5000%

Defect 1890278: When you ran the process with the Include – FSA/HSA Deductions checkbox cleared, the application included HSA from prior years.

Defect 1887448: You could not generate a direct deposit ACH file record for a W record because the Void/Replace Posted Paychecks screen populated the CHK_DT column on the EMPL_PAYROLL table. 

Defect 1874591: You encountered deadlock issues when multiple users were simultaneously creating, committing, and approving a budget.

Defect 1882179: Changes to the financial statements did not reflect correctly in the account profit and loss reports.

Defect 1882177: Changes to the financial statements did not reflect correctly in the organization profit and loss reports.

Defect 1867654: Changes to the financial statements did not reflect correctly in the project profit and loss reports.

Defect 1858907: Issues on timesheet ORG_ID occurred due to Costpoint org defaulting rules. As a result, the values in the Pending column for Indirect Cost were not calculated and did not display in Project Status.

Defect 1884892: You encountered intermittent null pointer issues when you imported budgets from Excel.

Defect 1891876: You encountered issues when you committed budgets/EACs mass utilities. The commit process has been modified to resolve the issues.

Defect 1848175: You encountered deadlock issues when multiple users were simultaneously creating, committing, and approving a budget/EAC.

Defect 1871876: You encountered issues when creating, committing, and approving a budget/EAC.

Defect 1894632: You encountered errors when creating, committing, and approving a budget/EAC with duplicate records in Staff Hours and Subcontractor Hours links.

Defect 1884298: You encountered a system error when adding, modifying, and assigning PTO hours.

Defect 1669225: When you used the Unit billing formula, Current ACRN Value did not equal Invoice Amount (on the Manage ACRN Bills screen) in the second invoice after you computed bills with the Release Withholdings checkbox selected on the Calculate Standard Bills screen. The difference was equal to the Sales Tax amount in the first invoice.

Defect 1753682: As with existing functionality, when the Use Project Mapping checkbox is selected on the Manage ACRN Bills screen, only one line in the Project ACRN Details table window can have the Include Schedule Bill checkbox selected. The issue comes in when you have Calculation Method set to Proration and you have more than one line in Project ACRN Details with the same Project Level at And Below value.

After you processed Calculate ACRN Bills, the schedule bill amount was not always allocated in full since Costpoint was prorating this amount across the lines with the same Project Level at And Below value, and allocating it only in the single line where Include Schedule Bill was selected.

Logic has been updated such that Costpoint will not include the schedule bill amount in proration computation. This amount will be allocated after the proration of non-schedule bill amounts or what remains of the ACRN value for the line where Include Schedule Bill is selected.

Defect 1824536: The application was taking too long to finish processing.

Defect 1708430: When you calculated retroactive bills for the RSBFNLBF (Loaded Labor Rate w/Burden w/Fee plus Non-Labor w/Burden w/Fee) formula, the fee calculation did not take labor discounts into account.

As a workaround, you can manually edit fee amounts on the Manage Standard Bills screen.

Defect 1708432: Fee calculations were incorrect for multicurrency bills with an LLRFNLBF (LLR w/Fee Plus Non-Labor w/Burden w/Fee) formula and labor discounts.

As a workaround, you can manually edit fee amounts on the Manage Standard Bills screen.

Defect 1755623: The sales tax computation was incorrect for multicurrency retroactive bills. Tax was calculated on Total Fee only.

As a workaround, you can use Calculate Standard Bills' standard/retroactive billing options. Select Indirect Costs for combo/retroactive bills and None for loaded labor rates.

Defect 1873628: The application was not picking up rows with MUX_RATE_GRP_ID set to null in the BILLING_DETL_HIST table during calculation.

Defect 1892261: The application was taking too long to complete processing.

Defect 1842752: An invoice with the Included in iRAPT File checkbox selected and File Name and Alt File Location already populated in Manage Standard Bills was still included in another iRAPT file. In addition, when the Clear iRAPT File Flags checkbox was selected on the Create iRAPT Billing Files screen, Costpoint did not clear the Included in iRAPT File checkbox and the File Name and Alt File Location fields after the iRAPT file was created.

Defect 1842385: When the entered unit usage falls outside the period of performance (POP), the Manage Unit Usage screen correctly displayed the POP warning message. However, when you used Import Units Usage Files to import unit usage information, Costpoint did not display a warning message.

Defect 1812119: The pasted pool rates on this screen were incorrect when copied from Microsoft Excel.

As a workaround, you can manually update the pasted pool rates in Manage Cost Pools, or update the rates' column format in Microsoft Excel to percent with six decimal places before copying the values.

Defect 1878690: When you ran this application with the T&M Analysis checkbox selected, the process took longer than expected to complete.

Defect 1818976: When you queried projects and then moved the Allow Charging column one position to the left, the Allow Charging checkbox became selected for all records, even for those which did not have this checkbox initially selected.

As a workaround, you can refresh the screen to correctly display the Allow Charging checkbox selection prior to the move.

Defect 1768489: When you added a vendor employee, the application took longer than expected to save a record.

Defect 1766405: You could not see the barcode on the MO Pick List report when you used either Chrome or MS Edge as web browser. As a workaround, use Mozilla Firefox when you run the report.

Defect 1856862: The data from queries in the Employee model in Business Intelligence did not match with those in Costpoint due to an issue with the Join function.

Defect 1859668: The NAICS Code description in the Contracts package did not display the correct value.

Defect 1874724: Errors occurred in the dashparts when you run the Smart AI Planning dashboards.

Defect 1877427: CER Consumers and CER Users could only create subscriptions and schedules of reports by day.

Defect 1877562: A validation issue occurred in the Remainder of the Year filter when you opened the Smart AI HR Management data module.

Defect 1877678: An error occurred on the PO drill-thru on the PO and Line Detail report. This error affects you if you use an Oracle database.

Defect 1882538: The NvoicePay report needed modifications to properly integrate with Marketplace.

Defect 1884201: The Fiscal Year prompt on the General Ledger Detail report was sorted in random order when it should have been descending.

Defect 1890084: The Subcontract Status Report was automatically generated after a company on the prompt page was selected. This error made users unable to select other prompts. The report is in Team Content » Subcontractor Management » Subcontract Status Report.

Defect 1890089: The Work Assignment Charge Detail Report was automatically generated after a company on the prompt page was selected. This error made users unable to select other prompts. The report is in Team Content » Subcontractor Management » Work Assignment Charge Detail Report.

Defect 1890110: The following error occurred when you ran the Labor Utilization report in Costpoint Enterprise Reporting for Budgeting and Planning: "An error occurred while performing operation 'sqlPrepareWithOptions' status='-9'." This issue affects Oracle clients only.

Defect 1890112: An error occurred when you ran the Opportunity Dashboard in CRM & Contracts. The following error message displayed: “The request was canceled by the user.” This error affects you if you use Oracle as your database.

Defect 1899052: In Smart AI, you could not refresh data sets and jobs for Purchase Order Data.

Defect 1878805: The Amount value on the My Expense Reports dashpart did not match the Total To Me value on the Expense Report screen.

Defect 1871824: Support was added for the following new currency codes: SLE, STN, SVC, UYW, VED, VES, and ZWL.

Defect 1707796: When two users had a set of expense reports open at the same time and both approved a different task on separate expense reports, one user received an error message indicating that the rows had been updated by another user.

Defect 1878713: When a charge was restricted, the person who should have been able to use the charge was the one restricted from doing so.

Defect 1463805: When you exported advances directly to Costpoint, the advance was not created and no Costpoint import report was produced.

Defect 1870245: When an EPROXY role was assigned to a user in Co. 2 and you performed an attachment task for a user in Co.1, you received an error that you did not have rights to upload an expense report attachment.

Defect 1877232: When a user had two roles where one was allowed to make ceiling adjustments and the other was not, neither role could make the adjustment.

Defect 1891108: Lookup Favorites for a stored procedure was updated to account for recent changes to Favorites that caused Generate Timesheets to fail.

Defect 1894102: When you printed timesheets for multiple users, it resulted to some missing revision numbers and not in descending order.

Defect 1894110: When you printed a timesheet from multiple users, the cell comments from it were not listed in date order.

Defect 1891895: A new Show Signatures on Timesheet when Available checkbox was added to the Time Settings application. When this option is selected, the signature line displays as long as the timesheet status is not Missing or Open. This allows you to display the timesheet signature when it is present.

Defect 1873865: After a replacement signature was made on a timesheet, the original from the supervisor was not removed.

Defect 1877382: When you saved a timesheet with 56 hours recorded, you received an error stating that the timesheet has fewer than the minimum number of regular hours.

Defect 1891009: You were unable to save PLC changes on the line to your Favorites.

Defect 1891046: When you signed your timesheet with a total of eight hours in the summary, you received an error message stating that the time entries overlapped.

Defect 1891605: When you entered a time entry that ends at 12 AM, you received negative values for your hours.

Defect 1891902: Timesheets that are not in a Missing or Open status will display the signature when Show Signatures on Timesheet when Available is selected in the Time Settings application.

Defect 1891930: The LLA setup on an MO was not displaying the resources from the UDT02 screen who could approve the charge.