•  Refresh
  • Tools
  •  
  • Expand All
  • Collapse All
  • Locales
  • Get File Link
  • Report Typo
  • Print
  • Export

Interbranch Account Mapping

When an organization consists of multiple companies or branches, it often has documents and transactions that involve different companies or branches. It is necessary to set up the proper processing of interbranch transactions to eliminate the risk of balances being calculated incorrectly.

In the topics of this chapter, you will find general information on configuring account mapping rules for balancing transactions, an implementation checklist, and an activity with instructions on how to configure the rules.

Back to TopIn This Chapter

  • Interbranch Account Mapping: General Information
  • Organizations can be configured in Acumatica ERP in a variety of ways, with multiple companies and multiple branches within companies. As such, multiple branches or companies may be involved in a particular transaction.
  • Interbranch Account Mapping: Implementation Checklist
  • Before users begin to create intercompany and interbranch transactions, you must make sure that the system has been configured properly and that all required entities have been created, as described in the following table.
  • Interbranch Account Mapping: Implementation Activity
  • The Muffins & Cakes company registers transactions between its branches in the system. Its branches use separate accounting, so they require balancing. The company also registers transactions with the SweetLife head office and retail shop. The account mapping rules between the Muffins & Cakes head office branch (MHEAD in the system) and the Muffin & Cakes retail store branch (MRETAIL) have already been defined in Acumatica ERP as well as mapping rules between the Muffins & Cakes head office branch and the SweetLife head office branch (HEADOFFICE). You will review these rules. You need to define account mapping rules for transactions between Muffins & Cakes head office branch and SweetLife retail shop (RETAIL).