Orchid Inter Entity Trade
Do you manage multiple entities that trade with each other? Are you expanding into new markets, or across borders? Is processing of routine transactions impeding efficiency and growth?
What is Inter Entity Trade?
Inter Entity Trade automates the flow of transactions in Sage 300 (Accpac) when related entities (companies, branches, divisions etc.) buy and sell products or services to and from each other.
Reciprocal documents are created according to business rules you set up. When you initiate a transaction in one entity, Inter Entity Trade creates the corresponding entries in the other. You no longer need to manually enter mirrored entries for each side of the transaction.
How It Works
- Map AP Vendor in Source company to AR customer in Target company (or vice versa).
- Map Source document GL Account to Target document GL Account.
- Automate elimination entries in a consolidation or elimination company.
- Configuration options:
- Specify a multiplier to mark up or mark down the Target document.
- Include Sage 300 Project & Job Costing fields to be transferred from Source document to Target document.
- Create transactions from:
- AP Invoices to AR Invoices
- AR Invoices to AP Invoices
- AP Credit Notes to AR Credit Notes
- AR Credit Notes to AP Credit Notes
- AP Payments to AR Receipts
- AR Receipts to AP Payments
- Account to Account mapping. Map OE customer in Source company to PO vendor in Target company (or vice versa).
- “Ship Via” to Account Mapping. Map OE “Ship Via” in Source company to PO Vendor in Target company (or vice versa).
- Configuration options:
- Include Sage 300 Project and Job Costing fields to be transferred from the Source document to the Target document.
- Include Sage 300 IC Serial and Lot Number fields to be transferred from the Source document to the Target document.
- Override the category on the Target OE documents to easily identify intergroup transactions for consolidated reporting.
- Override the location on the Target OE or PO documents to easily identify intergroup transactions for consolidated reporting.
- Map IC items across companies if not identical.
- Allow bi-directional processing. E.g. if POs in Company 1 against Vendor 2 automatically created Sales Orders (SOs) in Company 2 against Customer 1, you can either:
– “Receive” the PO, which will cause the SO to be shipped, or;
– Ship the SO, which will cause the PO to be receipted.
- Create documents from:
- OE Orders to PO Orders
- OE Shipments to PO Receipts
- OE Invoices to PO Invoices
- OE Credit Notes to PO Returns
- PO Orders to OE Orders
- PO Receipts to OE Shipments
- PO Invoices to OE Invoices
- PO Returns to OE Credit Notes