More About Find

Last updated on: December 19, 2025 | ⏱ 7 min read

Find in TallyPrime | Find with Conditions | List of field names | FAQ

Find helps you locate user-entered information in master and transaction, be it text, numbers, dates and alphanumeric values. The system organises results based on spelling accuracy and keyword frequency, showing the most relevant information first.

Learn How Find Works

It creates an index file of company data, similar to a book’s table of contents. The system then uses this index to quickly identify the required information.

Locating Text

Exact Match: Shows results for the exact keyword entered, like John, Samsung.
Similar Spelling: Enable this option to include spelling variations. For example, if you type Sourav Traders, you will get results for both Sourav Traders and Sourabh Traders.
Contains Match: Enable this option if you remember partial keywords. For example, if you type Bhagya Solutions, you will get results where Bhagya or Solutions are present, such as Bhagyalakshmi Solutions.
Special Characters: If there is a special character in your party name or stock item and you are using All Words Are Present, then enter such keywords in single quotes. For example, ‘A.B.C. Traders’, ‘Shirts Ladies/Men’ or ‘KA-51-3456’.
In case you are using Any Word Is Present, you can type any keyword if you want to find Shirts Ladies/Men, such as Shirts or Ladies, or Men.

Identifying Numbers and Alphanumeric Values

Works only with exact matches.
Similar spellings or contains match will not work with numbers, as numbers don’t have spelling variations, and using contains match with numbers may lead to too many results. To get accurate results, you must provide the complete keyword.
- If you are looking for PAN, then type the complete PAN, such as APRPB2567G.
- If you are looking for a vehicle number, then type KA513456.
- If you are looking for a voucher number, then type INV/123/24-25.
For values with spaces or special characters, enter the keyword in single quotes, such as ‘INV 123’.

Locating Dates

You can look for all the date formats, such as 1-apr-25, 01/04/2025, and so on. This gives results from all fields that contain a date.
If you want to look for the date in a particular date field, then you can write Date:1-apr-25, Date:01/04/2025 and so on. You can view the List of field names here.

Index for Find

TallyPrime triggers indexing in three broad scenarios: Index creation, Index updation, and Re-indexing.

Index Creation

Index Creation occurs when the system needs to build a fresh index, typically in situations where data is new.

It happens when,

The system migrates data.
The system splits data.
The system creates a new company (even without vouchers). In this case, the system creates an index for the default masters generated at company creation—Cash ledger, Profit & Loss account, and standard groups.

Index Updation

Index Updation takes place while you are actively working with data. Instead of rebuilding everything, TallyPrime updates only the portions that have changed.

It happens when,

A single master or single transaction is created or altered – When you create or alter an individual master (such as a ledger or stock item) or save a transaction, the system updates index related to that specific change.
Multiple masters or transactions are created or altered through multi-entries – When you create or modify masters or transactions in bulk, the system incrementally updates the index.
Data is imported (manual or sync) – When you import data into the company, the system updates the index only for the newly added or modified masters and transactions.

Re-indexing

Re-indexing is required only when the system needs to rebuild the index from scratch. It is triggered due to following reasons.

Manual repair is done. Repair Data process includes indexing.
First find after Data Restore (the index file is not part of the backup) or Renaming your Company.
First find after index corruption – If you are a TallyPrime customer and the system detects that the index is corrupted, it automatically performs a full re-index the first time you use Find, ensuring the index is restored to a consistent state. If you are a TallyPrime Server customer, you will need to manually re-index.

Incremental Indexing

The system uses incremental indexing when it detects a partial mismatch between the data and the index and can safely fix it without rebuilding everything.

First activity after client crash during batch posting (Sync / Import) – If the client crashes during batch posting, the system may write some data while leaving the index update incomplete. When the company loads again, or when the first user activity occurs (whichever happens first), the system reads the pending details from the message files and updates only the missing portions of the index.

Exception Scenarios

In certain exceptional situations, the system performs re-indexing to protect data correctness

First Find after physical corruption (checksum failure) – When the system detects a checksum mismatch indicating physical corruption, it rebuilds the index to restore correctness. The system identifies checksum issues in other parts of the file only when it accesses those portions during Find. In such cases, Find fails, and the system displays an information message in the report, prompting the user to manually run Repair Index. The system does not trigger this repair automatically.
First Find after index file deletion – If the index file is missing or deleted, the system automatically rebuilds it when you initiate Find for the first time, or during currency migration for Beta customers.
Any mismatch between “GUID” in data and index.
Any mismatch between “limit of occurrences of keywords” in data and index.
Any mismatch between “vault” property of data and index.
7.0 Beta to 7.0 Gold scenarios:
- Vaulted / Unvaulted / Re-vaulted companies – To ensure the index aligns correctly with encrypted data, re-indexing is triggered for specific companies. When moving from Beta to Gold, currency migration is introduced, and re-indexing for Vaulted, Unvaulted, or Re-vaulted companies is performed as part of this migration—specifically towards the final stage.
  This re-indexing occurs only in the following scenarios:
  - Vaulting, unvaulting, or re-vaulting was performed during the Beta phase, and Find was never initiated in Beta, or
  - The company data was already vaulted.
    Unvaulted companies do not undergo Repair Index when migrated from Beta to Gold.
- Renaming Company – In the Beta phase, the system changed the company identifier from the Company Name to a GUID. As a result, customers who renamed their company during Beta experience a one-time re-indexing to realign the index with the GUID-based identifier.
  
  This re-indexing would normally occur during the first Find operation in Beta. However, if you have never initiated Find during Beta, the system performs re-indexing as part of the currency migration to Gold, instead of triggering it during Find.
- Index Corruption – In some scenarios, the index may become corrupted. Under normal circumstances, the system triggers re-indexing during the first Find operation. With the introduction of currency migration from Beta to Gold, the system performs re-indexing as part of the migration process. This happens specifically in the final stage.
  The system also triggers re-indexing when you change the Limit for Keyword Occurrences in F11.

Handling Index Issues

If the index file is missing, incorrect or corrupted:
- The system rebuilds it automatically during the next use of Find.
If auto-fix fails:
- After you run a Find operation and the results page loads, a note will appear at the bottom of the page with steps to manually rebuild the index. Go to F1 (Help) > Troubleshooting > Repair Index for Find.

This limit allows you to control how many times a keyword appears in masters and transactions for Find to display results.