Monday, 19 April 2021

GST2A Reconciliation

 

Documentation for GSTR2A reconciliation for India’s leading Retail Chain

Reason for the development of the module:

 

The module has been developed for chartered accountants and end clients to help resolve the GSTR2A reconciliation issues.

Why is this module required?

·         The data been handled for GSTR2A reconciliation can be very large. With excel handling of the data could be very cumbersome

·         There are a large number of conditions by which GSTR2 might not make a match between the client purchase invoices and the client buyer sales invoices. The reasons for the variations could be with regards to document number, document date, Recepient GSTIN, buyer GSTIN and even the transaction amounts. In order to handle the mismatches between these types of invoices there are a large number of join conditions involved.

·         The developed solution can be a standalone module for Chartered accountants not involving the complete GST extraction and services from various data providers

·         Benefits with regards to ERPs:

o   The solution is based on Azure cloud. It uses the high processing power of Azure cloud for faster data processing

o   The solution offers web and mobile access for GSTR2A reconciliation

o   The client can also share with the vendors using whatsapp and email any discrepancy details

o   The development team is bringing with itself automated extractors from Tally and other ERPs.

o   The development team is bringing with itself specialized Chartered  accountants with experience is GST 2A reconciliation(https://www.linkedin.com/in/sharad-maheshwari-688b733/)

o   The data should be secure(on Microsoft Azure cloud) and there should be facility for each company to see its own data(row level security)

o   The business logic should be auditable.

 

The following are the steps followed for the GST2A Audit process:


 For the GSTR2 A reconciliation the sample client is using the following composite keys

·         Document number

·         Document date

·         Supplier GSTIN

·         Company GSTIN

·         Taxable Amount

·         Total GST amount

 

There can be some variations in the Taxable amount and the total GST amount. That logic has to be incorporated into the final audit report.

Supplier GSTIN and Company GSTIN have to match. However there can be discrepancies in Document Number and document date because of different ERP systems.

The client’s logic entailed that match shall include all 6 criteria. Alternatively, if 4(supplier GSTIN, Company GSTIN, taxable amount and Total GST amount) criteria match but there is discrepancy in the remaining 2 criteria (document number an document date) then it should still be considered matched.

Methodology of the development of the solution:

·         The solution was developed in Powerbi for the following reasons:

o   Consolidate the data from different data sources

o   Incorporate the client logic

o   Easy and secure viewing through the Azure portal

o   Standardization of the formulae.

o   Reduce the handling times for GSTR2A reconciliation with large and varied data.

o   No row limitations as far as the processing of the data is concerned



Attached is the methodology for the same:

1.       Find the exact match for the entries:



1.       Find those entries where the client has filed the returns but the returns are not in GST audit-sample code


3.       Find those entries where the client’s customer has filed the data but client has not filed the data


3.       Find those entries where the client’s customer has filed the data but client has not filed the data


 3.) Find those entries where the document number is not matching:


4.) Document date mismatch data


Once  the above analysis has been done then specific matching criteria can also be done by GST number, document number and document date



Other reports: Based on the analysis after steps 1 ,2 and 3 it is possible to divide the data to find the exact mismatch

Custom variations based on Total tax amount and total amount are also possible. A sample case study is attached herewith:

4.       Match  the ERP and the GST data . The ERP data shall come from any ERP(including Tally). The GST data shall come from the GST portal as part of the GSTR2 reconciliation).


1.       Exclude the entries not in the exact match


5.       Extract those entries that have matching Taxable amount, Total amount, recipient GSTIN, Supplier GSTIN but not matching document number and document date

5.       Extract those entries that have matching Taxable amount, Total amount, recipient GSTIN, Supplier GSTIN but not matching document number and document date





Please contact the following for automating your GST 2A audit process

 

Apoorv Chaturvedi(Phone: +91-8802466356, email: support@turbodatatool.com, support@mndatasolutions.com)


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



Monday, 11 January 2021

Sell more of your inventory to existing customers-Consulting service from M&N BI Analytics

 

Downloading of Powerapps Mobile app on your mobile from google store:



Username: mnnbiapps@mndatasolutions.onmicrosoft.com

Password: Bhaiya80$


 Video of the  usage of the Powerapps app: https://www.youtube.com/watch?v=oO9Dzasavwo&feature=youtu.be





Why there is a need for the service?

Many clients have large stocks of inventory and there is a need to sell the inventory to various prospects. These prospects could be current customers or additional new customers. The given consulting solution proposes to increase the product sales to the existing customers:

·         The existing customers could have ready access to the inventory of the Tally client.

·         The ready customer can ask for a quotation from the Tally client.

·         The Tally client administrator(owner, senior manager or the sales resource) can access the accounts receivable status of the client.

·         The customer of the Tally client can also intimate of the payments that could be done. This process shall help the Tally client devise an effective payment follow strategy.

·         The system shall help the Tally client devise a dynamic pricing strategy based on the order requirements and payment history of the customer.




What do we offer?

·         Best in class inventory analysts with knowledge of business intelligence modules and inventory optimization techniques.

·         Best in class receivable analysts with knowledge of business intelligence modules from Microsoft

·         Built in extractor with data consolidation modules with Tally ERP 9.0.

·         Readymade apps for the solution.

What is unique about the M&N BI Powerapps solution?

·         Per user limitation has been taken away in this solution: Most of the other mobile apps have per user costs associated with them on a per month/per year basis. In this mobile app the per user limitation has been taken away. That is it is possible for the end client to give the required mobile app to its customers. The applicability  for the Tally partners and other software vendors is as follows:

o   Ability to develop one’s own market place based on the client requirements. Say a company has 500 customers for steel tubes. Then all the customers inventory  data  can be uploaded onto the cloud and possibilities for the secondary sales be done.

o   Usage of workflows: The workflows are important for capturing the quality of the client prospect. Since the solution is extracting the data to the datawarehouse, extensive control systems can be defined for the end clients. Also due to the massive data compression and sql reduction on the datawarehouse cloud the refresh times for the complex reports can be significantly reduced.

 

Workflow for the sales problem

Attached is the suggested workflow for additional sales of items

Sample Mobility apps to be given to the Tally client’s customers:

 

Inventory visibility:

Workflow system







User view:




Administrator View:

Admin Sign Up [Company Account Creation]







User name: Email
Password: 123456





Option to the end client for giving forecasted requirement



Receivable snapshots for the client


Option for client to give the payment dates


  Admin view

Admin view sign up


Mnnbianalytics-adminsignup is used for the sign up of the client (Company creation for the MNNBI Analtics) that is used for the Admin Login in the MNNBI Analytics App by the client

User Name: Client User Name used for the Admin Login for the company (User Name should be Unique)

Email: Client Company Email

Company Name: Company Name present in Tally ERP which data is extracted

Company Name is used for the Validation purpose that check the admin info exist in the database or not

Password: Password used by the client for the security & Authenticate the login



MNNBI Analytics Admin Login Page:



User Name & Password: Created by client in Mnnbianalytics-adminsignup

For login: Company Name is used for the Validation purpose that checks the admin info exist in the database or not  






Admin view of inventory




The sample username for admin is "samplecompany" and password is "123456"

The administrator gets the stock and forecasted requirements on his mobile







Admin view of accounts receivable



Client commitments to payments




How to get the mobile app working for your firm?

Points to note: The given mobile app shall work for only one company per Tally serial number.

Pre requisites for starting the package:



Download the automated Tally extractor

 Video of the  usage of the Powerapps app: https://www.youtube.com/watch?v=oO9Dzasavwo&feature=youtu.be

Drop box link:

https://www.dropbox.com/sh/8oauya52463n1eg/AAD6oViLTmafzQX1rAt5_GPca?dl=0

Follow the scheduling steps as given in the video above: https://youtu.be/2MKXknOqwlA















Contact: Apoorv Chaturvedi

Email: support@turbodatatool.com, support@mndatasolutions.com

Phone: 8802466356, 7982891666

website:https://mn-business-intelligence-india.business.site/

Resolving Running Sum problem using DAX from Tally

 The given product helps resolve the following problems with regards to valuations across large number of ERP installations.

Attached videos explains the demo:



Copy of the demo:

https://youtu.be/5XIlNLABCIY


The video below gives the following:

Testing the collections and linking the dashboards to the cloud:

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


Powerbi app  trial login:

Username: guest@mndatasolutions.com.microsoft.com

Password: Bhaiya80$


Download of the sample dashboards-through dropbox:

Dropbox login: powerbimnnbitrial@gmail.com

Password: Bhaiya78$




Client problem: The end client is looking for perpetual inventory and ledger valuations on the date and year month granularity.  This is required for calculating the perpetual gross profit and the perpetual trial balance for the end client.

The issue to be resolved is as follows:




Problems to be resolved for the end client:
a.) Get right inventory valuations by weighted average method for the end client. this shall impact the closing stock value for the end client.
b.) Find the historical accounts receivable ageing for the ledgers at various levels of granularity.  the granularity in the current extract is on daily and year-month basis.

To calculate the running sum in sql or the other languages like TDL is quite complicated in terms of the code. Hence the developer has used the Powerbi DAX coding for simplifying the coding process.

One normally gets the ledger balanaces as a snapshot from various ERPs like Tally( as given below):

However there is a requirement to do the ledger analysis on the basis of dynamic time entries. That is the time framework is not a snapshot but dynamic. 
In order to get the ledger balances in a dynamic fashion one needs to combine the opening ledger balance along with the historical ledger entries

The opening ledger balance is obtained from the ledger snapshot as shown below:



The historical ledger entries is obtained by walking the voucher across allledger entries as shown below:

The issue is that the snapshot and the historical ledger entries need to be combined to get the consolidated running ledger entries.

Thereafter consolidation needs to be done based on time intelligence aggregates.



In order to do the consolidation one needs to either do a join or develop a custom function for walking the collection.
The above process is replaced by DAX code. This DAX code shall ultimately be executed in the cloud.

The method of aggregation is to combine ledger snapshot(with filter conditions for the parent ledger type been "Sundry Debtors" and "Sundry Creditors") and the voucher-allledgerentries to be filtered by parent vouchertypename as "Sales", "Journal" and "Receipt". The value of total credit minus the total debit is the net amount for the given fiscal date. This is then combined with the opening ledger entries to give the consolidated ledger balances.


The join conditions entails joining between a snapshot(Ledger) entity and a cumulative(Voucher-allledgerentries) entity.


The running total is calculated in DAX using the cumulative entries and the date dimensions.




Other dashboards for the product.


This set of dashboards gives the comprehensive Profit and loss analysis based on the dynamic date filter.
The clients should get gross profit, net profit, cost of goods sold, revenue aggregates at various levels of heirarchy(year to date, month to date and quarter to date). Also the clients shall get store wise sales numbers at various time granularities.



Historical inventory analysis; this dashboard gives the inventory profitabiluty analysis at voucher-allinventoryentries level. The granularity of analysis could year, year-quarter and year month. The clients  shall get profitability analysis by items.




The above dashboard is ledger wise profit and analysis sales dashboard. There are readymade objects for sales, gross profit, net profit and cost of sales.


Accounts receivable analysis: this gives the analysis of accounts receivable by ledger snapshot and ledger historical entries.

In case one desires top buy the product then the following are the payment details:



Payment details:


Pre requisites for the package are as follows:


In case the client desires to have the same on Powerbi desktop then the following are the pre requisites:


Initial and Incremental data Load Template by M&N Business Intelligence-SAP Data Services

  INCREMENTAL LOAD/CREATION OF DIMENSION TABLE LOGIC AT SAP DATA SERVICES END CLIENT In this particular document we shall be looking at the ...