Gathering Inter-Entity Transactions Data

After you activate Inter-Entity , you must add the data from your company's present system to Inter-Entity Transactions.

First, gather all your current Inter-Entity records. These can be manual records or printed listings and reports from other software

Tip: You may be able to enter Inter-Entity setup data by importing it directly from files created by another program. (e.g. linked accounts, transaction routes)

Questions to consider when planning Inter-Entity Transactions implementation

What types of transactions give rise to inter-company issues?

For example, do they involve expense / revenue allocations across companies or are there Bank Transfers, Cash Receipts / Cash Payments on behalf of related companies as well?

If bank entries are required, how many bank accounts are involved?

This determines how much set up is required under Options and how many Source Types need to be set up in the General Ledger.

How many companies will be initiating inter-company transactions

Are they part of one Sage 300 Company Database or are there more than 1 Company Databases?

Do inter-company transactions go directly between companies, or do some transactions clear through an intermediary company?

This determines how many companies you need to activate and configure Inter-Entity Transactions and Inter-Entity Trade, as well as how many Due To / Due From Loan Accounts, Linked Accounts and Transaction Routes you need to create.

Do you already have a G/L Segment for company in your chart of accounts?

If not, this will require the chart of accounts to be restructured to support at least one company segment that you can use to generate the Due-to and Due-from balancing entries on an inter-entity transaction.

If there are multiple company databases, are the Charts of Accounts the same across all companies or different?

Do you want to include accounts from 1 company in the chart of accounts of other companies?

This determines whether we need to restructure the Charts of Accounts to make them standard, or use the G/L Trigger “G/L Entity Substitution” to move transactions between company databases without the need to replicate the chart of accounts in each company.

It may also mean creating Optional Fields to use with G/L Triggers.