• Who We Are
    • About Us
    • Factor - D
    • Our Networks
    • Accolades
  • What We Do

    SERVICES

    • Consulting / Implementation
    • Migration
    • Development

    OUR SOLUTIONS

    • GUMU Integration
    • BPortaly
    • Sales Commission
    • Shipping
    • IOT

    COMPREHENSIVE SERVICES FOR

    ERP

    • Acumatica
    • Sage Intacct
    • Sage X3
    • Sage 300
    • Sage 100
    • Sage 500

    CRM

    • Salesforce
    • D365 CRM
    • Sage CRM
    • Creatio
    •  

    Other Solutions

    • E-commerce
    • EDI
    • POS
    •  
    •  
  • Resources
    • Case Study
    • Blogs
    • Videos
    • Ebooks
    • News
  • +1 888 221 6661
Contact us
Career |
  • Africa
  • Middle East

Sage 300 ERP – Tips, Tricks and Components

Explore the world of Sage 300 with our insightful blogs, expert tips, and the latest updates. We’ll empower you to leverage Sage 300 to its fullest potential. As your one-stop partner, Greytrix delivers exceptional solutions and integrations for Sage 300. Our blogs extend our support to businesses, covering the latest insights and trends. Dive in and transform your Sage 300 experience with us!

GL Control Account Feature in Sage 300 ERP

By sage300 | June 4, 2012
0 Comment

We come across requests that are sometimes so straight forward and some really need you to be a cracker and maybe that’s why we love Sage (Accpac) 300 ERP which makes our life simpler.
Suppose there are 2 different users wherein one user does the AP Invoice entries while the other user performs operations on AR entries. There is a possibility of accidentally selecting an account which is to be used for AP entries. Hence to avoid such mistakes, we were looking for a feature in Accpac which will restrict the user from using the Accounts which are meant for the AP Transactions.
As far as Accpac is concerned we can definitely restrict the users from avoiding this mistake using control Account feature which is inbuilt in GL module of Accpac. Let us see how it works and how it can ensure your accounts are in order.
Consider, we have a GL account which is being used for our bank account and this account should be affected only by AP transactions [by vendor] and not by any of other modules. In such case we will follow below procedure:
1) Open the GL Account screen and select the GL Account which has been set as bank Account. On the detail tab we will check the option Control Account, the new tab as Subledger gets added on the screen as shown in below screenshot.

2)    Go to Subledger tab and choose the subledgers which will have a control on this account. Here we are adding AP source codes as sub ledgers as shown in below screenshot.

Now let’s check the same by doing a normal GL Entry from GL Module on this account. For this go to GL Transactions>>GL Entry and select source code as GL-JE and add select the Account 1020 for Transaction entry. As we select this account for entry, a pop-up screen appears as shown in below screenshot. It will restrict us to make GL entry by another source code which has not been set as subledger on in GL Account screen.

It will accept GL transactions only created by AR Receipt and AP payment Transactions as set against the account sub ledger. If we want to allow account to get affected by other transactions also then we need to add  Source codes of those respective transactions into subledger of GL Account. The transactions created by only those subledgers may be posted to the account. General Ledger checks the ledger by looking at the first two characters prefixed on the source code for each sub ledger Transaction. These first two characters must match the subledger codes.  For example, all transactions created by Accounts Payable use source codes that begin with AP.

This way we can avoid user’s repetitive mistakes which would have been difficult for the admin to keep a hold.

Related Posts

  • Available options to migrate GL Account into Sage 300 ERP
  • GL Clearing Report in Sage 300 ERP
  • Migration of GL accounts from Sage BusinessWorks to Sage 300 ERP
Category: Sage 300 Tags: account, control
Post navigation
← Customer Number Merge in Sage 300 ERP Solving the Access denied error in Sage Simply Accounting →

Greytrix Websites and Blogs

  • Greytrix
  • Greytrix Africa
  • Sage X3 – Tips, Tricks and Components
  • Sage 100 & 500 ERP Tips and Tricks
  • Sage CRM – Tips, Tricks and Components
  • Salesforce.com Tips and Tricks by Greytrix
  • Sage Intacct– Tips, Tricks and Components
sage crm and sage 300 integration

Categories

  • Sage 300
    • ACCPAC SDK
  • Sage 300 People
  • Sage 50 US
  • Sage Business Cloud
  • TDS
  • Uncategorized

Recent Posts

  • Input Service Distributor (ISD) for Sage300
  • Customization of Default commits quantity on greymatrix order entry screen.
  • Introduction to Whatsapp Integration addon in Sage300 ERP
  • Introduction to Digital Signature Addon in Sage300 ERP
  • The “On Hold” feature on the Order Entry screen of GreyMatrix for Sage 300.

Archives

Awards

Premier Partner of the Year Premier Partner of the Year
Platinum Partner of the Year Platinum Partner of the Year
The CEO Story The CEO Story
Gold Partner pf the Year Gold Partner pf the Year
Top Excellence Distributor Top Excellence Distributor
  • na.sales@greytrix.com
  • +1 888 221 6661
  • B301, 3rd Floor, Everest Nivara Infotech Park, MIDC, Turbhe,
    Navi Mumbai 400 705. India

Our Global Locations >>

Who We Are

  • About Us
  • Factor - D
  • Our Network
  • Accolades
  • Career
  •  
  •  

Services

  • Consultation & Implementation
  • Migration
  • Development

Solutions

  • GUMUTM Integration
  • BPortaly
  • Sales Commission
  • Shipping
  • IOT
  •  
  •  

ERP

  • Acumatica
  • Sage Intacct
  • Sage X3
  • Sage 300
  • Sage 100
  • Sage 500

CRM

  • Salesforce
  • D365 CRM
  • Sage CRM
  • Creatio
  •  
  •  
  •  

Other Solutions

  • E-commerce
  • EDI
  • POS

Resources

  • Case Study
  • Blogs
  • Videos
  • E-books
  • News
  •  
  •  

Connect

  • Contact Us
  • Privacy Policy
  • Terms Of Use
  •  

© 2025. Greytrix, All Rights Reserved