Service level agreements for Tally to Powerbi module and Tally to SQL Server Reporting level module

 Problem statement: Many firms use the top down approach in Tally for report generation. The firms face bottlenecks with regards to complete report generation. 

For example for collections the companies could look at debtor closing balance besides the one in 'Sundry Debtors'. 

For example: take the case of the following company:

Mobile app number:

However the receivables can be in other groups also.

Many customers desire a more comprehensive collection process by doing a bottom up approach.

The same is done with respect to our json extract from Tally.

Attached are the service level agreements that we can sign:

a.) Unlimited companies extract.

b.) Report refresh time of less than 5 seconds. 

c.) Complete trial balance extract up to any level of ledgers.

d.) No parameterization of reports required for ledgervouchers, stockitemvouchers and costcentrevouchers.

e.) Complete ledger and group level hierarchy flattening up to 10 levels.

f.) If the SQL Server database is used then using the incremental data load the extract time can be reduced to less than 10 seconds(on per voucher extract).

g.) No load on Tally in the time that the reports are been refreshed.

h.) Minimal tables for analysis: in our core module without the cost centre we propose to reduce the number of table extracts to one. 

• The single extract shall include voucher ledger, inventory movements, item hierarchy and ledger hierarchy movements   in the Tally Powerbi module.
•  The single table extract shall include, voucher ledger, voucher item, batch, bill history, item hierarchy and ledger hierarchy movements in Tally SQL Server module.

 

Note about inventory valuations: we shall offer only inventory valuations.based on weighted average valuations. The entries shall include only isoptional:no,isvoid:no,iscancelled:no,isdeleted:no, isinvoice:yes and purchaseaccounts:yes. Any direct expense entries associated with the isinvoiced entries should be in the same voucher.

A separate note on cost centre  module

Cost center module is separate than the core single table module. This is because there are lot of complications with regards to cost centre(specifically with regards to inventory movements). We are however extracting ledger and inventory movements with regards to the cost centre movements.

Contact us for a free demo on the Tally extraction methods using xml and odbc methods. You shall get sample Tally to excel extract for xml.

Name: Apoorv Chaturvedi

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

Phone:+91-8802466356

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