A user can't type in a non-existent Job-Phase-Category when entering a Payables invoice, because an error message will pop up that prevents them from saving.

But they CAN enter a non-existent J-P-C when entering a JobCost Cost Batch, and Adagio won't complain (the Phase and the Category do have to exist but not the J-P-C estimate).

Even worse, when the cost batch is posted, JobCost auto-adds the non-existent J-P-C to the estimate table, and then posts the transaction!

This leads to all kinds of problems. You can say they should pop the Finder to confirm that the J-P-C estimate exists, but that won't help when they import cost batches from Excel. Even with the Validate box ticked, it still allows the import and posting of invalid J-P-C transactions.

Is there are way to: 1) validate that a J-P-C estimate already exists, or failing that, 2) stop JobCost from auto-adding the J-P-C and throw the invalid transaction into an error batch?

Thanks

Steve

Hello Steve,

I have added a suggestion to the wishlist for a future release.

Is there a workaround? It's SOO un-Adagio-like to allow invalid codes that then auto-add when posted.

Steve

Hello Steve,

No, there is no workaround.

This functionality has been in JobCost for Simple costing jobs since JobCost was first designed. It was in the original JobCost and it had to be supported in Adagio JobCost.

I have requests on the wishlist to add the same 'timesaving' feature to Payables and Receivables.

I don't have a problem with the functionality, but it should be optional.

Thanks for the clarification.

Steve

Hello Steve,

A new option to control the validation in JobCost Entry has been added in the JobCost 9.3A (2024.04.29) Upgrade just released. From the release notes:

There is a new Company Profile option on the Options tab under Data Entry Options, ‘Verify J-P-C for Simple Cost Tracking’. If this option is selected, new batch entries and timecards will require valid estimates in Batch or Timecard Entry and Import.