Inventory optimization Solution

www.mnnbi.net

Consolidation of MS Excel spreadsheets

Contact details of blog writer:

Video in Hindi: https://www.facebook.com/apoorv.chaturvedi.330/videos/1015686005248243/UzpfSTUyNDk5OTE5NDE4MTk1NjoyMTY4NDk1ODEzMTY1NjEx/

Video in English: https://www.facebook.com/apoorv.chaturvedi.330/videos/1015702448579932/UzpfSTEwMDAwNDIwNTU4ODA4NDoxMDE1NzA0MjcxOTEzMDgz/

Issues in consolidation of MS Excel data: https://www.facebook.com/apoorv.chaturvedi.330/videos/1019477321535778/?notif_id=1525763406981956&notif_t=page_wall&selected_item_id=207446349868644

Name: Apoorv Chaturvedi

Email: apoorv@mnnbi.com

Phone: +91-8802466356

website: www.mnnbi.com

Blogs:  http://mndatasolutionsindia.blogspot.in/

Most of the businesses use MS Excel spreadsheets for data capture, data reporting. A common set of problems that arise during spreadsheet consolidation are as follows:

•       Data consolidation takes times
•       Manual process.
•        Error prone: auditing of data is an issue.
•        Inflexibility of  analysis: the end clients do not get graphs and dashboards
•        The process is very time consuming

Turbodata helps resolve the problem by taking the following approach.

Turbodata has readymade datawarehouses associated with inventory, ledger where the on fly calculations are matching with a standard accounting package such as Tally ERP. The product has been designed using the philosophy of Goldratt, Deming and Toyota Production system. There are readymade extractors using C#,.Net for extracting data from ERPs such as Tally, SAP, Navision and even custom spreadsheets.

How does Turbodata help solve the problem?

•        The input spreadsheets could be imported in an xml format into a shared folder. The condition is that the input spreadsheet formats should not change for the end client.
•        The xml inputs are then imported to the database from wherein the reporting takes place.

Why use Turbodata?

•       Turbodata has a readymade datawarehouse for ledger and inventory with built in on fly calculations.  Turbodata inventory and Turbodata ledger have readymade data with perpetual valuations to re generate any type of MS Excel report.
•        The data extraction shall take place in such a way that minimal RAM is used. This shall help the end client in the following ways:
•         Multiple end users can update the spreadsheet data while data extraction is happening without any problems
•           The source machine shall not be stuck.
•        The solution shall be plug and play and very easy to use.
•        The data audit step of matching the output with the source table entries shall be part of the solution
•        The end client can get dashboards using a Business Intelligence tool of its choice. If the consolidated data is below 1 GB then Microsoft PowerBI can be used for getting best in class dashboards
•        Data entry and data validation shall be designed as part of the solution.
•     Lower cost of the solution through data compression and sql reduction.
•        Reduced manual data entry time and quick turnaround times for development of the final reports.

•     Consolidated Trial Balance and Stock Summary Reports.

Sample end client cases for consolidated trial balance reports.

Next steps:

The end client could send the following to the above email address:

·       Sample output spreadsheet to be automated

·       Sample input spreadsheets to be consolidated/The details of the source systems to be consolidated.

How Turbodata helped lower the costs of developing a datawarehouse and helped the end clients do predictive analytics with quickness and ease-applicable for retail sales and inventory(Website: www.mnnbi.com)

Purpose of the development of the product: The Turbodata team intends to reduce the costs of the analytic solutions by creating a single platform for ETL, Reporting, Reporting development and predictive analytics. The team also intends to provide the best in class analytics on the same machine on which the ERP is running or with the addition of minimum hardware requirements for the end client. This has been done to develop scalable systems that can be deployed over a large number of customers(with limited budgets) with ease(deployment, delivery and usage) and convenience(maintenance).

The end goal is to increase derisking and predictability for the end clients at lower costs.

Methodology for achieving the required ends for the end client:

·         Turbodata adopted the Inmon methodology for datawarehouse development so that multiple data sources could be added onto the same datawarehouse. That is the change from one data source to another was done with ease. More details on the attached web page link: http://mnnbi.com/mnnbi_tallydataconsolidation.html

o   The benefits of the normalization of data were as follows:

§  The incremental data load took minimum time and had minimum impact on the source system. The ETL team was able to commit the incremental data load to a maximum of 2GB RAM from multiple source systems. The source systems did not hang with the incremental data load working.

§  Error handling was done with ease at staging layer.

§  Massive data compression took place due to reduced data redundancies.

§  The business logic was coded between staging and the ODS layers thereby reducing the length of the final sql code.

The attached video shows a more detailed description of the benefits listed above:

https://www.youtube.com/watch?v=k9Oe9EDRfTM&feature=youtu.be

The joins were reduced in the data mart layer(over which a reporting layer was built).

The ETL team was able to develop extremely complex reports using the datawarehouse as in the attached sample:

https://www.youtube.com/watch?v=1ySNrgI4Na0&feature=youtu.be

Due to the data compression for most projects the ETL team are able to bring the data within 1 GB. Hence the desktop version of Microsoft Power BI could be used free of cost for the end client.

Reducing the cost of predictive analytics solutions

 Most of the end clients use high end predictive tools over the datawarehouse/ over the direct data extract from various source databases. With large datasets predictive analytics using in memory solutions entails high usage of RAM. The ETL team has gone around this issue in the following manner:

o   A seamless environment was created for ETL, reporting and thereafter predictive analytics on SQL/C# and .Net. The reasons for the same are attached herewith:

§  Maintenance becomes easier since there is a single platform for all aspects.

§  The cost comes down since the resources to be used for ETL can also be used for predictive analytics

§  Error handling becomes very easy since errors can be captured before in the

Hypothesis testing

Based on the hypothesis testing, the ETL team developed ARIMA analysis and Market Basket analysis in SQL using seamless integrated set of stored procedures. That is the ARIMA analysis flowed from the datawarehouse A,B,C categorization. The ETL team thus reduced the requirement for high end R and Python developers to code over the datawarehouse thereby presenting a seamless solution to the end client on a 8GB RAM machine.

Benefits to the end client:

·         The end client gets immediate and confirmed peace of mind and satisfaction through immediate deployment of predictive and forecasting analytics modules.

·         No additional hardware/software requirements need to be taken

·         The costs are way lower for the end client.

·         Large scale deployment is possible with the given set of solutions.

Please check the attached video for the same:

https://www.youtube.com/watch?v=PQfsfWLkaP8&feature=youtu.be

A more detailed video is attached herewith:

https://www.youtube.com/watch?v=7DoZDBay-bQ

Example of predictive analytics with Turbodata: Example of predictive analytics-Turbodata

Epilogue

The ETL team has been inspired by the following management books:

·         ‘Profit Beyond Measure’ by Thomas Johnson and Anders Brohms

·         McKinsey Mind by Ethan Rasiel and Paul Friga.

·         Blue Ocean Strategy by W. Chan Kim and Renee Mauborgne

·         Better India, Better World by Narayana Murthy


Capturing Data Entry/Data Audit Errors

A number of times the end client types in wrong data into the source ERP system thereby resulting in wrong outputs and results. Junk inputs imply junk outputs.  The ETL team would recommend an auditable output from Turbodata to be used as part of the reporting purposes.  Wrong data inputs can impact the end client in one or more of the following ways:

•        Wrong tax filing specifically in online scenario.
•         Wrong business picture
•         Wrong predictive analytics.

As per the Toyota ProductionSystem, bad inputs should not be processed further as it adds to the final costs.

The ETL team(my firm) has found the following errors with regards to the data entry inputs specifically with Tally ERP 9.0.  

·         Stock input has been in one godown but stock outward movement has been from other godowns:

·         Missing purchase or sales order entries resulting in negative stocks at given points in time. One cannot have negative stock balances at any point in time.

Other data input errors that we have commonly seen are as follows:

•       Duplicate payment entries
•      Duplicate sales entries
•        Receipt note entries but no purchase invoice entries
•         Payments not having the required bill reference numbers.

How to resolve the errors:

·         In an object oriented program it is difficult to catch the errors on a real time basis. The ETL team recommends using the relational databases for catching the errors. The real time extraction module for Turbodata should be used for the same.

·         Transferring the data onto the third normal database is recommended. This helps catch data duplicity based on the composite keys.

For example if an end client has made the same amount payment for a given voucher on a given fiscal date, then the same should come as part of the discrepancy report. It is possible that the end client could be correct. There is also a possibility that the payment entries have been made by 2 different resources. Further handling of the given situation is as follows:

·         If the end client desires to catch the following error then the username by which the data entries have been done shall not be added to the composite key. In such a scenario there is a discrepancy between the Turbodata ledger balance output and the Tally report. The end client to approve the discrepant entry before the data is input into the system for auditing purposes.

Using perpetual valuations for ledger and inventory instead of periodic valuations. For example if an end client relies on periodic valuations for ledger balances then a duplicate payment entry then the periodic balances at the end of the fiscal month are difficult to catch. For example if an end client has a duplicate entry of Rs. 100k(One hundred thousand  only) over a balance of say Rs. 15000k(One fifty million only).

However using the perpetual system it is easy to catch the data entry errors.

Matching the consolidated trial balances and closing stock balances at the database level with the on fly calculations at the software level.

A small story for the end user: as Yuval Harari is Sapians says that mankind is primarily driven by myths. Hence many a managers are driven by myths regarding software or the consulting companies having the right audit numbers(with the managers inputting junk numbers).

A small story from one of my favourite books(Raag Darbari by Srilal Shukla) could best illustrate the point.

The protagonist Ranganath had gone from the city to visit his relative, an aunt’s husband , in the village. During the course of the village fair, it was suggested that the group goes and sees the village temple for the local goddess. At the temple Ranganath found that the statue instead of been of a goddess was of a soldier( for a goddess he was looking for two lumps  in front and two lumps in the back). The priest asked for donations for the goddess. To this request Ranganath refused saying that the statue was not of a goddess but of a man. There was an ensuing scuffle between the villagers and Ranganath. Ranganath was eventually rescued by his cousin. On going out and meeting other people, the cousin mentioned the following:

"My cousin has come from the city and is very well read. That is why he talks like a fool."
The author has always associated himself with Ranganath.

Deployment of Turbodata for Retail company based out of Western India

Source system: multiple installation of Tally ERP 9.1.

Problem : The end client desired to have a custom installation of Turbodata based on the unique requirements of its business. The product shall be used for designing a custom web interface for customer interaction. The key tenets of the solution that differed from the standard deployment of turbodata were as follows:

·         Standard price list instead of weighted average or FIFO pricelist.

·         Closing stock value was to be calculated at a godown and item level.

·         The solution was to work across multiple locations seamlessly with maximum RAM usage been 1 GB for both initial and incremental data loads.

·         Custom masters extraction for item, stock group, category .

·         GST classification to be extracted for the end client.

Time duration of the project: 2 weeks.

Approach of the ETL team:

·         Choosing the appropriate set of attributes to be loaded based on the modular approach. That is the required fields to be loaded for ledger and inventory were chosen.

·         Custom extraction for the tables: The process of normalization helped in the same since the attribute is to be loaded only once.

·         Testing of initial and incremental data loads in terms of time and load on the system. The incremental data load process helped at reducing the time of data load.

·         Data cleansing: special characters were removed from the item names. Also separation of the numeric values from the character fields

·         Data consolidation: multiple types of voucher types were loaded onto the datawarehouse.

Project has been done successfully. Hereafter the end client shall go for a MVC interface over the datawarehouse for reporting and customer interaction purposes.


Facebook post: https://www.facebook.com/Consolidation-in-MS-Excel-2007-524999194181956/

How to optimize Inventory While Maximizing Sales

DO YOU WANT TO OPTIMIZE INVENTORY WHILE MAXIMIZING SALES
EASY TO USE PLUG AND PLAY SOLUTION

Contact: apoorv@mnnbi.com

Website: www.mnnbi.com

Phone: +91-8802466356

Linkedin page: https://www.linkedin.com/company/13700898/admin/updates/

Facebook page: https://www.facebook.com/Turbodatainventory/?ref=bookmarks

Blogger link: http://mndatasolutionsindia.blogspot.in/2018/03/developing-optimization-module-for.html

Why variations are more important than averages for inventory

Attached is a video explaining the same.

https://www.youtube.com/watch?v=sb7xkMUWX7Q&t=1s


For more detailed explanation: http://mndatasolutionsindia.blogspot.in/2018/03/developing-optimization-module-for.html

Proud to announce the first integrated GST connector for Tally and SAP R/3.

What is the problem that we have solved?

Contact details of blog writer:

Name: Apoorv Chaturvedi

Email: apoorv@mnnbi.com

Phone: +91-8802466356

website: www.mnnbi.com

Blogs:  http://mndatasolutionsindia.blogspot.in/

•         Developed a solution that is scalable
•          Automated
•          Tamper proof
•          Works across all types of ERPs
•          Works on the standards accepted by the market. In India Tally ERP is the standard.
•          Easy to deploy, easy to deliver and easy to use

We have developed the first integrated connector, that is tamper proof, automated and very easy to deploy and deliver,  for SAP R/3 and  Tally[currently these have been integrated in collaboration with a GSP partner(GST Suvidha Partner) ]. The GST reports from the connector match with the business logic of GSTR reports from Tally GSP.

Key points of integration:

·         Once the standard integration with Tally had been done, the integration with SAP took less than 15 days.

·         The solution was developed remotely with minimal number of resources(only 5 resources were involved).

     Why an immediate need?

•     Under filings in GST: https://timesofindia.indiatimes.com/business/india-business/govt-grapples-with-rs-34000cr-gst-puzzle-over-tax-mop-up/articleshow/63262422.cms
• 
  
•             Lower than expected revenue for government: http://www.financialexpress.com/economy/gst-revenue-stagnant-february-collections-to-drop-to-rs-85175-crore/1113201/
• 
  
• 
  

How did we solve this problem?

Understanding the psyche of large number of Indian end users

This blog attempts to understand human behaviour is absence of standards or changing standards in our day to day lives.

According to the book ‘Seven Secrets of Pursuasion’ by James Crimmins, human beings, whose brain is governed to a large course by the reptilian instincts, follow a 'Law of Imitation'.

What is Law of Imitation: in hedgehogs the scientists found that females tended to get attracted to males already having prior female partners. The new prospect females would tend to ignore the eligible males but not having prior female partners. In human construct this implies fan following for super stars like Katrina Kaif and our belief in various social constructs(based on religious or societal norms).

‘Seven Secrets of Pursuasion’ also states that human beings look for immediate and confirmed emotional benefit rather than a long term rational benefit whose outcome could be uncertain. That explains millions of people smoking(the threat if cancer is in the future and uncertain).

‘Sapians’ by Harari refers to the same as ‘memetics’ or the propagation of cultural memes. The memes are self propagating and can be self destructing also. Memes do not necessarily benefit the person propagating the same.

According to 22 Immutable Laws of Marketing, human beings follow the ‘Law of Mind’ and the ‘Law of Focus’ wherein human beings use products that first come into the mind. The product should lead to a specific word in the prospect’s mind.

Where does it lead us? Based on the above, the following could be considered by Indian customers:

·         Tally is associated with matching balance sheet and profit and loss numbers in the Indian customer’s mind. Tally has the first mover advantage.

·         The Indian consumer could like the GSTR reports to be matching with the Tally GSTR reports on a plug and play basis. We are looking at immediate benefit for the consumer by matching numbers with an accounting software commonly used by the businesses in India.

·         The Indian consumer would like automated filing of taxes to reduce the prospect of manual errors.

In case your are looking at automated filing of taxes with numbers matching with Tally GSTR reports then please check the following link:

http://mndatasolutionsindia.blogspot.in/2018/02/why-turbodata-gst.html

Details of GST filing:http://mndatasolutionsindia.blogspot.in/2018/01/automated-gst-Turbodata.html

Automated GST Filing using Turbodata and GSP Partners

Are you facing the following issues with regards to GST filing?

• ·         Delay in filing
• ·         Concern regarding the changing regulations from the government
• ·         Concern regarding reconciliation: specially for customers using MS Excel upload.
• ·         Have a manual process for GSTR filing. The manual process is prone to error
• ·         Have high manpower costs related with GST filing.

Turbodata shall help your firm with faster, easier and more convenient GST filing.

How is Turbodata different?

• ·         All the reports for the end client shall be developed on the cloud installation. Only a minimal extract for all the vouchers and masters shall be done from the end client location. The ETL team shall commit to usage of maximum amount of RAM for the same(say 1 GB for incremental data extract)
• ·         The end client can do the prior change of the data. The system shall automatically take care of the same. This is enabled through incremental data load process using data normalization.
• ·         No reports shall be developed at the client location. All the reporting work shall be done at the server location.
• ·         Initial and incremental transaction data extract shall be done from the end client location.
• ·         The end client need not worry about re filing the GST reports since it shall be done by the GSP partner automatically.
• ·         The package is very easy to deploy, deliver and maintain. No high end software are required. The system can extract data from SAP, Tally and other source systems with ease.
• ·         Dependence on MS Excel for tax filing purposes is taken away since it could result in data errors and discrepancies.

  Current system:

Why is the Turbodata system better?

Turbodata system:

·         Turbodata system is inspired by ‘The Deming Way’, ‘The Goal’ and the Toyota production system and the Inmon methodology.  In a nutshell the following are the features copied from the above systems by Turbodata:

o   No error prone data should be passed for the reporting purposes. The data needs to be cleansed, audited and consolidated before report development.

o   The processing of the transaction should be done as soon as the transaction has been fed in the source system. That is the processing should take place on a real time basis and not specifically at the end of the month. Turbodata enables this feature in the following manner:

§  Each transaction fed into the end client source system is assumed to be an order from the end client.

§  The system offers the facility for real time extract and upload(current system is manual but the data can be loaded on a daily basis by the end client go the server)

o   Once the data has been loaded onto the server, it is transferred to a normalized database(insert, update and deletes). At the data warehouse level the data cleansing, data transformation, data consolidation activities are done

o   Once the data has been cleansed at the datawarehouse level then the reports for GST are developed. In one single lot, GSTR1, GSTR2 and GSTR3 reports can be developed.

o   Turbodata is integrated with at least one GSP partner. The end client could look at other GSP partner solutions if it desires the same.

o   The deployment of the solution is very easy and convenient. For any end client the deployment should take not more than 20(twenty) minutes. Minimum installation pre requisites are required.

o   The data for the end client is stored in a datawarehouse. The end client does not need to worry about changes in the statutory requirements. Other high end services like inventory optimization and predictive analytics are possible on the cloud.

To check why should the end client consider Turbodata GST, please check the following linkage:
http://mndatasolutionsindia.blogspot.in/2018/02/why-turbodata-gst.html

Indicate the following:

·         ERP system/ERP systems

·         Turnover: frequency of load

·         Number of locations

  Sample video link: https://www.youtube.com/watch?v=sYbeBfc3ozo&feature=youtu.be

       The product uses optimum RAM so that the source system does not hang during extraction as given in the following video:
       https://youtu.be/7CULkzc5h2g

      Resolving Data Reconciliation Errors for GST

P Problem:

TThe ETL team intends to solve the following problems regarding GST filing:

·        Wrong data entries

Solve the problems of under filings for the government: As per the Times of India article, the government is dealing with under recovery for GST collections in India.

https://timesofindia.indiatimes.com/business/india-business/govt-grapples-with-rs-34000cr-gst-puzzle-over-tax-mop-up/articleshow/63262422.cms

o   Help the end clients meet the statutory requirements

·        Manual processes in filing taxes

·        Reconciliation of taxes: the ETL team believes that tax refund should be the ultimate target: As per the changed government norms, the buyers and suppliers could have  to reconcile the entries before filing the GST Returns.
http://www.business-standard.com/article/economy-policy/infosys-chief-nandan-nilekani-plan-on-gst-invoice-matching-may-be-tweaked-118022300073_1.html

·        Work across multiple systems: plug and play module

           Solution: Automated GST Filing using Turbodata and GSP Partners

         Are you facing the following issues with regards to GST filing?

• ·         Delay in filing
• ·         Concern regarding the changing regulations from the government
• ·         Concern regarding reconciliation: specially for customers using MS Excel upload.
• ·         Have a manual process for GSTR filing. The manual process is prone to error
• ·         Have high manpower costs related with GST filing.

     Turbodata shall help your firm with faster, easier and more convenient GST filing.

    How is Turbodata different?

• ·         All the reports for the end client shall be developed on the cloud installation. Only a minimal extract for all the vouchers and masters shall be done from the end client location. The ETL team shall commit to usage of maximum amount of RAM for the same(say 1 GB for incremental data extract)
• ·         The end client can do the prior change of the data. The system shall automatically take care of the same. This is enabled through incremental data load process using data normalization.
• ·         No reports shall be developed at the client location. All the reporting work shall be done at the server location.
• ·         Initial and incremental transaction data extract shall be done from the end client location.
• ·         The end client need not worry about re filing the GST reports since it shall be done by the GSP partner automatically.
• ·         The package is very easy to deploy, deliver and maintain. No high end software are required. The system can extract data from SAP, Tally and other source systems with ease.
• ·         Dependence on MS Excel for tax filing purposes is taken away since it could result in data errors and discrepancies.

  Current system:

    Why is the Turbodata system better?

     Turbodata system:

·         Turbodata system is inspired by ‘The Deming Way’, ‘The Goal’ and the Toyota production system and the Inmon methodology.  In a nutshell the following are the features copied from the above systems by Turbodata:

o   No error prone data should be passed for the reporting purposes. The data needs to be cleansed, audited and consolidated before report development.

o   The processing of the transaction should be done as soon as the transaction has been fed in the source system. That is the processing should take place on a real time basis and not specifically at the end of the month. Turbodata enables this feature in the following manner:

§  Each transaction fed into the end client source system is assumed to be an order from the end client.

§  The system offers the facility for real time extract and upload(current system is manual but the data can be loaded on a daily basis by the end client go the server)

o   Once the data has been loaded onto the server, it is transferred to a normalized database(insert, update and deletes). At the data warehouse level the data cleansing, data transformation, data consolidation activities are done

o   Once the data has been cleansed at the datawarehouse level then the reports for GST are developed. In one single lot, GSTR1, GSTR2 and GSTR3 reports can be developed.

o   Turbodata is integrated with at least one GSP partner. The end client could look at other GSP partner solutions if it desires the same.

o   The deployment of the solution is very easy and convenient. For any end client the deployment should take not more than 20(twenty) minutes. Minimum installation pre requisites are required.

o   The data for the end client is stored in a datawarehouse. The end client does not need to worry about changes in the statutory requirements. Other high end services like inventory optimization and predictive analytics are possible on the cloud.

To check why should the end client consider Turbodata GST, please check the following linkage:
http://mndatasolutionsindia.blogspot.in/2018/02/why-turbodata-gst.html

  Sample video link: https://www.youtube.com/watch?v=sYbeBfc3ozo&feature=youtu.be

       The product uses optimum RAM so that the source system does not hang during extraction as given in the following video:
       https://youtu.be/7CULkzc5h2g

Why Turbodata GST?

Based on the above philosophy, the following are the reasons one should look at Turbodata GST as a GST filing solution.

·         Law of Focus: The end client should have one word embedded into customer’s mind. In such a scenario most of the end clients have Tally embedded into their minds for GST filing. Turbodata GST matches the numbers with Tally GST reports to give customers peace of mind and satisfaction.

·         Law of opposites:

o   Turbodata offers cloud based GST filing system while Tally offers desktop/server based GST filing system

o   Turbodata enables faster, easier and more convenient data upload facilities than Tally ERP 9.0.

o   Turbodata offers historical data correction automatically for GSTR reports while in case of Tally the end client shall have to re file the offering.

o   Turbodata GST can work with multiple ERP systems and is extremely scalable.

·         Law of Ladder: Tally has top of mind recall for the customers for accounting accuracy. Turbodata GST team recognizes the same. It matches the GSTR reports with those of Tally GSTR while making it easier and more convenient than Tally to file GST taxes.

·         Law of Mind: Tally stands for accuracy while Turbodata stands for speed matching with Tally numbers. Turbodata GST offers GST filing services matching with Tally ERP 9.0 for any ERP.

      Capturing data entry errors:

A number of times the end client types in wrong data into the source ERP system thereby resulting in wrong outputs and results. Junk inputs imply junk outputs.  The ETL team would recommend an auditable output from Turbodata to be used as part of the reporting purposes.  Wrong data inputs can impact the end client in one or more of the following ways:

•        Wrong tax filing specifically in online scenario.
•         Wrong business picture
•         Wrong predictive analytics.

As per the Toyota ProductionSystem, bad inputs should not be processed further as it adds to the final costs.

The ETL team(my firm) has found the following errors with regards to the data entry inputs specifically with Tally ERP 9.0.  

·         Stock input has been in one godown but stock outward movement has been from other godowns:

·         Missing purchase or sales order entries resulting in negative stocks at given points in time. One cannot have negative stock balances at any point in time.

Other data input errors that we have commonly seen are as follows:

•       Duplicate payment entries
•      Duplicate sales entries
•        Receipt note entries but no purchase invoice entries
•         Payments not having the required bill reference numbers.

How to resolve the errors:

·         In an object oriented program it is difficult to catch the errors on a real time basis. The ETL team recommends using the relational databases for catching the errors. The real time extraction module for Turbodata should be used for the same.

·         Transferring the data onto the third normal database is recommended. This helps catch data duplicity based on the composite keys.

For example if an end client has made the same amount payment for a given voucher on a given fiscal date, then the same should come as part of the discrepancy report. It is possible that the end client could be correct. There is also a possibility that the payment entries have been made by 2 different resources. Further handling of the given situation is as follows:

·         If the end client desires to catch the following error then the username by which the data entries have been done shall not be added to the composite key. In such a scenario there is a discrepancy between the Turbodata ledger balance output and the Tally report. The end client to approve the discrepant entry before the data is input into the system for auditing purposes.

Using perpetual valuations for ledger and inventory instead of periodic valuations. For example if an end client relies on periodic valuations for ledger balances then a duplicate payment entry then the periodic balances at the end of the fiscal month are difficult to catch. For example if an end client has a duplicate entry of Rs. 100k(One hundred thousand  only) over a balance of say Rs. 15000k(One fifty million only).

However using the perpetual system it is easy to catch the data entry errors.

Matching the consolidated trial balances and closing stock balances at the database level with the on fly calculations at the software level.

A small story for the end user: as Yuval Harari is Sapians says that mankind is primarily driven by myths. Hence many a managers are driven by myths regarding software or the consulting companies having the right audit numbers(with the managers inputting junk numbers).

A small story from one of my favourite books(Raag Darbari by Srilal Shukla) could best illustrate the point.

The protagonist Ranganath had gone from the city to visit his relative, an aunt’s husband , in the village. During the course of the village fair, it was suggested that the group goes and sees the village temple for the local goddess. At the temple Ranganath found that the statue instead of been of a goddess was of a soldier( for a goddess he was looking for two lumps  in front and two lumps in the back). The priest asked for donations for the goddess. To this request Ranganath refused saying that the statue was not of a goddess but of a man. There was an ensuing scuffle between the villagers and Ranganath. Ranganath was eventually rescued by his cousin. On going out and meeting other people, the cousin mentioned the following:

"My cousin has come from the city and is very well read. That is why he talks like a fool."
The author has always associated himself with Ranganath.

    Reconciliation for GST filing: 

   Understanding the behavior of average Indian customer.

This blog attempts to understand human behaviour is absence of standards or changing standards in our day to day lives.

Based on the above philosophy, the following are the reasons one should look at Turbodata GST as a GST filing solution.

·         Law of Focus: The end client should have one word embedded into customer’s mind. In such a scenario most of the end clients have Tally embedded into their minds for GST filing. Turbodata GST matches the numbers with Tally GST reports to give customers peace of mind and satisfaction.

·         Law of opposites:

o   Turbodata offers cloud based GST filing system while Tally offers desktop/server based GST filing system

o   Turbodata enables faster, easier and more convenient data upload facilities than Tally ERP 9.0.

o   Turbodata offers historical data correction automatically for GSTR reports while in case of Tally the end client shall have to re file the offering.

o   Turbodata GST can work with multiple ERP systems and is extremely scalable.

·         Law of Ladder: Tally has top of mind recall for the customers for accounting accuracy. Turbodata GST team recognizes the same. It matches the GSTR reports with those of Tally GSTR while making it easier and more convenient than Tally to file GST taxes.

·         Law of Mind: Tally stands for accuracy while Turbodata stands for speed matching with Tally numbers. Turbodata GST offers GST filing services matching with Tally ERP 9.0 for any ERP.

·         The Indian consumer would like automated filing of taxes to reduce the prospect of manual errors.

    Data reconciliation for GSTR reports: 

   

• Consolidated platform for data consolidation, data cleansing and data transformation.