A Story of the 180-Day Rule Trap

 The Ghost in the Ledger: A Story of the 180-Day Rule Trap

sample report

The Complacency of "Screen Truth" Amit, CFO of a manufacturing firm, confidently reviewed his Tally screens. Navigating the Sales Register and Sundry Creditors via standard shortcuts—D+A+S, ALT+F2, and F12—the "Screen Truth" showed manageable payables. He assumed vendor payments were on track.

The Audit Storm Dread set in when a GST Audit Notice arrived. The auditor invoked the second proviso to Section 16(2) and Rule 37, demanding a report of all inward supplies unpaid within 180 days of the invoice date.

The Technical Blind Spot Amit’s team tried exporting data via Tally’s standard ODBC interface, triggering a crisis. Standard exports are restricted to snapshots and often fail to provide details below the second level of hierarchy—missing the bill history and batch details needed to track individual settlements. Worse, bank payment details (NEFT/cheques) lived on a separate "data island." Without linking "Against Reference" payments to specific "New Reference" invoices, Amit couldn't prove when bills were settled.

The Cost of "Missing" Data Unable to provide transaction-level forensic proof, the law was absolute: Amit had to reverse Input Tax Credit (ITC) on those supplies plus pay 18% interest. This "technicality" cost his firm ₹12 lakhs in one quarter—cash essentially "stolen" by poor data visibility.

The Forensic Restoration Amit realized Tally handles operations but doesn't explain the numbers. He deployed TurboData’s Finance Intelligence Infrastructure, using specialized TDL extraction to flatten Tally’s data into a relational 2NF/3NF schema. Unlike standard exports, TurboData’s "Single Table" architecture joined VoucherLedgerDetails, VoucherInventoryDetails, and VoucherLedgerBillDetails using a surrogate MasterID.

1. Automated Ageing: Instantly generated ageing buckets including >180 days.
2. Bank-to-Bill Linking: Used bridge records to connect bank instrument details (NEFT ID, dates) directly to bill settlements.
3. Forensic Truth: Using Frozen SQL Snapshots, Amit produced reproducible reports for any past date, proving exactly what was owed and paid.

The Moral Tally is for entry; structured data is for defense. Missing bill-wise history is a direct cash leak under Rule 37.

"Audit log tells you what changed; TurboData tells you exactly what existed at the transaction level."

#TallyPrime #GSTAudit #Rule37 #AccountingAutomation #CFOInsights #ForensicAccounting #TurboData #FinanceIntelligence #AuditReady

Your sales is hiding under sundry creditors-tally

 Case Study: The Case of the Missing Millions — Why Your Sales are Hiding in the Creditors

Have you ever wondered why your Profit & Loss statement shows record-breaking sales, yet your bank balance is bone-dry? You check your Sundry Debtors, you chase every invoice, but the numbers just don't add up.

The Story: Meet Rajesh, the CFO of a fast-growing distribution firm. Rajesh was proud of his team; they were hitting their targets, and the Sales Register (D+A+S) in Tally was glowing. But there was a ghost in the machine. While the "Screen Truth" in Tally showed healthy receivables, the company was facing a massive cash flow crunch.

Rajesh did what every CFO does: he looked at his Sundry Debtors ageing. Everything seemed under control. But then he deployed TurboData’s Finance Intelligence Infrastructure.

The Discovery: The TurboData "Single Table" architecture revealed a startling forensic truth: Rajesh’s sales were hiding in the creditors.

In Tally’s hierarchical database, a party is often pigeonholed into one group. Rajesh had several large parties who were both customers and suppliers. While the sales team saw them as "Creditors" (because they bought raw materials from them), they were also selling finished goods to the same parties. Because their net balance sat in the 'Sundry Creditors' primary group, they were completely invisible to the receivables team.

The "Forensic Truth" Metric: Weighted Average Payment Days Rajesh was only looking at static snapshots. TurboData’s engine did something deeper. It utilized a perpetual "Running Sum" logic across every ledger movement—Sales, Journals, and Credit Notes—across unlimited companies.

Instead of just looking at "Total Due," the system calculated the Weighted Average Payment Days for these "hiding" parties. The formula wasn't just a simple average; it was weighted by the invoice value to determine the true speed of cash recovery.

The Result:

Found the Hidden Cash: Rajesh discovered ₹1.8 Crores in receivables that were "netted off" against payables in the Creditors group, but the payment for the sales side was actually 90 days overdue.

Eliminated Drudgery: His team stopped the "keyboard marathon" of manual Excel VLOOKUPs between Debtors and Creditors lists, saving over 700 hours of manual labour per year.

Audit-Proofed the Books: By using Frozen SQL Snapshots, Rajesh could reproduce these numbers for his auditors instantly, proving the "Forensic Truth" of his cash flow.

The Moral of the Story: Standard Tally handles operations, but it often hides the business reality. If you only look at your Sales Register, you are seeing an "on-the-fly" calculation, not the ledger truth.

Stop looking at your "Screen Truth." It's time to find your hidden sales with TurboData.

#TallyPrime #AccountingAutomation #CFOInsights #CashFlow #ForensicAccounting #TurboData #FinanceIntelligence #WeightedAverage #AuditReady

Sample sales report: http://103.211.202.97:5002/salessingletable

How a large education institution reduced its dependence on shortcut keys in Tally for report export-AI and automation

 Case study:One the largest educational institutions in central India. Its data is in 2 instances of Tally: Tally Prime and Tally edit log. Each instance has more than 40 companies(total number of companies 85). The institution is looking at usage of Powerbi and automation through say UIPath and Python.  For such a scenario the bot or the robot needs to track the possible keystrokes.

The Problem: Reporting Required Repeating 15+ Keystrokes Per Company

To extract a Bills Receivable or Bills Payable report, the operator had to press:

• ALT+F3 → Switch company (done 84 times)

• ALT+G or D + S + O + R → Navigate to report

• F4 → Filter by group (assume 5 groups)

• F5, F8, F12 → Configure columns, ledgers, periods

That’s 15+ keystrokes per report, per company, per group.

Manual Keystroke Estimate

• 15 keystrokes x 2 reports (Receivable & Payable)

• x 84 companies

• x 5 groups
  = 12,600 keystrokes per day

Assuming 20 working days = 252,000 keystrokes/month

How TurboData Replaced 252,000 Keystrokes with 1 Shortcut

Using TurboData’s backend automation engine, the institute replaced manual ALT+F3, F4, F8, F12 sequences with a single shortcut key – ALT+0.

Our tool:

• Automatically switched companies (multi-F3 logic)

• Loop-processed all groups and ledgers

• Applied date filters & aging configs (F12)

• Pushed clean data into SQL Server and Power BI

Daybook Analysis Automation with TurboData

For Tally users, analyzing the Daybook involves a repetitive set of manual keystrokes that eat up valuable time every single day.

🔁 Typical Shortcut Key Sequence:

• D + D – Open Daybook

• ALT + F2 – Select Date Range

• ALT + F3 – Change Company

• F4 – Choose Voucher Type

• B – Basis of Values

• F12 – Configuration (Ledger, Cost Centre, Item-wise, Bill-wise)

That’s at least 6–7 keystrokes per query, repeated for different filters and settings.

---

🔢 Real-World Impact: The Hidden Cost of Manual Keys

Let’s break it down for a multi-company setup:

• 84 Companies

• 10 Query Points per Day

• 20 Working Days a Month

➡️ That’s a minimum of 12 key strokes x 10 queries x 84 companies x 20 days
➡️ = 201,600 keystrokes/month

That's not just exhausting — it's error-prone and non-scalable.

Balance Sheet Automation: Say Goodbye to Repetitive Keystrokes

Generating a Balance Sheet in Tally isn’t as simple as just hitting "Display". For every view — group-wise, ledger-wise, or filtered — users must go through the same set of shortcut keys manually.

🔁 Manual Keystroke Sequence:

• D + T + ALT + F1 – Open Balance Sheet (detailed)

• B + ALT + F1 – View Basis of Values (detailed)

• F3 – Company Selection

• F4 – Group-Wise View

• F5 – Ledger-Wise View

• F12 – Configuration (Cash/Bank, Profit & Loss, Pending, etc.)

That’s a minimum of 6+ key presses per company just to get a single view.

---

🔢 The Numbers: Keystroke Overload

Let’s calculate the manual effort for a typical organization:

• 84 Companies

• 2 Balance Sheet Queries/Day

• 20 Working Days/Month

➡️ 6 keystrokes × 2 queries × 84 companies × 20 days
➡️ = 20,160 keystrokes/month

And that’s just for the Balance Sheet!
Add in Receivables, Payables, Daybook… and we’re talking about hundreds of thousands of unnecessary keystrokes.

In case a bot is to be programmed for getting all the data the total iterations could be more than 453000. 

All the above programming steps have been automated using Turbodata.

Contact:

Apoorv Chaturvedi

Phone:+91-8802466356

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

Youtube channel:@mndatasolutions2042.

Reduce costs:Paying for each mobile number for Mobile access for ERP/Tally ERP data

 Problem statement: for many companies the number of internal mobile users for ERP/Tally ERP data on mobile are significant. Say the number of mobile users is 10. The other issues to be raised are as follows:

a.) The clients could have multiple companies.

b.) The client could desire to have complete control over the data.

c.) The costs could increase exponentially.

d.) The client could desire to give access to external stakeholders as well.

The solution to this problem can be envisaged in multiple ways. We have looked at the following ways:

a.) Giving access through excel

b.) For tamper proof access giving access through Powerbi[no database involved]

c.) For lowest cost over a large number of end users access through sql server database using row level security.

Access through Excel:

For many of the reports Tally could be used as a webserver and the data imported into Ms Excel. The data could be extracted into Excel through powerquery or odbc.

sample xml import into excel for Tally:

let

    // Define the Tally URL

    Tally_URL = "http://localhost:9000",

    // Define the XML Input

    XML_Input = "

        <ENVELOPE>

            <HEADER>

                <VERSION>1</VERSION>

                <TALLYREQUEST>Export</TALLYREQUEST>

                <TYPE>Data</TYPE>

                <ID>Balance sheet</ID>

            </HEADER>

            <BODY>

                <DESC>

                    <STATICVARIABLES>

                        <EXPLODEFLAG>Yes</EXPLODEFLAG>

                        <SVEXPORTFORMAT>$$SysName:XML</SVEXPORTFORMAT>

                    </STATICVARIABLES>

                </DESC>

            </BODY>

        </ENVELOPE>",

    // Send HTTP POST request to Tally and fetch the response

    Response = Web.Contents(

        Tally_URL,

        [

            Headers = [#"Content-Type" = "application/xml"],

            Content = Text.ToBinary(XML_Input)

        ]

    ),

    // Parse the XML Response

    XML_Data = Xml.Tables(Response)

in

    XML_Data

The odbc extract is straight forward and can be taken from Tally website.

Once the Excel sheet has been extracted it can be shared via onedrive,googledrive or shared drive.

b.) Usage of Powerbi: Powerbi offers a free on mobile version using the Microsoft platform.Our Powerbi integration would work with the following:

i.) odbc extract :Tally as a webserver

ii.) XML extract: Tally as a webserver

iii.) Json extract: no need of Tally as a webserver, unlimited companies, the business logic has been pre coded in Powerbi.

With the Powerbi version we can also design customized mobile apps for large scale viewing.

Please see our channel for lots of videos and details regarding the same.

SQL Powerbi training module:https://www.youtube.com/watch?v=ptn-rwYGUwY&list=PLZPWImFqOkLtJk2MoUPjb6ap_wFbJN53E

Summarized Powerbi app: https://www.youtube.com/watch?v=eIT4YAITIIg&list=PLZPWImFqOkLvDtnthqV9MzLoXDfoYWNSO

Points to note: If the Myworkspace in the Powerbi module is used then the app can be used by unlimited personnel.

However in case one requires row level access to the data then multiple Powerbi licenses are required. The cost of each Powerbi pro license is USD 10 a month[the data is hosted on the Microsoft cloud servers].

c.) In case the following is the scenario:

i.) Large number of people need to be given access to the data

ii.) Secure row level access for the data is required.

iii.) Data entry features are required.

Then we recommend Web app through SQL Server. The same will work with xml,odbc and json.

Website link:http://103.211.202.97:5002/

Username:Rohit

Password:Rohit@123

View reports: http://103.211.202.97:5002/view-reports?

Data entry format: http://103.211.202.97:5002/data_entry_masterpage?

In this case unlimited people can access Tally data in a secure fashion using row level security.

Please give us a chance for ETL demo.

Name:Apoorv Chaturvedi

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

Phone:+91-8802466356

youtube channel:www.youtube.com\@mndatasolutions2042

Incomplete collections-Tally (a different approach)

 Problem statement: a number of customers still have cash flow issues after taking the following actions:

a.) Usage of Tally

b.) Usage of third party mobile apps.

Here is an analysis of how one can seek to resolve the problem.

a.) Complete receivable data: the complete receivable data is very challenging with Tally. Normal approach is as follows:

i.) Look at ledger closing balances from current assets and to sundry debtors as follows:

Most mobile apps give the debit balance of the sundry debtors as the total to be collected.

Problem with this approach:

a.) Tally calculates sales amount as those entries that affect the ledger primary sales accounts, not optional, not void and not cancelled. The entries can be with multiple voucher types and can affect sales accounts.

For example sales can be done to sundry creditors and the same can be left by this approach.

Issue with using sundry debtors. There could be certain sub groups in sundry debtors and sundry creditors where we might not like to do the payment follow ups. For the same we need to do the group ledger hierarchy flattening. The same can be addressed by looking at the following collection extracts:

Issue with Trial balance extract. The trial balance extract does not give the complete parent hierarchy and does not give the ledger details below the second level hierarchy.

For example with the trial balance export:

<ENVELOPE>

<HEADER>

<VERSION>1</VERSION>

<TALLYREQUEST>Export</TALLYREQUEST>

<TYPE>Data</TYPE>

<ID>Trial Balance</ID>

</HEADER>

<BODY>

<DESC>

<STATICVARIABLES>

<EXPLODEFLAG>Yes</EXPLODEFLAG>

<SVEXPORTFORMAT>$$SysName:XML</SVEXPORTFORMAT>

</STATICVARIABLES>

</DESC>

</BODY>

</ENVELOPE>

we will get output as follows:

In the details attached above one finds that the parent details are not available completely. Also the ledger name below second level are not exported in trial balance. Hence one has to use ledgerprimary from Tally for ledgers below second level of hierarchy. 

The second step is to analyze the bills receivable statements by group wise. There could be certain groups to be excluded in the collections process.

These ledgers and their groups need to be excluded from any payment collection process.

2.) Adjusting the credit entries : for the same net closing balance needs to be taken that subtracts the debit and the credit closing balances. Simply using the debit balances might not help.

3.) Looking at the bills receivable details. There could be some bills that are part of the bills receivable, group payable , ledger payable and bills payable details.  Using our json extract we have combined all the receivables, payables, group and ledger-group details across unlimited companies.

4.) One will have some collections from bills receivable, bills payable combine along with group ledger hierarchy.

5.) We need to check the ledger credit period for all the remaining ledgers.

6.) Thereafter we will have to find those invoices that have still been left unpaid with onaccount entries. A single table across multiple companies would help.

Once all the above steps have been done then one can make a list of vouchers for which bills receivable intimation is to be done.

The intimation facilities can be done with sms, email or whatsapp.

Contact us for accounting analysts to help solve your problem.

Name: Apoorv Chaturvedi

Phone:+91-8802466356

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

youtube channel:www.youtube.com\@mndatasolutions2042.

Our performance guarantee: full payment follow ups in a period of 2(two) months.

Pre requisites; Tally ERP, powerbi, SQL Server(if preferable)

Data insertion-Tally(approaches)

 Problem statement: Many softwares look to insert data into Tally from their application.This blog looks at issues and approaches for the same.

There arer two ways of inserting the data into Tally(as per Tally site):

a.) Tally development code

b.) Tally xml.

Tally xml: For insertion into Tally from an external application there are two aspects that need to be taken care of.

a.) Insertion and update of Masters

b.) Insertion, update and delete of Vouchers.

Attached is the process step for doing the same  using XML:

Insertion and updates of masters:

a.) Export the copy of the masters by using the daybook or the ledger master copy in xml format.

b.) Use Tally as a webserver and assign a port for the same.

c.) Decide on the scripting language to be used to insert the data into Tally. We chose python. The data insertion could be done directly from the python web form or from the database.

Insertion/updation/deletion of vouchers:

For example to insert the data from an excel sheet to Tally using python the following code could be used:

from flask import Flask, request, redirect, url_for, flash, render_template_string

import requests

import pandas as pd

# Load Excel file and read the data into a DataFrame

file_path = 'C:\Tally_difference\sample_import\sample_purchase_import.xlsx'  # Replace with your Excel file path

df = pd.read_excel(file_path)

# Tally server URL

tally_url = 'http://localhost:9000'

# Filter rows where the 'index' column is greater than 5

df_filtered = df[df['index'] >= 1]  

for index, row in df_filtered.iterrows():

    # Collect data from form

    Remoteid=row['Remoteid']

    company_name = row['Companyname']

    voucher_type = row['Vouchertype']

    voucher_date = row['Voucherdate']

    party_ledger = row['partyledgername']

    ledger_name = row['Ledgername']

    amount = row['Amount']

    # XML payload

    xml_data = f"""<ENVELOPE>

     <HEADER>

      <TALLYREQUEST>Import Data</TALLYREQUEST>

     </HEADER>

     <BODY>

      <IMPORTDATA>

       <REQUESTDESC>

        <REPORTNAME>Vouchers</REPORTNAME>

        <STATICVARIABLES>

         <SVCURRENTCOMPANY>{company_name}</SVCURRENTCOMPANY>

        </STATICVARIABLES>

       </REQUESTDESC>

       <REQUESTDATA>

        <TALLYMESSAGE xmlns:UDF="TallyUDF">

         <VOUCHER REMOTEID="{Remoteid}"  VCHTYPE="{voucher_type}" ACTION="Create">

          <DATE>{voucher_date}</DATE>

          <VOUCHERTYPENAME>{voucher_type}</VOUCHERTYPENAME>

          <PARTYLEDGERNAME>{party_ledger}</PARTYLEDGERNAME>

          <ALLLEDGERENTRIES.LIST>

           <LEDGERNAME>{ledger_name}</LEDGERNAME>

           <AMOUNT>-{amount}</AMOUNT>

          </ALLLEDGERENTRIES.LIST>

          <ALLLEDGERENTRIES.LIST>

           <LEDGERNAME>{party_ledger}</LEDGERNAME>

           <AMOUNT>{amount}</AMOUNT>

          </ALLLEDGERENTRIES.LIST>

         </VOUCHER>

        </TALLYMESSAGE>

       </REQUESTDATA>

      </IMPORTDATA>

     </BODY>

    </ENVELOPE>"""

    # Send data to Tally

    headers = {'Content-Type': 'application/xml'}

    response = requests.post(tally_url, data=xml_data.encode('utf-8'), headers=headers)

print(f"Status Code: {response.status_code}")

print(f"Response Content: {response.text}")

 

Explanation: 

• Tally is declared as webserver

# Tally server URL

tally_url = 'http://localhost:9000'

• Excel sheet is run row by row
• The xml request is run. The unique row in the excel row is identified by rowid( REMOTEID="{Remoteid}). The given remoteid helps capture insert, update and deletes for vouchers.
• Response code sends the requests to post the data into Tally.

Insertion/updation of ledgers: for the case of ledgers Tally has a clause called @@dupkeycombine as specified in the sample xml request.

from flask import Flask, request, redirect, url_for, flash, render_template_string

import requests

app = Flask(__name__)

app.secret_key = 'your_secret_key'  # Replace with a strong key for production

# Tally server URL

tally_url = 'http://localhost:9000'

# HTML template as a string

html_template = """

<!DOCTYPE html>

<html lang="en">

<head>

    <meta charset="UTF-8">

    <meta name="viewport" content="width=device-width, initial-scale=1.0">

    <title>Tally Ledger Entry Form</title>

</head>

<body>

    <h1>Tally Ledger Entry Form</h1>

    {% with messages = get_flashed_messages(with_categories=true) %}

        {% if messages %}

            <ul>

                {% for category, message in messages %}

                    <li class="{{ category }}">{{ message }}</li>

                {% endfor %}

            </ul>

        {% endif %}

    {% endwith %}

    <form action="{{ url_for('submit_data') }}" method="POST">

        <label for="company_name">Company Name:</label><br>

        <input type="text" id="company_name" name="company_name" required><br><br>

        <label for="ledger_name">Ledger Name:</label><br>

        <input type="text" id="ledger_name" name="ledger_name" required><br><br>

        

        <label for="ledger_parent">Ledger Parent:</label><br>

        <input type="text" id="ledger_parent" name="ledger_parent" required><br><br>

        

        <button type="submit">Submit to Tally</button>

    </form>

</body>

</html>

"""

@app.route('/')

def index():

    return render_template_string(html_template)

@app.route('/submit', methods=['POST'])

def submit_data():

    # Collect data from form

    company_name = request.form['company_name']

    ledger_name = request.form['ledger_name']

    #reserved_name = request.form['reserved_name']

    ledger_parent = request.form['ledger_parent']

    #ledger_name = request.form['ledger_name']

    #amount = request.form['amount']

    # XML payload

    xml_data = f"""<ENVELOPE>

<HEADER>

<VERSION>1</VERSION>

<TALLYREQUEST>Import</TALLYREQUEST>

<TYPE>Data</TYPE>

<ID>AllMasters</ID>

</HEADER>

<BODY>

<DESC>

<STATICVARIABLES>

<IMPORTDUPS>@@DUPKEYCOMBINE</IMPORTDUPS>

<SVCURRENTCOMPANY>{company_name}</SVCURRENTCOMPANY>

</STATICVARIABLES>

</DESC>

<DATA>

<TALLYMESSAGE>

<LEDGER NAME="{ledger_name}">

      <OLDAUDITENTRYIDS.LIST TYPE="Number">

       <OLDAUDITENTRYIDS>-1</OLDAUDITENTRYIDS>

      </OLDAUDITENTRYIDS.LIST>

      <CREATEDDATE>20231224</CREATEDDATE>

      <PARENT>{ledger_parent}</PARENT>

      <ENTEREDBY>a</ENTEREDBY>

      <CREATEDBY>a</CREATEDBY>

      <TAXCLASSIFICATIONNAME>&#4; Not Applicable</TAXCLASSIFICATIONNAME>

      <TAXTYPE>Others</TAXTYPE>

      <GSTTYPE>&#4; Not Applicable</GSTTYPE>

      <APPROPRIATEFOR>&#4; Not Applicable</APPROPRIATEFOR>

      <SERVICECATEGORY>&#4; Not Applicable</SERVICECATEGORY>

      <EXCISELEDGERCLASSIFICATION>&#4; Not Applicable</EXCISELEDGERCLASSIFICATION>

      <EXCISEDUTYTYPE>&#4; Not Applicable</EXCISEDUTYTYPE>

      <EXCISENATUREOFPURCHASE>&#4; Not Applicable</EXCISENATUREOFPURCHASE>

      <LEDGERFBTCATEGORY>&#4; Not Applicable</LEDGERFBTCATEGORY>

      <ISBILLWISEON>No</ISBILLWISEON>

      <ISCOSTCENTRESON>No</ISCOSTCENTRESON>

      <ISINTERESTON>No</ISINTERESTON>

      <ALLOWINMOBILE>No</ALLOWINMOBILE>

      <ISCOSTTRACKINGON>No</ISCOSTTRACKINGON>

      <ISBENEFICIARYCODEON>No</ISBENEFICIARYCODEON>

      <ISEXPORTONVCHCREATE>No</ISEXPORTONVCHCREATE>

      <PLASINCOMEEXPENSE>No</PLASINCOMEEXPENSE>

      <ISUPDATINGTARGETID>No</ISUPDATINGTARGETID>

      <ISDELETED>No</ISDELETED>

      <ISSECURITYONWHENENTERED>No</ISSECURITYONWHENENTERED>

      <ASORIGINAL>No</ASORIGINAL>

      <ISCONDENSED>No</ISCONDENSED>

      <AFFECTSSTOCK>No</AFFECTSSTOCK>

      <ISRATEINCLUSIVEVAT>No</ISRATEINCLUSIVEVAT>

      <FORPAYROLL>No</FORPAYROLL>

      <ISABCENABLED>No</ISABCENABLED>

      <ISCREDITDAYSCHKON>No</ISCREDITDAYSCHKON>

      <INTERESTONBILLWISE>No</INTERESTONBILLWISE>

      <OVERRIDEINTEREST>No</OVERRIDEINTEREST>

      <OVERRIDEADVINTEREST>No</OVERRIDEADVINTEREST>

      <USEFORVAT>No</USEFORVAT>

      <IGNORETDSEXEMPT>No</IGNORETDSEXEMPT>

      <ISTCSAPPLICABLE>No</ISTCSAPPLICABLE>

      <ISTDSAPPLICABLE>No</ISTDSAPPLICABLE>

      <ISFBTAPPLICABLE>No</ISFBTAPPLICABLE>

      <ISGSTAPPLICABLE>No</ISGSTAPPLICABLE>

      <ISEXCISEAPPLICABLE>No</ISEXCISEAPPLICABLE>

      <ISTDSEXPENSE>No</ISTDSEXPENSE>

      <ISEDLIAPPLICABLE>No</ISEDLIAPPLICABLE>

      <ISRELATEDPARTY>No</ISRELATEDPARTY>

      <USEFORESIELIGIBILITY>No</USEFORESIELIGIBILITY>

      <ISINTERESTINCLLASTDAY>No</ISINTERESTINCLLASTDAY>

      <APPROPRIATETAXVALUE>No</APPROPRIATETAXVALUE>

      <ISBEHAVEASDUTY>No</ISBEHAVEASDUTY>

      <INTERESTINCLDAYOFADDITION>No</INTERESTINCLDAYOFADDITION>

      <INTERESTINCLDAYOFDEDUCTION>No</INTERESTINCLDAYOFDEDUCTION>

      <ISOTHTERRITORYASSESSEE>No</ISOTHTERRITORYASSESSEE>

      <IGNOREMISMATCHWITHWARNING>No</IGNOREMISMATCHWITHWARNING>

      <USEASNOTIONALBANK>No</USEASNOTIONALBANK>

      <BEHAVEASPAYMENTGATEWAY>No</BEHAVEASPAYMENTGATEWAY>

      <OVERRIDECREDITLIMIT>No</OVERRIDECREDITLIMIT>

      <ISAGAINSTFORMC>No</ISAGAINSTFORMC>

      <ISCHEQUEPRINTINGENABLED>Yes</ISCHEQUEPRINTINGENABLED>

      <ISPAYUPLOAD>No</ISPAYUPLOAD>

      <ISPAYBATCHONLYSAL>No</ISPAYBATCHONLYSAL>

      <ISBNFCODESUPPORTED>No</ISBNFCODESUPPORTED>

      <ALLOWEXPORTWITHERRORS>No</ALLOWEXPORTWITHERRORS>

      <CONSIDERPURCHASEFOREXPORT>No</CONSIDERPURCHASEFOREXPORT>

      <ISTRANSPORTER>No</ISTRANSPORTER>

      <ISECASHLEDGER>No</ISECASHLEDGER>

      <USEFORNOTIONALITC>No</USEFORNOTIONALITC>

      <ISECOMMOPERATOR>No</ISECOMMOPERATOR>

      <OVERRIDEBASEDONREALIZATION>No</OVERRIDEBASEDONREALIZATION>

      <ISECDIFFINSDATE>No</ISECDIFFINSDATE>

      <SHOWINPAYSLIP>No</SHOWINPAYSLIP>

      <USEFORGRATUITY>No</USEFORGRATUITY>

      <ISTDSPROJECTED>No</ISTDSPROJECTED>

      <ISSALARYMULFILE>No</ISSALARYMULFILE>

      <FORSERVICETAX>No</FORSERVICETAX>

      <ISINPUTCREDIT>No</ISINPUTCREDIT>

      <ISEXEMPTED>No</ISEXEMPTED>

      <ISABATEMENTAPPLICABLE>No</ISABATEMENTAPPLICABLE>

      <ISSTXPARTY>No</ISSTXPARTY>

      <ISSTXNONREALIZEDTYPE>No</ISSTXNONREALIZEDTYPE>

      <USEFORKKC>No</USEFORKKC>

      <USEFORSBC>No</USEFORSBC>

      <ISUSEDFORCVD>No</ISUSEDFORCVD>

      <LEDBELONGSTONONTAXABLE>No</LEDBELONGSTONONTAXABLE>

      <ISEXCISEMERCHANTEXPORTER>No</ISEXCISEMERCHANTEXPORTER>

      <ISPARTYEXEMPTED>No</ISPARTYEXEMPTED>

      <ISSEZPARTY>No</ISSEZPARTY>

      <TDSDEDUCTEEISSPECIALRATE>No</TDSDEDUCTEEISSPECIALRATE>

      <ISECHEQUESUPPORTED>No</ISECHEQUESUPPORTED>

      <ISEDDSUPPORTED>No</ISEDDSUPPORTED>

      <HASECHEQUEDELIVERYMODE>No</HASECHEQUEDELIVERYMODE>

      <HASECHEQUEDELIVERYTO>No</HASECHEQUEDELIVERYTO>

      <HASECHEQUEPRINTLOCATION>No</HASECHEQUEPRINTLOCATION>

      <HASECHEQUEPAYABLELOCATION>No</HASECHEQUEPAYABLELOCATION>

      <HASECHEQUEBANKLOCATION>No</HASECHEQUEBANKLOCATION>

      <HASEDDDELIVERYMODE>No</HASEDDDELIVERYMODE>

      <HASEDDDELIVERYTO>No</HASEDDDELIVERYTO>

      <HASEDDPRINTLOCATION>No</HASEDDPRINTLOCATION>

      <HASEDDPAYABLELOCATION>No</HASEDDPAYABLELOCATION>

      <HASEDDBANKLOCATION>No</HASEDDBANKLOCATION>

      <ISEBANKINGENABLED>No</ISEBANKINGENABLED>

      <ISEXPORTFILEENCRYPTED>No</ISEXPORTFILEENCRYPTED>

      <ISBATCHENABLED>No</ISBATCHENABLED>

      <ISPRODUCTCODEBASED>No</ISPRODUCTCODEBASED>

      <HASEDDCITY>No</HASEDDCITY>

      <HASECHEQUECITY>No</HASECHEQUECITY>

      <ISFILENAMEFORMATSUPPORTED>No</ISFILENAMEFORMATSUPPORTED>

      <HASCLIENTCODE>No</HASCLIENTCODE>

      <PAYINSISBATCHAPPLICABLE>No</PAYINSISBATCHAPPLICABLE>

      <PAYINSISFILENUMAPP>No</PAYINSISFILENUMAPP>

      <ISSALARYTRANSGROUPEDFORBRS>No</ISSALARYTRANSGROUPEDFORBRS>

      <ISEBANKINGSUPPORTED>No</ISEBANKINGSUPPORTED>

      <ISSCBUAE>No</ISSCBUAE>

      <ISBANKSTATUSAPP>No</ISBANKSTATUSAPP>

      <ISSALARYGROUPED>No</ISSALARYGROUPED>

      <USEFORPURCHASETAX>No</USEFORPURCHASETAX>

      <AUDITED>No</AUDITED>

      <SORTPOSITION> 1000</SORTPOSITION>

      <ALTERID> 10511</ALTERID>

      <OPENINGBALANCE>0.00</OPENINGBALANCE>

      <SERVICETAXDETAILS.LIST>      </SERVICETAXDETAILS.LIST>

      <LBTREGNDETAILS.LIST>      </LBTREGNDETAILS.LIST>

      <VATDETAILS.LIST>      </VATDETAILS.LIST>

      <SALESTAXCESSDETAILS.LIST>      </SALESTAXCESSDETAILS.LIST>

      <GSTDETAILS.LIST>      </GSTDETAILS.LIST>

      <HSNDETAILS.LIST>      </HSNDETAILS.LIST>

      <LANGUAGENAME.LIST>

       <NAME.LIST TYPE="String">

        <NAME>{ledger_name}</NAME>

       </NAME.LIST>

       <LANGUAGEID> 1033</LANGUAGEID>

      </LANGUAGENAME.LIST>

      <XBRLDETAIL.LIST>      </XBRLDETAIL.LIST>

      <AUDITDETAILS.LIST>      </AUDITDETAILS.LIST>

      <SCHVIDETAILS.LIST>      </SCHVIDETAILS.LIST>

      <EXCISETARIFFDETAILS.LIST>      </EXCISETARIFFDETAILS.LIST>

      <TCSCATEGORYDETAILS.LIST>      </TCSCATEGORYDETAILS.LIST>

      <TDSCATEGORYDETAILS.LIST>      </TDSCATEGORYDETAILS.LIST>

      <SLABPERIOD.LIST>      </SLABPERIOD.LIST>

      <GRATUITYPERIOD.LIST>      </GRATUITYPERIOD.LIST>

      <ADDITIONALCOMPUTATIONS.LIST>      </ADDITIONALCOMPUTATIONS.LIST>

      <EXCISEJURISDICTIONDETAILS.LIST>      </EXCISEJURISDICTIONDETAILS.LIST>

      <EXCLUDEDTAXATIONS.LIST>      </EXCLUDEDTAXATIONS.LIST>

      <BANKALLOCATIONS.LIST>      </BANKALLOCATIONS.LIST>

      <PAYMENTDETAILS.LIST>      </PAYMENTDETAILS.LIST>

      <BANKEXPORTFORMATS.LIST>      </BANKEXPORTFORMATS.LIST>

      <BILLALLOCATIONS.LIST>      </BILLALLOCATIONS.LIST>

      <INTERESTCOLLECTION.LIST>      </INTERESTCOLLECTION.LIST>

      <LEDGERCLOSINGVALUES.LIST>      </LEDGERCLOSINGVALUES.LIST>

      <LEDGERAUDITCLASS.LIST>      </LEDGERAUDITCLASS.LIST>

      <OLDAUDITENTRIES.LIST>      </OLDAUDITENTRIES.LIST>

      <TDSEXEMPTIONRULES.LIST>      </TDSEXEMPTIONRULES.LIST>

      <DEDUCTINSAMEVCHRULES.LIST>      </DEDUCTINSAMEVCHRULES.LIST>

      <LOWERDEDUCTION.LIST>      </LOWERDEDUCTION.LIST>

      <STXABATEMENTDETAILS.LIST>      </STXABATEMENTDETAILS.LIST>

      <LEDMULTIADDRESSLIST.LIST>      </LEDMULTIADDRESSLIST.LIST>

      <STXTAXDETAILS.LIST>      </STXTAXDETAILS.LIST>

      <CHEQUERANGE.LIST>      </CHEQUERANGE.LIST>

      <DEFAULTVCHCHEQUEDETAILS.LIST>      </DEFAULTVCHCHEQUEDETAILS.LIST>

      <ACCOUNTAUDITENTRIES.LIST>      </ACCOUNTAUDITENTRIES.LIST>

      <AUDITENTRIES.LIST>      </AUDITENTRIES.LIST>

      <BRSIMPORTEDINFO.LIST>      </BRSIMPORTEDINFO.LIST>

      <AUTOBRSCONFIGS.LIST>      </AUTOBRSCONFIGS.LIST>

      <BANKURENTRIES.LIST>      </BANKURENTRIES.LIST>

      <DEFAULTCHEQUEDETAILS.LIST>      </DEFAULTCHEQUEDETAILS.LIST>

      <DEFAULTOPENINGCHEQUEDETAILS.LIST>      </DEFAULTOPENINGCHEQUEDETAILS.LIST>

      <CANCELLEDPAYALLOCATIONS.LIST>      </CANCELLEDPAYALLOCATIONS.LIST>

      <ECHEQUEPRINTLOCATION.LIST>      </ECHEQUEPRINTLOCATION.LIST>

      <ECHEQUEPAYABLELOCATION.LIST>      </ECHEQUEPAYABLELOCATION.LIST>

      <EDDPRINTLOCATION.LIST>      </EDDPRINTLOCATION.LIST>

      <EDDPAYABLELOCATION.LIST>      </EDDPAYABLELOCATION.LIST>

      <AVAILABLETRANSACTIONTYPES.LIST>      </AVAILABLETRANSACTIONTYPES.LIST>

      <LEDPAYINSCONFIGS.LIST>      </LEDPAYINSCONFIGS.LIST>

      <TYPECODEDETAILS.LIST>      </TYPECODEDETAILS.LIST>

      <FIELDVALIDATIONDETAILS.LIST>      </FIELDVALIDATIONDETAILS.LIST>

      <INPUTCRALLOCS.LIST>      </INPUTCRALLOCS.LIST>

      <TCSMETHODOFCALCULATION.LIST>      </TCSMETHODOFCALCULATION.LIST>

      <LEDGSTREGDETAILS.LIST>      </LEDGSTREGDETAILS.LIST>

      <LEDMAILINGDETAILS.LIST>

       <ADDRESS.LIST TYPE="String">

        <ADDRESS>NANANA</ADDRESS>

       </ADDRESS.LIST>

       <APPLICABLEFROM>20170401</APPLICABLEFROM>

      </LEDMAILINGDETAILS.LIST>

      <GSTRECONPREFIXSUFFIXDETAILS.LIST>      </GSTRECONPREFIXSUFFIXDETAILS.LIST>

      <CONTACTDETAILS.LIST>      </CONTACTDETAILS.LIST>

      <GSTCLASSFNIGSTRATES.LIST>      </GSTCLASSFNIGSTRATES.LIST>

      <EXTARIFFDUTYHEADDETAILS.LIST>      </EXTARIFFDUTYHEADDETAILS.LIST>

      <TEMPGSTITEMSLABRATES.LIST>      </TEMPGSTITEMSLABRATES.LIST>

      <VOUCHERTYPEPRODUCTCODES.LIST>      </VOUCHERTYPEPRODUCTCODES.LIST>

      <LEDADDRESS.LIST>      </LEDADDRESS.LIST>

      <DEFMULTIPLETOPHONENO.LIST>      </DEFMULTIPLETOPHONENO.LIST>

     </LEDGER>

</TALLYMESSAGE>

</DATA>

</BODY>

</ENVELOPE>

"""

    # Send data to Tally

    headers = {'Content-Type': 'application/xml'}

    response = requests.post(tally_url, data=xml_data.encode('utf-8'), headers=headers)

    # Handle response

    if response.status_code == 200:

        flash("Data submitted to Tally successfully.", "success")

    else:

        flash("Failed to submit data to Tally.", "error")

    return redirect(url_for('index'))

if __name__ == '__main__':

    app.run(debug=True, use_reloader=False)

These are the key points to be attached with the xml import for vouchers.

Tally import with tdl:

The data for masters and transactions can also be imported with tdl.

In case of TDL it becomes a little bit more complex since the matching of the ledger names code needs to be added. Sample function is given below:

[function: Add_Stockitem]

00: Walk Collection: testcoll

0X: IF : $$IsEmpty:@@itemexists

Variable:setdate:Date

Variable:setrate:Rate

00A:Set:setdate:$$Date:"01-04-2023"

01E:Set:setrate:$$AsRate:"100"

01A: New Object: StockItem

01BA: Set VALUE:NAME:$$LocaleString:$item_name;$item_name

01BC: Set VALUE:PARENT:$item_type;$item_name

01BD: Set VALUE:CATEGORY:$sub_category_name

01BD1: Set VALUE:DESCRIPTION:$sku_code

01BE: Set VALUE:GSTAPPLICABLE:$$LocaleString:"Applicable"

01bF: Set Value: BASEUNITS:$$LocaleString:$Uom

01bG: Set Value: NARRATION:$$LocaleString:$sku_code

 ;; Set cost & selling price

                0010       :  INSERT COLLECTION OBJECT  : STANDARDCOSTLIST

                0011       :  Set Value   : Date   : "1-11-2017"

                0012       :  Set Value   : Rate   : $$TgtObject:$$AsRate:@@RateVal1

                0013       :  Set Target            : ..

                0014       :   INSERT COLLECTION OBJECT        : STANDARDPRICELIST

                0015       :  Set Value             : Date       : "1-11-2017"

                0016       :  Set Value             : Rate       : $$TgtObject:$$AsRate:@@RateVal2

                0017       :  Set Target            : ..

01D1:SAVE Target

01D:End If

;02: END WALK

02: END WALK

021CC:Create Target

Addition of voucher using TDL: for addition of voucher using tdl we have yet to figure outt how to use remoteid. Hence the same has been excluded in this blog.

Contact us for data insertion into Tally.

Name: Apoorv Chaturvedi

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

Phone:+91-8802466356

youtube channel:www.youtube.com\@mndatasolutions2042