Before you start

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

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

Party Code

The Party represents Business Central companies that exchange data with other companies through messages.

  • All companies must agree on a unique party code. This code identifies each company in the system.
  • Use a clear and scalable naming convention, example: Instead of “UK,” use “UK10,” “UK11,” ….

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

Master Data

Decide how to manage master data across the group:

  • Will one company provide master data for all?
  • Or will each company manage its own?

If you choose a central provider, pick one company to share master data with the others. Key Considerations:

Tables to transfer:
Decide which tables to share. Ensure all 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.

Restrictions or Filters:
Identify and implement any necessary restrictions, filters, or field-level mappings.

Code Harmonization:
Ensure codes are consistent across companies. Align and update the codes if needed.

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

Pryme intercompany project includes two pre-defined templates for transferring ledger entries. The templates can be used individually or together.

Time entries - Time entries and resources.
Project ledger entries - Time, expenses and item ledger entries.

Before you start setting up the Topics and Subscriptions, decide which transactions you want to transfer, and which templates to use.

Time Entries Template

What it does:

  • Transfers time entries when timesheet is submitted in the performing company.
  • In the “selling company” the project manager can preview, approve and comment the entries until they are posted in the performing company.
  • After posting the time sheet in the performing company, project ledger entries are created in both companies.

Limitations:

  • Only transfers time entries, not expenses or item entries.
  • Entries moved between projects using “Move entries” or entries created in a project journal are not transferred.
  • If you re-open a posted time sheet, the changes are not transferred.

Project Ledger Entries Template

What it does:

  • Transfers posted project ledger entries for time, expense, and item to the project journal.
  • Creates project ledger entries in the selling company.

Limitations:

  • Project managers in the selling company can’t preview time entries before posting.
  • Is not transferring resources.

Combining Templates

To preview time entries (and use the approval flow) and transfer expenses and item entries, use the templates together.

  • Time Entries → Time and Resources
  • Project Ledger Entries → Expenses and Item Entries