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 Inter-Entity to generate the balancing transactions with the configured loan accounts between entities.

Transaction routes are used in Inter-Entity Transactions and Inter-Entity (Cash Management).

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.

Autopost Exported Batches: Select Yes if you want batches created in the target company to be auto posted. Select No if you want the batch to be created in the target company, but not posted. 

The G/L batches resulting from bank entries created by Cash Management can be auto-posted, depending on the G/L Integration options in Bank Services.

Bank Setup G/L Integration Tab

Option 1: Configure the Create G/L Transactions by option to Creating and Posting a new batch

The resulting G/L Batches for all Bank Entries (both auto-created by Inter-Entity Transactions and manually entered Bank Entries) are auto-posted, except G/L Batches resulting from reversal bank entries created by Cash Management.

When posting a reversal in Bank Services, you get the error message "No active transactions allowed for auto-post."

This is because you have configured the G/L Integration option in Common Services > Bank Services > Bank Setup to "Create G/L Transactions by" to "Creating and Posting a New Batch".

Although you get the error above when posting an A/P or A/R reversal in Bank Services, Cash Management is actually creating the bank entries according to the configuration for banks configured in Cash Management. The resulting G/L Batch is created correctly. But you need to post the resulting G/L Batch manually.

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

Cash Management 1-step processing caters for bank reversals done in Bank Transactions. If using 1-step processing, Cash Management will generate the bank entries for the reversal in the source and the target companies.

If you use 2-step processing , Cash Management doesn't cater for A/P and A/R Reversals done in Bank Transactions. When A/P or A/R Transactions relating to a bank configured in Inter-Entity (Cash Management) two-step processing are reversed, A/P and A/R Credit Notes need to be manually entered in the target databases and applied to the A/P and A/R Invoices generated by Inter-Entity.

The default values in the Common Services -> Bank Services -> Bank Setup -> Bank Options > Processing tab should be blank as Cash Management will set the G/L Accounts based on the Inter-Entity transaction routes.

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.

Once Inter-Entity is configured, you can use the Sage 300Web Screens to enter transactions that trigger the Inter-Entity automation. This includes Inter-Entity Transactions, including Cash Management and Inter-Entity Trade for A/P-A/R and O/E-P/O transactions.

However, 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).

Common XAPI errors and resolutions

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.

Inter-Entity Cash Management Audit Inquiry displays the history of the Inter-Entity Cash Management transactions.

This screen displays transactions that are waiting to be processed (pending), those that have been processed successfully (exported) and those that have not been processed due to an error (error). Batch information and error messages also appear on this screen.

Use Cash Management Periodic Processing to process transactions in error after fixing the underlying cause of the error.

See IET Periodic Processing - Cash Management Tab.

In Cash Management, the bank entry is created with the standard Transaction numbering setup in Bank Services.

You can map some additional fields in Inter Entity Setup > Options > Cash Management.

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.

Bank Transfers

• Process bank transfers between companies. When you post a bank transfer in the source company, a bank transfer is automatically created in the target company.

AR Receipts across companies:

• Allocate a receipt to a customer in one company and have the receipt go into a bank account in another company

• Bank a receipt into a bank account in one company and allocate it against A/R transactions which originated in other companies.

• Allocate a miscellaneous receipt to G/L accounts in one or more companies whilst receipting the funds into a bank account in another company.

• Combined A/R Trial balance across multiple companies.

AP Payments across companies

• Process a payment against a vendor in one company and have the payment come out of a bank account in another company.

• Process an A/P payment out of a bank account in one company and allocate it against A/P transactions which originated in other companies.

• Allocate a miscellaneous payment to G/L accounts in one or more companies whilst drawing the funds from a bank account in another company.

• Combined A/R Trial balance across multiple companies Bank transfers between bank accounts across companies.

Transaction routes are used by Inter-Entity to generate the balancing transactions with the configured loan accounts between entities.

See details in :  Transaction Routes