Inter-Entity Release Notes

• Additional warning and error messages in Inter-Entity Transactions when posting G/L batches and recording entries in IY Audit logs.

• Improvements to XAPI connection error handling.

• IET Cash Management - 1-Step Bank Reversals AP and AR - no longer using original transaction remittance date. Will post the bank reversal entry using the reversal date.

• IET G/L Trigger Setup - delete button was not working. Fixed. Pressing delete button will now remove a trigger setup record.

• Fixes issue when using Inter-Entity Trade to create A/P Payments and A/R Receipts and Inter-Entity isn't activated in the target company.

• IET OE/PO Trade - OE Invoice to PO Invoice - corrected an issue where IET was unable to locate a P/O receipt in the target company when using CSQRY

• Fixes an issue with the Inter-Entity Account Balance Report and Inquiry if the Source and Target companies have a different fiscal calendar.

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

Sundry usability improvements. Refer to IY Options > Updates Tab for details.

IET OE/PO Trade - Enabling the creation of unmatched O/E Credit Notes from unmatched (without P/O Receipts) P/O Returns.

Inter-Entity now supports complex passwords. You need the latest update of Sage 300 System Manager to enable complex passwords. Refer to Sage help for details. There is no special configuration in the Orchid module.

Generate IET Transactions now includes G/L Triggers. Generate IY Entries

G/L Triggers setup documentation updated.

In Cash Management, Bank entry number from the source entry is now available as a field to map in Option > Cash Management >Bank Services Integration. Refer to Cash Management Options for details on configuring Cash Management integration options.

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.

Reprocess Exported Transactions - If selected, users can view and select the "Exported Transactions", check boxes on the Periodic Processing (for G/L Transactions, Cash Management, AP/AR Trade, and OE/PO Trade). This option is also required for the "Clear Audit Entries" on the Periodic Processing for /G/L Transactions and G/L Triggers and "Rebuild Audit Entries" for G/L Transactions.

Note that users need to have "Perform Period End Processing" selected for this security option to be taken into account.

P/O Drop Ship address

• P/O Drop Ship address details (from first line that has a Drop Ship address) to O/E Ship to Address -

Notes:

If IET has been setup to copy the ship-to address fields from PO to OE, then IET will overwrite that with the first drop ship address it finds in the PO details.

All fields are copied, including all Address fields, contact phone, fax, email, and the ship-to email.

It is not going from OE to PO

New fields and filters in the I/Y Audit Inquiry, I/Y G/L Triggers Audit Inquiry, I/Y Trade A/P A/R Audit Inquiry and I/Y Trade O/E - P/O Audit Inquiry (Date, Time and User created by, Date, Time and User Amended by)

New keys to Inter-Entity Trade audit tables to improve performance. Refer to Updates Tab for details.

New keys to Inter-Entity Transactions audit tables to improve performance. Refer to Updates Tab for details.

New Options in Inter-Entity Trade

• In Inter-Entity Trade, new option in IET Setup to create AP Payments from AR Receipts.
• Transactions are applied based on the audit trail in the source company or the target company (if the invoice was first recorded in the target company).
• Ability to select a custom Source Application in AP/AR Trade.

Refer to A/P - A/R Trade Options Screen Guide

Orchid Module Version 2018 (6.5) Product Update 0.00 is now compatible with Sage 300 version 2018 (6.5)

In Inter-Entity Trade

Special Fields - Location to Location, On Hold , Comments and Instructions field mappings.

• Location to Location field mapping now defines whether IET Trade is to take a source document detail location and send it to a trade document detail line. If mapping is not defined between location to location, then the default location will be used at the target/trade document side. (By Default the Location is transferred between O/E and P/O documents )

• OnHold field is now a mapping option. This allows the onhold status from source document to be transferred to the target/trade document. (By Default the On Hold field is NOT transferred between O/E and P/O documents)

• Mapping source and destination document comments and instructions is now possible. Comments and instructions can be copied in their entirety from a source document's details to a trade document's details. (this applies to both A/P - A/R Integration and O/E - P/O Integration Tabs)

• In Inter-Entity Trade, AP/AR Trade, in the AP-AR Trade Partner setup you can now map

  · a G/L Revenue Account (used in A/R in the Source Company) to an AP Distribution Set to achieve a one-to-many distribution of expenses in the target company

  ·a G/L Expense Account (used in A/P) to an AR Distribution Set to achieve a one-to-many distribution of revenue in the target company

• New Options in Inter-Entity Trade
• Ability to create A/R Receipts from A/P Payments in Inter-Entity Trade

Inter-Entity Transactions is now compatible with Sage 300 2017.

A new tab on the IE Transactions Options showing the installed product update and product updates released since the installed product update to allow for easier viewing/checking of the installed against current product update.

• New Options in Inter-Entity Trade
• Ability to create A/R Receipts from A/P Payments in Inter-Entity Trade

• PU 4.1 (16/07/2015)

• The following update has been implemented as part of this release.

• • IET Periodic Processing Not Processing full range of transactions.

• When the user selected Posting Sequence 0 to 999999, the process was not running through the records in the IYAUDIT table and processing them. This was especially noticeable when connection errors occurred due to unavailable LanPAK licenses, etc. The problem stemmed from the process tripping over itself due to encountering a connection problem.

• This has now been resolved and IET's Periodic Processing will now run through posting sequences ranging from 0 to 999999.

• IET G/L Transactions freezing on posting a G/L batch with accounts that do not exist in G/L.

• When a batch was created in G/L by a sub-ledger, it was possible for the batch journals to contain accounts that did not exist in G/L. This happens when location overrides are used in either P/O or O/E, resulting in distribution accounts created that do not yet exist in the G/L database.

• As a consequence of this, IET G/L Transactions was encountering a hitherto unknown memory overrun generated when the process attempted to free memory that wasn't yet allocated, and the application was locking up.

• The problem has been addressed as part of this release.

• Importing IET Database-Entity Mappings.

• IET was reporting errors when attempting to import database-entity mappings by using the import functionality provided by the Entity-Database Mapping screen. The problem was due to field level attribute validation preventing the records from importing field values for organization id, userid, password, and other required fields.

• This problem is fixed as part of this release.

• PU 4.0 (02/06/2015)

• The following update has been implemented as part of this release.

• • IET Inter-Entity Transactions Processing Option - Process in Detail.

• New process supported by Inter-Entity Transactions that creates balancing inter-entity loan entries in the respective currencies of the source transaction. Refer to the on-line documentation for more information.

• New field added to IY Options to support this new feature.

• IET Multi-currency loan account entries in target companies When processing IET Loan account entries, IET Processing sums multi-currency journal details in source and functional currency by entity and currency, and generates loan account entries accordingly. In some circumstances if multiple different exchange rates are used in the source journal for the same entities, the original exchange rate(s) cannot be used in the target entry. This can lead to out of balance entries in the target entry if the prevailing exchange rate for the target company/journal date is not the same as the average rate used in the source company. A new option has been added to the IET Options\Processing tab “Process in detail”. Selecting this option will ensure Inter-Entity Transactions will create loan account entries between every journal detail line in the source journal and the default entity configured on the IET Options Segments tab (except for those source journal entries which are the Default Entity). If not selected, Inter-Entity Transactions will create loan account entries of the sum by currency and entity of the journal detail lines between the entities in the source journal.

• IET AP/AR Trade with G/L Eliminations AP/AR Trade now supports the new G/L Eliminations functionality. On an AP/AR Trade partner setup, you can select to Create Elimination entries, and select a company in which to create the elimination entries. If creating elimination entries, you must define the associated G/L accounts for the elimination entries for each of the Revenue/Expense mapping rows.
• IET OE/PO Trade - Discount Percentage on Document Total If selected, IET Trade will transfer the discount percentage on document totals from the source document to the recipient trade document.
• IET OE/PO Trade - Trade Reference Fields Upgrade Additional fields included into the OE to PO and PO to OE field mappings.

There is a new option to use consolidated Entity Processing. If selected, then the source journal lines will be totalled by entity and the debits will be set off against the credits to provide one net debit or credit per entity per journal entry prior to determining the required routes, and whether or not the default entity should be used. If not selected, then the debit lines will be totalled by entity and the credit lines will be totalled by entity. Debit and credit totals to the same entity will not be offset against each other prior to determining the required routes, and whether or not the default entity should be used. The default entity is used where Inter-Entity cannot establish a definite link between the debits and the credits in a journal when creating balancing loan account entries.

• Inter-Entity Trade now allows
  • for price list overrides when creating OE documents from PO documents
  • To use default Vendor Contract pricing when creating PO documents from OE documents

Previously the target unit price/unit cost was always derived from the unit cost/unit price of the source document multiplied by the optional multiplier

• The definition of a bi-directional Account-ship via relationship, to enable the bi-directional updating of selective document lines denoted by a ship-via.

• Inter-Entity Transactions now allows you to Total the source journal by entity (not further split by debit & credit totals) in determining the required routes and use of the default entity.

Optionally allows bi-directional processing. For example if POs in Company 1 against Vendor 2 automatically created SOs in Company 2 against Customer 1, then you can either “Receive” the PO which would cause the SO to be shipped OR Ship the SO which will cause the PO to be receipted. In prior versions, this automation could only go “one-way”

IET Trade. Ability to use wild cards (* and ?) in the IET Trade AP-AR Trade Setup if you have the G/L Account Mapping enabled. You are now able to map – for example all revenue accounts starting with 46??-1 to Expense accounts starting with 66??-2.

• IET Transactions : Additional Document Integration mappings for G/L Triggers to populate AR and AP Invoice detail descriptions

• IET Trade : AP-AR and OE-PO Trade. Additional Document Integration mappings for AP-AR and OE-PO trade documents to allow more fields on both the header and the detail of the documents to be mapped

IET Triggers. Ability to use wild cards (* and ?) in the G/L Triggers Setup. You are now able to map – for example all revenue accounts starting with 46??-1 in Entity one to Expense accounts starting with 66??-2 in Entity 2 without having to have an individual G/L Trigger setup row for accounts 4601-1, 4602-1, 4603-1 etc to 4699-1

Wild Card usage for IET G/L Trigger accounts

In IET G/L Trigger Accounts, you can now use the following wild cards for the G/L Trigger account to avoid having to have an entry in G/L Trigger account for each and every account which is to be a trigger account

For Example :

• 55??-20-1 : this covers the range from 5500-20-1 to 5599-20-1 or 55AA-20-1 to 55ZZ-20-1 for Alpha numeric accounts.

• 55* : this covers all accounts starting with 55, including all account structures

• IET Triggers. New options in IET Options to allow AP and AR batches/documents to accumulate by period, rather than an individual batch/document being created per G/L posting to the "trigger' account. 

• IET Cash Management. New Clearing account form CM Banks, to allow CM Bank transfers, 1-step processing, 2-step processing to be processed across multi-level IET Routes

• IET OE-PO Trade: Allow for a ship-via to account mapping. This allows Sales orders or Purchase orders to be created based on a ship-via code (vs by account)  

• IET OE-PO Trade. Allow for applying a factor to achieve a markup or markdown on the target documents 

• IET AR-AP Trade. Allow for applying a factor to achieve a markup or markdown on the target documents 

• IET Trade Options : For both AP-AR and AR-AP Trade Integration, allow "Batch Date" and "Entry Date" to be mapped to the target document fields.

• New Options in IET Options for Cash Management : Added Autopost checkboxes for source and target Bank Entries

• New Options in IET Receipt Selection Codes and Create Receipt Batch to include/exclude debit notes

• Sundry Performance improvements in IET Trade on Large PO/OE databases.

• Added "User ID" and "Organisation ID" for Bank Transfer to Bank Entry in Options/Cash Management.

• New option in IET Options “Use Home (functional) Currency” and IET Entity Database Mappings “Transfer Using Home Currency” to configure if, when using multi-currency source and target databases, the source amount only is transferred to the target database (and the currency tables are used to translate the functional amount) or both the source amount and functional amount is transferred to the target database (where both source and target use the same functional currency).

• IET Cash Management to

• Automate Bank Transfers from one Accpac Company {database} to another Accpac Company {database} without recording the transaction twice

• To automate payment and receipt processing to enable

  • One-Step Cash Management processing : where you run a management company to enable AR Invoices and AP Invoices to be recorded in one central database, but where the payment is to be made from or the receipt is to be processed into a second database.

  • Two-Step Cash Management processing : where you enter AP invoices and AR invoices in multiple Accpac databases for statutory and tax reporting, but wish to transfer the documents to a management company for consolidated payment and receipting.