Recalled Time card showing up as Capex
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
5 hours ago
Issue: Recalled Timecards Reclassifying from OPEX to CAPEX
We are experiencing an issue where recalled timecards are being reclassified from OPEX to CAPEX, even though the original timecard and all associated cost plans are OPEX.
What we’re seeing:
- Original timecard is submitted, approved, and posted correctly as OPEX
- When a user or their manager recalls the processed timecard:
- The system creates a reversing (negative) expense line
- That reversing entry is classified as Labor – CAPEX
- The newly resubmitted timecard then posts again as OPEX, resulting in mixed CAPEX/OPEX actuals for the same labor
Why this is a problem:
- There are no CAPEX cost plans on the project
- The task, project, and resource cost type are all configured as OPEX
- This creates incorrect financial reporting and requires manual cleanup
- IT has stated that recalled timecards are “not automatically classified as CAPEX,” but the data clearly shows otherwise
Issue: Recalled Timecards Reclassifying from OPEX to CAPEX
We are experiencing an issue where recalled timecards are being reclassified from OPEX to CAPEX, even though the original timecard and all associated cost plans are OPEX.
What we’re seeing:
- Original timecard is submitted, approved, and posted correctly as OPEX
- When a user or their manager recalls the processed timecard:
- The system creates a reversing (negative) expense line
- That reversing entry is classified as Labor – CAPEX
- The newly resubmitted timecard then posts again as OPEX, resulting in mixed CAPEX/OPEX actuals for the same labor
Why this is a problem:
- There are no CAPEX cost plans on the project
- The task, project, and resource cost type are all configured as OPEX
- This creates incorrect financial reporting and requires manual cleanup
- IT has stated that recalled timecards are “not automatically classified as CAPEX,” but the data clearly shows otherwise
Request for Community Support:
We are looking for help from the ServiceNow community to better understand and resolve this behavior. If anyone has encountered a similar issue, identified a root cause, or implemented a configuration, script, or workaround to ensure recalled timecards retain their original OPEX classification, we would greatly appreciate your guidance. Any insight into whether this is expected behavior, a known defect, or a misconfiguration would be extremely helpful.
Thank you in advance for any support or direction the community can provide.
