For CA offices

Every return filed,
on time.

FileRight is a simple desk for a chartered-accountant office. GST, TDS, advance tax and income-tax due dates turn into jobs by themselves, for every client. Each person sees their own jobs. The partners see what is late and who has too much on.

The demo opens straight in as a guest partner, with no sign-up. The office, its clients and their PAN and GST numbers are made up.

FileRight's Home page: how it works in three steps, three numbers (late, due this week, waiting), the five jobs to do first and this month's due dates
Home: three numbers, the five jobs to do first, and this month's due dates. Five menu items cover everything.
5menu items: Home, My work, Due dates, Clients, Team
7kinds of government due date, created for each client by themselves
1 clickto start a timer on a job, and one to stop it
0spreadsheets to copy forward each month
Why

The same due dates every month, kept in a spreadsheet.

A ten-person CA office files GST returns for twenty clients every month, TDS every quarter, advance tax four times a year, and audits and tax returns in one busy autumn. Every one has a government due date and a late fee.

Due dates get retyped

Someone copies last month's sheet and changes "Aug" to "Sep" thirty times. A client who registered for GST in June is still missing in October.

Work waits quietly

The tax audit can't be filed until the audit is signed, and the tax return waits for the tax audit. Nobody sees the chain until the last week.

Nobody knows who is busy

One person has fifty hours of work due this week, another has time to spare, and the partner finds out on Friday.

How it works

Three steps, every month.

STEP 1

Due dates make the jobs

Tell FileRight a client's PAN, whether it has a GST number or a TAN, and whether its accounts are audited. Every return it must file then appears as a job, with the government's due date and an earlier date to aim for.

STEP 2

Everyone does their jobs

My work shows each person their late jobs, today's jobs and what they are doing. Start the timer, mark it done, send it for checking. Big jobs like an audit break into steps.

STEP 3

Partners keep the team balanced

Team shows who has more work than hours this week and who can take some, with one click to move a job. Hours by client show which services are over budget.

ALWAYS

An assistant that explains itself

Ask what to do next, turn meeting notes into jobs, get a checklist for a return, or a weekly summary for the partners. It works without AI and says when it uses it.

A quick tour

Five places, nothing hidden.

Due dates

  • Every government due date in the month, client by client: GSTR-1 on the 11th, GSTR-3B on the 20th, TDS, advance tax, income-tax returns, tax audits and company filings.
  • "Create jobs for October" only ever adds what is missing, so pressing it twice is safe.
  • Each job gets an aim-by date a few working days early, skipping Sundays and the office's holidays.
The Due dates page for October: returns grouped by due date with each client, who does it, the aim-by date and the status
Due dates for the month, grouped by date, with who is doing each one.

My work

  • My jobs: what's late, what's due today, what I'm doing, and what's waiting for someone else.
  • All jobs, a Board and a Calendar show the same jobs three ways.
  • My hours: the week's timesheet, filled by the timer or by hand.
  • A job can have steps, and can wait for another job: the tax audit waits for the signed audit, so it can't be started too early.
An audit job with twelve steps in three groups, some done, the reporting steps marked waiting
An audit in progress: the reporting steps wait until the checking work is done.

Team

  • Who is busy: a bar per person against the hours they work in a week. Red means more work than hours.
  • Who can help: jobs not started yet, suggested for the person with the most free hours. One click moves them.
  • Hours by client and service, a Weekly summary, Activity and People.
The Who is busy page: a bar per person against a line for their weekly hours
Who is busy this week, and who has room to help.

On a phone, too

  • My jobs and the timer work on a phone, so hours get logged when the work happens.
  • The calendar shows the whole month: returns edged orange, late jobs in red, done jobs struck through.
The month calendar with due dates clustered on the 11th, 20th and 31st
My jobs on a phone: a running timer, late jobs and today's jobs

The assistant

  • What should I do next: your three most urgent jobs, with the reason.
  • Meeting notes: "Priya to reconcile 2B for Sri Balaji by Friday" becomes a job for Priya, for that client, due Friday. Nothing is created until you tick it.
  • Suggest steps: the office's checklist for each return, such as the six steps of a GSTR-3B.
  • Weekly summary: four sentences for the partners, every number counted from FileRight.
The assistant turning four lines of meeting notes into four proposed jobs with people, clients and dates
Four lines of meeting notes become four jobs to tick and create.
What's built

What works today, and how we checked.

This list comes straight from our build tracker. Something is marked built only after its test has been run; ideas we have not built yet are listed as coming next.

46 of 52 tracked capabilities built and verified · 0 partial · 6 on the roadmap. Generated from the build tracker; each row names the test that proved it.

AreaCapabilityStatusProof (acceptance test)
FoundationsSchema: users, invites, clients, engagements, tasks, task dependencies, compliance templates, subscriptions, time entries, holidays, eventsBuiltdb.init() on an empty file creates exactly those tables plus schema_version; running it twice is a no-op (row counts unchanged)
FoundationsSynthetic seed: a Hyderabad CA firm, its team and thirty clientsBuiltseeded DB holds 10 users across partner/manager/staff, 30 clients of >=4 constitution types (company, LLP, firm, individual, trust), >=40 engagements, >=250 tasks covering every status and priority, >=8 weeks of time entries and generated compliance tasks for the current and previous month; reseeding an empty DB gives the same counts
FoundationsApp shell: FastAPI boot, /healthz, base layout with design tokensBuiltcurl /healthz returns 200 JSON with ok=true, db path, client/task/user counts and ai provider; the signed-in dashboard returns 200 HTML with the nav
FoundationsTest harnessBuiltpytest -q runs >=1 test against a temp DB via TestClient and passes
Clients & engagementsClient register with PAN/GSTIN validation and constitution typeBuiltPOST a client with a malformed PAN or a GSTIN whose embedded PAN differs returns 422 with a field error; a valid one is created; GET /clients?q=<fragment> lists only matches
Clients & engagementsClient detail: engagements, open tasks, filings this month, hours this monthBuiltGET /clients/{id} shows its engagements and open tasks; the hours figure equals the SQL sum of that client's time entries in the current month
Clients & engagementsEngagements with type, budget hours, fee and up to 10 custom fieldsBuiltcreating an engagement with 11 custom fields returns 422; with 3 it stores and renders all 3 on the engagement page
Clients & engagementsEngagement health derived: % done, overdue count, hours vs budget, a red/amber/green flagBuiltunit test: an engagement with an overdue task or hours >110% of budget is red; >=90% hours or a task due in 2 days is amber; else green — health is never stored
TasksTask register with filters (status, priority, assignee, client, due window, search)BuiltGET /tasks with each filter returns exactly the SQL-matching ids; submitting the form with every select on its blank 'All' option returns 200 (never 422)
TasksLifecycle: todo -> in progress -> review -> done, plus cancelled; every change writes an eventBuiltan illegal transition (done -> todo without reopen) returns 409; a legal one writes a 'task.status' event with from/to; reopen works from done and cancelled
TasksSubtasks to any depth; parent progress derived from leavesBuilta three-level tree renders nested on the task page; the parent's progress equals done leaves / all leaves; a parent cannot be marked done while a subtask is open (409)
TasksDependencies (finish-to-start): blocked derived, cycles rejectedBuiltadding B depends-on A makes B 'blocked' until A is done; adding A depends-on B then returns 422 (cycle); starting a blocked task returns 409
TasksBoard view (columns by status, move by button) and month calendar by due dateBuiltGET /board shows one column per status with card counts equal to SQL; GET /calendar?month=YYYY-MM puts each task with a due date in that month in its day cell (headless: cell counts match SQL, 0 console errors)
TasksMy day: my overdue, due today, in progress and blocked, in that orderBuiltGET /me as a staff user lists only their tasks in the four groups; overdue is derived from due date and status
Statutory calendarCompliance templates: GSTR-1, GSTR-3B, TDS return, advance tax, ITR, tax audit, ROC annual filingBuilteach template has a frequency and a due-date rule; unit test: for FY 2026-27 the rules give GSTR-3B on the 20th of the following month, TDS 24Q/26Q on 31 Jul/31 Oct/31 Jan/31 May, advance tax on 15 Jun/Sep/Dec/Mar
Statutory calendarClient subscriptions derived from profile (GST-registered, TAN holder, audit applicable, company)Builta company with GSTIN, TAN and audit gets GSTR-1, GSTR-3B, TDS, advance tax, tax audit, ITR and ROC; an individual without GSTIN gets only advance tax and ITR; overrides can add or drop a filing
Statutory calendarGenerator: idempotent, statutory due date plus an internal target N working days earlierBuiltrunning the generator twice for the same period creates tasks once; the internal target skips Sundays and listed holidays (unit test with a holiday on the natural target)
Statutory calendarFiling calendar: a month of statutory deadlines with status per clientBuiltGET /filings?month=YYYY-MM shows every generated filing task in that month grouped by due date with its client and status; the filed count equals SQL
TimeTimer on a task: start, stop; one running timer per personBuiltstarting a second timer stops the first and records its minutes; stopping writes an entry whose minutes equal the elapsed time (frozen clock test)
TimeManual time entry with validation (date, minutes 5-720, billable flag)Builtan entry of 0 or 800 minutes or a future date returns 422; a valid one appears on the task and in the timesheet
TimeWeekly timesheet per person (days x tasks grid, totals)BuiltGET /time?week=YYYY-Www renders one row per task with entries that week; each day total equals SQL
TimeTime report: hours by client and engagement, billable share, budget burn, CSV exportBuiltGET /reports/time?from&to totals equal SQL sums; /export/time.csv has one row per entry in the window
Workload & dashboardCapacity per person and load from remaining estimates due in the windowBuiltunit test: a person with 40 h capacity and 46 h of remaining estimate due this week is 'over' by 6 h; load excludes done/cancelled tasks and counts logged time against the estimate
Workload & dashboardWorkload page: a bar per person, over-capacity flagged, suggested reassignmentsBuiltGET /workload shows one bar per active user; an over-capacity person has >=1 suggestion to move a task to the least-loaded eligible colleague
Workload & dashboardDashboard: overdue, due this week, filings due, blocked, running timers, hours this weekBuilteach dashboard tile equals its SQL count (headless check against the seeded DB, 0 console errors)
Workload & dashboardActivity log with filtersBuiltevery create/status/assign/time action appears in GET /activity newest first; ?kind= filters
AssistantProvider selection and honest labelling (Anthropic, OpenRouter, heuristic)Built/healthz names the provider; with no key the assistant answers from the heuristic path and every answer is labelled with its provider
AssistantAuto-prioritise: a score per open task with the reasons shownBuiltunit test: an overdue statutory filing outranks a later internal task; each score lists its factors (due, penalty, blocks others, priority); /tasks?sort=score orders by it
AssistantNext three actions for the signed-in personBuiltGET /assistant/next returns 3 of the person's unblocked open tasks, highest score first, each with a one-line reason
AssistantDraft subtasks for a task (checklist per filing type; LLM when configured)BuiltPOST /tasks/{id}/draft returns >=3 subtasks for a GSTR-3B task from the heuristic path; accepting creates them as children
AssistantMeeting notes to action itemsBuiltPOSTing notes with lines like 'Priya to reconcile 2B for Sri Balaji by Friday' proposes tasks with assignee, client and due date resolved; nothing is created until confirmed
AssistantWeekly practice report narrativeBuiltGET /reports/weekly returns a narrative whose every number (filings filed/due, hours, overdue) equals SQL
AccountsUsers, PBKDF2 passwords, stateless signed sessionsBuiltwrong password returns 401 on /login; a session cookie from one instance is accepted by another with the same secret
AccountsRoles: partner, manager, staff with a permission mapBuiltstaff cannot create clients or reassign others' tasks (403); manager can; partner can manage users
AccountsShared OC Apps guest login and the gate-off guest sessionBuiltguest-YYMMDD-xxxx with the derived password signs in as partner-view; OC_GATE_OFF=1 on the twin lands /app on the dashboard with a guest session
ShipJSON API with feed token (tasks, clients, time)BuiltGET /api/v1/tasks without token returns 401 JSON; with ?token=<FEED_TOKEN> returns 200 with count equal to the task table
ShipLocal lane under pm2 on :8391Builtpm2 shows 'fileright' online; curl 127.0.0.1:8391/healthz ok=true after pm2 restart fileright; pm2 save done
ShipHeadless walk of every pageBuilttools/walk.py exits 0 against :8391, light and dark, 1280/820/390 px, 0 console errors, 0 failed requests
ShipHosted twin on Vercel at fileright.ajaykongala.onlineBuiltfileright.ajaykongala.online/healthz returns ok=true; /app opens the dashboard with a guest session while OC_GATE_OFF=1; walk against the twin exits 0
ShipBetadoc LONG: story, architecture, honest matrix generated from this tracker, documentation pageBuiltGET / and /documentation.html on the twin return 200; the matrix block equals tools/matrix.py output for the current tasks.db; light and dark at 1280/390 px have 0 console errors
ShipOC Apps card: apps.json entry, mark, /fileright/ rewrite, measured memory, deployBuilttools/check_apps.py says schema ok; the probe finds every FileRight link answering; oc-apps.ajaykongala.online/fileright/ returns the betadoc with and without the oc_access cookie
ShipRegister: port registry rows, HOME.md line, mirror repo ajay-453/filerightRoadmapport_registry.py list shows 8391 and 6805; tools/mirror_repos.sh fileright pushes and prints the commit count
Beyond v1Integrations: calendar feed, email-in to task, Slack/WhatsApp remindersRoadmapan .ics feed per person validates and lists their due tasks; an email to the inbox address creates a task
Beyond v1Gantt view with critical path across dependenciesRoadmapGET /gantt?engagement= renders bars by start/due; the critical path equals the longest dependency chain by estimate
Beyond v1Client portal: document requests and uploadsRoadmapa client link lists requested documents; an upload marks the request received and notifies the assignee
Beyond v1GST portal status sync (filed / not filed per return)Roadmapa sandbox call for a GSTIN returns filing status per period and updates the matching filing tasks
Beyond v1Invoicing from timesheets and fixed feesRoadmapan invoice for an engagement totals billable hours x rate plus fixed fee, with GST at 18%, and exports to PDF
Rename and simplifyRename to FileRight everywhere: app, twin domain, card, registry, mirror nameBuiltgrep finds the old name nowhere in the app, the card or the product page outside its generated matrix; fileright.ajaykongala.online/healthz says app=FileRight; the old domain redirects to it
Rename and simplifyFive-item menu (Home, My work, Due dates, Clients, Team) with tabs for the restBuiltheadless: the top menu has exactly 5 links on every page; every former page is reachable from the menu plus one tab; 0 console errors
Rename and simplifyPlain words: job, step, service, waiting, due datesBuiltheadless: no page's visible text contains 'engagement', 'blocked', 'subtask' or 'filings'; tests updated and green
Rename and simplifySimpler Home: three numbers, five jobs to do first, a three-step 'how it works'BuiltHome shows exactly 3 number tiles, each equal to its SQL count, a 'Do these first' list of 5 and the 3-step intro; walk 0 console errors
Rename and simplifyProduct page and documentation rewritten for FileRight and the new menuBuilt/ and /documentation.html on the twin say FileRight, use the new menu names, matrix equals tools/matrix.py; light and dark at 1280/390 px clean
Coming next

What offices ask for after this.

Bills from hours

A bill per service from the hours logged and the agreed fee, with GST, ready to send to the client.

A page for clients

A link where each client sees which documents the office still needs this month and uploads them.

Check the GST portal

Mark a return done automatically when the portal shows it filed, even if the client filed it.

Reminders and a timeline

Reminders on WhatsApp or email, a calendar feed for each person, and a timeline view of a big job.

Setup

Runs in your office, or ours.

In your office

One small program and one data file on the office computer or server. Client PAN numbers and papers never leave the office. Backups: copy one file.

  • Works without any AI service; add an AI key later if you want drafted steps and summaries.
  • Phones and laptops on the office network open it in a browser.

This demo

The same program, hosted. It resets to the made-up office every time it restarts, so try anything: nothing you change is kept.

  • Every list can be downloaded as a spreadsheet (CSV). Importing clients from a spreadsheet is not built yet.

Have a look around.

Open Due dates to see this month's returns, open a late job and start its timer, paste a few lines of meeting notes into the assistant, and check Team to see who is busy.