Multi-Entity Management Features by Module

Multi-Entity Management Features by Module

Multi-Entity Management at its core supports these Dynamics GP modules: Accounts Receivable, Accounts Payable, General Ledger, and Bank Reconciliation.

If you would like to extend the power of Multi-Entity Management beyond these core modules, please check out the information below.

Multi-Entity Management Modules

Bridge

Multi-Entity Management Core

Bridge

Purchase Order Processing

Purchase Order Processing

Sales Order Processing

Sales Order Processing

Inventory Management

Inventory Control

Fixed Asset Management

Payroll Management

Payroll Management

Project Accounting

Project Accounting

Manufacturing Orders

Manufacturing

“We found that the combination of GP and Binary Stream’s Multi-Entity Managment product gave us the financial controls we needed to better manage our many long-term care facilities.”

Andrew Borzumato Accounting Manager, Mission Health Of Georgia

“When we implemented Microsoft Dynamics GP ERP, we realized we needed a solution to integrate with GP and allow us to manage multiple databases into one. Binary Steam’s MEM solution does exactly that.”

Justin WestSenior Director of Finance, Willamette Dental

“Binary Stream provides excellent support and their software releases keep pace with Microsoft’s, when others lag behind. Many professionals recommend Binary Stream’s MEM solution, and I do so regularly too.”

Bill BreitenbachSignature Healthcare

Multi-Entity Management Core Features

Multi-Entity Management allows you to consolidate data from all of your individual Dynamics GP databases into a single database. Multi-Entity Management’s core product supports your general ledger, receivables management, payables management, and bank reconciliation. Here are some key features:

  • Share Master Records such as Vendors, Customers, Items, and GL Accounts across multiple entities in a single Dynamics GP database; this allows for inquiries and reports to be run for a single entity, multiple entities, or all entities.
  • Full intercompany transaction functionality within one consolidated database including audit trails within posted transactions.
  • Centralized Processing for payments or receipts. A payment batch can be generated where a ‘parent’ can pay invoices on behalf of itself and invoices posted to ‘child’ entities. A receipt batch can be generated where a ‘parent’ can receipt its own invoices as well as invoices posted to ‘child’ entities. In both cases intercompany processing is part of the payment/receipt process.
  • Arm’s Length transactions between 2 entities who require a vendor invoice in entity A which in turn creates a sales invoice in entity B (as opposed to intercompany distributions between entities).
  • Allow for a ‘Head Office/Parent’ entity to leave its fiscal period open while closing the same fiscal period for all subsidiary entities (allows the Head Office/Parent entity to make final JEs while all other entities GL are ‘closed’).
  • Bank Accounts can be defaulted for particular cash transactions per entity such as Bank A for payments, Bank B for receipts and Bank C for banking transactions, Bank D for payroll disbursements.
  • Preset allocation templates allow for quick apportionment of AP/AR invoices to multiple entities.
  • Run Bank Deposits, Transfer funds between bank accounts of different entities which will also include intercompany distributions.
  • Run 1099 reports for one, many, or all entities either one after the other or consolidated where necessary.
ATTACHMENT DETAILS URL http://cdn.binarystream.com/wp-content/uploads/2017/02/MEM-module-MEM-feature-image-1.png

Receivables Trial Balance Report Options

MEM Bridge Module Database Diagram

Bridge Module

The Bridge module is an add-on to Multi-Entity Management (MEM) built to offer MEM functionality to companies where it was previously not possible. The Bridge module bridges the gap between all of the databases in a way that allows the system to operate as if all the data are in a single database. While MEM does its job of consolidating data to a single database for each currency and for each fiscal year-end, Bridge works behind the scenes to connect the remaining individual databases. Bridge can connect any number of databases regardless of whether they have MEM or are without MEM. A company using MEM along with Bridge can go from having to manage dozens, hundreds, or even thousands of databases to having just a few databases.

Circumstances that may necessitate Bridge:

  • Dealing in multiple functional currencies
  • Operating companies that have different fiscal year-ends
  • Having more than one chart of accounts structures and they vary widely
  • Using more than one inventory valuation method

Purchase Order Processing Module

Purchasing in a multi-company environment presents organizations many challenges. Some organizations have centralized their purchasing function allowing them to take advantage of volume discounts. Others choose to keep purchasing de-centralized at the entity level.

Multi-Entity Management’s Purchase Order Processing (POP) module allows organizations to accommodate both centralized and de-centralized purchasing. With centralized purchasing, a corporate head office is able to process a single purchase order for multiple companies and receipt for one company or multiple companies.

Key Features

  • Create automatic numbering of purchase orders and receipt numbers by entity.
  • Account substitution codes purchase orders and their resulting accruals and invoices to the proper entity eliminating coding errors. Proper entity coding flows seamlessly from PO creation to accrual, to invoice, to payment.
  • Purchase orders can be tagged with a “type” which allows the user to differentiate between different types of purchases (e.g. consumables vs. capital purchases).
  • Integration with popular requisition software is also available.
Using the PO Document ID on a Purchase Order, notice the Document ID and PO Number fields

Purchase Order Entry Window

Creating a sales order for one entity

Sales Transaction Entry Window

Sales Order Processing Module

Sales order processing in multi-entity organizations can bring a myriad of complex issues. Many organizations require security to ensure that users can only see the sales orders and sales documents that apply to their individual entities. Others may want the flexibility to create documents from other locations and provide cross-entity visibility into those transactions.

Multi-Entity Management’s Sales Order Processing (SOP) module allows organizations to filter what sales documents users can see and what they can enter. Sales document types can be associated to one entity. This provides unique documents from entities with their own auto-numbering sequences.

Key Features

  • Filter sales orders and invoices by entity.
  • Account substitution codes all SOP transactions to the proper entity, eliminating coding errors common in multi-entity environments.
  • Allocate different document ID types, such as quotes, orders, and invoices to specific entities.
  • Auto-number and have unique document numbers by entity for quotes, orders, invoices and returns.
  • Arm’s Length Transactions where a sales invoice from Entity A is created along with a payables invoice for Entity B.
  • Fulfill stock for a sales invoice from another entity with all the proper intercompany distributions required for this process.

Inventory Control Module

Handling inventory transactions in a multi-company environment is often very challenging. With Multi-Entity Management’s Inventory Control module, organizations are able to perform a number of key inventory transactions directly between entities. Users have access to Items during transactions, inquiries, and reports according to their user-entity access rights.

Key Features

  • Items, Item Pricing, and Item Sites can be restricted or shared between entities.
  • Item Transfers, In-Transit Transfers, and Item Transactions can be processed by entity with account substitution and automatic intercompany distributions to the correct entities.
  • Item Transactions can be performed.
  • Stock Count Schedules are processed per entity.
  • Inquiries for Item and Inventory Transactions can be viewed by entity.
Site Security by Entity

Entity Relation Setup Window

Streamline your ERP Processes

General Fixed Asset Window

Fixed Assets Module

Multi-Entity Management’s Fixed Assets module allows users with proper entity access to see fixed assets for any entity and run transactions for those fixed assets. Fixed assets in the multi-entity environment are associated to one entity and can be transferred to a different entity as required.

Key Features

  • Transfer assets between entities with proper account distributions taking place during the transfer.
  • Account substitution “codes” standard fixed asset transactions such as monthly depreciation, transfers, retirements, and related mass functions, to the proper entity GL accounts eliminating coding errors.
  • Create only one set of default accounts by Asset Class. Multi-Entity Management will ‘assign’ the correct entity GL segment when creating the asset.
  • Restrict user access to assets by entity.
  • Group functions such as Select Assets only allow groups to be formed through assets that a user has entity access to.
  • Can perform month-end processing such as additions, depreciation, disposals for all entities at once or for a specific entity or group of entities.
  • Filter inquiries and reports by one entity, many entities, or all entities.

Payroll Module

Multi-Entity Management’s Payroll module gives organizations the flexibility to perform both centralized and de-centralized payroll processing. The Payroll module allow only users with proper entity access to see employee records and to run payroll for those employees.

Key Features

  • Ability to process all the payroll for all entities at once, or by one entity, or a group of entities.
  • Payrolls can be paid from each employee’s respective company bank account or can be paid from a ‘central/head office’ bank account.
  • Users can only see the employees that belong to entities they have access to.
  • Employee records are associated to a single entity.
  • Share master tax schedules, benefits, and deductions across entities to eliminate redundancy.
  • Specific Tax IDs, including federal IDs, can be associated to individual entities.
  • Print W3s and Create W2s for magnetic media by entity.
  • Do period-end/W2 reporting by entity.
  • Run Payroll SUTA/FUTA reports by month, quarter, or year from all entities at once.
  • Ability to ‘allocate’ payroll expenses such as wages, benefits and taxes when an employee works for two or more entities but receives a single W-2 from their home entity at the end of the payroll year.

Payroll Check Window

Project Maintenance Window

Project Accounting Module

Multi-Entity Management’s Project Accounting module allows organizations the flexibility to use project accounting data in a centralized or a de-centralized manner to suit their needs.

Key Features:

  • Assign projects to an entity to restrict project access to users with the proper entity access.
  • Assign Cost Categories, Fee Maintenance, Equipment Maintenance, Miscellaneous Maintenance, and Contract Maintenance and control user access and work with entity permissions.
  • Project Accounting transaction windows are assigned to entities to only show transactions that the user has access to.
  • Submit Personal Data Keeper (PDK) project accounting timesheets to entities.

Manufacturing Module

Multi-Entity Management’s Manufacturing module provides organizations with the ability to manage the manufacturing process by entity. The Manufacturing module will also perform Account Substitution and intercompany logic during the posting of manufacturing transactions.

Key Features

  • Manufacturing transactions such as Orders, Receipts, Close Orders, Quick MOs, and Bills of Materials perform account substitution and automatic intercompany distributions can be processed to specific entity.
  • Users can process various manufacturing transactions by entity.
  • Users can be given access to a specific entity or entities when processing or inquiring in the Manufacturing module.
  • Manufacturing Processing and Inquiries can be performed by entity without having to log in and log out of multiple databases.
  • Purchase Request Resolution processing can be performed by entity.
  • In MRP Quantities Query can be processed by entity and account substitution will occur here from the originating entity creating the MOs and POs.

Manufacturing Module

Streamline your ERP Processes

Collections Module

Collections Module

Multi-Entity Management’s Collections module allows organizations to manage their collections processes by entity within a single database environment. Building queries, reviewing aging periods and collections amounts can all be performed at the entity level.

Key Features

  • Collections Main window restricts queries, displays Aging Periods, Total Amounts, YTD Sales, Unposted Sales, Unposted Cash by entity.
  • Customer information restricted by entity.
  • Email and Print Selection functions are restricted by entity.
  • Task List is restricted by entity.
  • Receivables Summary Inquiry information can be viewed by entity.
  • Days Sales Outstanding information can be viewed by entity.
  • Reports can be generated by entity.

Returns Management Module

The Returns Management module enables companies to quickly and easily manage the Returns process.

Key Features

  • Users can assign return merchandise authorization (RMA) returns/transactions to entities.
  • Access to RMA returns/transactions is controlled based on entities that users have access to.
  • Distribution accounts are substituted based on the entity of the transaction.
Returns Managment

RMA Returns/Transactions Windows

Contract Management

Contract Entry/Update Window

Contract Management Module

The Contract Management module gives companies an efficient way to manage Contracts within Dynamics GP.

Key Features

  • Users can assign Contracts to entities.
  • Access to Contracts is controlled based on the entities that users have access to.
  • Distribution accounts are substituted based on the entity of the transaction.

Are you interested in implementing Multi-Entity Management to your organization?

Free personliazed Demo

These companies trust Binary Stream.

 
Comcast logo - Binary Stream, accounts, accounting, software
Binary Stream Software Logo - Nikon
TSX logo - binary stream
American Red Cross logo - Binary Stream
BT logo - binary stream

Looking for something more?

See which Industries need MEM

See who integrates with MEM

Browse our Multi-Entity Management resources.

4 Signs that your Team is Ready for Super-Charged Subscription Billing Software

Download this whitepaper for insights into our new Subscription Billing Software for Microsoft Dynamics.

Subscription Billing Product Brochure

Discover Subscription Billing for Microsoft Dynamics GP & Dynamics 365 for Operations.

ASC 842 - The New Leasing Standard

Because of ASC 842, and its IFRS cousin, IFRS 16, that’s why! While these new standards are slightly different (IFRS requires all lessee leases to be treated as “direct finance” or capital leases, while ASC 842 classifies some leases as direct finance and others as operating leases), both are going to drastically change financial statement preparation and presentation, and hence will affect your everyday accounting.

Contact Us

×
{ "@context": "http://schema.org", "@type": "Organization", "url": "http://binarystream.com/", "logo": "http://binarystream.com/wp-content/uploads/2015/03/BS_LogoTagline_RGB_blue.jpg"}