I would like to gather suggestions on how we cam handle intercompany transaction under a single Job in Acumatica? Also, looking to restrict the visibility of for instance, Company A data to not be visible under Company B and Vice Versa.
What could be best practice?
Best answer by aryanjadhav50
Hi
In Acumatica, projects are company-specific, so the best practice for intercompany work under one job is to create a mirror project in each company and use intercompany AR/AP transactions to move costs between companies. Each company records its own expenses in its own project, and intercompany billing is used to transfer charges. Billing rules can be configured on the Billing Rules (PM207000) form to control time and material or progress billing .
To restrict visibility, keep each legal entity as a separate company and control access through roles and user company assignments. Users should only be granted access to their respective company (and branches if applicable) to ensure Company A data is not visible in Company B and vice versa.
Hope this helps.
Hi
In Acumatica, projects are company-specific, so the best practice for intercompany work under one job is to create a mirror project in each company and use intercompany AR/AP transactions to move costs between companies. Each company records its own expenses in its own project, and intercompany billing is used to transfer charges. Billing rules can be configured on the Billing Rules (PM207000) form to control time and material or progress billing .
To restrict visibility, keep each legal entity as a separate company and control access through roles and user company assignments. Users should only be granted access to their respective company (and branches if applicable) to ensure Company A data is not visible in Company B and vice versa.
Hope this helps.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
