How Ledger Accounts work with Locations

Created by Travis Lander, Modified on Mon, 14 Oct at 10:17 AM by Travis Lander

Description

SoftLedger allows companies to set up their organization hierarchy through a Location structure by setting up Locations. Once your Locations are setup, users have a form of control by determining which Ledger Accounts can be used with which Locations. This article describes the way SoftLedger handles posting journal entries to nested locations and ledger accounts restricted by location.

 

Setup

Locations

The first thing to setup for this relationship is the Location structure. Each Location has a Parent Location that the Location rolls up to, and when viewed in aggregate looks like the below:

 

 

Ledger Accounts


Next, you can set up the availability of each Ledger Account within these Locations through the account setup:

 


Select the Location in the Ledger Account creation process, and toggle the Include Child Location field On or Off (the toggle controls whether or not this Account can post to the child Locations of its selected Location).

Note: A Ledger Account can never post to a Parent Location of its selected Location.


Example

Say we have the following Location hierarchy:

 


If we have the following Ledger Account:

 


This Ledger Account can post to the following locations:

  • European Operating Entity
  • UK Entity

If you toggle Include Child Locations to Off:

 

Then you would only be able post with this Ledger Account ONLY to the European Operating Entity location, and not the Global location above it, or the children locations below it.

 




Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article