Costpoint now has the capability to export 1099 information into a CSV file for submission through IRIS. The IRS Information Returns Intake System (IRIS), introduced in 2025, will be the only intake system for FIRE-related forms once FIRE reaches its targeted retirement schedule on January 2027.

With this enhancement, you can generate IRIS-aligned CSV files for 1099-NEC and 1099-MISC directly from Costpoint using existing 1099 reporting logic, helping you prepare for upcoming IRS filing requirements as the transition away from FIRE approaches.

The export applies standard 1099 thresholds and withholding rules, and validates required recipient information before file creation. When record counts exceed IRS limits, Costpoint automatically generates multiple CSV files, helping ensure the output is ready for IRIS submission.

Note: For more information on IRIS, refer to https://www.irs.gov/pub/irs-efile/iris-101-07292025.pdf.

 

Important Notes:

• The CSV output includes only fields currently available in Costpoint and mapped to IRIS requirements; some optional IRIS fields are not included.

• Corrections are not supported when creating a 1099 CSV file.

• If the total number of records exceeds 250, Costpoint generates multiple CSV files.

• Required recipient information (such as Recipient TIN Type and name) must be complete; missing required data prevents CSV creation.

• The CSV export uses existing 1099 federal reporting logic and thresholds. State-specific filing is not supported in this feature. View this Important Notice for more information on the removal of the 1099 state filing capability in Costpoint.

• The CSV file is intended for data submission and does not replace printed 1099 forms or correction workflows.

  

 

Manage Vendors (APMVEND)

Multiple enhancements have been added to the Manage Vendors screen to support the 1099 CSV file creation capability.

The screen has been updated with a new 1099 tab, where the former 1099’s group box from the Header tab has been relocated. In addition, the following recipient information fields have been added to this tab:

• Recipient TIN Type: Use this field to select the type of tax identification number of the recipient. It has the following options:

• EIN: A nine-digit taxpayer identification number issued by the IRS to identify business entities, estates, trusts, and other non-individual taxpayers for federal tax reporting purposes

• QI-EIN: An Employer Identification Number assigned to a foreign entity or certain U.S. branches that have entered into a Qualified Intermediary (QI) agreement with the IRS and assume primary withholding and reporting responsibilities for certain U.S.-source income

• SSN: A nine-digit taxpayer identification number issued by the Social Security Administration to U.S. citizens and eligible residents, used to identify individuals for employment and federal tax reporting purposes

• ITIN: A nine-digit taxpayer identification number issued by the IRS to individuals who are required to file U.S. tax returns but are not eligible for a Social Security Number. An ITIN is used for federal tax reporting purposes only.

• ATIN: A temporary taxpayer identification number issued by the IRS for a child in a pending domestic adoption when the adopting parents are unable to obtain the child’s Social Security Number before filing a federal tax return

• UND: An indicator used in information return reporting when a recipient’s taxpayer identification number has not been provided or cannot be determined at the time of filing, despite required solicitations. The IRS does not consider this a valid TIN and may assess penalties for missing TINs.

• Recipient First Name: Use this field to enter the recipient’s given name. This field is required if the Recipient TIN Type represents a person (SSN, ITIN, or ATIN).

• Recipient Middle Name: Use this field to enter the recipient’s middle name or initial.

• Recipient Last Name: Use this field to enter the recipient’s family or surname. This field is required if the Recipient TIN Type represents a person (SSN, ITIN, or ATIN).

• Recipient Suffix: Use this field to enter the suffix associated with the recipient’s name (such as Jr., Sr., or III), if applicable.

Recipient information is required so the IRS can identify the payee, match reported income to the correct taxpayer, and validate the tax information returns during electronic filing. These fields are validated during 1099 CSV creation.

In addition, all recipient information fields, along with the 1099 Type, Name fields, and the Print 1099 Form checkbox, are now available as query parameters. 

 

 

 Import Vendors (AOPUTLVU)

The Import Vendors screen has been enhanced to support importing recipient information required for 1099 CSV creation. The following new fields can now be included when importing vendor data:

Column Name	Costpoint Table/Column	Type	Length	Required or Optional	Format
Recipient TIN Type	S_1099_RECPT_TIN_TYPE	Alphanumeric	10	Optional	E: EIN Q: QI-EIN S: SSN I: ITIN A: ATIN U: UND
Recipient First Name	S_1099_RECPT_FNAME	Alphanumeric	20	Required if Recipient TIN Type is S, I, or A.
Recipient Middle Name	S_1099_RECPT_MNAME	Alphanumeric	20	Optional
Recipient Last Name	S_1099_RECPT_LNAME	Alphanumeric	20	Required if Recipient TIN Type is S, I, or A.
Recipient Suffix	S_1099_RECPT_SUFFIX		20	Optional

  

 

Create 1099 Information (APP1099C)

Enhancements to the Create 1099 Information screen ensure that recipient information are stored with 1099 records to support IRIS-aligned CSV output. The following columns are now populated in the Vendor 1099 Information (VEND_1099) table during the 1099 creation process:

• Recipient TIN Type (S_1099_RECPT_TIN_TYPE)

• Recipient First Name (S_1099_RECPT_FNAME)

• Recipient Middle Name (S_1099_RECPT_MNAME)

• Recipient Last Name (S_1099_RECPT_LNAME)

• Recipient Suffix (S_1099_RECPT_SUFFIX)

 

 

Edit 1099 Information (APM1099)

The Edit 1099 Information screen has been updated to display key recipient fields used for 1099 CSV creation. The following read-only fields have been added to help identify missing or incomplete data:

• Recipient TIN Type

• Recipient First Name

• Recipient Last Name

These fields can be queried and sorted to assist with data review prior to CSV generation.

 

 

Print/Create 1099s and Magnetic Media (APR1099)

The Print/Create 1099s and Magnetic Media screen has been enhanced with a new option to create a 1099 CSV file for IRIS filing. The following new screen elements have been added:

• Create CSV option in the Generate group box

• Create 1099 CSV File option in the Actions drop-down list

When you select Create CSV:

• In the Generate group box, the Correction checkbox is disabled.

• In the Magnetic Media Information group box, all fields except for Location and File Name are disabled.

• CSV files are generated for 1099 NEC and 1099 MISC using existing 1099 magnetic media creation logic.

• Multiple CSV files are automatically created when record limits are exceeded.

 

 

Print 1099 Edit Report (APR1099E)

The Print 1099 Edit Report has been updated to include recipient fields required for 1099 CSV creation. The following fields now display on the report:

• Recipient TIN Type

• Recipient First Name

• Recipient Last Name

These additions help identify missing recipient information that could prevent successful CSV file generation.

 

 

This enhancement requires the following:

• cp82_dbc_820_12046_001.zip
  

• cp82_app1099c_003.zip

This enhancement enables Costpoint to apply sequenced withholding for 401(k) and 403(b) deductions so that standard contributions are fully applied before any Roth catch-up contributions are applied. This helps you ensure that employees receive the full intended tax benefits of standard retirement contributions and aligns payroll processing more closely with regulatory guidance under SECURE 2.0 Act.

You can enable this new functionality on the Configure Payroll Settings screen. When enabled, Costpoint suppresses catch-up deductions until the standard contribution limit is reached, then automatically routes excess amounts to designated Roth catch-up deductions within the same payroll. This feature applies to 401(k) and 403(b) plans.

Note: W-2 changes are not part of this Costpoint release and will follow in a future release.

 

Configure Payroll Settings (PRMPRSET)

Use this screen to enable and control catch-up deduction sequencing. The screen adds the Enable catch-up deduction sequencing checkbox to the Payroll Computation/Reporting Options group box. When you select the Enable catch-up deduction sequencing checkbox, Costpoint sequences 401(k) and 403(b) deductions so that standard contributions are applied before catch-up contributions.

Field	Description
Enable catch-up deduction sequencing	When selected, 401(k) deductions will automatically transition to Roth catch-up when the statutory limit is reached. This is unchecked by default.

 

Manage Deductions (PRMDED)

You can now define deduction types that support catch-up deduction sequencing. This release updates the Deduction Type field to support new catch-up deduction type codes for both standard and Roth plans. You can now assign deduction types that represent standard and Roth catch-up configurations for 401(k), 403(b), and 457(b) plans.

Deduction Type	Description
401C	401k StdCatchUp Age 50-59,64+
401C+	401k SupCatchUp Age 60-63
401RC	Roth401k StdCatchUp 50-59 64+
401RC+	Roth401k SupCatchUp Age 60-63
403C	403b StdCatchUp Age 50-59,64+
403C+	403b SupCatchUp Age 60-63
403RC	Roth 403b StdCatchUp 50-59 64+
403RC+	Roth 403b SupCatchUp Age 60-63
457C	457b StdCatchUp Age 50-59,64+
457C+	457b SupCatchUp Age 60-63
457RC	Roth 457b StdCatchUp 50-59 64+
457RC+	Roth 457b SupCatchUp Age 60-63

 

Manage Retirement Elections (AOMESSRB)

The application will prevent assigning more than one catch-up deduction for the same plan type. An error will display when multiple catch-up deductions exist for a single 401(k), 403(b), or 457(b) plan type.

A warning will display when a catch-up deduction is assigned without a corresponding base plan deduction.

 

Manage Employee Deductions (PRMEDED)

The application will prevent assigning more than one catch-up deduction for the same plan type. An error will display when multiple catch-up deductions exist for a single 401(k), 403(b), or 457(b) plan type.

A warning will display when a catch-up deduction is assigned without a corresponding base plan deduction.

 

Manage Employee Information (LDMEINFO)

On the Deductions subtask of the screen, the application will prevent assigning more than one catch-up deduction for the same plan type. An error will display when multiple catch-up deductions exist for a single 401(k), 403(b), or 457(b) plan type.

A warning will display when a catch-up deduction is assigned without a corresponding base plan deduction.

 

Compute Payroll (PRPCPR)

The Compute Payroll process will now automatically transition 401(k) and 403(b) deductions to Roth catch-up deductions when you select the Enable catch-up deduction sequencing checkbox on the Configure Payroll Settings screen.

Catch-up deductions remain configured at the employee level but are not calculated until you reach the 401(k) deferral limit on the Manage Federal Taxes (PRMFTI) screen. During the payroll in which the limit is exceeded, only the residual (excess amount) is applied to the catch-up deduction. In subsequent payrolls, the catch-up deduction is calculated based on its configured amount or percentage. This feature does not affect existing deduction calculation logic or limit enforcement, including the group limit.

Costpoint now allows you to report Fair Labor Standards Act (FLSA) overtime information for One Big Beautiful Bill Act (OBBBA) compliance using the Print Timesheet History Report screen. This enhancement allows you to identify employees’ FLSA overtime hours and premium amounts directly from historical timesheet data, which is useful if your organization does not use Costpoint Payroll.

You can access this functionality if you have appropriate permissions for the Labor module and labor reporting screens. The feature uses existing posted timesheet data and does not require additional setup beyond configuring applicable pay types. It is available to both Payroll and non-Payroll clients, with removed license restrictions for certain pay type settings. The report uses only historical timesheets and excludes recast overtime transactions, so you may need additional analysis for specific state rules.

 

Print Timesheet History Report (LDRTHFR)

This enhancement updates the Print Timesheet History Report application to include new OBBBA-specific report options. To support this feature, the following updates were applied:

• You can now select the type of report that you want to print from the Report Type options:

Field	Description
Report Type	Select the type of report to print. Valid options are: Timesheet History Summary FLSA Overtime for OBBBA Detail FLSA Overtime for OBBBA

• The report now filters data to include only pay types with FLSA overtime (OBBBA) enabled.

• The summary report displays overtime hours and overtime premium amounts aggregated by employee.

• The detail report displays overtime hours and overtime premium amounts per employee, pay type, and timesheet.

• The report excludes recast overtime lines and includes only original posted timesheet records. You can include employees with overtime activity only, based on FLSA-qualified pay types.

• You can select the Include Part-Time Employees and Include Temporary Employees checkboxes when running OBBBA report types. Costpoint disables Show Pay Type Totals when you select either OBBBA report option.

 

Manage Pay Types (LDMPAYTP)

This enhancement updates the Manage Pay Types application to support OBBBA overtime reporting for all users. This means that non-Payroll clients can now configure overtime-related pay types. You can now select the new FLSA overtime (OBBBA) and Exclude hours from overtime recalculation (OBBBA) checkboxes regardless of Payroll license.

Field	Description
Overtime	Select this checkbox if this pay type is an overtime or premium-type of pay type.
Exclude hours from overtime recalculation	When licensed for Payroll, select this checkbox if hours associated with this pay type should be excluded when calculating the FLSA overtime hours for the employees’ W-2 as part of the One Big Beautiful Bill Act (OBBBA) changes in 2025. The Recompute Taxable Wages screen uses this checkbox to determine if the pay type’s hours from the timesheet should be included when calculating FLSA overtime hours for states that calculate overtime hours on a daily basis. It is not used if a state calculates overtime based on 40 hours per week. This checkbox is information only if your company does not have a Payroll license.
FLSA overtime (OBBBA)	Select this checkbox if any overtime hours associated with this pay type are based on a 40-hour work week. If your company has a Payroll license, this checkbox is used by Recompute Taxable Wages when calculating FLSA overtime premium amounts for employees’ W-2’s as part of the One Big Beautiful Bill Act (OBBBA) changes in 2025. The checkbox is also used by the Timesheet History report to report on FLSA overtime hours and overtime premium amounts.

 

This enhancement requires the following:

• cp82_bundle_CYE2025_002.zip

• cp82_dbc_820_12081_001.zip

• cp82_ldmpaytp_002.zip

• cp82_ldrthfr_001.zip

• DeltekCostpointMaintenanceRelease_2025.2.0.5023.exe

Arkansas released the updated Withholding Tax Employer’s Instructions effective January 1, 2026. The update issued on May 29, 2026 supersedes previously issued 2026 withholding guidance. The changes include:

• The tax brackets have been adjusted with the highest tax rate decreased from 3.9% to 3.7%, and the bottom two rows were removed. The last row starts at $97,601 of annual income instead of $97,801.

• The supplemental tax rate decreased from 3.9% to 3.7%.

Attention: For more information, see:

• Formula: https://www.dfa.arkansas.gov/wp-content/uploads/Withholding-Tax-Formula.pdf

• Instructions: https://www.dfa.arkansas.gov/wp-content/uploads/Withholding-Tax-Instructions-for-Employers.pdf

To support the state tax updates, this release adds records on the following screens:

• Manage State Standard Deductions (PRMSSD)

• Manage State Tax Tables (PRMSTT)

• Manage State Tax Withholding Adjustments (PRMSTAC)

• Manage State Taxes (PRMSTI)

This enhancement requires patch dbc_820_12155.

Costpoint updates the California Pay Data Report output generated through the Print EEO-1 Report screen so that you can meet the 2025 filing requirements by reporting employee groups using the additional attributes now required for the reporting year.

The changes to the Print EEO-1 Report are:

• The file layout was updated and new data fields required for 2025 reporting were added.

• The calculation of existing data fields was updated to factor exemption status and employment type into the employee group.

• The selection criteria was updated so employees with gender other than male, female, and non-binary are included in data selection to support warning-report output.

• All employee types (Part Time, Regular, and Temporary) are now included in the report outputs.

• A legend was added to the report layout to clarify report labels and values.

• In the California Pay Data Warning Report, the existing warning message regarding unknown race/ethnicity was removed. New warning messages were added in cases when an employee was excluded from the report because race/ethnicity or gender cannot be identified.

This enhancement requires:

• cp82_hareeo1_005.zip

• deltekcostpointmaintenancerelease_8.2.12.5013.exe

Georgia revised the Employer’s Tax Guide in June 2026. The changes effective January 1, 2026 are:

• The tax rate was reduced from 5.19% to 4.99%.

• The standard deductions were increased from $24,000 to $30,000 annually for the married filing jointly status and from $12,000 to $15,000 annually for other statuses.

• The dependent allowance increased from $4,000 to $5,000 annually.

• The supplemental tax rate decreased from 5.19% to 4.99%.

Attention: For more information, see: https://dor.georgia.gov/employers-tax-guide.

To support the state tax updates, this release adds records on the following screens:

• Manage State Standard Deductions (PRMSSD)

• Manage State Tax Tables (PRMSTT)

• Manage State Tax Withholding Adjustments (PRMSTAC)

• Manage State Taxes (PRMSTI)

This enhancement requires patch dbc_820_12162.

This enhancement updates Michigan SUTA electronic filing to comply with Version 2 of the MiUI EFW2 file format. The update ensures that employee-level reporting aligns with the revised Employee Detail Record (RS) requirements, particularly for adjustment reason handling and out-of-state wages formatting.

Compared to version 1, version 2 introduces three related updates:

• Reason or Adjustment Code (RS 344-345) defaulting logic: Blank Reason or Adjustment Codes now default to:

• 00 for original submissions

• 01 for adjustment submissions replacing the v1 behavior where blank adjustment records defaulted to 10 (Out of State Wages)

• Explicit definition of Reason or Adjustment Code 00: The description of code 00 has been updated to explicitly state that it represents an original submission that does not include out-of-state wages.

• Out of State Wages (RS 348-358) field formatting: If there are no out-of-state wages to report, the Out of State Wages field must contain exactly eleven (11) blank spaces.

Attention: For more information, see: MiUi EFW2 File Format Employer Reference Document.

 

Create Quarterly SUTA Tax File (PRPSMM)

Use this screen to generate the quarterly SUTA tax file for Michigan with the updated EFW2 Version 2 format.

• The screen sets the File Layout to EFW2 and disables the field to prevent changes.

• The Adjustment Reason Code field in the file was updated so that it will use 10 and not 00 if there are out-of-state wages.

• When no out-of-state wages exist, the application will fill Out of State Wages field with exactly 11 blank spaces.

• Informational messages display during processing when:

• There are no QTD out-of-state wages but Adjustment Reason Code is 10.

• There are QTD out-of-state wages but Adjustment Reason Code is not 10.

 

Manage SUTA Quarterly Reporting Data (PRMQRD)

Costpoint uses the Adjustment Reason value from this screen when determining the correct RS 344-345 output for Michigan filings. The Adjustment Reason Description of 00 was updated from “Original submission” to “Original submission of a record that does not include out of state wages.”

 

This enhancement requires patch dbc_820_12151.

Texas is transitioning to the TxUS unemployment insurance system, and Costpoint now supports generating the Texas wage report file using the new TxUS ICESA specifications. This enhancement helps you prepare Texas quarterly SUTA electronic filings that align with the updated TxUS layout while still supporting the existing ICESA format during the transition.

For Texas processing, Costpoint adds the TxUS ICESA file layout option and keeps ICESA as the default so you can continue filing during the transition period.

Note: The Texas Workforce Commission specifications are subject to change, and clients may still use the old format for Q1 2026 reporting depending on TxUS rollout timing.

 

Manage SUTA Tax File Data (PRMSMM)

On the Manage SUTA Tax File Data screen, you maintain Texas SUTA setup values used to generate ICESA output files, including transmitter contact details. When you select TX (Texas) as the SUTA State, the screen enables the E-mail field so you can provide the submitter email address used by the TxUS ICESA output file.

 

Create Quarterly SUTA Tax File (PRPSMM)

On this screen, you generate the quarterly SUTA tax file for Texas and choose the file layout used for ICESA output. The following are the updates for Texas processing:

• When SUTA State is TX, the screen enables File Layout field and adds the TxUS ICESA option so you can select either the existing ICESA layout or the TxUS ICESA layout for Texas filing. The File Layout is set to ICESA by default. Cumulative out-of-state taxable wages functionality was added.

• When you set File Layout to TxUS ICESA, Costpoint generates the quarterly SUTA tax file using the TxUS ICESA specifications for Texas.

• Costpoint enables the Amended checkbox so you can generate an amendment file for Texas.

 

Manage SUTA Quarterly Reporting Data (PRMQRD)

The Manage SUTA Quarterly Reporting Data screen provides the following updates:

• Texas adjustment reason codes were added to the S_SUTA_ADJ_RSN_CD table so you can select valid Texas amendment reasons for TxUS ICESA filing.

• The screen now validates that when Adjustment Reason Code is 12, you must specify Incorrect SSN Reported.

• The screen limits the Adjustment Explanation field to District of Columbia, Maryland, North Carolina, and South Carolina. The screen validates and enables the Adjustment Explanation field only when Adjustment SUTA State is DC, MD, NC, or SC and Adjustment Reason Code is 10.

Utah updated the Withholding Tax Guide, which introduced the following changes for payroll periods beginning on or after June 1, 2026:

• The tax rate decreased from 4.5% to 4.45%.

• The base allowance used in the formulas increased to $485 for single employees or $970 for married employees, up from $450 or $900.

• The amounts subtracted from wages in the formulas increased to $9,348 for single employees or $18,696 for married employees, up from $9,107 or $18,213.

Attention: For more information refer to:

• https://tax.utah.gov/forms-pubs/

• http://www.irs.gov/pub/irs-pdf/fw4.pdf

To support state requirements, this release adds records to the following screens:

• Manage State Standard Deductions (PRMSSD)

• Manage State Tax Tables (PRMSTT)

• Manage State Tax Withholding Adjustments (PRMSTAC)

This enhancement updates Vermont Quarterly SUTA electronic filing to align with the state’s current ICESA file layout requirements for the modernized UI system. It updates Vermont-specific processing on the Create Quarterly SUTA Tax File and Manage SUTA Tax File Data screens so you can generate files that match the revised state format and reporting rules. The update also changes how Vermont employer account numbers, total hours worked, business status indicators, and other file elements are reported.

For Vermont, some controls are now unavailable because the state no longer requires or accepts those values in the same way. This enhancement applies only when the filing state is Vermont.

 

Manage SUTA Tax File Data (PRMSMM)

The Manage SUTA Tax File Data screen now applies Vermont-specific behavior for fields that are no longer used in the updated Vermont ICESA file layout. When you select VT (Vermont) as the filing state, the screen:

• Disables the Media Transmitter/Auth. No./Suffix Code/EFT controls.

• No longer validates Media Transmitter/Auth. No./Suffix Code/EFT as numeric.

• No longer reports the Media Transmitter/Auth. No./Suffix Code/EFT value in the Vermont Code A Authorization Code field.

 

Create Quarterly SUTA Tax File (PRPSMM)

The Create Quarterly SUTA Tax File screen now includes Vermont-specific updates that support the revised ICESA file layout and reporting requirements. When you select VT (Vermont) as the filing state, the screen:

• Sets the default value of the Computer Manufacturer field to DELTEK.

• Enables the Amended checkbox.

• Updates the Business Status (Vermont) drop-down list under Other Filing Info with Vermont-specific filing options.

• Uses the latest Vermont file layout which includes the following updates:

• Code A 141-153 Original or Amended: Added field and source is the Amended checkbox

• Code A 208-213 Authorization Code: No longer report the Media Transmitter/Auth. No./Suffix Code/EFT fields

• Code A 243-250 File Creation Date: Renamed field name

• Code E 173-179 VT Employer Account Number: Must be right -justified and zero-filled

• Code S 155-161 VT Employer Account Number: Must be right -justified and zero-filled

• Code S 235-238 Total Hours Worked: Now applies to all employees (previously hourly employees only)

• Code S 239-244 Filler: No longer report the hourly wage, must be zero-filled

• Code T 2-8 Total Number of Employees: Corrected data type to numeric

• Code C 2-18 VT Employer Account Number: Must be right-justified and zero-filled

• Code C 243-250 Unemployment Contribution Amount Due: Renamed field name

• Code C 112 Employer no longer has employees/Discontinued operations in Vermont: Renamed field name, updated source

• Code C 113 Out of Business: Renamed field name, updated source

• Code C 114 Employer change in address or name: Renamed field name, updated source

• Code C 115 Employer change in payroll service provider: Renamed field name, updated source

West Virginia reduces personal income tax rates for the 2026 tax year effective January 1, 2026, retroactively. The percentage method withholding tables have been updated, reducing the tax rates from a range of 2.22% - 4.82% to 2.11% - 4.58%.

To support the state tax updates, this release adds records on the following screens:

• Manage State Standard Deductions (PRMSSD)

• Manage State Tax Tables (PRMSTT)

• Manage State Tax Withholding Adjustments (PRMSTAC)

• Manage State Taxes (PRMSTI)

Attention: For more information, see:

• https://tax.wv.gov/Individuals/Pages/PersonalIncomeTaxReductionBill.aspx

• https://tax.wv.gov/Documents/Withholding/it100.2a.pdf

Note: The Opt-In capability is available to Costpoint Cloud Customers only.

As an administrator, use the new Opt-In capability to enable designated new features for your Costpoint users. Opt-In features are optional during a specific timeframe. In a future Costpoint release, the features will be enabled automatically for all users.

This enhancement supports testing by users in your company. When you enable an Opt-In feature in a sandbox database, you give your users the opportunity to experience how that feature will potentially impact their workflow, data, and application use. You control the timing of this testing, which can take place before you enable the feature in a production database and before the feature is automatically enabled for all users in a release.

During the opt-in timeframe, you can also disable most Opt-In features if necessary. Once the opt-in timeframe is complete, the features are automatically enabled in the subsequent Costpoint release. While some Opt-In features may have additional settings or security to enable, most will become standard in the product.

Enable and disable the Opt-In features during the opt-in timeframe in the Manage Opt-In Features (SYMFEATURE) application in Costpoint.

The following Costpoint 2026.3 features include the option to opt-in:

• Assessment Ratings

• CPARS Creation Agent

• Proposal Generation Agent for Government Solicitations

• Remove File Imaging from Expense Settings

• Expanded Leave Type Support

Attention: See Costpoint Opt-In Features for more information.

Throughout the Costpoint content, the Opt-In feature topics will be identified with the following label: (Opt-In Available).

In addition, the opt-in feature topics will include the following statement:

Note: For Costpoint Cloud, you can choose to opt in to this feature for the Costpoint 2026.3 release. The ability to opt in is temporary and will be removed when the feature becomes automatically enabled for all users as part of a future Costpoint release. For more information, see the Opt-In Features section of these release notes.

For more information about Costpoint’s Opt-In capability, see Knowledge Base article #115359 in the Deltek Customer Care Knowledge Base.

Command Center’s Agentic Financial Close tab now provides a centralized view of project product and customer product bills that Dela flagged for manual review. Click the flagged count on the Review Customer Product Bills and Review Project Product Bills summary cards to open the Exceptions report on a new tab, where you can view detailed records requiring your attention. From this report, you can also drill through to the Manage Customer Product Bills and Manage Project Product Bills screens. 

Note: To enable Dela to automatically review bills, configure the settings in the Dela Defaults group box on the Configure Billing Settings screen. Assessment results are displayed on the Dela tab of the relevant Costpoint screens. 

In addition, the new Financial Anomaly Analysis summary card highlights the income statement and balance sheet anomalies detected by Dela. You can click the Financial Statement Line field on the drill report to open the Financial Anomaly Analysis application. 

Note: To learn more about Costpoint’s financial anomaly detection process, refer to the Run Financial Anomaly Detection online help topic. 

The Buyer Command Center is now available and includes a Purchase Orders (PO) dashboard tab that consolidates unpaid POs into a single, status-based view. You can review and prioritize POs across the following key stages:  

• Pending Approval 

• Pending Receipt 

• Pending Inspection 

• Awaiting Invoice 

• Pending Voucher Approval 

• Awaiting Payment 

Two-way match POs are excluded from Pending Receipt and Pending Inspection statuses to ensure accurate classification. The dashboard also excludes Void and Closed POs and displays only POs assigned to you for a more focused review.  

In addition, the table is sorted by POs with the highest number of Overdue Lines to support timely follow-up. Click the PO ID field to open the Manage Purchase Orders screen. You can also open a drill report to view PO line details. 

Note: To access the Buyer Command Center, you must be assigned to the CC__BUYER user group using the Manage Users application. 

The following updates were made to the grid interface across all Command Center tabs to improve usability:

• Saved Panel and Column Widths: When you adjust the panel width or resize a grid column, your changes are now saved to local storage and retained across browser sessions. You can also set a default panel width to ensure a consistent starting layout. 

• Double-Layer Column Filtering: When you filter data in any Command Center grid column, you can now apply two simultaneous filter conditions to narrow results more precisely. This reduces the number of steps needed to isolate specific data ranges within a grid. 

The Command Center now supports cascading queries, enabling you to open Costpoint applications with both header-level and refined detail-level filters applied. For example, when you open the Closing Plan application from the Closing Manager dashboard tab, Costpoint retrieves the active closing plan and filters the Tasks subtask by Assigned User and Status. This improves navigation from Command Center to targeted data sets within Costpoint screens that require multi-level query context. 

All existing Command Center user groups now automatically include access to the Command Center module, removing the need to assign module rights separately. This update applies to the following user groups: 

User Group ID	User Group Name
CC__ACCOUNTANT	Command Center Accountant
CC__AI_CLOSE_ANALYST	Command Center AI Close Analyst
CC__BUYERS	Command Center Buyer
CC__PJ_PLAN_ANALYST	Command Center Project Plan Analyst
CC__PROJ_ANALYST	Command Center Project Analyst
CC__TE_MGR	Command Center T&E Manager

Costpoint now has the capability to automatically post approved journal entries. This enhancement streamlines journal entry processing by reducing manual posting steps and provides visibility into unsuccessful posting attempts and results across journal entry maintenance, approval, inquiry, and posting applications.

 

 

Configure General Ledger Settings (GLMSETNG)

The Configure General Ledger Settings screen now includes the Allow Auto Posting checkbox on the Approval Settings subtask. Use this checkbox to enable automatic posting for each journal entry type. It is available only when Approval Required is selected.

A new Batch Job Email Notification subtask has also been added, which allows you to configure email notifications for unsuccessful General Ledger batch jobs. This subtask includes the following fields:

• Send Unsuccessful Emails: Select this checkbox to send email notifications for unsuccessful batch jobs.

• Unsuccessful Email List: Use this field to enter the email addresses of notification recipients. You may separate email addresses using a semicolon (;) or enter each email address in a new line.

 

 

Manage Journal Entries (GLMJE) and Approve Journal Entries (GLMJEA)

The Manage Journal Entries and Approve Journal Entries screens now automatically submit approved journal entries when the auto posting feature is enabled for the journal entry type. 

When you approve and save a journal entry, Costpoint displays a message confirming that the approved  journal entry has been submitted for posting. In the background, Costpoint runs the Post Journal Entry process and passes the journal entry’s fiscal year, period, subperiod, and journal entry number, with Allow Out of Balance Posting cleared by default. 

 

 

Post Journal Entries (GLPJE) 

The Post Journal Entries screen now identifies journal entries processed through auto posting by checking the JE_HDR_HS_AUTO_POST_LOG table. Journal entries posted automatically are excluded from the manual posting process.

 

 

View Journal Entries (GLQJEI) 

The View Journal Entries screen now includes a Journal Entries selection range that allows you to filter results by journal entry number. You can choose to display all journal entries, a single journal entry, or a range of journal entries.

 

 

Print Posted Journal Entries (GLRPOST)

Costpoint now provides the Print Posted Journal Entries screen, which allows you to print a report for journal entries that have been posted. You can access this screen in General Ledger » Journal Entry Processing » Approvals and Posting.

The printed output uses the same format as the report generated by the Post Journal Entries screen.

Use this screen to print or reprint posted journal entries without having to rerun the Post Journal Entries screen.

You can filter the records to be included in the report by: 

• Accounting Period

• Journal Type

• Journal Entries

• Users

• Approver User

Costpoint introduces the ability to save Accounts Payable vouchers as drafts. This functionality allows you to distinguish vouchers that are still being worked on from those that are finalized and ready for approval or posting. 

Vouchers saved as drafts remain editable, while submitted vouchers can trigger Dela’s automated approval workflow or be processed through manual approval. This functionality establishes the foundation for future automated posting capabilities.

 

 

Configure Accounts Payable Voucher Settings (APMSETVR)

A new checkbox, Create New A/P Vouchers in Draft Status, is now available on the Configure Accounts Payable Voucher Settings screen.

When you select this checkbox, newly entered Accounts Payable vouchers are created with an Entry Status of Draft, and the voucher submission workflow is enabled. To prevent unintended approval of draft vouchers, Costpoint disables the Approved checkbox in Manage Accounts Payable Vouchers.

If the draft feature is disabled, newly entered vouchers are created as Submitted and are routed through your configured approval process, if applicable.

 

 

Manage Accounts Payable Vouchers (APMVCHR)

The Manage Accounts Payable Vouchers screen now supports the entry and maintenance of draft vouchers and indicates whether a voucher has been submitted. 

When the draft feature is enabled, the following screen elements display: 

• Submit: Use this button to submit a draft voucher. When you click Submit, Costpoint updates the Entry Status of the voucher to Submitted, automatically saves the record, and disables all screen fields, except Entry Status.

For submitted vouchers that have not been posted, the Submit button changes to Unsubmit. Click Unsubmit to revert the voucher as a draft, allowing you to make additional changes before resubmitting the voucher.

• Entry Status: Use this drop-down list to specify whether a voucher is a draft or submitted. If you update the entry status, you must manually save the record. 

When the draft functionality is enabled, vouchers that you enter or create from other Costpoint screens are created as drafts and remain editable until submitted.

If Require Approvals is selected in Configure Accounts Payable Voucher Settings and the voucher amount exceeds the value entered in Approval Required Above:

• If Allow Dela Approval is selected, submitting the voucher, either by modifying the Entry Status or clicking Submit, triggers Dela’s automated voucher assessment process.

• Otherwise, you must manually review and approve submitted vouchers in Approve Vouchers.

 

 

Approve Vouchers (APMVCHRA)

The Approve Vouchers screen has been enhanced to exclude draft Accounts Payable vouchers from the approval process when the draft feature is enabled.

 

 

Reverse Posted Vouchers (APPREVVR)

When you reverse posted vouchers, Costpoint sets the Entry Status of the reversed vouchers to Submitted, maintaining the existing behavior that reversed vouchers cannot be modified.  

Approval details are populated based on the setting of the Approve Vouchers checkbox at the time you run the reversal process. 

The following table describes how the Entry Status and approval details are populated for reversed vouchers:

Approve Vouchers	Entry Status	Approval Details (Approved, Approval Date, Approver)
Selected	Submitted	Populated per current approval logic
Cleared	Submitted (Hidden)	Blank

  

 

Print Voucher Edit Report (APRVCHR)

The Print Voucher Edit Report screen now includes an Entry Status group box containing the Draft and Submitted checkboxes.

Use these checkboxes to filter vouchers to be included in the report by Entry Status. The checkboxes are selected and disabled by default. They become enabled when you select Unposted Only in the Posting Status group box.

The selected Entry Status options also display in the report output.

 

 

Print Pending Vouchers Report (APRPEND) 

When you print a Pending Vouchers report, only submitted vouchers are included in the output.

 

View Voucher History Inquiry (APQVCHRH)

The View Voucher History Inquiry screen now includes the Entry Status field in the Voucher History Table window. This field displays only when you select Include Unposted Vouchers. 

For unposted vouchers, the field displays Draft or Submitted. For posted vouchers, this field is blank.

 

 

Import Accounts Payable Vouchers (AOPUTLAP) and Import Accounts Payable Multicurrency Vouchers (AOPUTLAM) 

When you import vouchers using these screens, Costpoint sets the Entry Status for each voucher after the import process completes. If the draft feature is enabled, imported vouchers are created with an Entry Status of Draft. If the draft feature is disabled, imported vouchers are created with a Submitted status in the database, but the Entry Status field does not display in Manage Accounts Payable Vouchers.

 

 

Create Recurring Accounts Payable Vouchers (APPRECVR) 

When you create recurring Accounts Payable vouchers, Costpoint assigns a default Entry Status for the new vouchers. If the draft feature is enabled, vouchers are created with an Entry Status of Draft. If the draft feature is disabled, vouchers are created with a Submitted status in the database, and Costpoint assigns approval details based on the current approval setup, including manual approval and Dela approval.  

However, the Entry Status field does not display in Manage Accounts Payable Vouchers when the draft feature is disabled.

 

 

Import TE Expenses/Advances (AOPUTLTE) 

When you import records using this screen, Costpoint sets the Entry Status and approval details for vouchers created by the import based on the Mark Vouchers as Approved checkbox selection and whether the draft feature and approval options are enabled in Configure Accounts Payable Voucher Settings.

The following table describes how the voucher Entry Status is populated when the voucher is created:

Create New A/P Vouchers in Draft Status (APMVCHR)	Mark Vouchers as Approved	Entry Status (APMVCHR)
Selected	Cleared	Draft
Selected	Selected	Submitted
Cleared	Select or Cleared	Submitted (Hidden)

 

The following table demonstrates how voucher approval details are populated when vouchers created from the import have an Entry Status of Submitted.

Require Approvals (APMSETVR)	Mark Vouchers as Approved	Above Approval Threshold (APMSETVR)	Approved Flag (APMVCHR)	Approval Date, Approver (APMVCHR)
Cleared	Cleared	N/A	Selected	Populated
Selected	Cleared	Yes	Cleared	Blank
Selected	Cleared	No	Selected	Populated
Selected	Selected	N/A	Selected	Populated

 

 

Create Accounts Payable Vouchers (PRPAPVCH) and Post IWO Journal (IWPPOST)

When you run the Create Accounts Payable Voucher screen in the People domain or the Post IWO Journal screen in the Projects domain, Costpoint sets a default Entry Status for the vouchers created from these screens.

If the draft feature is enabled, new vouchers are created as drafts. Otherwise, their status defaults to Submitted.

Costpoint introduces the ability to save PO vouchers as drafts. This functionality allows you to distinguish vouchers that are still being worked on from those that are finalized and ready for approval or posting. 

PO vouchers saved as drafts remain editable, while submitted vouchers can trigger Dela’s automated approval capability or be processed through manual approval.

 

 

Configure Purchase Order Voucher Settings (POMAPSET)

A new checkbox, Create New PO Vouchers in Draft Status, is now available on the Configure Purchase Order Voucher Settings screen.

When you select this checkbox, newly created PO vouchers are created with a Status of Draft, and the voucher submission workflow is enabled. To prevent unintended approval of draft vouchers, Costpoint disables the Approved checkbox in Manage Purchase Order Vouchers.

If you leave the Create New PO Vouchers in Draft Status checkbox cleared, newly created PO vouchers are assigned a Status of Submitted and are routed directly through your configured approval process, if applicable.

 

 

Manage Purchase Order Vouchers (POMPOVCH)

The Manage Purchase Order Vouchers screen now supports the entry and maintenance of draft PO vouchers and indicates whether a PO voucher has been submitted.

To support this functionality, the following screen elements are available when Create New PO Vouchers in Draft Status is selected in Configure Purchase Order Voucher Settings:

• Submit: Use this button to submit a draft PO voucher. When you click Submit, Costpoint updates the Status of the voucher to Submitted and enables the Approved checkbox.

• Unsubmit: For submitted PO vouchers that have not been posted, Submit changes to Unsubmit. Click Unsubmit to revert the Status to Draft, allowing you to make additional changes before resubmitting the voucher.

• Status: Use this drop-down list to specify if a voucher is a Draft or is Submitted. The value of this drop-down list also automatically changes when you click the Submit or Unsubmit button for a voucher.

When the draft functionality is enabled, PO vouchers that you enter or that are created from other Costpoint screens will default to Draft status. Draft PO vouchers remain editable until they are submitted.

If the draft functionality is disabled, the Status field and Submit/Unsubmit buttons are hidden, and PO vouchers default to Submitted status in the database.

 

 

Approve Vouchers (APMVCHRA)

The Approve Vouchers screen has been enhanced to exclude PO vouchers with a Status of Draft.

Only PO vouchers with a Submitted status are available for approval.

 

 

PO Voucher Status Assignment from Approved Invoices

When PO vouchers are created from invoices approved through the following screens, Costpoint sets the voucher Status based on the Create New PO Vouchers in Draft Status setting in Configure Purchase Order Voucher Settings:

• Manage Invoices (SPMINVC)

• Approve PO Invoices (POMAINVC) 

• Approve Subcontractor Invoices (SMMAINVC)

• Manage Subcontractor Invoices (SMMMINVC)

• Create Subcontractor Invoices (SMPINVC)

If the draft feature is enabled, newly created PO vouchers will default to Draft status.

Otherwise, newly created PO vouchers default to Submitted status and can proceed directly to the approval process, either through Dela’s automated approval workflow or through manual approval, when applicable.

 

 

PO Voucher Status Assignment from Creation Screens

When you import or create PO vouchers using the following screens, Costpoint sets the Status for each voucher based on whether Create New PO Vouchers in Draft Status is selected in Configure Purchase Order Voucher Settings:

• Import Purchase Order Vouchers (AOPPOVCH)

• Recompute and Print Discrepancies (POPDISCR)

• Create Debit Memos (POPDM)

• Create PO Vouchers from POs/Receipts (POPPOVCH) 

• Create Subcontract Purchase Order Vouchers (POPSCVCH)

If the draft feature is enabled, newly created PO vouchers default to Draft status. Otherwise, the vouchers default to Submitted status in the database.

This feature enhances bank reconciliation processing by adding fiscal year, period, and subperiod support across bank statement entry, bank transaction acceptance, inquiries, and bank reconciliation reports. You can associate bank statements and cleared bank transactions with specific accounting periods and view reconciliation results and reports by either statement date range or accounting period.

 

 

Manage Bank Statement Information (GLMSTMT)

You can now assign fiscal year, period, and subperiod values to bank statements using new fields added to the Bank Statement Info Detail table window:

• Fiscal Year

• Period

• Subperiod (Costpoint Advanced only)

When you enter a Bank Statement Ending Date, Costpoint automatically defaults the fiscal year, period, and subperiod based on the accounting period that includes the ending date. When you upload a bank statement, Costpoint uses the ending date from the upload to as default values for these fields.

You can modify the fiscal year, period, and subperiod, and enter values regardless of whether the Bank Statement Ending Date falls within the selected combination. 

This update does not modify existing records. If the Fiscal Year, Period, and Subperiod fields were not previously populated, you must manually enter the values. Manual entry is required only if you already enabled the Enhanced Bank Reconciliation feature in Costpoint 2025.3. Otherwise, the fields are automatically populated. 

 

 

Accept Bank Transactions (New) (GLMACPTN)

Fiscal year, period, and subperiod information have been added to the Accept Bank Transactions (New) screen.

In the GL Transactions table window, the following fields are now available:

• Fiscal Year Cleared

• Period Cleared

• Subperiod Cleared (Costpoint Advanced only)

In the Bank Statement table window, the following fields are now available:

• Bank Statement Ending Date

• Bank Statement Fiscal Year

• Bank Statement Period

• Bank Statement Subperiod (Costpoint Advanced only)

Fiscal year, period, and subperiod values default from the Date Cleared based on the accounting period in which the date falls. These fields are required and can be edited to populate missing cleared period information. The new fields are available for query selection.

 

 

Transfer Plaid Bank Transactions (CMPPLDDAT)

Plaid-imported bank transactions now include accounting period information.

When a new bank statement record is created from a Plaid import, the fiscal year, period, and subperiod for the transaction are populated based on the bank statement ending date.

The populated values are stored in both the BANK_ACCT_END_BAL and BANK_ACCT_STMT_DTL tables.

 

 

Accounting Period Selection Option for Reports

You now have a new option for filtering records included in bank statement and bank transaction inquiry and reports.

A Date Type group box has been added to multiple inquiry and reporting screens, allowing you to specify whether records are retrieved by Accounting Period or Statement Date Range. 

When you select Accounting Period, use the Fiscal Year, Period, and Subperiod (Costpoint Advanced only) fields, added in the Selection Ranges group box, to specify the accounting period to be used to retrieve inquiry or report data. Report headers also reflect the statement end date and the selected fiscal year, period, and subperiod.

This enhancement has been applied to the following screens:

• Print Bank Reconciliation Detail Reports (GLRBKREC)

• Print Bank Reconciliation Summary Report (GLRBKSUM)

• Print Bank Statement Report (GLRSTMT)

• View Bank Reconciliation Summary (GLQBKINQ)

 

 

Process Bank Transaction Acceptances (GLPBATCH)

The Fiscal Year, Period, and Subperiod (Costpoint Advanced only) fields have been restored in the Bank Acceptance Info group box and are required when you process bank transaction acceptances.

When you enter a Date, Costpoint automatically populates the fiscal year, period, and subperiod based on the accounting period in which the date falls. 

If you delete the values of these fields and run the process, an error displays.

 

 

Accept Bank Transactions (GLMACPT)

The old Accept Bank Transactions screen is no longer available. All bank transaction acceptances must be processed using Accept Bank Transactions (New) (GLMACPTN).

Costpoint now monitors and records changes to the status of accounting periods, subperiods, and the journal entry code statuses associated with them when you update and save or close periods in the following General Ledger screens: 

• Manage Accounting Periods

• Manage Subperiods (Costpoint Advanced only)

• Close Periods

Changes are written to audit log tables, along with the previous and new values, the user who made the change, and the timestamp.

 

 

Manage Accounting Periods (GLMPD)

When you save changes on this screen, Costpoint logs status change details in the following tables:

• ACCTING_PD_AUDIT_LOG

• Fiscal Year

• Period

• Old Status Code

• New Status Code

• Modified By

• Timestamp

• JNL_STATUS_AUDIT_LOG

• Company ID

• Fiscal Year

• Period

• Journal Code

• Old Open Flag

• New Open Flag

• Modified By

• Timestamp

Manage Subperiods (GLMSUBPD)

When you save changes on this screen, Costpoint logs status change details in the following tables:

• SUB_PD_AUDIT_LOG

• Fiscal Year

• Period

• Subperiod

• Old Status Code

• New Status Code

• Modified By

• Timestamp

• SUB_PD_JNL_STATUS_AUDIT_LOG

• Company ID

• Fiscal Year

• Period

• Subperiod

• Journal Code

• Old Open Flag

• New Open Flag

• Modified By

• Timestamp

Close Periods (GLPCLOSE)

When you successfully close a period, Costpoint logs the resulting status changes, depending on which accounting periods, subperiods, and journal entry code statuses are affected. It also sets the Status of all journal codes in that period to Closed for each affected company and adds audit log rows for each company/journal code combination. These changes are recorded in the following audit log tables: 

• ACCTING_PD_AUDIT_LOG

• JNL_STATUS_AUDIT_LOG

• SUB_PD_AUDIT_LOG

• SUB_PD_JNL_STATUS_AUDIT_LOG

This feature allows you to use Dela to create a purchase order from a requisition and complete the process without manually creating the PO on the Create Purchase Orders screen.

Note: This enhancement is coded under Opt-In Feature 2411396 which is dependent on Feature 2307499 in the Opt-In tool and both are automatically enabled in Costpoint 2026.4. 

 

 

Import Purchase Order Vouchers

This application now supports AI-assisted approval when imported PO vouchers meet the required conditions. If AI approval is enabled and the voucher qualifies, Costpoint can automatically approve the voucher or recommend it for approval. The voucher record also stores AI review details such as approval description, confidence level, date and time, and reason. 

Approve PO Invoices (POMAINVC)

You can now use AI-assisted auto-approval for PO vouchers created from supplier-approved and internally approved PO or subcontractor invoices.

This change also applies to the following screens:

 

• Manage Invoices (SPMINVC)

• Manage Subcontractor Invoices (SMMMINVC)

• Approve Subcontractor Invoices (SMMAINVC)

 

 

Recompute and Print Discrepancies (POPPOVCH)

These applications now use AI-assisted approval logic when creating PO vouchers. When the voucher qualifies, Costpoint can approve it automatically or recommend it for approval, depending on user setup. The applications also update the DELA result fields and support the same notification and manual review behavior used in other voucher approval flows.

This change also applies to the following screens:

 

• Create PO Vouchers from POs/Receipts (POPDISC)

• Create Subcontract Purchase Order Vouchers (POPSCVCH)

• Create Debit Memos (POPDM)

 

 

This change requires the following:

• cp82_cmnlib_pompolib_006.zip 

• cp82_poppovch_002.zip

• cp82_popscvch_004.zip

• cp82_dbc_820_11825_001.zip

• cp82_dbc_820_11841_001.zip

• cp82_dbc_820_11947_001.zip

• cp82_dbc_820_11854_001.zip

• deltekcostpointmaintenancerelease_8.2.8.5009.exe

Costpoint now supports creating purchase order vouchers using Intelligent Character Recognition (ICR) and Content Management Integration (CMI). This enhancement lets you attach and scan PO invoices and have Costpoint automatically extract invoice data and load it into a new PO voucher. This feature reduces manual data entry while ensuring that existing purchase order validations and matching rules continue to apply.

 

 

Manage Purchase Order Vouchers (POMPOVCH)

When the Manage Purchase Order Vouchers screen is set up with the CMI functionality, the Attach & Scan option becomes available in the Attach drop-down list. This option allows you to upload and scan a PO invoice and automatically populate PO voucher fields using extracted invoice data.

When you scan an invoice, Costpoint extracts the following information:

• Vendor name

• Invoice number

• Invoice date

• Invoice amount

• Purchase order number

• Payment terms

• Invoice due date

• Notes

• Line details, including quantity, unit price, and line amount

Costpoint displays the extracted invoice information in a Scan Results pop-up, where you can review and update the data before creating a voucher. Some extracted details, such as invoice line quantities and unit prices, are not displayed in the initial scan results view but are loaded onto the PO voucher when you apply the scan results.

When you click Apply in the Scan Results pop-up, Dela then processes the extracted invoice data and determines whether a PO voucher can be created.

Dela performs the following checks using existing Costpoint logic:

• Vendor validation

• Duplicate invoice check

• Purchase order status check

• Match rule evaluation:

• 2-way matching (PO and invoice)

• 3-way matching (PO, receipt, and invoice)

Note: If no packing slip and/or receipt ID is provided, Costpoint searches and loads all available receipts associated with the purchase order.

During matching, Dela evaluates:

• Quantity tolerance

• Price tolerance

• Receipt availability (for 3-way matching)

All other existing validations that apply when manually creating and saving a PO voucher also apply when vouchers are loaded through ICR.

 

Validation Messages

Costpoint may display the following messages if it encounters issues during processing:

Condition	Type	Message	Behavior
Purchase Order is already closed	Warning	This Purchase Order is already closed.	Costpoint still allows data to be populated on the screen. This is an existing validation and behavior.
Purchase Order ID or release does not exist in the PO_HDR table	Error	Purchase Order / Release does not exist.	Costpoint does not load any information on the screen.
Vendor name on the PO invoice does not match the vendor for the PO ID	Warning	Vendor Name on the PO Invoice does not match the Vendor Name associated to the Purchase Order.	Costpoint does not populate the vendor from the scanned invoice. Instead, it populates the vendor associated with the purchase order.
Receipt ID does not exist for the purchase order	Warning	Receipt ID is not linked to the specified Purchase Order.	Costpoint does not load the receipt ID or any receipt details on the screen.
Packing slip does not exist for the purchase order	Warning	Packing Slip is not linked to the specified Purchase Order.	Costpoint does not load the receipt ID or any receipt details on the screen.

 

Costpoint automatically creates the PO voucher and assigns a Draft or Submitted status based on whether the draft feature is enabled. If approval is required, Costpoint can trigger Dela’s automatic approval or route the voucher through the manual approval workflow.

 

This enhancement requires the following:

• cp82_cmnlib_mmorgseclib_001.zip

• cp82_cmnlib_pompolib_007.zip

• cp82_pompovch_011.zip 

Note: For Costpoint Cloud, you can choose to opt in to this feature for the Costpoint 2026.3 release. The ability to opt in is temporary and will be removed when the feature becomes automatically enabled for all users as part of a future Costpoint release. For more information, see the Opt-In Features section of these release notes.

Costpoint now allows you to exclude selected rating codes from performance score calculations. This update provides more control over how assessment scores are calculated by ensuring that only applicable factors impact the results.

The following applications have been updated for this enhancement.

 

Manage Performance Rating Codes (CTMCART)

You can now select the new Exclude From Calculation checkbox for each rating code. When this checkbox is selected, any assessment factor that uses the rating code is excluded from the overall assessment score.

A new Update Contracts button is now also available on this screen to apply changes made to the Exclude From Calculation checkbox. When you modify the Exclude From Calculation value for a rating code, Costpoint displays a prompt reminding you to save your changes and click Update Contracts to apply the updates. Clicking Update Contracts updates all contract records that use the modified rating code and recalculates scores across the following levels in Manage Contracts:

• Assessment Details and Other Areas Details subtasks (section totals and percentages)

• Performance Assessment tab (total score and percentage)

• Contract header (average rating percentage)

 

Manage Contracts (CTMCNTR)

On the Assessment Details subtask of the Performance Ratings tab, each factor now includes an Exclude From Calculation checkbox. The checkbox defaults to the value defined for the rating code on the Manage Performance Rating Codes screen and cannot be edited in Manage Contracts. To modify this setting, update it in Manage Performance Rating Codes.

When an assessment factor is excluded, Costpoint removes it from the score and recalculates the percentage automatically. Updates are reflected immediately on both 

• the Assessment Details subtask (Section Total Score and Percent) 

• the Performance Assessment tab (Total Score and Percent)

The field label in Assessment Details has also been updated from Total Score to Section Total Score.

 

Calculation Behavior

Some rating codes (such as Not Applicable (NA), Insufficient Data, or similar values) are informational and are not intended to affect scoring.

Previously, all responses were included in the calculation, which could lower the overall score even when certain factors were not applicable.

With this update, excluded rating codes do not contribute to the score. As a result:

• Scores reflect only evaluated criteria.

• Calculations align more closely with assessment intent.

This behavior is particularly relevant for organizations that must record responses for compliance or audit purposes without affecting scoring.

For example, a contract includes five assessment factors, each worth 10 points. One factor is marked Not Applicable (NA) with a score of 0.

• Before this update

The NA factor remains in the calculation and contributes 0 points.

Result: 25 out of 50 = 50%

• After excluding the NA factor

Costpoint removes the factor from the calculation.

Result: 25 out of 40 = 60%

In this scenario, excluding the NA factor prevents it from lowering the overall score.

Note: For Costpoint Cloud, you can choose to opt in to this feature for the Costpoint 2026.3 release. The ability to opt in is temporary and will be removed when the feature becomes automatically enabled for all users as part of a future Costpoint release. For more information, see the Opt-In Features section of these release notes.

This enhancement extends Contract Performance Assessment Reporting System (CPARS) functionality in Manage Contracts by introducing AI-based extraction of CPARS documents and expanding the Performance Assessment data model. Uploaded CPARS documents can be scanned to populate structured assessment fields, reducing manual data entry.

 

AI-Based CPARS Data Extraction

You can upload CPARS documents using the Attach & Scan option in Manage Contracts. PDFs are supported (image format only). Costpoint performs the following logic:

• For each scan, a new performance assessment record is created in the contract.

• Extracted data is mapped to existing and new fields on the Performance Assessment tab.

• Up to 10 assessment factors can be extracted and stored in dedicated fields.

• For all AI-generated records:

• Assessment Format defaults to an IMPORT format and is not required.

• Extracted values are validated against existing lookup tables where applicable.

• Unmatched required fields must be completed before saving the record.

 

Performance Assessment Tab Updates

The Performance Assessment tab includes new and updated fields to support structured CPARS data:

• Contractor Comments: This new field stores contractor-provided inputs.

• Recommended Comments: This new field stores additional recommendation information about the contractor’s ability to perform contract requirements.

• Total Score now equals the sum of the Section Total Score from the Assessment Details subtask and Section Total Score from the Other Areas Details subtask. 

• Existing fields on the Performance Assessment tab as well as on the Assessment Details subtask are populated using extracted values and validated against system records.

 

New Other Areas Details Subtask

A new Other Areas Details subtask on the Performance Assessment tab captures evaluation factors not included in standard assessment categories.

• Fields are populated from the CPARS document during scanning.

• Each row represents an extracted assessment factor with: 

• Assessment Factor description

• Rating (mapped to rating codes when matched)

• Comments

• Includes scoring fields: 

• Section Total Score (sum of factor scores)

• Percent = (Total Score / Maximum Score) × 100

• If selected, the Exclude From Calculation checkbox indicates that specific factors are omitted from score calculations.

 

Manage Application/Content Links (SYMCMIAL)

This update adds a new ICR Scan Type drop-down list to this screen to support scan routing for different AI-driven document processing scenarios.

ICR Scan Type allows administrators to specify which scanning prompt is invoked when documents are processed using the Attach & Scan functionality on the Manage Contracts screen. Valid values include:

• None: This uses the default contract document scanning behavior at runtime.

• CPARS: This uses the CPARS document scanning behavior at runtime.

This new drop-down list displays only when the Show Scan button checkbox is selected in Manage Application/Content Links. The CPARS option is available only if CTMCNTR is selected in the Application field. 

Note: For Costpoint Cloud, you can choose to opt in to this feature for the Costpoint 2026.3 release. The ability to opt in is temporary and will be removed when the feature becomes automatically enabled for all users as part of a future Costpoint release. For more information, see the Opt-In Features section of these release notes.

Costpoint includes an AI-enabled proposal generation agent that helps you process government solicitation documents and create structured, compliant proposal content.

The agent uses AI and Intelligent Character Recognition (ICR) to ingest solicitation files, such as Requests for Proposal (RFPs) and amendments, extract key requirements, and generate a structured proposal outline with annotations. You can then assign contributors, draft content in Microsoft Word, and track proposal progress through approval workflows.

This capability reduces manual effort when reviewing solicitation documents, creating outlines, organizing requirements, and coordinating proposal development.

A new application has been added, and several existing applications have been updated to support this enhancement.

To use this functionality, follow this general procedure:

1. Define proposal settings on the Configure Opportunity/Proposal Settings, Manage Contract Management Roles, Manage Contract Management Document Types, and Manage Capture Stages screens. 

2. Use the Manage Opportunity Proposals screen to create a proposal, upload solicitation documents, generate the outline, assign sections, and notify contributors.

3. Use the Costpoint Word add-in to draft content, submit sections for approval, and review, approve, or reject sections.

4. Track section and proposal status in Manage Opportunity Proposals.

Attention: For more details about this enhancement as well as on the step-by-step procedure on using the agent, see Proposal Generation Agent in the Costpoint online help.

Manage Opportunity Proposals (CTMPROP)

This enhancement introduces the Manage Opportunity Proposals application, a new workspace for creating, structuring, and managing proposals generated from government solicitation documents.

Note: This application requires the separate PL (Manage Opportunity Proposals) add-on license in addition to the CTM (Capture & Contracts) module license.

Manage Opportunity Proposals integrates AI-driven outline generation, contributor assignment, document management, and workflow tracking into a single interface.

This application supports the full proposal lifecycle:

• Generate proposal outlines from solicitation documents using AI

• Maintain a structured outline of proposal sections with annotations

• Assign contributors and approvers to proposal sections

• Track section status and overall proposal progress

• Integrate with Microsoft Word for drafting and review

• Store and manage proposal documents within Costpoint

Costpoint automatically updates proposal status based on section-level progress and workflow activity.

You can link proposals to opportunity records. When linked, Costpoint synchronizes key data between the opportunity and proposal to maintain alignment throughout the capture and proposal process.

When creating and managing proposals, note the following: 

• You must upload and select solicitation documents before generating an outline.

• Regenerating the outline removes existing section assignments.

• Proposal completion locks the record but can be reversed if additional updates are required.

• Proposal content is created and edited in Microsoft Word using the Costpoint Word add-in.

To access this new screen, go to Capture & Contracts » Opportunities » Manage Opportunity Proposals.

Manage Opportunities (CTMOPP)

This enhancement introduces proposal integration within the Manage Opportunities application.

On the main screen, the following fields have been added:

• Proposal ID: This field displays the proposal ID associated with the opportunity. 

• Proposal Name: This field displays the name of the proposal linked to the opportunity. You can click the hyperlink to open the Manage Opportunity Proposals screen and view additional details.

• Start Proposal: This button displays only when no proposal is associated with the opportunity. Click this button to open the Manage Opportunity Proposals application, initiate a new proposal, and link the proposal to the opportunity. This button is available only in Form view.

On the Status tab, the Stage field has been renamed to Capture Stage. 

On the RFP Info tab, the RFP Dates fields have been reformatted into four columns. These dates now synchronize with the proposal when a proposal is linked to the opportunity.

On the Team tab, a new Email column has been added to the Opportunity Employee Team subtask. Information on this subtask now populates the Proposal Team subtask in Manage Opportunity Proposals when a proposal is linked to the opportunity.

On the GovWin IQ subtask of the main screen, the following changes have been made:

• The IQ Opportunity Link field has been renamed to Source URL. This field displays the external web site address of the agency associated with the opportunity.

• The Duration field has been relocated to display below the Estimated Value field.

• A new GovWin IQ URL field has been added to display the URL of the opportunity record in GovWin IQ.

On the Documents subtask of the main screen, when a proposal is linked to the opportunity, documents associated with that proposal also display on this subtask. If the Include in Outline checkbox is selected for a document in Manage Opportunity Proposals, you cannot delete that document from the Documents subtask in Manage Opportunities.

Import GovWin IQ Data (CTPIQDAT)

Integration has been updated to populate the new GovWin IQ URL field added to the GovWin IQ subtask in Manage Opportunities.

Configure Opportunity/Proposal Settings (CTMOPSET)

Previously labeled as Configure Opportunity Settings, this application has been renamed to Configure Opportunity/Proposal Settings to reflect the addition of proposal-related functionality.

A new Proposal Settings group box allows you to configure how proposals are created and managed. You can enable automatic assignment of proposal IDs for records created on the Manage Opportunity Proposals or require manual entry. You can also restrict users to viewing only the proposal sections assigned to them.

You can specify the default location for generated proposal documents and select the template file used when creating proposal documents.

In the Label Settings section, a new Proposal Date column has been added. This column is enabled only for RFP Dates 1–12 and allows you to designate a date as either a Proposal Due Date or an Award Date. Only one RFP Date can be assigned to each option. If you assign more than one RFP Date to either the Proposal Due Date or Award Date, Costpoint displays an error message.

Manage Contract Management Roles (CTMROLES)

Use the new Proposal Access column on this screen to define what each role can do in the opportunity proposal workflow. Valid options are:

• Full/Approver: Can edit sections and approve or reject content

• Edit: Can create and update assigned sections

• Read Only: Can view proposal content but cannot make changes

• None (default): No access to proposal features

These permissions apply to both the Manage Opportunity Proposals application and the Costpoint Word add-in.

Because users can be assigned multiple roles, access can vary by section. For example, you can have Edit access to one section as a technical writer and Full/Approver access to another section as a proposal manager.

Manage Contract Management Document Types (CTMDOCTP)

This application has been renamed from Manage Document Types to Manage Contract Management Document Types. 

The screen now also has the new Proposal Default checkbox, which allows you to mark a document type as the default for proposal-related documents. Only one document type can be set as the proposal default at a time. By default, this checkbox is selected for the RFP document type, but you can change it. Costpoint uses the selected document type during proposal processing, including when creating proposal documents and handling proposal-related files.

Manage Capture Stages (CTMSTAGE)

Manage Opportunity Stages has been renamed to Manage Capture Stages to reflect broader capture process support, aligning stage management not just for opportunities but also for proposal workflows introduced in this enhancement.

The following system-defined stage codes have also been added to this screen:

• REVIEW: Under Client Review

• PROTEST: Protest

In addition, the Grouped Stage Name column has been renamed to BI Stage Name.

Approve Prospective Customers (CTMCUSTA)

When you approve a prospective customer, Costpoint now updates all associated proposals to use the newly created active customer ID. This process runs automatically when the record is saved with an Approved status.

Only the Customer ID on the Manage Opportunity Proposals screen is updated; all the other data are not affected. 

Manage User Groups (SYMGRP)

Two user groups have been to support proposal workflows:

• STD_PROP_LEAD (Proposal Leadership): This provides full access to proposal-related applications and functionality.

• STD_PROP_CTRBR (Proposal Contributor): This allows users to view proposal records and sections as well as submit sections for approval.

Microsoft Word Integration (Costpoint Word Add-in)

The Costpoint Word Add-in enables proposal contributors and approvers to work directly in Microsoft Word while remaining connected to Costpoint.

The add-in includes a dedicated ribbon tab and side panel that mirror key functionality in Manage Opportunity Proposals, allowing users to perform proposal-related tasks without leaving Word.

You can:

• Open and edit assigned proposal sections directly in Word, with updates synchronized to Costpoint. 

• Complete proposal workflow actions such as Submit, Approve, and Reject.

• Use the side panel to view section details and annotations, milestones, and other proposal information.

A new "Have an Idea?" offering has been added to the Ask Dela interface, allowing you to submit suggestions for improving Dela. This feature provides a streamlined way to capture Dela-related feedback from users who may not have access to the Idea Portal. In-App Guidance must be enabled to use this feature. You can enable In-App Guidance on the In-App Guidance tab in Configure System Settings.

Breadcrumb navigation has improved navigation efficiency. When enabled via the Screen Configuration Panel under the avatar image, breadcrumbs allow you to click on a specific breadcrumb to open the navigation menu and focus on the selected area. Hovering over a breadcrumb displays a copy icon, enabling you to copy the full breadcrumb path. This setting is stored per device for personalized usage.

Deltek introduces the Dela AI Package which provides support for Model Context Protocol (MCP), enabling Dela to operate as both a client and a server when connecting with external AI tools and platforms. It also includes the AI Agents Framework in the Extensibility Tool, giving users the ability to build custom AI agents, integrate AI-driven capabilities, and extend AI functionality within Costpoint.

 

With this enhancement, organizations can extend Costpoint beyond its core functionality by enabling external AI solutions to interact with Dela, supporting more connected, cross-platform AI workflows.

Costpoint 2026.3 supports domain-based passkeys, so users can use the same passkey across Costpoint environments or URLs within the same domain. Previously, passkeys were tied to a specific URL, which could require users to create a new passkey when switching environments or when a URL changed. No administrator setup is required; if needed, users are prompted to register or update their passkey during sign-in.

Costpoint 2026.3 adds the Manage Web Services (SYMWIC) screen, which provides a faster way to make Costpoint applications available as Data Web Services. You can select an application and create import or export web services based on the operations the application supports, instead of configuring each endpoint in the Web Integration Console. 

Use export web services to read data from Costpoint and import services to add or update records. For example, if the Manage Project User Flow (PJMBASIC) screen supports reading, adding, and updating project records, you can make it available as an export service to retrieve project data and as an import service to create or update project records. 

The Manage Web Services screen makes the full selected application available as a web service, including its supported subtasks and fields. It also shows applications already available as web services, including the integration method ID, module ID, and whether each method is for import or export. You can create a new integration method and module or add a new method to an existing integration module. 

This screen does not replace the Web Integration Console. Use the Web Integration Console when you need more control over the specific subtasks or fields included in a web service. 

This release includes an enhanced mobile view with a new navigation and action model. In mobile view, navigation controls and application actions are now consolidated in a bottom action bar, making them easier to access on smaller screens.

Actions that were previously available in the page header, such as Save and Query, now appear in the bottom action bar or the More options menu. This update also includes redesigned navigation controls, including an updated Back button and larger mobile controls.

Dela can now operate as a Model Context Protocol (MCP) server, enabling authorized external AI tools to connect to Costpoint through a standard interface.

This enhancement allows you to extend Costpoint by connecting AI platforms, such as Copilot or other MCP-compatible tools, to access Dela capabilities and interact with Costpoint data and workflows.

This release establishes the foundation for cross-platform AI integrations and expanded workflows across your organization’s AI ecosystem. Enable the new Dela MCP server connection on the Dela tab in Configure System Settings.

This feature is included in the Dela AI Package.

The new user experience is now the default user interface for all users. This update standardizes the user experience across Costpoint.

The following updates are included:

• New UI enabled by default: The new UI is set as the default user interface in Configure System Settings.

• UI mode switching disabled: The Allow user to switch between UI Modes option is cleared by default for all users in Manage Users.

• Default UI setting for new users: The New User Interface setting is updated to Default for users whose current value is No. Users already set to Default or Yes are not changed.

These changes help provide a consistent interface and simplify navigation as you move to the new UI.

A new Preview button has been added after the Print button on the Action bar for print-type applications (Print Organization List, etc.) allowing you to review your output before printing. The Action button is now hidden for print-type applications unless actions are available. If actions become available via a child record, the Action button will dynamically appear. This ensures a more intuitive interface by displaying the button only when relevant.

CPWebIntegrationUtility.cmd Update

Missing parameters have been added to the CPWebIntegrationUtility.cmd.

Cleanup of Unused Parameters in the View Process

Unused parameters in the View process have been cleaned up to streamline functionality and improve maintainability. 

New URL Rewrite Rules on Web Server (IIS)

 

To support the new 2026.3 capability that lets you use Costpoint as an MCP server with ChatGPT, M365 Copilot, and other MCP-compliant chatbots, configure two new URL rewrite rules on the Web Server (IIS). The QR installer (Web Tier option) and DeltekCostpoint82MaintenanceReleaseInstallation.pdf provide guidance for this configuration.

The Maintenance Repair and Overhaul (MRO) is a new module to manage service requests and work orders for items that require maintenance, repair, or overhaul.

Use service requests to record the item that needs work, add service lines for the required tasks, and perform work directly on the service request. You can add parts as components or load them from a bill of materials (BOM) when one is available, then issue the parts to the service request. When additional work must be completed, you can generate a work order that includes service lines, parts, and labor charged to the service request. Labor charging for work performed directly on the work order is planned for a future phase.

The following are the changes across updated and newly added applications for the new module:

 

Manage Parts (PDMPART)

A service request item type is added to Item billings to allow parts to be used on service requests. This is visible when the MRO license is enabled. A new checkbox, COTS Item, is added to mark items as Commercial Off the Shelf (COTS). The MRO license is not needed to see/use the COTS Item checkbox.

 

Manage Services (PDMSERV)

 

A service request items type is added to allow parts to be used on service requests. When the MRO License is enabled, the field displays as SR Item Type.

The valid Service Request (SR) item type is Invoice, where the item is eligible for invoicing as soon as the sales order (SO) is approved.

 This change also applies to Manage Item Billings (PDMIBILL).

 

Manage Routings (RUMROUT)

 

You can now mark routings, via the new MRO Routing checkbox, as MRO-specific, making them available for work orders and preventing changes if they are already in use.

Manage Maintenance Types (RUMMAINT)

 

You can now create additional maintenance classes—such as Maintenance, Corrective Maintenance, and Predictive Maintenance—and define frequencies and required labor hours.

Manage Warehouses (INMWHSE)

 

Several new transaction descriptions are added to allow you to assign MRO transaction types (Issue to Service Request, Issue to Work Order, Work Order Receipt, Service Request, and Work Order) and autogenerate numbering for these transactions.

Manage Sales Group Abbreviations (PDMSALES)

 

You can now enable sales group abbreviations for use on service requests via the Service Request checkbox.

Post Inventory Journal (INPEDJNL)

 

You can now post inventory journals using new MRO transaction codes for issuing service requests and work orders.

Manage Inventory Projects (INMPROJ)

 

You can now use the new MRO Project checkbox to control whether inventory abbreviations are available for MRO and exclude inappropriate abbreviations from manufacturing orders.

The Last MO field changes to Last WO when the MRO Project checkbox is selected.

 

Manage Service Requests (ROMMSR)

 

Use this screen to create and manage service requests for MRO work. Create a service request header for the item being serviced, add service lines for the work to be performed, add components when applicable, and create work orders for lines that require additional more complicated work.

Enter Service Request Issues (ROMISSU)

 

Use Enter Service Request Issues to issue components to a specific service request line or to all lines on a service request.

• Component requirement: To issue a part to a service request, the part must first be included in the Components list.

• Transaction changes: After you save the transaction, you cannot delete or update the issue. To correct a mistake, use Reverse Transaction to reverse the original issue.

• Reversed issues: Reversing an issue to service request reopens the requirement for the components, but it does not create a new reservation.

• Cost update: When you save the issue, the component cost is added to the overall service request cost.

• Inventory abbreviation: The inventory abbreviation from the Service Request Component subtask (Manage Service Requests screen) defaults as the inventory source for the parts, but you can change it if needed.

Print Service Request Pick Lists (RORPICK)

 

Use this screen to print pick lists for any service request with pending material to be issued.

You can select pick lists (or pick tickets) by catalog, customer, service request, and warehouse. You can then sort the lists by service request line number, item or preferred location. You can also pick material by item due date or ship by date.

Manage Service Request Invoices (ROMINVC)

 

Use this screen to view, create, and maintain service request invoices.

• Header information: You can update fields such as Invoice Date, Due Date, Customer PO, Terms, and Recalc Due Date. You can also specify additional notes and print settings for invoices.

• Line information: You can update line details such as SR Line Notes, Item Description if allowed in the settings, and Invoice Quantity for service request lines without components.

• Quantity validation: If the quantity exceeds the service order quantity, the application displays a validation message.

You can also create an invoice directly from this screen. After the invoice is posted, you can no longer edit or change it.

Create Service Request Invoices (ROPINVC)

 

Use Create Service Request Invoices after a service request is marked as Ready for Invoice.

• Invoice selection: Select the invoice generation option. For example, select One to generate an invoice for a specific service request.

• Line types: Choose the service request line types to include on the invoice.

• Invoice number: Load the starting invoice number. The number can be entered manually or assigned automatically based on the settings in Configure Service Request Entry Settings.

• Invoice details: Verify the invoice date.

• Accounting period: Enter the fiscal year, period, and subperiod.

Print Service Requests Invoices (RORINVC)

Use Print Service Request Invoices to print service request invoices with the appropriate selection range, format, and print options.

• Selection range: Choose the invoices to print. For example, select One and enter a specific service request.

• Format option: Select the format to use for the printed invoice.

• Print options: Choose which information to include on the service request invoice.

• Text placement: Print the standard text and header notes at the top or bottom of the invoice.

Post Service Request Journal (ROPPOST)

Use Post Service Request Journal as the final step in processing a service request invoice.

• Posting setup: Enter the period to post and select the invoice options. For example, you can select one invoice for the fiscal year, period, and subperiod.

• Review before posting: Preview the posting report to verify the project, accounts, and organizations that will be affected. These values come from the sales group abbreviation on each service request.

• Post the journal: After you verify the information, print or post the invoice journal.

Manage Work Orders (ROMWOMNT)

Use the Manage Work Orders screen to create, maintain, and view information about work orders.

Work orders are used to track maintenance, repair, and overhaul work. You can add component parts to a work order, and tracks all related costs and use them to calculate the value of the completed work order. You can also copy a manufacturing bill of materials to a work order to create a list of required materials and reserve inventory. If needed, you can copy routings to track labor steps required to complete the work.

 

Enter Work Order Issues (ROMWOISS)

Use the Enter Work Order Issues screen to issue components to a work order and update work order issue quantities and costs. If there are open requirements, you can use Autoload to load requirement lines that have open quantities. You can also manually issue additional parts that are not in the requirement table.

 

Enter Work Order Reliefs (ROMRELWO)

Use Enter Work Order Reliefs to relieve a work order part and either issue it to a service request or move it to inventory, depending on the selected relief option.

• Relieve to Service Request: Enter a To Location and Service Request Relief Quantity. When you save, the application creates the relief and automatically creates an Issue to Service Request transaction for the work order part.

• Relieve to Inventory: The part is relieved to the furnished abbreviation specified on the Allocations subtask (Manage Work Orders screen).

When the part is issued to the service request, the application updates the service request cost by the value of the work order.

 

Print Service Request Acknowledgement (RORSRACKN)

Use this screen to print service request acknowledgements using improved formatting options and optionally display “QUOTE” on the printed output.

 

Print Work Order Documentation (RORWODC)

Use the Print Work Order Documentation screen to print work order forms such as the work order and part list.

 

Configure Service Request Entry Settings (ROMSRSET)

Use this screen to configure key service request entry settings, including invoice numbering, revenue recognition, processing defaults, and print options.

• Invoice numbering: Choose how service request invoice numbers are assigned: Manual, System, or Use Billing Invoice Number.

• Revenue recognition: Select the revenue recognition method, such as Shipment Sales, Unbilled Accounts Receivable, or Prepay.

• Processing and print defaults: Set default processing options and print settings for service requests.

 

Configure Work Order Settings (ROMWOSET)

Use this screen to establish and maintain control parameters and default information.

Set up this screen after initializing work order and before entering a service request.

 

Manage Service Request User Defined Labels (ROMSRUDL)

Use Manage Service Request User Defined Labels to configure up to 15 user-defined fields for service requests, map each field to a service type, and display the mapped fields on the Service Request Types subtask based on the service type selected on the Manage Service Requests screen.

 

Manage Service Request Types (ROMSRT)

Use Manage Service Request Types to define the type of service order being created.

• System-defined types: These include Maintenance, Overhaul, Repair, and Schedule Maintenance.

• User-defined types: Add custom service request types as needed to support your business processes.

 

Manage Failure Codes (ROMFAIL)

Use this screen to define failure codes unique to each company that technicians can select on work orders.

 

This enhancement requires the following:

• cp82_dbc_820_11839_001.zip

• cp82_sypcomp_001.zip

• cp82_dbc_820_11890_001.zip

• cp82_cmnlib_pdmibilllib_001.zip

• cp82_cmnlib_rumroutlib_002.zip

• cp82_dbm_820_11833_001.zip

• cp82_dbc_820_11837_001.zip

• DeltekCostpointMaintenanceRelease_8.2.12.5013.exe

• DeltekCostpointMaintenanceRelease_8.2.8.5009.exe

You can now use the Dela AI Agent to create purchase orders directly from approved requisitions with Assign PO Information setup without going through the manual purchase order creation process or navigate to the Create Purchase Orders (PPPGPO) screen. This enhancement streamlines the purchase order creation process for supported scenarios.

 

With this agent, you can now:

• Create purchase orders from approved requisitions by prompting the Dela AI Agent.

• Create purchase orders for a specific vendor when the requisition includes the required vendor and Assign PO setup.

• Receive the generated purchase order ID after successful creation.

• Use Dela to create purchase orders without opening Manage Purchase Orders (POMMAIN) or Create Purchase Orders (PPPGPO).

• Start the purchase order creation process directly from Dela without navigating to application screens.

Key Behavior

• Dela can create a purchase order even if no buyer is assigned, as long as you are associated with a single buyer profile.

• Costpoint creates one purchase order per buyer and vendor combination.

• The requisition status updates to PO Generated after the purchase order is created.

• All existing validations from Create Purchase Orders (PPPGPO) still apply.

Requirements and Limitations

• Dela must be enabled in Configure System Settings (SYMSETNG).

• You must have full rights in Manage Purchase Orders (POMMAIN).

• Requisitions and requisition lines must be approved.

• Requisition lines must include a preferred vendor, or the vendor must be specified in your prompt.

• Assign PO Information must be set up in Apply PO Info to Purchase Requisitions.

• If purchase order numbering is set to manual, you must provide the purchase order ID.

• Dela supports creating purchase orders for one requisition and one vendor combination at a time.

 

This enhancement requires the following:

• cp82_pppgpo_005.zip

• deltekcostpointmaintenancerelease_8.2.8.5009.exe

This enhancement adds support for capturing part dimensions in Costpoint. Users can now record length, width, and height values for a part, along with a unit of measure for each dimension. 

Manage Parts (PDMPART) 

You can now capture and maintain length, width, and height values for parts, along with a unit of measure for each dimension. In Manage Parts, you can enter and update part dimensions directly on the Characteristics tab. You can also copy these values when you copy or clone part records. 

 

Import Items (AOPITEM) 

You can now import and update part dimensions in Import Items. This enhancement lets you include length, width, and height values, plus a unit of measure for each one, in the input file for supported record types. 

 

This enahancement requires the following:

• cp82_pdmpart_002.zip 

• cp82_dbc_820_12055_001.zip

• DeltekCostpointMaintenanceRelease_8.2.8.5009.exe

This feature helps you track routing work in more detail. You can enter start and completion times for each routing line, record actual touch time, and view operation hours more accurately. You can also enter a planned completion date for each operation. These updates give you more accurate operational data that can be used for reporting and integrated external tools for capacity planning and production analysis. The values are saved in the database and can also be updated through Web Integration Console (WIC).

 

Manage Manufacturing Orders (PCMMONT) 

You can now enter planned completion, start time, completed time, operation hours, and actual touch time for routing lines, giving you better visibility into more precise operational data.

 

Manage Work Orders (ROMWONT) 

You can now enter planned completion, start time, completed time, operation hours, and actual touch time for routing lines, giving you better visibility into more precise operational data.

 

Manage MO Operation Completions (PCMCOMP) 

You can now view and maintain start time, completed time, actual touch time, and operation hours in Manage MO Operation Completions when those values are saved from MO routing data. 

 

Manage MO Quality Control Inspection Results (PCMINSP) 

You can now view start date, start time, completed time, actual touch time, and operation hours in Manage MO Quality Control Inspection Results when those values are available from MO routing data.

 

Expedite Manufacturing Orders (MRMMEXPD) 

You can now view and update planned completion, start time, complete operation time, time in operation, and actual touch time in Expedite Manufacturing Orders.

 

View Manufacturing Order Status (PCQMOST)

You can now view planned completion, start time, complete operation time, time in operation, and actual touch time in View Manufacturing Order Status. These fields are read-only in this application.

 

Expedite Manufacturing Orders (PCMMEXPD)

You can now view and update planned completion, start time, complete operation time, time in operation, and actual touch time in the Expedite Manufacturing Orders application of the Production Control module. 

Costpoint users who are logged in to separate companies now have the ability to run processes concurrently with other users in Create MO WIP Variance Journal Entry (PCPWIPV). If multiple users are logged into the same company, they will still not be able to run the Create MO WIP Variance Journal Entry simultaneously as this only impacts multi-company users.

Enhancements have been applied to vendor punchout processing to ensure that punchout-related purchase order data is retained when purchase orders are archived and that vouchers created from punchout invoices are assigned the appropriate entry status during creation. These updates support consistent downstream processing of punchout purchase orders and vouchers.

 

Archive Purchase Orders (POPARCH)

The Archive Purchase Orders screen has been enhanced to ensure that vendor punchout information is retained when purchase orders are archived.

When you archive a purchase order that contains vendor punchout data, punchout-related fields are copied from the purchase order header to the purchase order history tables. Records from vendor punchout operational tables are also copied to the corresponding punchout history tables, and the active records are removed as part of the archive process.

 

Manage Purchase Order Vouchers (POMPOVCH)

When a voucher is automatically created from a vendor punchout invoice, a default Status is assigned. If the draft functionality is enabled, the voucher is assigned a Draft status. Otherwise, the status is Submitted.

 

This enhancement requires the following:

• cp82_cmnlib_punchoutlib_001.zip

This feature introduces the ability to view the original creation date and entry user for sales orders across multiple modules. These enhancements improve tracking and transparency of sales order creation details.

Manage Sales Orders (OEMNTSO1) and Manage Sales Order Supervisor (OEMNTSO2) 

You can now view the read-only Entry Date and Entry User fields to see when the sales order was originally created and who created it. Entry Date shows the order date, and Entry User shows the user who last modified the sales order.

Approve Sales Order (OEMAPPSO) 

You can now view the original creation date and entry user while approving sales orders. 

View Sales Order Status Inquiry (OEQSTAT) 

You can now view the original creation date and entry user in View Sales Order Status Inquiry. The application logic has been updated as well to get the data from Entry User instead of Modified By values. 

View Sales Analysis Information (OEQSALES) 

You can now view the original creation date and entry user for sales order lines in detailed sales order inquiry. The application logic has been updated as well to get the data from Entry User instead of Modified By values. 

Import Sales Order (AOPSOPP) 

You can now capture the creation date and user when sales orders are created through the import process, and be able to track who executed the import that created the sales order.

Timesheet and payroll administrators who have access to the Labor module can now use Dela to:

• Evaluate imported timesheets for auto-posting.

• Post eligible timesheets without manual review when the timesheet cycle is configured for automatic posting.

This enhancement also adds audit and tracking fields so you can review how Costpoint evaluated and processed each timesheet.

You configure auto-posting by timesheet cycle on the Manage Timesheet Periods screen, where the functionality is disabled by default. In this release, auto-posting applies to imported timesheets for salaried employees. Costpoint does not auto-post hourly employees. New employees may not be auto-posted until enough historical timesheets are available for comparison. Posting reports are saved to the Print Archived Reports location.

You can review the results of auto-post analysis on the Manage Timesheets, Manage Correcting Timesheets, and View Timesheet History Inquiry screens, where the following new fields have been added:

Field	Description
Outcome	This field displays the outcome for the timesheet during the auto-post analysis. Values are: A: Dela Authorized for Auto-Post NA: Dela Evaluated Manual Posting Required NR: Dela Evaluated Review Advised R: Dela Recommended
Reason	This field displays the reasoning behind the auto-post outcome.
Analysis Date	This field displays the date and time of the auto-post analysis.
Mode	This non-editable field displays the auto-post mode for the employee’s timesheet cycle at the time of the auto-post analysis.
Application ID	This field displays the application ID where the auto-post analysis was performed.
Process	Note: This field is not currently being used but is reserved for future use. This field will display the process within the application where the auto-post analysis was performed. This would only be applicable for applications that contain multiple processes, such as Apply timesheet Adjustments in Batch Mode.
Posting Status	This field displays if the Dela posting was successful. Values are: P: Dela Posted F: Posting Failed This field is blank if the timesheet is either unposted or manually posted. This field will only be populated if the auto-post mode for the employee’s timesheet cycle is set to Enforce.
Original Dela Confidence Factor	This non-editable hidden field displays the Auto-Post Confidence for the employee’s timesheet cycle at the time of the auto-post analysis.

 

Manage Timesheets (LDMTIME) / Manage Correcting Timesheets (LDMCTIME)

You can review the new auto-post analysis fields on the Entry Information tab after Costpoint analyzes an imported timesheet. You can also query by the new auto-post fields.

When you create correcting timesheets on the Manage Correcting Timesheets screen, D and N correcting timesheets do not inherit auto-post status values from the original timesheet. Those fields remain blank until a future phase populates them.

 

View Timesheet History Inquiry (LDQTHF)

You can use the View Timesheet History Inquiry screen to review auto-post analysis details for posted historical timesheets.

You can review new auto-post analysis details on the Entry Information tab for posted timesheets. You can also query by the new auto-post fields.

 

Manage Timesheet Periods (LDMTSPD)

You can use the new Auto-Post Options tab on the Manage Timesheet Periods screen to configure auto-posting for each timesheet cycle. This tab includes the following fields:

Field	Description
Auto-Post Mode	Select the mode to be used for timesheet auto-posting for salaried employees. This drop-down field is part of the auto-closing process. There are three options: Recommend Disable Enforce When you select Enforce or Recommend, Dela will compare an employee’s current timesheet to the employee’s historical timesheets to score how closely it matches prior timesheets. Dela compares the timesheet’s score to the Dela Confidence Factor number to determine if it should be selected for auto-posting. A higher confidence factor indicates that the timesheet must have a very close match to prior timesheets. A lower confidence factor indicates that there can be some differences between them. Enforce will allow Dela to automatically post any timesheets approved by Dela. Recommend means that Dela will not automatically post the timesheet but will make a recommendation based on the Dela Confidence Factor. You can review the timesheets before posting. Disable turns off the auto-post functionality so it is not used by Costpoint. Auto-posting may be used for timesheet cycles where the employees normally work a regular schedule that does not vary and few or no edits are required in the Labor module.
Dela Confidence Factor	The Dela Confidence Factor allows you to specify how certain Costpoint should be before accepting a match between an employee’s current timesheet data and the employee’s historical timesheet data. This setting is a value between 70 and 100. Low Confidence Level (e.g., 70): Costpoint will accept matches even if it is not very sure. This might result in more matches, but some could be less similar to the historical data. High Confidence Level (e.g., 100): Costpoint will only accept matches when it is very sure. This might result in fewer matches, but they will closely resemble the historical data. Adjust this setting based on how closely you need the results to match the historical data. Higher values mean more similarity, while lower values mean more flexibility in variation. This field is enabled only when the Auto-Post Mode is either Recommend or Enforce
Posting Error Email Addresses	This field is required when the Auto-Post Mode is set to Enforce. If an error causes a timesheet posting failure, an email notification will be sent to the listed email addresses.

Note: Existing fields on this screen are now on a separate Timesheet Options tab.

 

Import Timesheets from Deltek Time and Expense (LDPUPET) / Import Timesheets (AOPUTLTS)

You can use the Import Timesheets from Deltek Time and Expense screen or the Import Timesheets screen to trigger auto-post analysis for imported timesheets when the associated timesheet cycle is configured for auto-posting.

Costpoint selects imported timesheets for auto-post analysis when the related timesheet cycle uses the Enforce or Recommend mode and the timesheet has not already been analyzed. Hourly employees will be excluded from auto-post analysis. Dela evaluates salaried employee timesheets against historical timesheets and returns an outcome and, when applicable, a reason.

When the timesheet cycle uses Enforce, Costpoint either authorizes the timesheet for auto-posting or marks it for manual posting. When the timesheet cycle uses Recommend, Costpoint either recommends the timesheet or advises review.

Costpoint posts eligible timesheets individually through the Post Timesheets screen and updates the auto-post fields in the timesheet header and, if posting succeeds, in timesheet history.

If posting fails, Costpoint sets the posting status to Failed and sends a notification to the email addresses defined on the Manage Timesheet Periods screen. If the import process fails and the timesheet is not inserted into the header table, Costpoint does not run auto-post analysis and does not populate auto-post fields.

 

Print Data Dictionary Report (SYRDD)

The Data Dictionary Report now includes the following new auto-post fields on the Timesheet Header (TS_HDR) and Timesheet Header History (TS_HDR_HS) tables.

Field	Description
AUTOPOST_MODE_CD	This is the auto-post mode when the timesheet was analyzed. E: Enforce D: Disable R: Recommend
AUTOPOST_CONFID_NO	This is the Dela confidence setting of the timesheet cycle when the timesheet was analyzed. This is a hidden field.
AUTOPOST_OUTCOME_CD	This field indicates the outcome. A: Dela Authorized for Auto-Post NA: Dela Evaluated Manual Posting Required NR: Dela Evaluated Review Advised R: Dela Recommended
AUTOPOST_REASON_DESC	This is the description of the reason for the auto-post outcome.
AUTOPOST_TIME_STAMP	This is the date and time of the auto-post analysis.
AUTOPOST_STATUS_CD	This field displays if the Dela posting was successful. P: Dela Posted F: Posting Failed
AUTOPOST_SOURCE_CD	This is the auto-post transaction source.
AUTOPOST_PROCESS_CD	This is the auto-post process source.

This enhancement updates the Close Leave Year screen to use the standardized project period of performance (POP) validation logic. This update ensures consistency with the common POP logic introduced in Costpoint across various timesheet and payroll applications. You can enable this functionality through the Show Period of Performance Warning Message checkbox on the Configure Project Settings screen. When enabled, Costpoint evaluates whether transactions fall within valid project dates.

POP validation now uses a consistent approach across all affected processes, including lookup of project dates up the project structure when necessary. For validation, Costpoint will use the Subperiod End Date and not the transaction date.

The Close Leave Year application has been redesigned so you can understand your processing choices more easily, review clearer reports, and reverse a previously closed leave year when you need to make corrections. It also improves error reporting so processing issues can be reviewed together instead of stopping the process one issue at a time.

This update is intended for HR and payroll administrators who manage leave year-end processing. On the Close Leave Year screen, Process Type defaults to Close Leave Year, and Reconciliation Method defaults to Costpoint Reconcile Leave Balance. When multicurrency is enabled, the New Balance Method and Payout Method options are hidden and default to the current leave year hourly amount. The enhancement also adds acknowledgement requirements so you must confirm key processing conditions before you close or reverse a leave year.

You can reverse a previously closed leave year only when the leave cycle is eligible for reversal. The adjustment fiscal year, period, and subperiod must be available for data entry, and reversal is not allowed after at least one leave type has been transferred in the new leave year. The process also warns you when leave accruals, manual leave adjustments, or payout activity exist in the new leave year.

 

Close Leave Year (LDPCLSLVYR)

On the Close Leave Year screen, you can now choose whether to close a leave year or reverse a previously closed leave year, review clearer processing options, and generate redesigned reports that make year-end leave processing easier to review.

• You can use the Process Type option to choose Close Leave Year or Reverse Close Leave Year on the Close Leave Year screen.

• The screen now shows separate processing options for New Balance Method, Payout Method, and Reconciliation Method so you can see how your selections affect leave processing and General Ledger adjustments.

• When you select Reverse Close Leave Year, the screen hides the current and new leave year fields, populates the reversal values from the most recent eligible close leave year instance, and requires you to acknowledge the reversal impact before you continue.

• When you select Close Leave Year, the screen populates the current and new leave year information for the selected leave cycle and enables the processing options that apply to closing the leave year.

• The enhancement adds reverse close leave year functionality so you can reverse previously posted close leave year results and then rerun the process after you make corrections.

• The process now records successful close and reverse runs in a new audit table so Costpoint can track the parameters used for each run and associate reversal activity with the original close leave year process.

• The Close Leave Year report has been redesigned to improve readability.

• The process now uses an expanded error report so you can review processing errors and warnings together before you continue.

• If errors are found and the error report is generated, only the error report is displayed until you resolve the issues.

• The enhancement adds reverse processing reports, including the following:

• Leave Balance Deleted Records Report

• Leave History Reversed Records Report

• Employee Leave Deleted Payout Records Report

• General Ledger Reversal Report

• The General Ledger report format has been updated so that close and reverse processing use the same layout.

• The process can now create General Ledger adjustments for new leave year balance differences, payout differences, and negative carryover balances based on the selected processing method.

Costpoint provides the ability to define timesheet default values based on a combination of project and pay type. This enhancement introduces a new level in the defaulting hierarchy that allows you to configure defaults specific to both a project and its associated pay type.

Previously, timesheet defaults could be defined only by project or other existing levels. This enhancement improves configurability by enabling more precise defaulting for different labor scenarios.

This enhancement enables you to:

• Define different default values for the same project based on the pay type.

• Support billing scenarios where labor rates vary by pay type.

• Reduce manual entry and improve accuracy in timesheet processing.

This functionality is particularly useful when separate accounts or classifications are required for regular, overtime, or other pay types.

 

Manage Project/Pay Type Timesheet Defaults (LDMPPTD)

A new Manage Project/Pay Type Timesheet Defaults screen is available in the People » Labor » Timesheet Defaults menu, located below the Manage Project Timesheet Defaults screen.

You can use this screen to define default values for a specific combination of project and pay type.

You can configure defaults for the following fields:

• Account

• Organization

• Labor Location

• Withholding State

• Reference 1

• Reference 2

The Apply to Lower Levels option allows you to apply the defined defaults to lower-level projects within the selected project hierarchy.

Note: The Manage Project/Pay Type Timesheet Defaults screen is not available if Union functionality is enabled. The Reference 1 and Reference 2 fields may be hidden depending on licensing.

 

Pay Type and Project Combination Defaulting Hierarchy Update

Costpoint adds a new defaulting level for project and pay type combinations. The new level is processed after Manage Project Timesheet Defaults screen in the timesheet defaulting hierarchy. This updated hierarchy allows Costpoint to evaluate project and pay type-specific defaults before proceeding to lower-priority default sources.

The updated hierarchy is:

• Level 1: Manage Timesheet Line Type Defaults screen

• Level 2: Manage Employee Timesheet Line Type Defaults screen

• Level 3: Manage Employee Project Timesheet Defaults screen. Set up defaults based on a project for a specific employee.

• Level 4: Manage Employee Proj-Acct-Group Timesheet Defaults screen. Set up defaults based on the project account group for a specific employee

• Level 5: Manage Labor-Group Proj-Acct-Group Timesheet Defaults screen. Set up defaults based on a project for a specific Labor Group Type within an Account Group

• Level 6: Manage Project Timesheet Defaults screen. Set up defaults based on a specific project

• Level 7: Manage Project/Pay Type Defaults screen. Set up defaults based on a specific project and pay type combination.

• Level 8: Timesheet Defaults tab in Manage Employee Information screen. Set up default-related information about the employee who will be processed by the Labor module.

• Level 9: Manage Employee Salary Information screen. GLC and PLC will default from this screen.

• Level 10: Configure Labor Settings screen - Timesheet Line Defaults Group Box. Set up default Timesheet Cycle, Worker's Comp or Pay type.

The new project/pay type defaulting logic is triggered when you enter or update a pay type on a timesheet line. The Project field is not automatically populated by this enhancement.

 

Default Field Population

When both project and pay type are entered and a matching record exists on the Manage Project/Pay Type Timesheet Defaults screen, Costpoint can default values for the following fields:

• Account

• Organization

• Labor Location

• Withholding State

• Reference 1

• Reference 2

If a matching project/pay type default exists and one or more timesheet line fields already contain values, the screen will confirm with you before replacing existing information.

 

Application Updates

The new project/pay type defaulting logic is now incorporated into the following applications:

• Manage Timesheets (LDMTIME)

• Manage Correcting Timesheets (LDMCTIME)

• Create Auto-Pay Timesheets (LDPDUMTS)

• Import Timesheets from Deltek Time and Expense (LDPUPET)

• Import Timesheets (AOPUTLTS)

• Create Employee Allowance Timesheet Lines (LDPADD)

• Create Leave Payout Timesheets (LDPLPTS)

These applications now include an additional defaulting step that evaluates project/pay type defaults when applicable.

 

Database Updates

A new LAB_PROJ_PT_DFLT (Project Pay Type Timesheet Defaults) table has been added for this feature:

• This table stores timesheet default values based on project and pay type combinations.

• Records are used only when both project and pay type are specified on the timesheet line.

• Data is maintained by users through the new application.

The Print Data Dictionary Report screen has been updated to include this new table.

Costpoint now enables you to add and update employee address information through a guided, conversational interface in Ask Dela or Microsoft Teams. This capability reduces the need to navigate multiple application screens and streamlines address maintenance for both Human Resources (HR) administrators and employees.

You can enter natural language prompts to manage address information from the Manage Employee Information screen in the Employee module or the Address/Phone screen in Employee Self Service. Dela then guides you through the process and helps complete the requested update.

You can use prompts such as the following:

• Add a new address for Alex Morgan.

• Update my address in Colorado.

• Change Taylor Lee’s home address.

• Update my apartment number.

Access to this capability depends on your application or module permissions. HR administrators can update employee address records, while employees can update their own address information through self-service. All updates follow existing validation rules and audit tracking. In certain scenarios, such as vendor-linked employees or payroll state changes, Costpoint may require additional confirmation or processing.

This enhancement does not allow updates to inactive or terminated employees without confirmation and does not support direct deposit updates due to privacy considerations.

HR administrators and users with the right access can now update an employee’s salary, job title, and manager through Ask Dela in a guided conversation, including from Microsoft Teams. This reduces the need to open the Manage Employee Information screen or the Manage Employee Salary Information screen to make routine updates and helps you complete employee record maintenance faster.

Access to this enhancement follows your existing security setup. To update Annual Amount, Payroll Salary Amount, or Hourly Amount, your user ID must have Suppress Labor cleared in Company Rights for the login company, and you must have full rights either for the applicable screen or for the Employee module. When Dela saves a change through chat, Costpoint uses the same validation and defaulting logic that runs when you update records on the Manage Employee Salary Information screen.

This enhancement also improves auditability of AI-driven updates by recording agent usage when data is added or changed through Ask Dela or Teams. If you do not have an existing salary record for an employee, you must first create one on the appropriate screen; and if you have Labor Suppression enabled, you cannot change salary amounts through Ask Dela.

 

Manage Employee Information (LDMEINFO)

On the Manage Employee Information screen, you can initiate employee updates through Ask Dela and complete the update flow in Teams or in Costpoint as needed. The following are the updates:

• Ask Dela now supports updating an employee’s salary, job title, and manager through a guided conversation, reducing the need to manually locate and edit employee records on this screen.

• Ask Dela prompts you to confirm the employee and the requested changes, asks for an effective date when needed, and can provide a link to review the updated record.

• If an employee has no existing salary records, Ask Dela directs you to open the appropriate screen and enter a new salary record first.

• If you attempt to update your own salary record through Ask Dela, it blocks the update.

 

Manage Employee Salary Information (LDMEHIS)

On the Manage Employee Salary Information screen, Ask Dela can update salary details using the same validations and defaulting logic you get when you update records directly on this screen. The following are the updates to the application:

• Ask Dela now allows authorized users to update salary details such as Job Title Description, Detail Job Title code (HR license only), Annual Amount, Hourly Amount, and Manager through chat-driven confirmations.

• When you request salary changes, Ask Dela prompts you to update the current record or create a new record, and it can clone the most recent record when creating a new one.

• When you change Hourly Amount, Ask Dela confirms whether you also want to recalculate related salary amounts based on work hours and pay cycle details.

• When you change Annual Amount, Ask Dela can confirm whether you also want to recalculate related salary amounts based on work hours and pay cycle details.

• When HR licensing applies, Ask Dela validates Detail Job Title code against valid job title codes and provides an error message with valid options if the entered value is not valid.

• When you update the manager for an employee under HR licensing, Ask Dela can warn you when the selected manager is not assigned to the employee’s organization, based on your personnel defaulting method configuration.

• Ask Dela uses standard confirmation messaging for data changes and presents Continue and Stop options before saving updates.

• If you have Labor Suppression enabled and request to change salary amounts, Dela informs you that you do not have rights to change those fields.

• If you request changes for a terminated or inactive employee, Dela informs you of the status and asks whether you want to continue.

• When audit tracking is enabled and Dela saves the change, Costpoint records the update in audit history and saves the agent identifier as the transaction source for the update.

 

Print Data Dictionary Report (SYRDD)

On the Print Data Dictionary Report screen, the data dictionary now includes the new People-module AI agent usage table that tracks AI-driven updates. The following are the updates to the application:

• The data dictionary now includes the PE_AI_AGENT_ADT table, which stores usage records generated when an AI agent modifies data within a People module screen.

• The new table definition includes columns for agent identifier, updated table name, modify type, modifying user, timestamp, and row versioning as documented in the design specification.

 

This enhancement requires the following:

• cp82_cmnlib_ldmeinfolib_004.zip

• cp82_dbc_820_12100_001.zip

• DeltekCostpointMaintenanceRelease_8.2.15.5009.exe

You can now selectively override specific Costpoint ceiling calculation routines for Project Budgets / EACs by using override checkboxes on the Revenue Setup subtask. This feature enables Planning to ignore hours, burden, or cost ceiling enforcement logic during revenue calculations for forecast periods, without affecting other budget/EAC versions. The enhancement simplifies long-range planning for incrementally funded contracts and reduces the need to duplicate budget/EAC versions or modify ceilings in Costpoint projects.

The following checkboxes have been added to the Revenue Setup subtask:

• Override Burden Cost Ceilings

• Override Direct Cost Ceilings

• Override Hours Ceiling

By default, all override checkboxes are cleared. To enable these options, select the Override Settings checkbox. When these checkboxes are selected, Planning ignores the associated ceiling routines during revenue calculations for forecast periods. These overrides affect reports in Analysis by Period and Revenue Analysis.

Note: Override selections apply only to budget/EAC versions with a Working status. Newly created budget/EAC versions inherit the override settings from the source version. Changes to override settings do not affect previously created versions.

A new Budget & EAC Summary Comparison application was added under Planning » Project Budgeting » Supplemental Reports. This report allows you to view budget and EAC values side by side across all relevant WBS levels, including project, task, labor category, and resource. It enables quick comparisons between planned (Budget) and expected (EAC) outcomes without switching screens or manually reconciling data.

Key Features:

• Side-by-Side Display: View Budget (Hours, Amounts) and EAC (Hours, Amounts) in adjacent columns, with automatically calculated variance columns (Hours Variance, Amount Variance).

• Version Controls: The default view uses the Final version set for both EAC and BUD. Use filters to select specific budget or EAC versions.

• Drill-Down Navigation: Expand WBS levels to the lowest level supported by your project, including labor categories, employees, and vendors.

• Filtering: Filter the report by Project ID, Fiscal Year, and Budget/EAC Version.

• Security and Access: The report follows the configuration settings in Planning Org Security or CP Admin Org Security, so you can view only the projects you have access to.

The Project Budgets / EACs application now visually flags the health of each EAC using color-coded statuses. These indicators are based on factors such as overspend risk, delays, and frequent changes, enabling you to quickly identify budgets that require attention.

A new EAC Health Indicator column has been added to the Project Budget Status table. This column evaluates the status of each version using five key variance signals:

• Budget Revenue

• Hours

• Raw Cost

• Burdened Cost

• EAC Age

The EAC Health Indicator column displays one of the following statuses:

• Green (Healthy): Variance is within acceptable limits, and the EAC is actively maintained.

• Yellow (Warning): Variance is trending toward risk, and updates are infrequent.

• Red (At Risk): Major variance is detected, and the EAC is stale.

 

New EAC Health Indicator Subtask

A new EAC Health Indicator subtask provides detailed visibility into how Costpoint calculates EAC health. It displays a variance comparison between the selected EAC version and the final project budget, and it includes the calculation of EAC age.

The subtask includes the following fields:

Field	Description
Description	This field displays the five variance signals used to calculate EAC health.
Variance	This field displays the calculated variance between the EAC and the final BUD.
Variance %	This field displays the variance percentage based on the calculated variance and the final BUD.
Status	This field displays the color-coded EAC status.

 

Related Updates

EAC Health Inquiry via Ask Dela

Ask Dela now supports EAC health queries. It identifies EAC health inquiries and retrieves relevant data. Health information is sourced from the Project Budgets / EACs application and the EAC Health Indicator subtask. Dela provides system-calculated EAC health values and does not perform calculations or modify data. For projects with multiple EACs, Dela can summarize health across versions.

Important: For the initial query, include “EAC Health” or use the terms “Estimate,” “Completion,” and “Health” (in any order) to improve AI-driven insights.

Note: A link to the EAC Health Indicator subtask is always included in Dela’s response.

Pending calculations, such as pending approvals or pending values, are now computed and displayed consistently across all Planning experiences, including budget, EAC, dashboards, and reports. This ensures that you can trust the accuracy of the data you see, enabling confident and informed budgeting and EAC decisions without confusion caused by inconsistencies.

A new Pending Data Source option is available on the Integration tab of the Configuration Settings screen. This field enables you to select the source for pending calculations:

• Costpoint Job: Uses pending calculations based on the selected Costpoint Unposted Options in Projects » Project Inquiry and Reporting » Report Processing» Update Pending Report Tables

• Real Time: Includes all pending charges in the calculation.

This enhancement affects the results of the following reports:

• Project Revenue Analysis (BNP_CAQXPTR)

• My Budgeted Hours - Detail (BNP_SRQPMBH)

• Pending Details by Org (BNP_SRQSOA2)

• Org Job Summary (BNP_SRQSOA3)

• Project Status (BNP_SRQSPA5)

• Pending Charges (BNP_SRQSPA8)

This enhancement enables deeper analysis, such as predictive trend modeling, compliance auditing, and issue troubleshooting. It also gives AI the ability to evaluate how budgets evolve over time, offering insights into client behavior and system usage.

Key Benefits:

• Predictive and Trend Analysis: Identify patterns, forecast budgets, and detect anomalies.

• Baseline Comparison: Compare original budgets with final versions to evaluate performance.

• Auditing and Compliance: Track user activity to ensure processes follow established standards.

• Development Troubleshooting: Recreate client inputs and restore deleted data to resolve issues efficiently.

In the previous release, budgeting by units was implemented in Project Budgets / EACs and the top-level reports. Phase 3 extends this functionality to the level-down report, increasing visibility into how units affect budgeting and reporting.

In the Level Down Projects Future Revenue application, a Units option is now available in the Cost Type lookup. This option enables you to view unit-based revenue calculations with existing revenue breakdowns.

An expandable Units row is also available in the Revenue Breakdown sub report, where Units data displays when available.

Ask Dela is expanded in the Project Budgets / EACs application in this release. This feature provides a context-aware assistant that delivers smart suggestions, key updates, and data insights based on your current screen and project context. It enables you to take timely action, reduce manual guesswork, and maintain accurate, compliant, and up-to-date project financials.

When you open a budget or EAC, Dela provides default suggestions to help streamline your workflow, including:

• EACs Needing Update: Identifies estimates at completion (EACs) marked as Final version that require updates to keep forecasts aligned with current project progress. This helps prevent outdated cost projections and supports proactive financial control.

Note: Use the words “estimate,” “completion,” or “EAC” to help trigger AI-driven insights.

• Pending Approvals: Highlights project budget and EAC items that are awaiting approval to help prevent workflow bottlenecks and delays. This supports timely execution, compliance, and accuracy in project financial management.

Note: You can filter by project's EAC or BUD. Use the words “project” and “budget” to help trigger AI-driven insights.

 

New Budget Analysis Application

In support of AI functionality, a new Budget Analysis application was added under Planning » Project Budgeting » Active Level Reports. You can run and view the report by selecting a project or by using the link to the application included in Dela’s response.

Note: You do not need to open the Budget Analysis application to use Ask Dela.

The images in the table below show example Dela responses.

Prompt	Example Image
What are the EACs needing update?
Show me project budget pending approvals.

Costpoint now enables you to convert an employee’s hourly cost from the paid currency (transactional currency) to the company’s functional currency. This ensures that budget and report costs are displayed consistently in the functional currency, which improves accuracy and simplifies financial analysis.

A new Convert rates using Multicurrency option was added to the General tab of Configuration Settings. By default, this option is disabled.

When this option is enabled, Costpoint retrieves the employee’s Currency option in the Manage Employee Salary Information application (People » Employee » Basic Employee Information » Manage Employee Salary Information » Salary Info) and the company’s Functional Currency in the Set Up Company application (Admin » System Administration » System Administration Controls » Set Up Company). Costpoint then applies the applicable exchange rate from the Currency Schedules application in Time & Expense » Expense » Expense Controls to convert hourly costs for use in budget calculations and reports.

For example, if an employee is paid in EUR (€) and the functional currency is USD ($), with an hourly cost of €50 and an exchange rate of €1 = $1.10, Costpoint calculates the cost as $55 per hour for all budget calculations and reports.

The New Business Budgets application now includes budget by unit functionality, similar to the Project Budgets / EACs application. Enhancements have been made to Revenue Setup/Ceilings, Revenue Analysis, and Analysis by Period subtasks to incorporate unit-based budgeting. Additionally, a new Units subtask has been added to streamline unit-specific budget management. These updates provide greater flexibility and precision in tracking and analyzing budgets by unit.

 

Units Added to Revenue Setup/Ceilings Subtask

New fields were added to the Revenue Setup subtask to streamline revenue calculations. The subtask now supports unit-based budgeting to improve budget configuration.

Field	Description
Units	This is a new budget category that allows you to choose how you want Costpoint to calculate revenue. You can select Rev on Cost, Rev on Burden, or Fee on Cost/Burden. Note: This applies only to New Business Budgets with a Working status.
Use Unit Price	Select this checkbox to calculate revenue using the unit price from the Contract Line Item Number in Projects » Project Setup » Unit Pricing Information » Manage CLIN Information.

 

New Units Subtask

A new Units subtask is now available to improve revenue setup and ceiling configuration. This subtask automatically displays unit-related details based on the options you select during revenue setup, helping you ensure accurate and consistent data management.

The Units subtask includes the following fields:

Field	Description
Warnings	This field displays the number of warnings that occurred per record.
Item Type	Select the item type you want to enter. Choose from the following options: Contract Line-Item Number (CLIN) Price Catalog
CLIN/Catalog	Select the CLIN/catalog you want to enter.
Item	Select the item you want to enter.
Revision	This field displays the revision number of the resource.
Acct ID	This field displays the account ID of the resource.
Org ID	This field displays the organization ID of the resource.
Vendor	This field displays the vendor's name of the resource.
Subcontract No	This field displays the subcontract number of the resource.
Cost Per Unit	This field displays the cost per unit of the resource.
Unit Price	This field displays the unit price of the resource.
Rev	Clear this checkbox if you do not want revenue calculated on this resource.
Brd	Clear this checkbox if you do not want burden calculated on this resource.
Cost	Clear this checkbox if you do not want cost calculated on this resource.
Total	This field totals the numbers for each resource during the date range selected for the budget.

 

Revenue Analysis Subtask

A collapsible Units row was added to improve data organization and visibility. The Hours column label was updated to Hours/Quantity to more accurately reflect the values displayed. These updates introduce unit-based functionality, providing deeper visibility into revenue insights.

 

Analysis by Period Subtask

A collapsible Units row was added to improve data organization and visibility. The Hours column label was updated to Hrly Rate/Unit Price to more accurately reflect its calculation requirements. This enhancement now supports unit-based analysis, enabling more detailed period evaluations.

 

Related Screen Updates

Mass Upload Project Budgets to Organization Budgets (BNP_BGMOUP)

You can now import unit-based accounts into Non Labor lines, with unit details displayed when available.

 

Audit Budget Group Details (BNP_OAQAOM4)

A new Units option was added to the Format drop-down list when you select New Business in Project.

 

New Business Budget Summary (Revenue/Cost) (BNP_NBQNBBS)

A new Units column has been added to the Top-Level subtask that displays total unit cost for New Business Budget. In addition, an expandable Units row has been added to All Cost Breakdown subtask, where Units data displays when available.

 

Multi-New Business Budget Consolidation (Revenue/Cost) (BNP_NBQMNBBC)

An expandable Units row has been added to All Cost Breakdown subtask, where Units data displays when available.

 

Structured New Business Budget Summary (Revenue/Cost) (BNP_NBQSNBBS)

An expandable Units row has been added to All Cost Breakdown subtask, where Units data displays when available.

 

Create Project Budget from New Business Budget (BNP_NBQNPI8)

New Business units have been added when creating a project budget from a new business budget.

Powered by Dela, Costpoint now detects anomalies in cost pools and indirect rates. When you compute pool rates, you can select the new Run AI Analysis checkbox on the Compute/Print Pool Rates screen to evaluate rate calculations and pool balances against historical patterns and identify anomalies before journal entries are created.  

You can then review flagged variances as well as compare current and past pool data on the Pool Analysis Inquiry screen, where AI-generated summaries provide context so you can investigate and resolve issues more efficiently. To access this new application, click Projects » Cost and Revenue Processing » Cost Pool Processing » Pool Analysis Inquiry.

The Compute/Print Pool Rates application now supports multi-user processing, allowing users in different companies to execute processes concurrently. If two users within the same company try to start the process, one of the users will get an error message.

You can now prompt Ask Dela, or use the Costpoint Microsoft Teams app, to create new projects. This is phase 1 of a multi-agent process to set up a fully functional project in Costpoint with all possible applications completed. 

To create a new project, you can copy an existing project or define required fields and project structure, with support for building and validating the project WBS through a conversational workflow. After creating a project, Ask Dela provides a link to Manage Project User Flow that displays all project IDs that were set up. 

 

To learn more about using Ask Dela for projects, click the Help icon on the Ask Dela window, navigate to the Projects section, and watch the Projects overview video or click any of the suggested prompts. 

The revenue formula has been added to the model for the Project Status Report (PSR). This update displays Revenue Formula at the revenue level on the PSR, providing greater transparency and clarity for revenue calculations.  

Nonconformance Dashboard

 

The Nonconformance Dashboard is now available in BI, providing a centralized view for monitoring nonconforming materials, analyzing trends, identifying impacted orders, and evaluating average days to disposition. Built on the Materials BI Package, the dashboard includes key performance indicators (KPIs), Pareto analysis, summary views, and order impact details to support faster decision-making and more effective material management. The Nonconformance Dashboard is available in Team Content » Materials.

Automated User Group Mappings for Standard BI User Groups

 

The Utilities program now automates user group mappings for the standard BI user groups. This enhancement builds on the capability setup automation introduced in 2026.2 and reduces the manual effort required for both Deltek Cloud teams and on-premises customers. By eliminating the need to add members to each Costpoint group before mapping, the update streamlines setup and helps reduce the risk of manual errors.

Report Views Added to Billing Folder for Core Accessibility

 

Report views for Goods List, Parts List, Services List, and Item Vendors have been created from their source locations and made available in the Billing folder. This ensures accessibility to these reports as part of the core Product Definition, even though their original locations are tied to an add-on module.

Workforce Start and End Dates Added to Projects Package

 

Workforce start and end dates have been added to the Projects package within Project Reporting. This addition provides greater visibility into workforce timelines, enabling more accurate tracking and planning for project resources.

New Active/Inactive Flag for Project Account Groups in Projects Package

 

The Account Group Active (Y/N) active/inactive flag has been added for project account groups in the Projects package. This update makes it easier to identify active and inactive entries, improving visibility for project reporting and management. 

New Vendor Columns

 

Additional columns have been added to Vendor in the Accounts Payable package. New columns include LGBTQ+ Owned, Punchout Vendor, Punchout Maximum Amount, Punchout Vendor Enabled (Y/N), Invoice Integration (Y/N), Invoice Notification (Y/N), Invoice Notification Email (Y/N), Vendor Status, and SM Subcontractor (Y/N). The CMMC Level column has been removed. In addition, the Subcontractor (Y/N) column has been renamed Payment Control (Y/N) to align with the naming used on the Manage Vendors screen.

New Billing User Group Status Fields

 

The Billing Group Active (Y/N) field has been added to the Billing package to indicate whether a billing group is active. In addition, the Billing Group Active (Y/N) field and the Bill Group Description field have been added to the Project Reporting package. These updates improve visibility into billing group status and strengthen the organization of billing-related data across packages.

New Manage Manual Checks Application Fields

 

The Manage Manual Checks application now includes three new fields to support payment tracking and data entry. The Payment Transaction Type field identifies the payment source, such as EFT, check, wire, or credit card. The Payment Reference Code field captures authorization numbers or longer check numbers for payment tracking. The Additional Notes field lets you record supplemental information related to the manual check. Together, these additions provide more complete payment details and improve manual check recordkeeping.

New Project Status Details Fields in Project Planning Reporting Package

 

The Project Status Details (EREPORT_PROJ_DETAIL) table now includes additional fields to support project planning reporting. These fields provide more detailed budget and actual amounts for allowable and unallowable costs, including burdened amounts and unposted transactions. 

• LINKED_BGT_ID 

• LINKED_BGT_NAME 

• BUD_ALLOW_COM_AMT 

• BUD_ALLOW_BURD_AMT 

• BUD_UNALLOW_COM_AMT 

• BUD_UNALLOW_BURD_AMT 

• ACT_ALLOW_BURD_AMT 

• TGT_ALLOW_BURD_AMT 

• ACT_UNALLOW_BURD_AMT 

• TGT_UNALLOW_BURD_AMT 

• UNPOSTED_TGT_ALLOW_BURD_AMT 

• UNPOSTED_ACT_ALLOW_BURD_AMT 

• UNPOSTED_TGT_UNALLOW_BURD_AMT 

• UNPOSTED_ACT_UNALLOW_BURD_AMT 

These additions provide greater detail for tracking and analyzing project budgets and actuals, supporting more comprehensive financial reporting and decision-making.

You can now calculate Start/Stop Summary time in minutes, benefiting from greater accuracy in entering time when Start/Stop Detail cannot be used, such as when premium pay is also required. This helps prevent rounding-related validation issues that can occur when saving timesheets and improves accuracy for organizations that rely on start and stop time entry.

This option is enabled when the Calculate Start/Stop Time in Minutes checkbox is selected in Timesheet Classes (Time » Timesheets). With the checkbox selected, you can specify a starting date in the associated Effective Date field. The Start/Stop Summary option must also be selected from the Entry Mode drop-down.

The update also extends minute-based visibility to timesheet review areas through the addition of a Minutes column, so managers and approvers can see the same level of detail on the Manage/Approve Timesheets screen and related timesheet views. Together, these changes improve consistency across time entry and review, reduce confusion caused by rounded values, and support more accurate payroll and approval processes.

Managers can now review and approve employee leave requests directly in Dela. This allows managers to take timely action from one place without needing to switch between multiple systems.

Note: For a general introduction to Ask Dela, see the Introduction to Ask Dela video available on the Deltek Learning Hub, which includes, for example, instructions on adding Costpoint to Teams.

The images below provide examples of the types of questions that will help you accomplish these tasks.

Task

Example Image

Approve or Reject Leave Requests

The images below provide an example of the leave approval process through Dela, but the process is similar for rejecting leave.     Note: The ability to request a specific timeframe of leave requests or choose a list or range of leave request numbers does not yet exist.   Choosing a single leave request number from the returned list allows you to either approve or reject that request. For example:   Dela provides the option to enter notes and confirms your request. For example: