Tally Configuration
Introduction
Tally is one of the most widely used business software. Several organizations use Tally for accounting solutions, financial and inventory management, sales and purchase management, invoicing, reporting and MIS. Relevant business data like inventory records, financial transactions, creditors and debtors list, sales records and even taxation details are saved in a company’s Tally servers.
In most business houses, Tally is used for an organization’s accounting, financial and inventory needs. With the help of Tally integration services, organizations can ensure easy transfer of data between E-commerce to Tally portals. Companies can import master and transaction data between the online platform and Tally software in real-time with no delays.
Tally and eRetail Integration
Tally and eRetail is integrated using APIs.
All the data including Master Data is present in the eRetail and Tally fetches those data from eRetail in the XML Format.
Tally sends the GET request to eRetail and in turns eRetail sends those data back to Tally.
Tally fetches the below mentioned data from the eRetail:-
Items/ SKU
Customer
Vendor
Sales Order
Sales Return
Purchase
Purchase Return
Tally Configurations in eRetail
For Tally configuration, user needs to navigate Master > Miscellaneous > Tally Configuration.
On the Tally Configuration screen, there are several configurations for Sales Order, Sales Return, Purchase and Purchase Return.
Please refer to the below mentioned table for the configurations present under the Tally Configuration screen.
The entire configuration can be done at the Default/ Company level.
Sales and Sales Return | ||||
| Name | Description | Sample Values | |
Sales Details | Voucher Type | A voucher is a document that contains details of a financial transaction and is required for recording the same into the books of accounts. | Sales Order, Sales Invoice etc | |
Voucher Number* | It refers to the Voucher no for each Sales Order transaction. User can select the Voucher no as either Invoice No, External Invoice No, External Order No. | 1.Invoice No | ||
Reference Number* | It refers to the reference no. for each Sales order transaction. User can select the Reference no as either Invoice No or External Order No. | 1.Invoice No | ||
Date* | It refers to the date of the Sales order transaction. User can select the date as Invoice Date, Order Date, Shipping Date. | 1.Invoice Date | ||
Sales Return Details | Voucher Type | A voucher is a document that contains details of a financial transaction and is required for recording the same into the books of accounts. | Sales return, Customer Return, etc. | |
Voucher Number* | It refers to the Voucher no for each Sales Return transaction. User can select the Voucher no as Return No. | 1.Return No | ||
Reference Number* | It refers to the reference no. for each Sales Return transaction. User can select the Reference no as either Invoice No, External Order No. or Return No. | 1.Invoice No | ||
Date* | It refers to the date of the Sales Return transactions. User can select the date as Return Date or Received Date. | 1.Return Date | ||
Sales Ledger Name | Sales Ledger Type* | It refers to the Sales Tax Ledger Type. | 1. Local/ Interstate | |
With Tax Percent | It refers to the representation of Taxes in percentage. | Ex. IGST@12% | ||
For Local * | It refers to the Local Tax ledger name defined in tally | Configurable | ||
For Interstate * | It refers to the Interstate Tax ledger name defined in tally | Configurable | ||
Tax Ledger Name | With Tax Percent | It refers to the representation of Taxes in percentage. | Ex. IGST@12% | |
SGST/UTGST * | It refers to the SGST/ UTGST Tax ledger name defined in tally | Configurable | ||
CGST * | It refers to the CGST Tax ledger name defined in tally | Configurable | ||
IGST * | It refers to the IGST Tax ledger name defined in tally | Configurable | ||
Party Name Configuration | Party Name | It refers to the Alias Name of the Party (Marketplace, Transporter and B2B Customer) as per the Tally. | Configurable | |
Purchase and Purchase Return | ||||
Purchase Details | Voucher Type | A voucher is a document that contains details of a financial transaction and is required for recording the same into the books of accounts. | Purchase Order, PO etc | |
Voucher Number* | It refers to the Voucher no for each Purchase Order transaction. User can select the Voucher no. as either GRN No, Inbound No or PO Code. | 1.GRN No | ||
Reference Number* | It refers to the reference no. for each Purchase order transaction. User can select the Reference no. as either GRN No, Invoice No or PO Code. | 1.GRN No | ||
Date* | It refers to the date of the Purchase order transaction. User can select the date as Invoice Date or Inbound Date. | 1. Invoice Date | ||
Purchase Return Details | Voucher Type | A voucher is a document that contains details of a financial transaction and is required for recording the same into the books of accounts. | Purchase return, PO Return, etc | |
Voucher Number* | It refers to the Voucher no for each Purchase Return transaction. User can select the Voucher no as Return No. | 1.Return No | ||
Reference Number* | It refers to the reference no. for each Sales Return transaction. User can select the Reference no as either GRN No, Invoice No, Inbound No. or PO Code. | 1.GRN No | ||
Date* | It refers to the date of the Purchase Return transactions. User can select the date as Return Date or Invoice Date. | 1.Return Date | ||
Expense Ledger Name | Expense Ledger Type* | It refers to the Expense Tax Ledger Type. | 1. Local/ Interstate | |
With Tax Percent | It refers to the representation of Taxes in percentage. | Ex. IGST@12% | ||
For Local * | It refers to the Local Tax ledger name defined in tally | Configurable | ||
For Interstate * | It refers to the Interstate Tax ledger name defined in tally | Configurable | ||
Tax Ledger Name | With Tax Percent | It refers to the representation of Taxes in percentage. | Ex. IGST@12% | |
SGST/UTGST * | It refers to the SGST/ UTGST Tax ledger name defined in tally | Configurable | ||
CGST * | It refers to the CGST Tax ledger name defined in tally | Configurable | ||
IGST * | It refers to the IGST Tax ledger name defined in tally | Configurable | ||
It refers to the Alias Name of the Party (Marketplace, Transporter and B2B Customer) as per the Tally. | Configurable | |||
Accounting Logs
User can see the Tally logs under the Accounting Logs screen. For Accounting Logs, user needs to navigate to Admin > Logs > Accounting Logs.
Accounting logs screens captures the data of other accounting systems as well, so user needs to select “Tally” from the top right section of the Accounting Logs Screen.
Accounting Logs Screen displays all the fetch record which is getting pulled by Tally.
Accounting Logs screen contains the below mentioned columns:-
Status:-
Error- When Error is received from the Tally Update status Api.
Success- When Success is received from the Tally Update Status Api.
Pending Acknowledge- When no update is received from the tally update status Api.
Waiting in Queue- When more than 100 records are fetched in a single API call.
Status API
Status update API is used to provide the status to eRetail from Tally for the fetched records.
Below mentioned parameter are used to provide the status to eRetail from Tally:-
Party Name Configuration
Party Name Configuration basically refers to the configuring the party attributes as per the Tally specification.
For Sales and Sales Return, the Party can be:-
1-Marketplace 2-Transporter 3-B2B Customer
In the same way, for Purchase and Purchase Return, the Party can be:-
Vendor
By making the use of Party Name Configuration, user can modify the name/ voucher type, ledger type, etc. of the Vendor, Transporter, marketplaces, and B2B customer as per Tally.
Kindly refer to the below mentioned table for the available alias for each Party:-
eRetail Tally APIs
Item/ Sku Fetch API
Item/ SKU fetch api is used to push the SKU master data to Tally.
The data/ response is sent in the XML format.
FromDate and ToDate are optional parameters in the API. If no date is passed in the request, then the data is fetched on the basis of date present in the LastTransmitdate column of transmitlog database table.
The data is fetched between the LastTransmitdate and LastTransmitdate + 24 hours.
To check the date, kindly refer to the below mentioned query:-
select * from transmitlog where intcode = 'TLY_ITEMS;
There is a batch limit of 100 items/call in the SKU fetch tally api. If there are more than 100 records in a single api call, then only 100 records will be pushed to Tally with status as “Pending Acknowledge” and rest records will be there with status as “Waiting in Queue”.
To fetch the SKU Master data from eRetail, below mentioned parameters needs to be passed in the api request.
Customer Fetch API
Customer fetch api is used to push the Customer master data to Tally.
The data/ response is sent in the XML format.
FromDate and ToDate are optional parameters in the API. If no date is passed in the request, then the data is fetched on the basis of date present in the LastTransmitdate column of transmitlog database table.
The data is fetched between the LastTransmitdate and LastTransmitdate + 24 hours.
To check the date, kindly refer to the below mentioned query:-
select * from transmitlog where intcode = 'TLY_Customer';
There is a batch limit of 100 items/call in the Customer fetch tally api. If there are more than 100 records in a single api call, then only 100 records will be pushed to Tally with status as “Pending Acknowledge” and rest records will be there with status as “Waiting in Queue”.
To fetch the Customer Master data from eRetail, below mentioned parameters needs to be passed in the api request.
Vendor Fetch API
Vendor fetch api is used to push the Vendor master data to Tally.
The data/ response is sent in the XML format.
FromDate and ToDate are optional parameters in the API. If no date is passed in the request, then the data is fetched on the basis of date present in the LastTransmitdate column of transmitlog database table.
The data is fetched between the LastTransmitdate and LastTransmitdate + 24 hours.
To check the date, kindly refer to the below mentioned query:-
select * from transmitlog where intcode = 'TLY_Vendor;
There is a batch limit of 100 items/call in the Vendor fetch tally api. If there are more than 100 records in a single api call, then only 100 records will be pushed to Tally with status as “Pending Acknowledge” and rest records will be there with status as “Waiting in Queue”.
To fetch the Vendor Master data from eRetail, below mentioned parameters needs to be passed in the api request.
Sales Order Fetch API
Sales Order fetch api is used to push/ fetch the Sales Order data to Tally.
The data/ response is sent in the XML format.
FromDate and ToDate are optional parameters in the API. If no date is passed in the request, then the data is fetched on the basis of date present in the LastTransmitdate column of transmitlog database table.
The data is fetched between the LastTransmitdate and LastTransmitdate + 24 hours.
To check the date, kindly refer to the below mentioned query:-
select * from transmitlog where intcode = 'TLY_Sales';
There is a batch limit of 100-line items/call in the Sales order fetch tally api. If there are more than 100 records in a single api call, then only 100 records will be pushed to Tally with status as “Pending Acknowledge” and rest records will be there with status as “Waiting in Queue”.
The status of the order should be shipped to get fetched in the Tally Api.
To fetch the Sales order Master data from eRetail, below mentioned parameters needs to be passed in the api request.
Sales Return Fetch API
Sales Return fetch api is used to push/ fetch the Sales Return/ Customer Return data to Tally.
The data/ response is sent in the XML format.
FromDate and ToDate are optional parameters in the API. If no date is passed in the request, then the data is fetched on the basis of date present in the LastTransmitdate column of transmitlog database table.
The data is fetched between the LastTransmitdate and LastTransmitdate + 24 hours.
To check the date, kindly refer to the below mentioned query:-
select * from transmitlog where intcode = ' TLY_RETURNS’;
There is a batch limit of 100-line items/call in the Sales Return fetch tally api. If there are more than 100 records in a single api call, then only 100 records will be pushed to Tally with status as “Pending Acknowledge” and rest records will be there with status as “Waiting in Queue”.
The status of the Sales Return should be closed to get fetched in the Tally Api.
To fetch the Sales Return data from eRetail, below mentioned parameters needs to be passed in the api request.
Purchase Order Fetch API
Purchase Order fetch api is used to push/ fetch the Purchase order data to Tally.
The data/ response is sent in the XML format.
FromDate and ToDate are optional parameters in the API. If no date is passed in the request, then the data is fetched on the basis of date present in the LastTransmitdate column of transmitlog database table.
The data is fetched between the LastTransmitdate and LastTransmitdate + 24 hours.
To check the date, kindly refer to the below mentioned query:-
select * from transmitlog where intcode = ' TLY_PURCHASE’;
There is a batch limit of 100-line items/call in the Purchase order fetch tally api. If there are more than 100 records in a single api call, then only 100 records will be pushed to Tally with status as “Pending Acknowledge” and rest records will be there with status as “Waiting in Queue”.
The status of the Purchase Order should be closed to get fetched in the Tally Api.
To fetch the Purchase Order data from eRetail, below mentioned parameters needs to be passed in the api request.
Purchase Return Fetch API
Purchase Return fetch api is used to push/ fetch the Purchase Return data to Tally.
The data/ response is sent in the XML format.
FromDate and ToDate are optional parameters in the API. If no date is passed in the request, then the data is fetched on the basis of date present in the LastTransmitdate column of transmitlog database table.
The data is fetched between the LastTransmitdate and LastTransmitdate + 24 hours.
To check the date, kindly refer to the below mentioned query:-
select * from transmitlog where intcode = ' TLY_PRETURN;
There is a batch limit of 100-line items/call in the Purchase Return fetch tally api. If there are more than 100 records in a single api call, then only 100 records will be pushed to Tally with status as “Pending Acknowledge” and rest records will be there with status as “Waiting in Queue”.
The status of the Purchase Order should be closed to get fetched in the Tally Api.
To fetch the Purchase Return data from eRetail, below mentioned parameters needs to be passed in the api request.
Database Information:-
Database Proc:-
Get_Tally_Document