Before you start

Things to do and consider before you start setting up the Pryme Intercompany app

3 minute read

Before diving into the setup of Pryme Intercompany, ensure that the following key considerations are addressed to ensure smooth implementation and integration.

Party code

All companies involved must agree on a unique intercompany partner identification code, also known as a Party Code. This code will help identify each company in the system.
Use a consistent and scalable naming system. For example, instead of just using a land code (e.g., “UK”), combine it with a number, such as “UK10,” “UK11,” etc.

Data conflicts

Ensure no data conflicts exist before setting up the app. Review and update existing entries to avoid issues.

Key Areas to Check:

Project numbers
Resource codes
Other shared references

Tip!

Use the company code as a prefix in the number series for projects to avoid overlap and improve clarity.

Master data

Determine how master data will be managed across the group. Will one company act as the central master data company for the entire group, or will each company manage its own master data? If choosing a centralized approach, designate one company to provide the master data to the others.

Key Considerations:

Tables to transfer - Identify which master data tables need sharing.
Field-level restrictions or filters - Ensure that any needed restrictions, filters, or field-level mappings are identified and implemented.
Code Harmonization - Do you have consistent coding schemes across the companies for master data? If not, align and update the codes to ensure consistency across the group.

If Pryme Intercompany for Projects is installed, exclude projects and resources from the master data, as these are managed by the app.

Make sure that related tables that are needed when importing data are included in the master data setup. This prevents data errors due to missing or incorrect data, saving time in the long run.

Transfer time, expense and item entries between companies

The Pryme Intercompany project app comes with two predefined templates to transfer time entries and project ledger entries. You can choose to use these templates individually or in combination.

Time entries Template

Functionality:

Transfers time entries to the External time entries table when timesheets are submitted by the performing company.
The project manager in the selling company can preview the entries, and can approve and comment the entries in an approval flow that is for informational purposes only.
After posting, project ledger entries are created in both companies (performing and selling).

Limitations:

Only time entries will be transferred. If you move entries between projects using Move entries or a Project journal, these will not be transferred through intercompany automation as they don’t create time entries; only project ledger entries.

Project ledger entries Template