How to "restrict" what Branches can be used with Projects
Is there an ability to restrict or at least warn that the branch entered in whatever type of transaction is NOT consistent with the Default Branch recorded in the Project record? Example: Branch 200 is the Default Branch for Project 1022000 and should always be recorded as a Branch 200 transaction. The AP Clerk enters a bill and records the transaction to Branch 100 Project 1022000, is it possible that either a "warning" or "error" notifies the AP Clerk that the transactions cannot be saved because of issue with the Branch/Project configuration and prompts a correction prior to Release and Posting of transaction. To be applicable across all modules (i.e. Finance, Banking, Time & Billing, Payables, Receivables)
Does the AP clerk has access to both branches?
Here on AUGForums.com, most of the forums will now focus on reporting, with the exception of general topics in the Everything Else (click here) forum and the AUGForums.com Real Talk Podcast (click here) where we'll continue to focus on real Acumatica customer stories (click here if you'd like to participate).
For more info about how AUGForums.com compares to the new official Acumatica Community, checkout this post: