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

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.

In interbranch or intercompany transactions, because credit and debit amounts are posted to different branches or companies, the account balances of the branches or companies may not be in balance. You may need to configure the system to automatically generate balancing entries for interbranch or intercompany transactions so that transactions are balanced in each involved branch or company.

If you have extended a branch as a customer or as a vendor and want to use them in AP and in AR documents, you do not need to configure the account mapping. For more details on how to extend a branch as a customer and as a vendor, review Intercompany Sales Setup: Implementation Activity.

Back to TopLearning Objectives

You will learn how to configure account mapping rules for transactions between companies and between branches that require balancing.

Back to TopApplicable Scenarios

You need to configure account mapping if you need to post GL transactions with different lines associated with different companies or branches, and you need to balance the transactions in the books of each company or branch.

For details on processing such interbranch and intercompany documents, see the following topics:

Back to TopInterbranch Balancing Entries

You need to set up the generation of balancing entries for interbranch transactions if any of the following transactions can be generated in the organization:

  • Transactions between different companies
  • Transactions between branches of different companies
  • Transactions between branches of one company that have separate accounting—that is, branches of a company with the With Branches Requiring Balancing company type specified on the Companies (CS101500) form

In these cases, transactions should be balanced in each company or branch involved so that the accounts of each entity will be in balance and so that you can prepare financial statements for each company or branch.

Balancing entries between Due To and Due From accounts cannot be used for entities with different base currencies. If you need to create a transaction between entities in different base currencies, you should first extend the involved companies to customers or vendors, and then create transactions for these customers or vendors. For details on extending companies to be customers or vendors, see Intercompany Sales: General Information.

Back to TopConfiguration of Interbranch Transactions with Balancing Entries

To configure in the system the rules the system will use to generate balancing entries, you have to do the following:

  1. Make sure that the Inter-Branch Transactions feature has been enabled on the Enable/Disable Features (CS100000) form.
  2. Define the rules according to which the system will generate balancing entries on the Inter-Branch Account Mapping (GL101010) form. In each rule, you specify the following:
    • The originating branch in which an interbranch transaction is initiated. This is the branch specified for the document whose release causes the transaction to be generated.
    • For the balancing entry in the originating branch, you specify the following:
      • The destination branch to which the interbranch transaction is targeted. This is the branch specified in the particular line of the document whose release causes the transaction to be generated.
      • The account range for mapping. That is, the range of accounts of the destination branch to which the rule applies.
      • The offset account to which the system will post the balancing entry in the originating branch. You can use as this offset account any asset or liability account assigned to an appropriate account class, depending on the organization reporting needs.
    • For the balancing entry in the destination branch, you specify the following:
      • The destination branch to which the interbranch transaction is targeted. This is the branch specified in the particular line of the document whose release causes the transaction to be generated.
      • The account range for mapping. That is, the range of accounts of the destination branch to which the rule applies.
      • The offset account to which the system will post the balancing entry in the destination branch.