Accounts Receivable > Setup > AR Branches

AR Branches

You use this program to maintain customer branch codes.

Branch Details

Field Description
Branch Indicate the code of the branch you want to maintain.
Branch Details  
Branch Indicates the code of the branch you are currently maintaining.
Description Enter a description for the branch code. This assists you in verifying that the correct branch has been entered.
Branch address  
Address lines Enter the address of the branch.
Language You can indicate the language code to use if you enabled the option: Multi-language for document printing in the System Setup program.
[Note]

The drop down option Global is the default selection and refers to the default language at the time of the entries' creation.

Sales value accounts You use these fields to enter the ledger codes required for the branch.

If Accounts Receivable is integrated to General Ledger, then you must enter a valid ledger code against each field.

Even if you do not make use of a particular sales order facility, you must still enter a valid (dummy) ledger code against the appropriate field.

AR control (Dr)

Indicate the General Ledger account to use for any transaction involving a sales amount for customers belonging to this branch.

The sales amounts (including tax) are posted as debits to this account.

The credit entries are either processed through the interface entry (for stocked and non-stocked and other charge line types) as defined against the AR Sales Ledger Interface (AR Sales Ledger Interface) or against the appropriate control accounts for the other types of entries as defined below.

This would be an Asset account on the Balance Sheet.

Freight charges (Cr)

This ledger account is credited when you charge customers belonging to this branch for freight.

The debit entry is posted to the AR control account.

This would be a Revenue account on the Income Statement.

Finance charges (Cr)

The ledger account that is credited when you levy finance charges on customer accounts.

The debit entry is posted to the AR control account.

This would be a Revenue account on the Income Statement.

Rounding error (Cr)

The ledger account that is credited when rounding errors occur.

The debit entry is posted to the AR control account.

Deposit revenue (Cr)

The ledger control account for deposits taken in Counter sales (Sales Order Entry) and Point of Sales (Point of Sale Entry).

This would be a Liability account on the Balance Sheet.

Sales tax (Cr)

The ledger control account to credit for the tax portion of sales made to customers belonging to this branch.

The debit entry is posted to the AR control account.

[Note]

This code is not used for ledger integration if you set Sales tax integration to general ledger at Tax code level (Company Tax Options Setup). The ledger account defined against the tax code is used as the account to which sales tax is credited for sales made to customers.

This would be a Liability account on the Balance Sheet.

GST (Cr)

The ledger control account to credit for GST on sales made to customers belonging to this branch (Canada only).

The debit entry is posted to the AR control account.

This would be a Liability account on the Balance Sheet.

Cost of sales  
Freight (Dr)

Indicate the ledger code to debit with the cost of sales value of freight charges raised against customers for this branch. This is typically an expense account in the General Ledger.

The cost is entered when processing freight charges against a customer order.

Non-stocked misc and freight (Cr)

Indicate the ledger code to credit for all transactions involving a cost of sale which does not relate to a stocked product code (i.e. transactions for non stocked items, freight charges and miscellaneous charges).

The debit entry is processed against the appropriate control account for these entries as follows:

  • Freight - Freight debit cost of sales
  • Non-stocked - per the interface entry (AR Sales Ledger Interface).
  • Other charges - as per the interface entry (AR Sales Ledger Interface).
[Note]

For dispatch notes, the account defined here is debited for non-stocked freight charges and non-stocked miscellaneous charges dispatched using the Dispatch Note Review program, when the Use non-stocked ledger control from branch option is enabled (Dispatch Notes Setup) and the Inventory module is not installed.

If the Inventory module is installed, then non-stocked items are also debited to this account.

Invoice numbering You can only access these fields if your Invoice numbering method is By branch (Set Key Information).

It is advisable to define a unique range of numbers for each branch to prevent duplicate numbering, especially if you allow the customer's branch to be overridden when generating invoices.

Prefix Enter up to 10 characters that will prefix invoice documents generated by this branch. This will help you to identify the branch for which the document was generated.

A prefix can only be associated with an invoice if the invoice numbering method is by branch and the key type for invoices is defined as alphanumeric (Set Key Information).

Because the prefix uses the digits allocated for the document number, a maximum of 10 digits can be used for the document number itself when using a prefix of 10 characters.

Next invoice Indicate the number that must be used for the next invoice you generate.
Next credit note Indicate the number that must be used for the next credit note you generate.
Next debit note Indicate the number that must be used for the next debit note you generate.
RMA numbering You can only access these fields if RMA numbering is at branch level (Set Key Information).
Prefix Enter up to 10 characters that will prefix RMA documents generated by this branch. This will help you to identify the branch for which the document was generated.

A prefix can only be associated with a RMA if the key type for RMA numbers is defined as alphanumeric (Set Key Information).

Because the prefix uses the digits allocated for the document number, a maximum of 10 digits can be used for the document number itself when using a prefix of 10 characters.

Next RMA Indicate the number that must be used for the next RMA you generate.
Sales order and del note numbering

You can only access these fields if the Sales Order numbering method is set to By branch and/or Delivery note numbering method is set to By branch with prefix (Set Key Information).

It is advisable to define a unique range of numbers to each branch to prevent duplicate numbering, especially if you allow the customer's branch to be overridden when generating sales orders, credit notes and debit notes.

Prefix Enter up to 10 characters that will prefix sales order documents generated by this branch. This can be used to identify the branch for which the document was generated.

A prefix can only be associated with a Sales order, Credit note or Debit note if the Sales orders - Key type is defined as alphanumeric (Set Key Information).

A prefix can be associated with a Delivery note if Delivery notes are being generated By branch with prefix (Set Key Information).

Because the prefix uses the digits allocated for the document number, a maximum of 10 digits can be used for the document number itself when using a prefix of 10 characters.

Next sales order Indicate the number that must be used for the next sales order you generate.
Next credit note Indicate the number that must be used for the next credit note you generate. This number can be a maximum of 15 digits and must begin with an eight (e.g. If your presentation length is 10 digits, then this number will be in the range 8 000 000 000 to 8 999 999 999).
Next debit note

Indicate the number that must be used for the next debit note you generate. This number can be a maximum of 15 digits and must begin with a nine (e.g. If your presentation length is 10 digits, then this number will be in the range 9 000 000 000 to 9 999 999 999).

Next delivery note Indicate the number that must be used for the delivery note you generate.

You can only access this field if you indicated that the generation of delivery note numbers is required at branch level (Set Key Information).

Settlement discount numbering  
Next settlement credit Indicate the number that must be used for the next settlement discount debit note you generate for the branch.
Next settlement debit Indicate the number that must be used for the next settlement discount credit note you generate for the branch.
Quotation numbering  
Prefix Enter up to 10 characters that will prefix quotation documents generated by this branch. This will help you to identify the branch for which the document was generated.

A prefix can only be associated with a quotation if Quotations - Numbering method is by Branch and the Key type for Quotations is defined as alphanumeric (Set Key Information).

Because the prefix uses the digits allocated for the document number, a maximum of 10 digits can be used for the document number itself when using a prefix of 10 characters.

Next quotation Indicate the number that must be used for the next quotation you generate for the branch.

Notes and warnings

Deletion considerations

  • You cannot delete a branch if non-zero values are held against either product classes (SalProductClassSum table) or salespersons assigned to the branch (SalSalespersonSum table).

    Running the Sales Analysis Update program ensures that these tables are updated.

    However, if the branch you are deleting doesn't exist in either the SalProductClassSum or SalSalespersonSum tables (e.g. Sales Analysis is not installed) then the branch is deleted without warning, regardless of whether sales/invoices exist for that branch.

Program access

  • Access to this program can be restricted per operator group (see Security Access).

  • Additional security can also be implemented in the following areas:

    • Functions/Activities can be restricted:

      • per operator (see Security Activities).

      • per operator role (see Role Activities and Fields Maintenance).

      • using Electronic Signatures (see eSignature Setup).

    • Fields can be restricted:

      • per operator (see Security Fields and Access).

      • per operator role (see Role Activities and Fields Maintenance and Role Access Control Maintenance).