From Notebook to Tally: A Spreadsheet-to-Tally Bookkeeping Workflow for a Modelled Kirana Store

Walk into any kirana store and you will find the whole accounting system in one ruled notebook: today's sales, the flour-mill purchase, the money the owner withdrew, and a running guess of what the wholesaler is owed. The numbers are mostly there — what is missing is structure, and structure is exactly what a B.Com student can supply.

From Notebook to Tally is a beginner-level computer-applications project built around the BCU B.Com SEP 2024 course 6.6 Internship (Semester 6, 4 credits, 100 marks, ≥ 90 hours). It ships a Kirana Bookkeeping Kit — an Excel workbook with daily-entry sheets, a cash book, party ledgers, a trial balance and a monthly summary — plus a starter Tally Prime company (masters and one month of vouchers, importable through Gateway of Tally → Import) and a step-by-step digitisation procedure.

The internship engagement is designed for a real small trader near you, kept anonymous in the report, while the kit's practice data describe "Sri Nandi Stores", a modelled kirana store that is explicitly fictional, so you can rehearse the full workflow before touching a real shopkeeper's records. By the end you can demonstrate the complete path — notebook entries → structured Excel sheets → Tally Prime company with matching reports — and write an honest internship report about what changed, what the owner adopted, and where the paper notebook still wins.

A kirana store's notebook records capture what happened but not what it means: the owner cannot state the month's profit, the amount any customer owes, or whether the business is approaching the turnover level at which GST registration becomes compulsory. When a bank asks for accounts for a small loan, or an accountant quotes fees to "set up the books", the trader has nothing to show and often gives up. Manual summarisation from a notebook is so slow that nobody ever does it.

What is needed is a simple, repeatable workflow that a B.Com student can execute in about ninety hours: capture the notebook into structured daily-entry sheets, generate the cash book, ledgers and trial balance automatically in Excel, set up a matching Tally Prime company for the owner to grow into, and monitor turnover against the GST threshold — all without demanding accounting expertise or software spending from the trader.

Abstract

Small grocery traders keep workable but unstructured records: a sales notebook, a mental stock list and occasional slips. This project designs and executes a six-week (≥ 90-hour) internship engagement that converts a kirana store's notebook records into two organised systems — an Excel bookkeeping workbook and a Tally Prime company — and produces monthly cash books, ledgers, trial balances and summaries the owner can actually use. The bundled kit contains all templates, modelled practice data for the fictional "Sri Nandi Stores", and the import procedure, so the workflow can be demonstrated end to end in the viva.

Introduction

Kirana stores are the smallest unit of Indian retail, and their accounting is usually the owner's memory plus a notebook. Typical pains: nobody knows the profit of a month until stock runs low, credit customers ("khata" entries) are reconciled from memory, and the owner has no document pack ready when a bank loan or a GST registration becomes necessary. GST makes this more than a convenience question — registration becomes compulsory for a goods trader once aggregate turnover crosses the threshold notified under section 22 (₹40 lakh for most states, including Karnataka), and the composition scheme under section 10 (up to ₹1.5 crore turnover for goods) is a realistic option worth planning for. A structured turnover monitor is therefore part of the kit.

Existing system

• One notebook for everything: sales, purchases, owner drawings, credit entries.
• No cash book as such; balances checked by counting the cash box.
• Khata (credit) customers reconciled from memory; disputes are common.
• No trial balance, no monthly profit figure, nothing a bank would accept.

Proposed workflow

1. Daily entry sheets in Excel with dropdown lists for accounts, so entries are consistent.
2. Automatic cash book summarising receipts and payments day by day.
3. Party ledgers built with SUMIF, giving every credit customer and supplier a running balance.
4. Trial balance and monthly summary generated from the ledgers with zero formula skills required from the owner.
5. Tally Prime starter company with the same masters and one month of vouchers (importable), so the owner can graduate to software when ready, and the student can demonstrate reports.
6. Turnover monitor comparing cumulative monthly sales against the GST registration threshold, with a checklist for the composition option.

Feasibility

• Time: 6 weeks at roughly 15 hours per week ≈ 90 hours, matching the course requirement.
• Cost: nil beyond travel; Tally Prime's educational mode is free for learning.
• Skill fit: only basic Excel formulas and Tally voucher entry — both taught in the first two semesters.
• Ethics: the engagement is with a willing trader; real figures are reported only in ranges or with the owner's written permission, and the modelled store is used for all examples.

In scope

• One small grocery/kirana store; cash-and-credit retail sales, wholesaler purchases on credit, household drawings and shop expenses.
• Two artefacts: the Excel Kirana Bookkeeping Kit and a Tally Prime starter company (educational mode).
• Three months of records in the modelled practice data; the internship digitises the real trader's recent entries as permitted.
• Monthly outputs: cash book, khata (customer) and supplier ledgers, trial balance, profit summary, turnover monitor.

Out of scope

• Full GST return filing — the store in the modelled data is below the registration threshold; the kit only monitors it.
• Stock valuation methods (FIFO/weighted average) and godown-level inventory in Tally; a simple stock-noted summary is included instead.
• Payroll, banking integrations and barcode billing.
• Multi-store or multi-user setups.

The engagement follows a simple six-phase plan over six weeks, sized so the total hours comfortably exceed the 90-hour course minimum.

Quality checks built into the phases: the daily-entry sheets use data validation so account names cannot be mistyped; the cash book closing balance must equal the counted cash box at week ends; every ledger's closing balance appears once in the trial balance; and the Excel vs Tally comparison in Phase 5 is the acceptance test for the whole workflow. All hours are recorded in the internship log with dates and the owner's acknowledgment, since the log evidences the ≥ 90-hour requirement.

The workflow is a small data pipeline from the notebook to two parallel bookkeeping outputs. All arrows show what flows between the artefacts.

flowchart TD
  NB["Trader's notebook (source records)"] --> DE["Excel daily-entry sheets (validated dropdowns)"]
  DE --> CB["Automatic cash book"]
  DE --> LG["Party ledgers (SUMIF)"]
  CB --> TB["Trial balance"]
  LG --> TB
  TB --> MS["Monthly profit summary"]
  DE --> TV["Tally Prime vouchers (one month, XML import)"]
  MS --> TM["Turnover monitor vs GST threshold"]
  TV --> TC["Tally company: Day Book, Trial Balance, P&L"]
  TB --> RC{"Reconciliation check"}
  TC --> RC
  RC -->|match| HD["SOP handover to shopkeeper"]
  RC -->|difference| FIX["Investigate and correct entries"]
  FIX --> DE

Sheet map of the kit

• Lists sheet — the single source of account names feeding every dropdown.
• Daily sheets — one per day; date, particulars, account (dropdown), receipt/payment and amount columns.
• Cash book — receipts and payments summarised by date with running balance.
• Ledgers — one block per party (khata customers, wholesalers) built with SUMIF over the daily sheets.
• Trial balance — every ledger and account balance pulled in, debits and credits totalled.
• Summary & monitor — monthly sales, expenses and surplus, and cumulative turnover against the GST threshold line.

Why two systems

Excel proves the student understands the accounting mechanics underneath; Tally proves the trader has a growth path. Reconciling the two is also the project's built-in test: if the trial balances disagree, an entry is wrong, and finding it is exactly the skill the internship is meant to build.

• Add a simple stock sheet with purchase/sale quantities and a reorder list for fast-moving items.
• Extend the kit to weekly markets or a second shop with consolidated monthly reporting.
• Introduce Tally inventory features (stock items, godowns) once the owner is comfortable with vouchers.
• Build a loan-application document pack (summary, bank statement mapping, stock list) from the kit.
• Compare one year of digitised records against the notebook era to quantify stock-loss and khata-dispute reduction.