# Deltek Costpoint Audit Trail Report for DCAA Readiness > Source: https://netray.co/erp-help/deltek-costpoint-audit-trail-report > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer Costpoint can record who changed which data and when, but audit trail coverage is something an administrator configures per table and field, so the first step is to confirm what is being tracked. Once enabled, you report on changes through the audit or change-tracking reporting in your release, and pair it with transaction history, timesheet change records and security reports for a complete DCAA story. ## Kind how-to ## System deltek ## Erp Deltek Costpoint ## Module Audit / Compliance ## Query deltek costpoint audit trail report ## Alternate Queries - costpoint audit trail dcaa - costpoint who changed record - costpoint audit log report ## Applies To Deltek Costpoint 7.x and 8.x; audit and change-tracking options and report names vary by release and configuration ## Steps ### Getting an audit trail you can show an auditor **Items:** - List the records auditors care about: timesheets and corrections, funding and contract values, rates, vendor and employee master data, journal entries, and security changes. - With your administrator, confirm which of these have audit tracking switched on and for which fields. - Enable tracking for the gaps in non-production first, check volume and performance, then enable in production. - Run the audit trail or change-tracking report for a test change and confirm it shows user, date and time, old value and new value. - Combine with timesheet audit information, transaction history and user security reports as relevant. - Set a retention rule so audit records are kept as long as your policy and contract require. - Restrict who can change tracking settings or purge audit data, and review that access. - Document the procedure so you can produce the evidence quickly during an audit. ## Sections ### What auditors actually want to see **Body:** A DCAA-minded reviewer wants evidence that labor and cost records cannot be changed without leaving a trace. For timesheets that means original entry, each correction with reason, who made it and who approved it. For master data it means who altered a rate, vendor bank detail or funding amount. A report alone is not a control. The control is the combination: tracking enabled, access restricted, review performed, and evidence retained. Be ready to show an example of a changed record flowing from change to report, because that demonstrates the system rather than a policy document. ### Configuration, volume and retention **Body:** Tracking every field on every table is rarely sensible. It increases storage and slows heavy processes. Choose tables and fields with compliance value, and review the volume after a month. Archive old audit data on a schedule rather than letting it grow unmanaged. Retention should follow your contract and records policy, not storage convenience. Purging audit data casually defeats its purpose, so restrict who can do it and log that action too. ### Reporting patterns that save time **Body:** Prepare saved report parameters for the common requests: all changes to a project's funding, all timesheet corrections for a period, all changes by a given user, all changes to vendor bank data. Auditors tend to ask the same questions, and having the answer ready is the best signal of a mature control environment. Combine audit output with the incurred cost submission process, since the same records support rate and cost reviews. See the ICS preparation page for how those come together. ## Pitfalls - Assuming audit tracking is on everywhere when only a few tables are covered. - Enabling tracking in production without testing the performance effect. - Letting users with broad admin access change or purge audit data. - No retention rule, so evidence disappears or storage balloons. - Producing a report without being able to show the control around it. ## Ai Angle An assistant grounded in Costpoint can answer audit questions in plain language: show every funding change on this project this year, or list timesheet corrections by one supervisor. ERPray is read-only, shows the query behind the answer and respects roles. Because audit data is sensitive, Netray deployments run on your own infrastructure, with no copy leaving your boundary. Formal audit submissions still come from your controlled reports. ## Faq ### Does Costpoint have an audit trail? **Answer:** Yes, Costpoint supports tracking of changes, but what is tracked depends on configuration. An administrator enables auditing for chosen tables and fields. Confirm your coverage and test that a changed record produces user, time, old value and new value. ### What audit evidence does DCAA expect for timesheets? **Answer:** The original entry, every correction with a reason, who made it and who approved it, retained for the required period. Costpoint's timesheet audit information and change tracking support this, but your procedures and access controls must complete the picture. ### Can audit trail data be deleted? **Answer:** It depends on who has access, which is why you should restrict purge and tracking-setting permissions and log their use. Retain audit data per your contract and records policy so evidence is available when requested. ### Does turning on auditing slow Costpoint down? **Answer:** It can, mainly when tracking many fields on high-volume tables. Enable it selectively for compliance-relevant data, test in non-production, and monitor storage and processing times after enabling it in production. ## Search terms deltek costpoint audit trail report, costpoint audit trail, costpoint dcaa audit, costpoint who changed record, costpoint timesheet audit, costpoint change tracking, costpoint audit log, costpoint dcaa compliance --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json