From Trial Balance to a review-ready pack.

Six steps take you from a new client to a downloadable statement pack.

1. 1

   Create a client

   Add an eligible Non-Corporate Entity, such as an individual, proprietorship, firm, AOP/BOI, society, or trust. Companies and LLPs are not accepted in AutoFS.

2. 2

   Open a financial year

   Set the FY you are preparing. Each year keeps its own Trial Balance, mappings, and pack.

3. 3

   Bring in the Trial Balance

   Import it from Tally Prime with the local connector, or upload an Excel or CSV Trial Balance.

4. 4

   Map ledgers

   Accept the auto-suggested heads and review anything unmapped. Mappings carry forward.

5. 5

   Generate the statements

   Build the full pack — Balance Sheet, Profit & Loss, notes, and accounting policies.

6. 6

   Export

   Download the pack as Excel or PDF, then review it before sharing it onward.

Uploading a Trial Balance is the quickest way in and always works — no install required.

• Inside the financial year, choose Upload Trial Balance and select your Excel (.xlsx) or CSV file.
• Each row needs a ledger name and a closing balance; debit and credit columns are both supported.
• AutoFS validates the file on upload and flags rows it cannot read so you can correct them.
• Once accepted, every ledger moves straight into the mapping step.

A sample Trial Balance template is available on the upload screen — start from it if you are exporting from another system.

The Tally Connector pulls the Trial Balance straight from Tally Prime on your own machine, so you skip the export-and-upload step. Uploading a Trial Balance is always available as a fallback.

Set up and pull

1. 1

   Install the Chrome extension

   Add the AutoFS Tally Connector from the Chrome Web Store, on the same computer where Tally Prime runs.

2. 2

   Open AutoFS and log in

   Sign in to AutoFS in the same Chrome profile and follow the connection status shown on the Tally page.

3. 3

   Enable Tally's HTTP server

   In Tally: F1 → Settings → Connectivity → Client/Server Configuration → set "TallyPrime acts as" = Both, Port 9000.

4. 4

   Select the company

   Choose the open Tally company you want to import from.

5. 5

   Pull the Trial Balance

   Trigger the pull from the Tally page — the extension reads directly from Tally and sends it into the mapping workflow.

Troubleshooting

Mapping assigns every Trial Balance ledger to a head in the chosen reporting format. Good mappings are what make the statements correct, so review them before each generation.

• Auto-suggestions place most ledgers on the right head as soon as the Trial Balance lands.
• Review the unmapped list — only the ledgers AutoFS could not confidently place need your attention.
• Set client-specific overrides and aliases where a ledger name is unusual.
• Your mapping decisions carry forward to the next financial year and to similar clients, so you map once.

Policies and note workings are part of the pack, not an afterthought.

• Select the accounting policies that apply to the entity from inside the product.
• Tailor the wording where the entity's circumstances call for it.
• Capture note workings — schedules, classifications, and supporting figures.
• Policies and notes render straight into the generated pack, so revisit them when circumstances change.

When mappings and policies are ready, generate the full statement pack and download it as Excel or PDF. Always open the file and check it before sharing it onward.

ICAI Guidance Note output for eligible Non-Corporate Entities is Available.

AutoFS uses the controls listed below. Contact us if your team needs a detailed security review.

• Encryption in transit on every request between your browser, the API, and the Tally connector.
• Role-based access so team members only see what their role allows.
• Tenant-scoped routes that keep each workspace's data isolated.
• Revocable sessions and hashed API keys — credentials are never stored in plain text.
• The Tally connector runs locally on your machine and reads Tally over a constrained command set.

Available features are ready for normal use. Beta and Preview features are still being validated, while Roadmap items are planned but not yet available. Review Beta or Preview output carefully before relying on it for final statements.