Before you start

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

3 minute read

Before setting up Pryme Intercompany, ensure that the following key considerations are addressed to facilitate smooth implementation and integration.

Party Code

All companies involved must agree on a unique intercompany partner identification code, referred to as the Party Code. This code helps identify each company within the system.
Establish a consistent and scalable naming convention. For instance, instead of using only a land code (e.g., “UK”), combine it with a number, such as “UK10,” “UK11,” and so on.

Data Conflicts

Ensure there are no data conflicts before setting up the app. Review and update existing entries to prevent 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. Decide whether one company will act as the central master data provider for the entire group or if each company will manage its own master data. In the case of 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 to be shared.
Field-Level Restrictions or Filters: Ensure any necessary restrictions, filters, or field-level mappings are identified and implemented.
Code Harmonization: Check if consistent coding schemes are used across the companies for master data. If not, align and update the codes to ensure consistency throughout the group.

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

Ensure that related tables required for importing data are included in the master data setup. This will prevent data errors due to missing or incorrect data and save time during setup.

Transfer Time, Expense, and Item Entries Between Companies

The Pryme Intercompany Project App includes two predefined templates for transferring time entries and project ledger entries. These templates can be used individually or together.

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, approve them, and add comments in an approval flow for informational purposes only.
After posting, project ledger entries are created in both the performing and selling companies.

Limitations:

Only time entries will be transferred. Entries moved between projects using Move Entries or a Project Journal will not be transferred through intercompany automation, as they do not create time entries; only project ledger entries are created.

Project Ledger Entries Template