Cost centre analysis add on-Tally

 Problem statement: Many companies require cost centre wise analysis(specifically with Tally). Their needs are as follows:

1. Profit analysis per cost centre

                2. Understanding the billing implications for various projects. Material could have been             purchased but billing would not have been done.

Relevant industries: any project related industries for construction.

In order to meet the need for cost center analysis we have a software add on for revenue analysis.

For quick querying we have developed the same over SQL Server. The clients can  also develop workflows over the cost center module.

Why is the SQL Server module required?

a.) The logic as per the required revenue accounts has been developed in the database. We extensively use ledger flattening for the same.\

b.) In order to make the system more secure and customizable we have used python code.

c.) The client can specify the screen to be shown based on ledger and item hierarchy flattening.

Why is this module better than the Tally system:

a.) Customized revenue models have been developed

b.) Better control flows can be specified using item hierarchy and ledger hierarchy flattening. That is a CEO can contact his subordinates with ease using the module.

Explanation of the module:

 In the sample screen below we make a preliminary snapshot of a sample cost center module developed for a company.

a.) Company name is a drop down box: we can work with unlimited companies

b.) Cost center: these are the associated cost centers for the company that has been selected in the combo box above.

Hereafter we explain each of the list boxes below:

1.) Sales: this gives the total sales entries as per the sales accounts for the given cost center.

2.) Purchase: this portion can be further customized base don the ledger flattening by the end client. Various sub groups can be added. this indicates the total purchase(across all voucher types) for the purchase accounts.

(Note: delivery notes, receipt notes, purchase order and sales order have been excluded. The revenue accounts report from Tally has been used to generate the given numbers).

The sales and purchase entries include both ledger and inventory movements(so the journal entries for the sales shall also be counted)

Labour, Transport and other expenses have been extracted from the ledger flattening.

The net profit per project is sales-purchase-indirectexpense-direct expense for a project per cost center.

Other customizations that are possible: 

For example automated emailing and whatsapp feature across various ledger level hierarchies are also possible(the same is been done for a client given below):

Inventory movement analysis: In order to make the module more comprehensive and showcase more details for the project movement we also have added sections to showcase the inventory movement for sales, purchase. In the module the following actions can also be taken:

a.) Conversion of units can be done

b.) Link with bill receivable can be done

c.) Workflows based on project completion can be done.

For deployment of the module please contact:

Name: Apoorv Chaturvedi

email: support@mndatasolutions.com;support@turbodatatool.com

Phone:+91-8802466356

Estimated cost: (To be decided on case by case basis)

Website: https://mn-business-intelligence-india.business.site?whatsapp

Youtube channel: https://www.youtube.com/@mndatasolutions2042

 

Workflows and secured custom reports access(unlimited users)-Turbodata

  Workflows and secured custom reports access(unlimited users)-Turbodata

 

 Who are the stakeholders with whom you need to share data?

Are you a customer who is on Tally server?

Then let us see who could be the possible users of your data?

For most firms the user hierarchy details are in ledger hierarchy.

Say in the internal hierarchy there are 25 people  each across various levels of hierarchy.

say the company has 50 sundry debtors and 20 sundry creditors. SO the total people involved for sharing information securely are atleast 95.

Methods of contact by whatsapp, email are time consuming.

a.) Internal users: The number of internal users could be large. Various reports with row level security could need to be shared with various end users.

b.) External users: primarily under the primary group sundry debtors and sundry creditors. Currently They are informed by whatsapp or email intimations. However

Additional details that can be shared are as possible:

i.) Pending sales orders

ii.) Pending purchase orders

iii.) Pending bills statements: https://mndatasolutionsindia.blogspot.com/2023/11/issue-problem-statement-in-many.html

iv.) Intimation regarding new receipts

v.) Sales order input forms.

vi.) Open stock position for reordering: https://mndatasolutionsindia.blogspot.com/2021/01/sell-more-of-your-inventory-to-existing.html

Additional requirements for internal users:

a.) Workflow approval requirements for sales orders and purchase orders within the internal heirarchy:

Current solution:

a.) Most companies use third party apps for getting one or more tasks done: issues regarding data security and data confidentiality are open in many cases.

b.) Tally server companies also use third party apps

Our proposed solution:

a.) If on server in Tally then use the same to give access to multiple end users without paying additionally for each user by using own server.

b.) Design custom workflows for approval process

c.) Get custom reports in a very quick and customized fashion without paying any licensee fees

Process steps for the same:

a.) Use Turbodata Powerbi module to understand the Tally data using ledger hierarchy and item hierarchy flattening: https://mndatasolutionsindia.blogspot.com/2021/10/turbofast-powerbi-reports-from-tally.html

b.) Load the data into SQL server. For faster incremental data load indicate masters entries for data load. Optimize the reports in SQL server: https://www.youtube.com/watch?v=m8Lg6Og9bcU,https://www.youtube.com/watch?v=PI5DmU5IUSo,https://www.youtube.com/watch?v=B-odSuZkYhU&list=PLZPWImFqOkLsGgXPGf82nHPVaaZtJx4BL&index=1

using views and functions : https://www.youtube.com/watch?v=B-odSuZkYhU&list=PLZPWImFqOkLsGgXPGf82nHPVaaZtJx4BL

c.) Set up row level security at the database level:  

d.) Use Turbodata data capture forms to give custom reports at each level of stakeholders.

Name: Apoorv Chaturvedi

email: support@mndatasolutions.com;support@turbodatatool.com

Phone:+91-8802466356

Hire sales analyst-Turbodata

 Sales Order Analyst:

Get specialized sales order analysts for your firm to handle multiple issues with regards  to sales orders and sales analysis

Profile: Accounting knowledge, SQL, python, Preferably Tally

Pre requisites; Turbodata(Powerbi module, SQL Server datawarehouse, python data configuration module)

 

Why is a sales analyst required for your firm?

·        Many firms are making sales over a large number of skus(stock keeping units) over a number of customers

·        The orders are coming from multiple sources and across multiple items

The owner requires the following:

·        Complete visibility of the profit of the transactions as per his logic across item hierarchy and ledger hierarchy(https://mndatasolutionsindia.blogspot.com/2020/08/weighted-average-valuation-from-tally.html)

 

·        Control over the process flow by which the orders are approved before the data entry into the Tally system(https://mndatasolutionsindia.blogspot.com/2020/01/turbo-analytics-batch-wise-bill-wise.html)

 

·        Look into the possibility of automation of data entry into Tally after the approval process.

·        Desire to sell the existing stock over the customers: https://mndatasolutionsindia.blogspot.com/2021/01/sell-more-of-your-inventory-to-existing.html

 

·        There is a need to check the credit worthiness of the parties. The parties credit worthiness can be checked based on the following parameters:

o   Prior cash inflow from the prospect

o   Receivable status of the client

o   Pending open sales order status

Based on the above parameters the sales analyst shall help make workflows to decide on the following parameters:

·        Whether to accept the order or not. Based on the analysis the sales analyst could recommend to accept or reject the order

·        Decide on the discount and the pricing of the product. An appropriate workflow based on the hierarchy could need to be decided for the same.

·        Payment terms: the payment terms can also be adjusted

·        Decision on factoring agencies: the sales analyst will help with the factoring agencies to discount the bills in case the parties with the credit terms are not of the best quality

·        Collections process: the analyst can help with designing custom email and whatsapp solutions or implementation of external solutions like Biz analyst for speedier collections process

Analysis for the parties shall be done based on each sales order.

 

Analysis of the Item profitability: many customers desire custom logic for their item profitability for the following scenarios(https://mndatasolutionsindia.blogspot.com/2018/09/fifo-logic-turbodata.html):

a.)   Batch wise items(https://mndatasolutionsindia.blogspot.com/2018/03/developing-optimization-module-for.html)

b.)  Non batch wise items(https://mndatasolutionsindia.blogspot.com/2018/01/reduce-retail-and-manufacturing.html)

c.)   Items both in batch and non-batch

d.)  Incorporation of the landing costs for the end client

e.)   Look into designing sales combos for the items for the end client(https://mndatasolutionsindia.blogspot.com/2019/08/market-basket-analysis-turbodata.html)

 

Issues involving splitting of companies, incorporation of the movement types need to be involved for the same.

 

The analyst shall help the owner arrive and report on the items costing based on Tally, costing based on the custom logic of the end client. Thereafter the anticipated profitability of the orders can be gauged.

 

Name: Apoorv Chaturvedi

email: support@mndatasolutions.com;support@turbodatatool.com

Phone:+91-8802466356

Youtube channel:

https://www.youtube.com/watch?v=f7GnueEDhVo&list=PLZPWImFqOkLtJk2MoUPjb6ap_wFbJN53E

Industry analytics module: https://www.youtube.com/watch?v=xGyQBZoEAaI&list=PLZPWImFqOkLtequtQueJLPdo4ngnZFUbx

https://www.youtube.com/watch?v=O8_3PMVBUv8

 Collections issue?

Problem statement: In many companies the data for the receipts has not been entered bill wise. There is a need to adjust the ledger entries against the bill entries.

The system has been designed to work across multiple companies. 

with various outstanding bills in the Tally system. There is direct integration with Tally. The data capture can also be done using Turbodata. The following method can be used for resolving the same:

a.) Check for a given  party whether the bill entries are pending or not. This can be done by doing the comparison between 2 reports from Turbodata

Trial balance analysis with ledger flattening(Ledger Balance)

Payable and receivable snapshot with ledger flattening(Payableandreceivable_snapshot). 

The ledger  hierarchies shall help verify of the bills belong to the correct group parent.

If there is a difference between the closing ledger balance and total from the bill details then bill adjustment needs  to be done.

b.) Look at the complete cash flow statement(debit entries)  from the Ledgerview(here 'isvoid' and 'iscancelled' vouchers are to be excluded). 

The filter conditions include the following:

At the ledger_3 filter use 'Cash' Bank statement'. 

This indicates that there has been cash outflow movement for the given party(partyledgername would need to be chosen). We would consider the debit entries of cash and bank  for the same.

c.) Select those entries in part b.) that are not part of the voucherledgerbill movements. For the same the entire voucher ledger bill history for the set of firms shall need to be extracted.

The extract has been given in the object voucherledgerbill. The comparison shall be done using masterid and companyname.

After the above analysis we shall get the following 2 set of entries:

i.) Debit cash and bank ledger entries not adjusted against any bill(Ledgerview)

ii.) Debit  cash and bank ledger entries not associated with any bill(Voucherledgerbill)

Manual interface: Based on the unadjusted entries for the parties, the client to indicate which ledger movements are for the bill and which ledger movements are not associated with any bill. The Turbodata interface shall help with the same. The client team will help with the same.

The ledger payments not adjusted against the bills shall then be extracted from the ledger movement.

Usage of Turbodata(SQL Server):Hereafter we insert the data into Turbodata SQL Server module. The bill entries in the database are adjusted based on the ledger movement and the bill due dates. We look at partyledgername, bill amount, bill due dates for automated adjustment

Usage of the python data capture script to confirm the adjustment for each bill: Turbodata input forms shall then be used to adjust the amount for each bill. On approval by the required authorities the data shall be entered into Turbodata and Tally friendly Excel module

Note: the logic for post dated checks and on accounts balances shall need to be indicated by the end client.

The adjustment against each bill shall need to be done at the Turbodata data capture level.

For basic extraction please contact the following

Name: Apoorv Chaturvedi

email: support@turbodatatool.com;support@mndatasolutions.com

Phone:+91-8802466356