Creating Intercompany Documents for Branches

Creating Intercompany Documents for Branches

G/L Allocations

In branch enabled Company, you must specify a Branch Code in the each top row when creating the following documents:
  1. G/L Branch Allocation
  2. G/L Allocation Posting Templates
  3. Recurring G/L Allocation Postings
    If Receiver Company is branch enabled, you must specify the receiver company branch code in the bottom matrix for the following documents:
  1. G/L Branch Allocation
  2. G/L Allocation Posting Templates
  3. Recurring G/L Allocation Postings



The system uses the Receiver Branch Code specified in the bottom matrix of the sender document to create the Journal Voucher/journal Entry in the receiver system.
With allocation enhancement available for IC PL30 or higher versions, the user is now able to select branch(s) of the self company (provided it is Multi-Branch Enabled) in the lower matrix of the following features:
  1. G/L Branch Allocation 
  1. G/L Allocation Posting Templates 
  1. Recurring G/L Allocation Postings 
  1. A/P Service Invoice Allocation (only for G/L Type)

Intercompany Trade

In branch enabled company, you must specify a branch in the header area when creating the intercompany type Sales and purchasing documents.
If Receiver Company is branch enabled, you must specify the receiver company branch code in the Receiver Branch field of sender documents.
  1. The system uses the Receiver Branch specify in the sender document to create the draft document in the receiver company.
  2. The system will not allow you to change the branch field value in the intercompany type draft receiver documents.



A/P Service Invoice Allocation

In branch enabled company, system automatically displays the branch as specified in the A/P service invoice.
If Receiver Company is branch enabled, you must specify the receiver company branch code in the bottom matrix of allocation window.



The system uses the Receiver Branch Code specified in the bottom matrix of the sender document to create the Journal Voucher/Journal Entry in the receiver system.
With allocation enhancement available for IC PL30 or higher versions, the user is now able to select branch(s) of the self company (provided it is Multi-Branch Enabled) in the bottom matrix of the following features:
  1. G/L Branch Allocation 
  1. G/L Allocation Posting Templates 
  1. Recurring G/L Allocation Postings 
  1. A/P Service Invoice Allocation (only for G/L Type)

Centralized Payment

In branch enabled company, you must specify a branch in the header area when delegating the payment line to the branch company.
If Receiver Company is branch enabled, you must specify the delegation branch in the sender documents.




The system uses the delegation branch code specified in the sender document for the journal Entry created in the receiver system.

Financial Consolidation

When you are consolidating the financial data from the branch enabled company to the consolidation company, system takes the values from the Branch (BPLId), Branch Name (BPLName) fields of the journal entry/journal voucher and transfer these values in to the Branch Code (U_CTX_BRCID), Branch Name (U_CTX_BRCNM) fields of the journal entry in the consolidation company.
  1. In Case of Multi-level consolidation, from the consolidation company, the values in the Branch Code (U_CTX_BRCID), Branch Name (U_CTX_BRCNM) fields of the journal entry goes in to the higher level of consolidation company in the Branch Code (U_CTX_BRCID), Branch Name (U_CTX_BRCNM) fields.
  2. You can view the data of an individual branch by filtering the SAP Business One financial reports in the Branch Name (U_CTX_BRCNM) field of the consolidation company.