Inter-Entity Transactions FAQs

The integration Tab lets you determine what data to include in the G/L Entry Description, G/L Detail Reference, G/L Detail Description, and G/L Detail Comment fields in general ledger transactions when using IET Triggers.  

Direct routes between entity 1 and entity 2 can be setup as well as more complex, indirect routes using multiple links between entity 1 and 2 (i.e. from entity 1 to entity 3, from entity 3 to entity 4, from entity 4 to entity 2).

Transaction routes are used by the Inter-Entity module to generate the balancing transactions. You can setup direct or indirect routes.

Use IET Triggers with G/L Target Account Substitution optional field configuration to map to different accounts in each target entity, even with completely different Chart of Accounts.

At least one segment (not the account segment) must be used to define which entity each account belongs to. For details, refer to Segments Tab

Inter-Entity supports the latest security changes in Sage 300 version 2023 PU3 and above.

When using Inter-Entity Transactions across multiple databases, it is helpful to use Source Types to monitor and identify transactions created by Inter-Entity Transactions in both the source company and in the target companies.

The Consolidated AP Aged Trial Balance Report provides a consolidated Open Aged Payables view across all on-line databases as defined in Inter-Entity Database Mappings icon.

Requirement! Inter-Entity Transactions Multi Edition

The Consolidated AR Aged Trial Balance Report provides a consolidated Open Aged Receivables view across all on-line databases as defined in Inter-Entity Database Mappings icon.

Requirement! Inter-Entity Transactions Multi Edition

Inter-Entity(IET) doesn't support GL Account Code change. The GL Accounts in Inter-Entity setup will not be updated. The main reason is that Inter-Entity relies on the segment structure and wildcard characters, and those settings cannot be mapped directly in GL Account Code Change.

Depending on what is changing in your Chart of Accounts and how your Inter-Entity is configured, different IET configurations will need to be updated.

Inter-Entity Transactions and Trade are triggered for transactions entered on the web screens. There are currently no web screens available for Inter-Entity. You need to use the Sage 300 desktop for Inter-Entity setup and inquiry screens.

The IET Account Balance Inquiry provides the balances for the Inter-Entity Accounts as set up in the Linked Accounts screen. 

This screen allows you to select a Year/Period, a Currency Type and Currency Code, and shows you the balances of all the GL Accounts set up in IET Linked Accounts across multiple databases.  For details, see Linked Accounts .

If all the associated IET G/L Batches are posted in all companies then these accounts will be in balance.

Inter-Entity Audit Inquiry displays the history of the Inter-Entity transactions. This screen displays transactions that are waiting to be processed (pending), those that have been processed (exported) and those that have not been processed due to an error (error).

XAPI errors relate to problems connecting to an external Sage 300 database. They can therefore occur with any multi-database product, including:

• Inter-Entity Transactions (Loan Account entry automation)
• Inter-Entity Transactions (G/L Triggers)
• Inter-Entity Transactions (Cash Management)
• Inter-Entity AP/AR Trade
• Inter-Entity OE/PO Trade

In order to run the consolidated Aged Trial Balance reports, you must: 

• Activate Inter Entity Transactions in the companies you want to run the Consolidated Trial Balances in.

• Configure those companies which you want to combine the AP and AR transactions into the source company using IET Setup>Entity Database Mappings in the source company.

• Copy the amended AP Aged Trial Balance reports and AR Aged Trial Balance Crystal Reports from the IY programs directory to both the AP and AR programs directory.

Tip: The following 3 options require users to have "Reprocess Exported Entries" Security Group. clearance: Process Exported Entries, Rebuild Audit Entries and Clear Exported Audit Entries.

Process Exported Entries: Use this to process re-process already processed entries for On-line and Remote Databases. You need to ensure the transactions are not in the target database before selecting that option (for example if you restore a backup for the target database before the transactions were processed in the source database).

Rebuild Audit Entries: Use this to process to rebuild audit entries.

Clear Exported Audit Entries: Use this process to clear the transaction data you no longer need. This will only remove transactions with the "Exported" status.