350+ Practice Management Reports in MyTask

Actions you can take from this screen

• Email all clients with pending work in one clickNot only the jobs with a logged issue — work not started, and work simply pending, can be chased the same way. Select the clients from the list and email all of them at once, with client name, service, financial year, period and task description filled in for each.
• Or send it as a message insteadThe same selection and the same filled-in details, sent through the Messaging Portal rather than as an email — for the clients who never open email. One capability, two channels, chosen at the point of sending.
• Raise a task without leaving the reportSpot the gap and fill it on the spot, rather than noting it down and going somewhere else to act on it.

Actions you can take from this screen

• View the whole dashboard for any date rangeToday, yesterday, this week, this month, this year or any dates you choose — the whole dashboard recalculates, not one panel of it.
• View the dashboard branch-wiseWhere your practice runs more than one office, every figure above reads for one branch or for the firm — the same screen, answering for whichever you ask.

Actions you can take from this screen

• View any user's activity for any periodChoose the user, the branch and the window — today, yesterday, last 7 days, last 30, or any two dates — and all sixteen summaries recalculate together.
• Filter by branchWhere a person works across offices, read their activity for one branch or for all of them.

Actions you can take from this screen

• View one client or a client groupSwitch between client-wise and group-wise. A family or a set of related entities is read as one relationship, which is how a practice actually bills them.
• Any financial year, back to 2004Twenty-three years of history on the same screen — outstanding balances do not respect a two-year retention window.
• Filter every column of the job listEach column of the task grid carries its own filter, so a list of every job for a client narrows to exactly the one being argued about.
• Export the client's positionThe whole report out to a file, for the client meeting or the recovery letter.
• Show the services added for this clientWhich services this client is actually signed up for, as opposed to which ones happen to have activity this year.

Actions you can take from this screen

• Filter by role: assigned user, leader, manager or memberAssigned user, task leader, task manager, task member, or any role at once. The same person's numbers change completely depending on which relationship you ask about, and reading only one of them is how a supervisor gets mistaken for someone who is overloaded.
• Pending, completed, or bothRun the whole report on open work, on finished work, or on both together.
• One branch, or every branch you can seeRead one office on its own or consolidate across all the branches a user has access to — the same report either way.
• Narrow to a financial year, period and serviceAll financial years, or drill down to one year, one period and one task type.
• Hide staff with no tasksDrop zero-count rows so a sixteen-person table shows only the six people who actually hold work.
• Click a number to see its tasksSwitch from the consolidated summary to the underlying task list, so a figure can be checked rather than believed.
• Download the dataThe chart as SVG or PNG for a partners' meeting, or the whole table as CSV.

Actions you can take from this screen

• Consolidate the branches that share a financial yearThe report adds up across offices on the same year end — which is the rule the whole product follows, not a limitation of this screen. Branch choice stays limited to the offices you are permitted to see.
• View all servicesTask types can be access-restricted per user, but this report shows all of them for a branch you are permitted to see. A partner gets the true firm-wide figure without having to be given day-to-day access to every service.
• Search for a staff memberSearch the staff columns by name rather than scrolling a table twenty-two people wide.

Actions you can take from this screen

• Read my dashboard for one branchWhere the firm runs multiple offices, a user's own home screen answers for whichever branch they are permitted to see.
• Open the activity behind my chartJump from the performance chart straight into what produced it.
• Filter my work by roleNarrow the whole role-wise breakdown to one relationship at a time.
• Add a to-do without leaving the screenCapture the small thing the moment it is said, on the screen already open.
• Keep notes on my own dashboardSticky notes that live with the work rather than on a monitor bezel.

What you can do here

• Set a batch up once, let it raise the work foreverThe Auto Bulk Task Batch: define the service, the clients and the frequency once, and the tasks appear on their own at every due cycle. For a recurring service like GST 3B that is the difference between a monthly administrative job and no job at all.
• Build a batch from a spreadsheetImport the client list for a batch straight from Excel rather than picking clients one at a time — which is how a practice with two thousand GST clients actually gets started.
• Service-wise batches that build themselvesYou do not set these up. MyTask keeps a batch for every service you sell — GST 3B, TDS 26Q, DIR-3 KYC, monthly accounting, tax audit — and populates each one on its own by reading which clients you have filed that work for before. It stops short of raising the tasks, deliberately: the list is proposed and you approve it, so a wrong inference cannot silently create two thousand jobs.
• Raise the whole batch on demandCreate every task in a batch in one action when you would rather choose the moment than wait for the schedule.
• Assign inside the batch, not afterwardsA batch carries its own type of assignment, task leader and task manager, so two thousand tasks arrive already allocated instead of arriving as two thousand unallocated jobs.
• See which batches are not ready to runThe list flags any batch whose settings are still incomplete, so a batch that would quietly fail to raise anything is visible before its due date rather than after it.
• Keep batches per branchWhere the firm runs several offices, batches and the tasks they raise follow that branch's own settings; a single-office firm gets the same process across the whole organisation.
• Find a batch in the listEvery column of the batch list carries its own filter — branch, name, assignment type, leader, manager.

What you can do here

• Build your own service tree, four levels deepCategory, then task type under it, then milestone groups, then the milestones themselves. GST holds 28 task types in the demo account; Income Tax 16; Audit, Accounting, ROC, Registrations, TDS and Finance Work their own. Nothing here ships fixed — a firm that files GSTR 1, GSTR 3B, GSTR 9C and LUT structures them the way it actually works, not the way a vendor guessed.
• Define the phases a job passes throughMilestones are the stages of a service in sequence — receiving information from the client, completion of accounting, vouching and verification, preparation of 3CB and 3CD, computation checking, uploading and filing the return. Every milestone report in MyTask reads off the ones you define here.
• Two workflows under one service, kept apartWhere the same task type is worked two different ways, build a milestone group for each and pick only the relevant milestones. Under Income Tax Return Filing, one group covers computation and return filing alone; another adds balance sheet preparation ahead of them. Monthly 3B carries 25 milestone groups in the demo account and GSTR 1 carries 17 — the same service, seventeen genuinely different processes.
• Name your own reasons for a job being stuckPending issue labels — Aadhaar information pending, digital signature pending, details from the client, tax payment — are defined here and shared across head office and every branch, so the same vocabulary is used firm-wide and the pending-issue reports stay comparable between offices.
• Give each branch only the services it providesA GST-only office does not carry your audit tree. Service-wise access per branch is what makes consolidation and separation work: figures line up across offices because the services underneath them line up.
• Say who is allowed to tick a stage offA milestone can be restricted to Task Leader, or Leader or Manager, or those plus the primary assigned user, or those plus team members. The app's own example is the one every firm recognises: if policy says a review is signed off by the leader alone, fix it here and nobody else can mark it complete.
• Refuse to close a return until the portal says it was filedA milestone can be set so it cannot be completed unless the return has actually been filed on the income tax portal. The difference between a job marked done and a return that was genuinely submitted is the difference between a clean season and a notice.
• Retire a pending issue automatically when a stage is reachedChoose which pending issue labels stop counting as pending once a milestone is complete — challan pending, information pending, DSC pending, TDS mismatch, Aadhaar PAN linking. They clear themselves in the task type dashboard rather than waiting for somebody to tick them off, so the pending-issue reports stay true without maintenance.
• Add a category or a task type at any timeNew services are added as the practice takes them on — a firm that starts filing FSSAI or trademark work adds it without waiting for a release.

Actions you can take from this screen

• See the client's outstanding from inside the taskThe job header carries file number, client, group, financial year, period, milestone group and assigned user — and the client's outstanding balance and billed status alongside them. Nobody has to go and look.
• Email the client from inside the jobCompose from the job itself with a saved template, choose which address the reply comes back to, pick recipients from the client's own contacts, attach up to 20MB — and it lands in this job's email log rather than in somebody's sent items.
• Message the client from inside the jobPull the right numbers from the client's contact roles straight into a Messaging Portal message, for the clients who never open email.
• Contact the right person at the client: owner, accountant or otherContacts are held by role — primary owner, secondary owner, accountant, other contact person — each with two numbers and two email addresses, so a query about the books goes to the accountant and a query about signing goes to the owner.
• Attach working papers, and share a link with the clientUpload up to 30MB per file across the usual working formats, link it to the job, and share a link with the client rather than emailing the file around.
• Keep the client's documents against the jobDocuments linked to this job with title, who linked them and when.
• Record documents received for this taskRecord what arrived, how it was received, the nature of the documents and whether it has been returned — attached to the tax audit it belongs to rather than to a general register.
• Record documents sent for this taskWhat left the office, by which mode, whether the originals went, whether they are returnable and whether they have come back.
• Add a team to the task: leader, manager and membersPrimary assigned user, task leader, task manager and any number of team members — the same four-role structure every workload report reads from.
• Schedule a follow-up, appointment or meeting on the jobWith the person, contact number, date, who it is assigned to, a remark, completion status and a join link for the meeting.
• Import a checklist into the jobBring a standard to-do list in rather than retyping the same twelve steps on every tax audit.
• Custom fieldsPAN, Aadhaar and GSTN sit on the job beside address, phone and email, with additional fields and client notes for whatever the firm needs that MyTask did not think of.

What you can do here

• Work follows whoever actually does itAuto assignment is on by default. An income tax return sits with one person; somebody else ticks off a stage on it — balance sheet checking, computation preparation — and the job becomes theirs. Nobody reassigns anything, and the record says who is holding it now rather than who was handed it in April.
• Pin a stage to a role, and the job moves there on arrivalSet a milestone to fix auto assignment to Task Leader or Task Manager, and the moment a return reaches that stage the assigned user becomes whoever holds that role — whether or not they were the leader or manager on the job before. Common across every branch.
• Or pin it to a named person, differently in each officeThe same milestone can route to a different individual per branch: balance sheet feeding goes to one person at the Beawar office and someone else elsewhere. Fix-to-role is firm-wide; fix-to-user is branch by branch, so a firm keeps one process and still respects who actually does that step in each office.
• And the job goes back where it came fromOnce the fixed milestone is completed the task auto-transfers back to the previous assigned user. So sending a return to a specialist for one stage does not quietly leave it parked with them — the specialist gets it, does the stage, and it returns.
• Or stop a job moving at allAuto transfer can be blocked in a task's own setting, so work that must stay with the person who signed it stays there however many people touch a stage along the way.
• Whoever picks a job up can end up owning itThe person completing a stage does not have to be on the job already. They might hold another role on it, or simply have access to that task type — an ITR, a TDS return, a GST filing — and the moment they complete a stage the job becomes theirs.

Actions you can take from this screen

• Emailed early every morning, automaticallySent automatically early each morning covering the whole of the previous day, with today's due work attached. Nobody runs it, nobody remembers to run it, and it reaches partners who never open the software at all.
• Superadmins and admins receive it by defaultEvery superadmin and admin is on the list by default; add, change or remove addresses as you like, or switch the whole thing off.
• A separate report per officeEach branch has its own daily report and its own recipient list — and branches here run genuinely different calendars: a Nepal office on a custom financial year, a Dubai office on the calendar year, and Indian offices on April to March. Each gets yesterday measured on its own year.
• Sent as a PDF with full detailsNot a summary email with a link to log in. The counts arrive with the full listings underneath them — twenty-five pages on an ordinary Thursday — so the report can be read, forwarded and kept.

Actions you can take from this screen

• The same alert reaches three places at onceIn the app, on the desktop while somebody is logged in, and as a push notification on the mobile app. A partner who is not at their desk still finds out that a job moved.
• It tells you why you are being toldOne task being created fires three separate notifications — one to the leader, one to the manager, one to the assigned user — and each says which role it is reaching you in. “Task created for A-159, ANAND SINGH in Loans for 2026-2027. Your Role: Manager.” Three people, one event, three different reasons to care.
• Some of it is the system telling on itselfNot every notification comes from a person. Attendance rules raise their own: a half day marked automatically against somebody's name for a given date, every day it happens, so the rule is visible rather than silently applied.
• Both ends of the exchange are toldNotifications go to both sides, not just downhill. Apply for leave and the approver is told; approve it and the applicant is told. A job moving between two people notifies the person it left as well as the person it reached. Most systems tell the recipient and leave the other party to find out, which is exactly how two people end up believing they both own a filing.
• Every approval, applied for and answeredLeave, expenses and disbursements each raise a notification when they are applied for and again when they are approved or refused — so a claim sitting unanswered is visible to the person waiting on it, not only to the person sitting on it.
• When work changes hands on its own, both people hear about itAuto assignment moves a job the moment somebody completes a stage on it. That would be alarming if it happened silently — so it does not: the person who had the job and the person who now has it are both notified, and the Assignment Change Log records it.
• Work allocated, comments posted, appointments, and more besidesWork allocated to you, a comment posted on a job you hold, appointments falling due, attendance rules raising their own. These are examples rather than the full set; MyTask notifies on a good many more events than are named here — among others.

Actions you can take from this screen

• Book a follow-up, an appointment, a meeting or a callAgainst a person and a number, on a date and at a time, with the nature of it recorded — so what the appointment is for survives the person who arranged it.
• Tie it to the job it is aboutA meeting linked to a task stops being a diary entry and becomes part of the record of that piece of work.
• Or tie it to the money owedThe other thing a schedule can be linked to is outstanding fees. A call booked against a client’s dues sits in the same register as everything else and is answerable in the same way — which is how a recovery call stops being something a partner keeps meaning to make.
• One person it is with, another who handles itThe appointment is booked FOR somebody at the firm, and separately ASSIGNED to whoever is to deal with it. A partner’s client meeting can be prepared and chased by the person who will actually do the work.
• Join it from the registerWhere a schedule is an online meeting, it is joined from the row rather than hunted for in an inbox.
• Complete it, move it, or drop itMarked done, rescheduled or deleted from the list itself — and all three states stay visible on their own tabs.
• Per office, and exportableEach branch keeps its own diary, and any view of it can be taken out to a file.
• And it shows on the client’s own account pageA group’s pending, completed and cancelled schedules appear on its account statement, beside what it owes. The conversation about an unpaid bill and the appointment booked to have it are on the same screen.

Actions you can take from this screen

• Any financial year back to 2004-05Twenty-three years, because outstanding balances do not respect a retention window.
• Click any line to see its detailsEach line expands into what makes it up, so a figure that looks wrong is investigated rather than queried.

Actions you can take from this screen

• Download the full statementThe whole running account as a file, ready to attach to an email or hand across a desk.
• Or just the unpaid billsA second download carrying only the outstanding invoices. A client chasing their own account rarely wants the year’s arithmetic, they want the list of what is open.
• Print itA printed statement for the client who still prefers one, off the same screen.
• Click any total to see its detailsEvery tile at the top of the screen — opening balance, billing, collection, outstanding, advances, expenses — leads to its own schedule further down. Nothing on the statement is a figure you have to take on trust.
• See the same account as analyticsThe group read as charts rather than as a ledger, on a second tab of the same screen.

What you can do here

• Let the outstanding chase itselfThe same chaser captured on the messaging side, seen from the ledger end: MyTask reads what a group owes and follows it up without anybody opening the statement. Most firms do not have a collections problem, they have a nobody-got-round-to-it problem.
• On whatever interval you setReminders go a chosen number of days apart, so a client is chased steadily rather than on the day somebody happens to look at the ledger — and the partner is not the one making the awkward call each time.
• And stop below an amount you chooseBelow the threshold the chasing stops. Nobody wants the firm pursuing a long-standing client for fifty rupees, and a chaser that cannot be told when to stop is one that gets switched off altogether.
• Sent to the number the group actually answers onSaved against the group, which in an Indian practice is usually one person settling for a wife, a firm and two associated concerns — so the reminder reaches whoever pays rather than each file separately.
• By message or by SMSThe one place a second channel is offered, because a payment reminder has to reach somebody who may not read anything else.

Actions you can take from this screen

• It reads inside the invoice, not just the totalEvery narration on every invoice is examined and matched to the segment it belongs to. Fifty invoices to one client, five narrations apiece, and the software works out that two hundred and fifty lines belong to GST, income tax and audit in some proportion — then consolidates them onto the billing dashboard. Revenue analysis elsewhere starts at the invoice total, which quietly forces a firm to raise one invoice per service just to be able to report on it.
• One invoice can belong to several segments at onceA single bill carrying “GST - GSTR 1 - 2018-2019 - QTR3” and “INCOME TAX - IT Return Filing - 2018-2019 - Annual” is not forced into one bucket or the other. It counts toward both, by the amount against each narration. That is how practices actually bill, and it is the case that defeats invoice-level reporting.
• And it does the same when a receipt is enteredThe segment split is applied to collection as the money arrives, not reconstructed afterwards. So the collection and dues figures follow the same lines as the billing figures rather than being an approximation laid over them.
• Across every firm you invoice throughInvoices raised through the firm, through an associate concern and through a private limited company are consolidated into one segment picture. The practice sees what its GST work earned, regardless of which of its own entities raised the bill.
• Segments are yours to defineGST, income tax, audit, ROC, project finance — whatever divisions the firm actually thinks in, rather than a fixed list decided by somebody who has never run a practice.

Actions you can take from this screen

• Nothing is raised until you have read itThis is the whole design. The software does the work of preparing thousands of invoices and then stops, because a wrong bill sent to a client costs more than the typing it saved. Issue them when the list is right, not before.
• Choose exactly what to billBy service category, by task type, by client group, by whether the work is pending or completed, by financial year and by period — monthly, quarterly, half-yearly or annual. A quarter’s GSTR-1 billing for every quarterly client is one selection.
• The amount is already filled inMyTask proposes a figure for each bill from what the practice itself has charged for that same work before, with a fee increase you set applied on top. A tentative best estimate to correct, rather than an empty column to fill in. The method is the firm’s own billing history, which is why the numbers are defensible when a client queries one.
• Correct one line, or every line at onceChange a date or an amount on a single record, or apply the change to the whole batch. Reviewing a thousand invoices is only realistic if a single correction does not have to be made a thousand times.
• The right firm raises each billWhere a practice invoices through more than one entity, each draft comes through against the organisation that should be raising it, and can be switched before issue.
• Each firm’s own number series continues correctlyBill numbers carry on from the last one that organisation issued, in an unbroken series, and a number already used is refused rather than quietly duplicated. Auto-generating a thousand invoices is worthless if the numbering will not survive an audit.
• And the narration names the workBuilt from the service category, the task type, the financial year and the period — so a bill reads “GST - Monthly 3B - 2026-2027 - February” and not “professional fees”. Editable, or chosen from a list. It is also what the segment-wise revenue reporting reads, so a bill raised this way is analysed correctly for free.
• Taxes applied where they applyAdded automatically according to the billing organisation raising the invoice, rather than remembered per bill.

Actions you can take from this screen

• Send a whole group’s invoices in a few clicksThe request every practice gets — “can you send me all the bills for the family” — used to mean digging out a year of PDFs one at a time. Select them in the register and send the lot.
• By email, or as a messageThe same invoices go out on whichever channel the client actually reads. A message reaches a proprietor who has not opened an email in a month.
• Narrow the register first, then send what is leftBy branch, financial year, client, group, file number or which of your firms raised the bill. The selection is the report, and the report is what gets sent.
• Or send one bill, to an address you typeWhere the client master holds an email address the invoice goes there; where a client wants it somewhere else this time, that works too.

Actions you can take from this screen

• All reports are available branch-wise and year-wiseThe same report for the head office or for any branch, in any financial year back to 2004-2005, so a multi-office practice reads the same figures at whatever level it manages.
• Filter inside the report, column by columnEach column carries its own filter, so a register of several hundred bills becomes the twelve rows a question is actually about without going back to the selection screen.
• The three expense reports are also available hereUnbilled, billed and non-billable expenses sit on this same menu — captured in the expenses module where their own screens live, and reachable from billing because that is where somebody asks the question.

Actions you can take from this screen

• Sweep five financial years in one runLeakage is not a this-month problem. Up to five years can be selected at once, so a practice can find what it never billed in 2022 as easily as what it never billed in August.
• The year the work was for, or the year it was raisedTwo separate year filters, because they answer different questions: a return for 2023-2024 created last week is a different kind of problem from a job raised in 2023-2024 and forgotten.
• Up to ten task types at a timeCheck the GST filings and the ITRs together, or one service on its own — the leak is rarely spread evenly across the practice, and this is how you find where it is.
• Narrow it by client, group, file, period or statusPending or completed or both, monthly, quarterly, half-yearly or annual work, one family group or one file number.
• And bill it, or mark it free, from the reportEach row carries the job itself, so the list is worked through rather than copied out. A leakage report nobody can act on from the page is a leakage report that gets printed and filed.
• Show only the columns you are readingEighteen columns are available and most questions need six. The report is set to the question rather than the question fitted to the report.

What you can do here

• Raise anything the billing side needsInvoices, receipts, debit notes, credit notes and advance receipts, each against the client, the group and the job it belongs to.
• Save a batch and it sends itselfDocuments raised into a batch go out to the clients the moment the batch is saved. Nobody returns to a list of finished invoices afterwards to send them, which is the step that actually gets skipped in a busy week.
• And the batch need not be built by handBatches can be assembled automatically as well as picked one by one — so a month’s billing can be raised, batched and sent without the batch itself becoming the new piece of manual work.

What you can do here

• An estimate is a proforma invoiceNot a quotation kept to one side. It is the bill in every respect except that it has not been raised yet, which is what a client asking for a proforma actually wants.
• Turn it into the invoice in one clickWhen the work is done the estimate becomes the invoice — no retyping, and no gap between what the client was quoted and what they are charged.

Actions you can take from this screen

• Two ways in: people, or moneyStaff Wise Utilisation asks whether time is being recorded and used well. Profitability Status asks whether the work made money. Same timesheet data, two entirely different questions, and a firm usually needs both in the same meeting.
• Any branch, any financial yearRead one office or another, for any year back to 2004-05.
• You see only the staff you have permission to viewTimesheet data is who worked how long and how well, so the whole dashboard is bounded by access rights: a user sees records and reports only for the people they have been granted. It is the one screen in MyTask where the permission model is the feature rather than the fine print.
• Edit another user's entry, if you have permissionWhere the right has been granted, a user can edit or delete another person's timesheet records — so a wrong entry is fixed by whoever spots it rather than chased through the person who made it.

What you can do here

• Clock-wise or hours-wise, and the app tells you which to pickClock-wise wants exact ranges — 10:00 AM to 12:00 PM. Hours-wise wants only the total. The app's own note says hours-wise is generally better because it is simpler and faster to post, which is an unusually honest thing for a settings screen to say about its own options, and it is right: a timesheet nobody fills in is worth nothing.
• One method across every branch, on purposeWhichever method the first branch chooses applies to them all. That is a deliberate constraint rather than a limitation: time records consolidate across offices, and two offices recording time in different shapes cannot be added together.
• But choose which branches keep timesheets at allA branch that does not run timesheets simply does not, while the offices that do share one method.
• A recovery rate per personEach member of staff carries their own cost per hour, which is what turns posted time into job cost, feeds invoicing, and makes profitability per service, per branch or per firm calculable at all.
• Minimum required and maximum allowable hours, per personA floor so short posting is visible, and a ceiling so a day cannot be filled with twenty hours by accident — eight required and twelve maximum in the demo account.
• The days each person is expected to workMonday to Saturday, or whatever that person's week actually is — so the required-hours figure is not computed against days they were never meant to be in.
• Decide who may see recovery rates and amounts at allA recovery rate is close enough to a salary that showing it to the wrong person is a problem. Who can see rates and amounts is its own setting, separate from who can see the timesheets themselves.
• Apply timesheets only to the services that need themBranch by branch, per task type — so a firm can cost its audits without asking anyone to log time against a PAN application.
• Only a branch's own people appear, because currencies differWhen timesheets are made applicable for a branch, only users whose primary branch it is are listed. The reason is currency: a recovery rate is denominated in the branch's own currency, so a person appearing under two offices would carry two incompatible rates. The constraint falls out of multi-currency rather than being imposed on it.
• Define what counts as chargeable on client and on officeThe split that makes the utilisation reports meaningful: chargeable client time, non-chargeable client time and office time are configured here rather than left to whoever is posting.
• Your own time codesClassify entries however the firm thinks about them, and filter the time records by those codes afterwards.
• Block the days nobody should be postingHolidays beyond the weekly off, marked so time cannot be booked against them.
• Allow posting after a job is finished, or do notWork often gets written up after it closes. Whether that is permitted is a setting rather than an accident.
• Stop people posting forwardFuture time posting can be restricted once the previous minimum required hours are already in — which blocks the habit of filling next week to make this week's numbers look right.
• Posting time after a job is billed needs its own permissionAnd it is granted on the individual task when it is created or edited, not globally — because time added after an invoice has gone out changes a profitability figure somebody has already acted on.
• Catch time posted outside attendanceTimesheet settings work with attendance, so hours booked beyond the hours somebody was actually recorded as present can be identified. Two independent records of the same day, checked against each other.

Actions you can take from this screen

• Search for the job, or pick from what you worked onPost against a task by searching for it directly, or let the screen offer the jobs already worked on that date. On a day spent across eleven GSTR-1 filings, the second route is the difference between a timesheet posted and a timesheet abandoned.
• Billable and non-billable on the same lineOne row per job carries both: chargeable hours and unchargeable hours against the same task, each with its own comment. A tax audit where four hours were billable and two were spent chasing the client for bank statements is recorded as exactly that, rather than as six hours of something.
• A reason for each halfSeparate comment fields for the billable and the non-billable time, so the unchargeable two hours carry their own explanation — which is what turns a write-off into an argument you can have with a client at renewal.
• Costing is calculated for you, not worked outRecord the time spent on a tax audit and MyTask costs it from that person's own recovery rate — no one calculates anything. The figure appears in rupees as the hours go in, and the same number feeds job costing, the invoice and every profitability report in the module.
• Classify the time as you record itEach entry carries an account code, so the firm's hours can be read back by category rather than as one undifferentiated pile.
• The branch is on the rowEvery line names the office the job belongs to, so a person working across branches posts once and the hours still land against the right office's costing and its own currency.

Actions you can take from this screen

• Costing happens once the time is postedNobody runs a costing exercise. Hours go in against a job, each person's recovery rate turns them into money, and the job carries its own cost from then on — into invoicing, into profitability, and onto the task card while the job is still open.

Actions you can take from this screen

• Narrow the whole office's time record to one clientThe report opens as every time record in the office for the year and filters down — by client, by branch, by whether the time was on a client or on the office.
• Export itOut to a file, for the fee discussion it was pulled for.

Actions you can take from this screen

• Approved leave shows as leave, not as a shortfallA day somebody was on approved leave prints “Leave Approved” across the row rather than counting them eight hours short. The report knows the difference between not posting time and not being there.
• Any dates, not just a financial yearPick the person, the branch and a from-and-to date — so a query about one fortnight is answered without reading a year.

Actions you can take from this screen

• Give the client a receipt as you take the papersAn acknowledgement is issued at the counter, at the moment of receipt. The client leaves with proof of what they handed over and the firm has the same record — which ends the argument about whether a document was ever provided before it can start.
• Export the registerOut to a file for an audit of the office’s own records.

What you can do here

• Record what has to go back, and tick it off when it doesReturnable documents are flagged when they are taken in and marked returned when they are handed back — done from the register itself, so the pending-returnable figure is maintained by the person doing the handing back rather than by somebody updating a list afterwards.

What you can do here

• Link one inward entry to as many jobs as it feedsA single bundle of papers often serves several filings. One entry can be attached to multiple tasks, and they need not even belong to the same client — a group’s documents arriving together are linked wherever they are actually used, rather than being entered again for each.
• And it appears on the job itselfOnce linked, the inward shows against the task, so whoever is doing the work can see what came in without going to the register.

Actions you can take from this screen

• Give the client a receipt for what they are takingAn acknowledgement issued as the documents leave, the mirror of the one issued when they arrive. Both halves of the handover carry proof.
• Record how it actually wentCourier, handed over in person, sent by bus or train, by post, or another route — chosen from a set list rather than typed, so a despatch can be traced by the way it travelled.
• Link the despatch to the client recordSo a client’s document history reads in both directions from one place.

Actions you can take from this screen

• Flag originals as originalsMarked at the point of despatch, which is what makes the originals-in-transit figure trustworthy — nobody reconstructs it afterwards from memory.

What you can do here

• Choose where the replies landEvery send names a “get revert on” address, so mail leaves MyTask but answers arrive in a real person’s inbox. System-sent email is usually a dead end — the client presses reply and it goes nowhere, or to a no-reply box nobody reads. Picking the return address per mailing means the partner who sent it is the one who gets answered.
• The firm’s letterhead and disclaimer are already thereThe message opens with the practice’s own sign-off: name, qualification, firm, address, telephone, and the confidentiality notice a professional firm is expected to carry on client correspondence. Nobody has to remember it, and nobody sends a bare email by accident.
• Or start from a saved templateImport a stored message rather than rewriting the same GST deadline reminder every quarter.
• Attach a fileUp to 5MB across the usual document and image formats — a computation, a challan, a signed certificate.
• Six ways to build a recipient listEvery list is of the firm's own clients: from your client list, from the clients' phone book, from a saved email list, by task type, from client details imported from an Excel sheet, or by typing a client's address in. A practice emails very different groups of its clients for very different reasons, and being made to build every list the same way is why most firms give up and use their own mail client.
• Email everyone who has a particular serviceAdd Using Tasktype builds the list from the work itself: every client with a GSTR 3B, every client with a tax audit, every client with a DIR-3 KYC. A deadline reminder goes to exactly the clients it applies to, because the list comes from the jobs rather than from somebody remembering who is on it.
• Or straight from the client masterAddresses pulled from the client record, which is where they are already maintained — so a corrected email address corrects itself everywhere.
• Import a list from a spreadsheetCSV or Excel up to 10MB, for the list that lives outside MyTask — a seminar invitation, a circular to people who are not clients yet.
• Mix sources in one sendThe recipient table records where each address came from, so a single mailing can combine clients, phone-book contacts and an imported list while still showing which is which.
• Send as a branchThe mailing is raised under a chosen office, so a branch writes to its own clients as itself.
• Emails can fire on events tooThe same event-driven idea runs on the email side, configured in its own settings: a daily office report, an email when a client is created, an alert when an issue is found in an income tax return, and a warning if an automated message fails to send.

What you can do here

• The client’s people are already on the screenPrimary owner, secondary owner, accountant and other contact person, each with two addresses, pulled from the client record and added to the email with one action. No lookup, and the right person gets the right question.
• Classify what kind of email it isEach message carries an email type, so a job’s correspondence can be read back by what the emails were for rather than as one undifferentiated thread.
• It is filed against the job, not in your sent itemsSender, recipients, cc, subject and attachments all land in that task’s email log — which is what makes “we told you in July” a thing the firm can show rather than assert.
• And MyTask’s own emails appear in the same historyAutomated messages such as a task-creation notice sit in the job’s log beside the ones people wrote, so the correspondence is complete rather than split between what the system sent and what a human did.
• Attach from a file or from a URLUp to 20MB, and a document can be pulled in by link rather than downloaded and re-uploaded first — useful when the file already lives somewhere the firm keeps things.

What you can do here

• Build a saved list the same six ways you build a one-off sendA list of the firm's own clients is assembled from the client list, the clients' phone book, another saved list, a task type, client details imported from an Excel sheet or typed addresses — the same picker the send screen uses. So “everyone with a GSTR 3B” can be turned into a named list once and written to whenever, instead of being rebuilt every quarter.
• See exactly who is on it before you save itName the list, add the addresses, then preview the whole thing — with each entry still showing where it came from. A mailing list nobody has checked is how a firm sends a client’s reminder to the wrong client.
• The partner writes it once, everybody sends itSave the wording for the emails a practice sends over and over — a GST deadline reminder, a request for bank statements, a reply to a routine notice — and any member of staff can send it properly. The quality of client correspondence stops depending on who happened to be free.
• One footer on every email, kept in one placeFirm name, address, telephone and the privileged-and-confidential notice are held as their own setting rather than inside each template, so every message carries them and a change of office address is one edit, not forty.
• Templates and footers per officeEach is assigned to the branches that use it, so a Dubai or Nepal office signs its mail as itself rather than as the head office.
• And save the lists you write to again and againA custom email list is kept and reused — the audit clients, the trustees, the people who get the monthly circular — and appears as one of the six sources when a mailing is built.

Actions you can take from this screen

• Write the email once and stop thinking about itContent, attachment and recipients are saved together as a named scheduler. The monthly request for bank statements, the weekly reminder to a client who never sends anything on time — written once and then sent by the system.
• Weekly or monthly, on the day you pickChoose the frequency and then the date of the month or the day of the week. A GST document request that has to land on the 5th lands on the 5th, whether or not anyone remembers it is the 5th.
• And you can still send it by handA scheduler does not lock the email away — the same saved message can be fired off manually when something needs chasing early. Automation that cannot be overridden is automation people work around.
• Recipients saved with the reminder, and previewedThe list is built and stored against the scheduler, with a preview of exactly who is on it before the setup is completed.
• Each office runs its ownSchedulers belong to a branch, so an overseas office chases its own clients on its own calendar.

Actions you can take from this screen

• Import the whole register in bulkChoose the file, preview it, let it validate, then import the rows that pass. A practice with three hundred tokens does not start by typing three hundred rows.
• Keep a register per officeWhere branches are enabled each maintains its own; where they are not, one register serves the firm.

Actions you can take from this screen

• Book a token out and back inPhysical movement recorded as it happens, so the register reflects the drawer rather than somebody’s recollection of the drawer.
• Tell the client when their token movesAn email or a message goes to the client when their DSC leaves the office and again when it returns — the same both-ends proof the inward and outward registers give for paper.

Actions you can take from this screen

• Mark one as permanently given, without losing itA token handed over for good drops out of the availability count and stays in the renewal tracking. Most systems would simply delete it, and the firm would then be the last to know it had expired.

Actions you can take from this screen

• Link one DSC to every client that uses itThe token then appears automatically on all their relevant jobs, so whoever is filing can see which signature applies without asking.

What you can do here

• Daily email on what is expiring and what has expiredSeven days’ notice and the expired list, arriving in the daily report rather than waiting to be looked up.

Actions you can take from this screen

• Three views: all, billed, or non-billable expensesAll details, billed expenses only, or non-billable only — because “what did we spend” and “what can we recover” are different questions.
• Any branch, any financial yearRead one office at a time or the firm as a whole.

Actions you can take from this screen

• Say exactly who may approve money — regardless of their job titleApproval authority is granted user by user and can be withdrawn the same way. It is deliberately NOT tied to system role: in the demo firm an admin is de-authorised while two office staff are authorised. Who signs off spending is a decision about trust, not about a permissions tier, and the software treats it that way.
• An approved expense becomes billable on its ownApproval moves the cost straight into unbilled expenses, where it waits on the client’s next invoice. Nobody re-keys it and nobody has to remember it exists — which is the whole reason the unbilled figure can be trusted.
• Claim what you have already spentPick the branch, say whether it was on a client or on the office, name the client, give the period the spending covers, and send it to an approver.
• Several items on one claim, each with its own receiptA claim carries as many lines as the trip had: nature of expense, description, amount and an attachment on each. Three days of travel is one submission with its own bills against each item, not three separate claims to chase.
• A claim covers a period, not a dayFrom and to dates, because expenses arrive as trips rather than as individual mornings.
• You choose who approves itThe approver is picked at submission from the people entitled to decide. Combined with the approver-wise report on the dashboard, that means a claimant knows exactly whose desk their money is sitting on.
• Or ask for the money before you spend itThe second half of the screen: request an advance or a disbursement against a named approver. Staff are not asked to fund a client’s disbursement out of their own pocket and wait a month to be reimbursed.
• Approve, refuse, or allow part of itThree outcomes rather than two. The third is the one that matches how expenses are actually settled, and it is recorded as a decision rather than as a resubmitted smaller claim.
• Open the claim behind any decisionDown to the individual lines and the receipts attached to them, so an approver is deciding on evidence rather than on a total.

Actions you can take from this screen

• The person who spent it says who it was forOn client or on office is chosen at submission, alongside the client it belongs to — not reconstructed at billing by somebody who was not there.
• And every expense report filters on itThe dashboard splits client from office across approved, rejected, pending and part-allowed; the billed and non-billable views read off the same field. One declaration at submission, and the whole module reports on it.

Actions you can take from this screen

• Export it to ExcelOut to a spreadsheet, which is how it reaches whoever raises the invoices.
• Open the claim and the receipt behind any lineDetails and the attached bill sit on the row, so an expense can be put on a client’s invoice with the evidence to hand rather than from a description.

Actions you can take from this screen

• Export either listOut to a file for whoever is reconciling recovery against the practice’s own costs.

What you can do here

• Define the expense categories your firm actually usesTravel and conveyance, food, stay, expenses incurred on behalf of a client, and anything else the practice needs. Every nature-wise breakdown in the module reports on this list, so it is worth setting up once properly rather than filing everything under Other.
• And give each office only the ones it needsEvery nature is assigned to branches individually, so offices in different countries are not forced to share one expense vocabulary.
• Expense emails configured per officeAuto-email settings are held branch by branch rather than firm-wide — so a head office and an overseas branch can notify different people.

What you can do here

• Upload against a job, or on its ownFinal audit reports, whatever the client sent, anything worth keeping — and a whole task can be exported to PDF for the physical file.

What you can do here

• Write something once and share it with named peopleKey client information for the partners, say — shared under rights that say who may edit it and who may delete it, rather than mailed round and forked into five versions.

What you can do here

• And everyone sees what has been shared with themViewable, editable or deletable strictly within the rights they were given.

What you can do here

• Raise the work that does not fit the service treeEmailing audit copies, paying the electricity bill, chasing something for a client that was never a formal service. Assign it to a person or a group, give it an expected completion date, and it stays live until somebody marks it done — so the work that falls outside the service tree is tracked rather than remembered.
• Link it to a client when it belongs to oneCompletion-based work can optionally be tied to a client, so a job that was never a formal service — chasing a document, returning a call, a one-off favour — still shows against the client it concerns rather than floating loose in somebody's head.
• Only that office's own people can be given itStaff selection is limited to users whose primary branch is the one chosen, so an office's internal jobs stay inside that office. Without branches enabled it simply works across the whole firm.

What you can do here

• Circulate a notice that clears itselfA legal update, Sunday working, an office announcement — to everyone or to chosen staff, with an expiry date after which it disappears on its own. Nobody has to remember to take it down, which is why the notice board still means something in month three.

Actions you can take from this screen

• Reply on it, but you cannot delete itThe person a job was given to can read it and post comments back, and that is all. Editing and deleting stay with whoever raised it, so an awkward item cannot be closed by the one person with a reason to make it disappear.

Actions you can take from this screen

• Leave Marked AutomaticallyThe dashboard syncs with the auto leave marking in geo-location attendance: where a rule says an absence or a short day becomes a half day, the system applies it and tells the person so. Those “rules defined half day leave marked by the system” notifications are this, arriving daily. Leave records that maintain themselves are the only kind that stay accurate.
• Any office, any financial yearRead one branch on its own or the single office as a whole, for any year.
• Find one person in the tableSearch by name rather than scroll fifty staff.

Actions you can take from this screen

• Approve or reject, but only for your own peopleOnly the approving user assigned to that person can act on their request. Leave cannot be signed off by whoever happens to be looking at the screen, and the applicant is notified either way — the two-way notification means an answer reaches them without anybody remembering to send it.
• Apply for leave from the same screen that shows the balanceThe request is made where the remaining days are displayed, so nobody applies for a week they have not got without seeing it first.
• Export your own leave recordOut to a file — useful at appraisal, and the sort of thing staff are otherwise told to take on trust.

Actions you can take from this screen

• The staff member is told whenever their balance changesEvery one of these adjustments notifies the person it was made to. A leave balance cannot be quietly altered — which is what makes the rest of this screen usable rather than something staff have to be protected from.
• Mark leave for somebodyChoose the person, the leave type and the dates, flag it as a half day if it is one, and say why. The description is required, so an entry never lands on a record without a reason attached.
• Grant compensatory leaveDays back for work done outside normal hours, added deliberately and against a named person — the (C) term on the leave balance, given a screen of its own rather than buried in an adjustment.
• Correct an opening balanceThe figure a person carried into the year. Firms migrating from a spreadsheet need this on day one, and it is the one number nothing else can derive.
• Adjust a balance, with the adjustment kept visibleThe (E) term in the leave formula. An adjustment is carried as its own column on every leave report rather than folded into the total, so a correction stays legible long after whoever made it has forgotten.
• Remove an approved leave recordFor the ones that were approved in error. It goes to the deleted log rather than vanishing.
• Only live branches and live people can be touchedSelection lists show enabled branches and enabled users only, so an adjustment cannot be applied to an office or a person outside the current operational scope.

What you can do here

• Attendance is marked from the phone, at the officeStaff punch in and out on the MyTask mobile app, and the app checks where they are. No register, no biometric device to buy and maintain, and no machine at the door that only works in one office.
• Inside the geofence it just works; outside, it goes for approvalA punch within two hundred metres of a saved location is clean. Outside it, under manual approval, the punch is not refused — it is sent to an administrator with the location it was made from. Somebody genuinely at a client site is never locked out; their day simply needs a human to agree to it.
• Two approval modes: approve every punch, or let them clearManual or auto. Under manual, punches wait for an administrator and anything marked outside a saved location is escalated with its location attached. Under auto they clear immediately — and MyTask still records where each one was made. A firm switching approval off gives up the queue, not the evidence.
• Two ways to enforce attendance, and the firm choosesContinuous compliance or a backdating window. One says every applicable day must be accounted for; the other says you may only mark attendance a few days late. A practice with articled assistants in and out of exam leave does not want the same rule as one with a fixed office team.
• Continuous compliance: every working day has to be accounted forAttendance is expected for all applicable days from the effective date — with approved leave, non-working days and blocked dates taken out automatically. Mark a previous date late and it is recorded as a late entry, shown in the attendance reports and emailed to the administrators as a variance.
• Or a backdating window: three days late, and no laterSet how many days back attendance may be marked — zero to ten. At three days, today minus three is the limit and nothing older can be entered. A firm that would rather bound the gap than chase every one gets a rule instead of an exception report.
• Holidays and blocked dates come out of the calculationPublic holidays and any other blocked dates are excluded, so nobody is chased for attendance on a day the office was shut — the same courtesy the timesheet extends with its own blocked dates.
• Office timings and holidays, per branchEach office sets its own hours and its own holiday list, which is what makes the in-and-out reports comparable between branches that do not keep the same week.
• Attendance settings per person, not just per officeForty-five staff, each with their own applicability — so somebody permanently at a client site is not held to the same rule as the office team.
• Lock MyTask until attendance is markedWhere the setting permits it, a user cannot get into MyTask at all until they have marked attendance. That is what makes the rest of this work: attendance stops being a form somebody remembers on Friday and becomes the door. And because a punch only counts within two hundred metres of a saved location, the person opening the software is demonstrably at the office.
• One device cannot punch for two peopleThe same handset cannot mark attendance for two logins. That closes the oldest gap in attendance systems — one person arriving and marking the register for a colleague who has not.
• A time that does not match the clock emails the partnersWhere the time entered differs from the time the punch was actually made, MyTask emails the saved administrators with the variance. Nobody has to audit attendance; the exceptions come to them, on the day, with the difference stated.

What you can do here

• Five saved locations — your offices, or your clients’A firm saves up to five places where a punch clears on its own: head office, a branch, a client’s premises somebody is stationed at. Each carries its own two-hundred-metre radius, so staff moving between them are present at any of the five rather than absent the moment they leave the main office.
• And the five is not a limit on where people can workLeave a member of staff with no set location and put them on manual approval, and they can mark attendance from anywhere — every punch arrives for a decision with the place it was made attached. The five saved locations are the places that clear AUTOMATICALLY; beyond them the count is unlimited and simply approved case by case. An audit team on the road is not a problem to be configured around.

What you can do here

• A missed punch becomes leave by itselfThree cases, each configured separately: neither in nor out marked, in-time missing, out-time missing. For each, the firm chooses full day leave, half day leave, or nothing — applied automatically once the backdating window closes, with the person notified. This is where those “rules defined half day leave marked by the system” entries in the notification feed come from.
• Hours actually present decide the daySet a minimum: stay that long and the day counts as half present, otherwise full day leave. Or set it so the day counts as full present, otherwise full day leave. Presence is measured from the gap between in-time and out-time, in hours and minutes, rather than from having turned up at all.
• Compensatory leave granted automatically for long daysStay beyond the set hours on a working day and the system grants half a day or a full day of compensatory leave without anyone asking for it. The (C) column on the leave dashboard fills itself.
• And a different rule for Sundays and holidaysWorking days, non-working days, holidays and blocked dates each carry their own compensatory rule. Coming in on a public holiday is not the same as staying late on a Tuesday, and the firm sets what each is worth.
• Decide how much clock drift is worth an emailSet the tolerance in minutes between the time a person entered and the real system time, separately for in-time and out-time, then choose what happens: tell nobody, tell the user, or tell the administrators and the user.
• Choose what happens when two people share a phoneEither refuse the second punch and keep only the first, or allow every user ID to mark from that device. A firm with a shared handset on a client site may want the second; most want the first.

Actions you can take from this screen

• View staff-wise or date-wiseStaff-wise answers “how was this person's month”; day-wise answers “who was in on the 14th”. Same data, and firms need both — one for review, one for the question somebody asks in a meeting.
• Summary and detailed viewA summary table of every status per person, with a detailed breakdown behind it, so a figure that looks wrong can be opened rather than queried.
• Save the group of people you always look atSaved user selections, so a partner reviewing the same eleven staff every month does not rebuild the list each time.
• Export to ExcelThe month out to a spreadsheet — which is how it reaches payroll, whatever payroll happens to run on.

What you can do here

• A day nobody marked becomes leave, by the rule you setWhere attendance is missing past the backdating window, the leave is marked automatically — full day or half day, whichever the firm's rule says — and the person is notified. The leave ledger keeps itself current without anyone reconciling a register against a calendar.
• And a day already booked as leave is never chasedApproved leave suppresses the attendance requirement for that day entirely: no nag, no missing-record entry, no variance email. The two modules agree about the day rather than arguing about it — which is the difference between an attendance system people tolerate and one they turn off.
• One answer, wherever you ask the questionBecause both modules read the same record, a day of approved leave reads the same everywhere — “Leave Approved” on the timesheet report, “not required to mark” on the attendance report, a day counted on the leave balance. Nobody has to work out which screen is telling the truth.

What you can do here

• Leave: applied, approved, rejected — all three notifiedApplying tells the approver; approving or rejecting tells the applicant. Nobody chases an answer and nobody discovers a refusal by noticing their balance did not move.
• Attendance approvals and rejections, the same wayWhere attendance is approved by hand, the decision reaches the person who marked it — approved or refused. An attendance record that was quietly rejected is a payroll argument three weeks later.
• A punch from outside the office arrives with its locationMarking attendance away from a saved location, under manual approval, raises it for a decision and carries where it was made. The administrator approves or refuses on the evidence rather than on a conversation, and the staff member is told either way.

What you can do here

• Watch the work instead of ringing about itThe client sees the same milestones the firm ticks off — balance sheet checked, computation prepared, return filed. The call that begins “any update?” stops being made, and client management stops costing the firm an hour a day of answering it.

What you can do here

• Send papers in, straight onto the jobDocuments uploaded from the client login attach to the task they belong to. Compare that with the inward register’s own leak report — papers received with no job raised against them — and this is the same problem solved from the other end.

What you can do here

• Fetch their own ITR copies and audit reportsAt eleven at night, when a bank asks for last year’s return, without the firm being the bottleneck.

What you can do here

• See their own bills and what is outstandingInvoices, debit notes, credit notes and the open balance — the account statement read from the client side, so a fee conversation starts from the same figures at both ends.

What you can do here

• Read the circulars the firm sendsAdvice issued to every client sits on the record in their own portal rather than in a forwarded message nobody can find later.

What you can do here

• Book an appointment without a call to arrange the callThe client picks a time, it lands in the firm’s own schedule register with everything else, and both sides are notified.

What you can do here

• Look up their own digital signatureValidity, password, and whether the token is with the firm — the question a client otherwise rings about on the morning of a filing.

What you can do here

• And their own portal loginsGST, income tax and the rest, in one place the client can reach. Every practice fields these requests and none of them should be answering with a message.

What you can do here

• See what their job is actually waiting onA challan, a document, a signature — named, and named as theirs. Most work that looks late is work waiting on the client, and a portal that says so ends the argument before it starts.

Actions you can take from this screen

• Look it up by client or by GSTINSearch by client name, file number or GST number, for any financial year back to 2004-05.
• Read it branch by branchWhere the firm runs multiple offices, the status report answers for one branch or across them.

What you can do here

• A GST task will not close until GSTN says the return was filedTurn this on and a job can only be completed once MyTask has verified with the government portal that the return for that financial year and that month has actually been filed. Not marked done — filed. The gap between those two is where a practice discovers in December that a client's August 3B never went.

What you can do here

• Fill a new client's details from the portalCreate a client and pull what GSTN already holds rather than retyping it — fewer keystrokes, and no transcription error in the number every future filing depends on.

Actions you can take from this screen

• Any assessment year, any branchSwitch the whole dashboard to another assessment year, or read one office at a time.
• Read straight from the Income Tax portalThe dashboard carries the time it last read the portal. Nobody logs into the income tax site client by client; MyTask does it and stamps when.
• Click any number to see the clientsEvery count is a list. Thirty-two refunds pending is a name-by-name list of who to chase, not a number to admire.

What you can do here

• Save a PAN and a password once, and stop logging inThat is the whole setup. From then on MyTask reads that client's income tax portal account itself, so nobody signs into three thousand accounts to find out what happened.
• Nothing to schedule — it checks on its ownThere is no job to run and no interval to configure. A scheduler on MyTask’s side signs into each saved PAN in turn and re-reads its status, continuously, in the background. The firm sets nothing up beyond the credentials.
• The email is triggered by the problem, not by the calendarNothing arrives on a weekly digest that nobody opens. When a re-check finds a client has moved into a problem state, that is what sends the email — so every alert in the inbox is a thing that has actually gone wrong, and an empty inbox genuinely means nothing has.
• Three levels, so a problem is not confused with a resultThe dashboard grades every state: red for the ones that need action, amber for a departmental adjustment waiting on a reply — a 143(1)(a) notice, prepaid taxes that failed to match — and green for a refund on its way. A pending refund is not a problem, and colouring it like one would train people to ignore the colours.

What you can do here

• An income tax job will not close until the portal says it was filedTurn it on and a task can only be completed once MyTask has confirmed with the income tax portal that the return for that client and assessment year is actually on record. Not marked done — filed. The gap between those two is where a practice discovers in December that a return it billed for never went.
• Gate the filing stage, and leave the rest aloneThe check is set on the milestone, not on the whole service, so computation and review still close the way they always did and only the stage that claims the return was filed has to prove it.

What you can do here

• Every filed-but-unverified return stays watchedThe scheduler keeps checking the returns that are lodged and still waiting on verification, electronic or physical, until they are verified or the window closes. Nobody has to keep a list.
• Under seven days left, and it emails youWhen a return drops inside a week of its verification deadline, the alert goes out naming the client. It is the one deadline where missing it undoes the work entirely rather than merely delaying it.
• Which is what keeps a filed return from turning invalidAn unverified return lapses and the client counts as never having filed. Catching it at seven days is the difference between a reminder call and a year of work to redo — and the department will not be the one to tell you.

What you can do here

• Due dates chase themselvesA message goes to the client before the deadline rather than after it. The firm sets it up once and every client with that service is reminded on time, every cycle — which is the difference between a practice that chases and one that is chased.
• Built from the work, not from a listReminders are raised against the tasks that carry the due date, so the recipients are whoever actually has that filing outstanding — not a list somebody maintains by hand and forgets to update.

What you can do here

• Messages to many clients, built the same way as emailThe same six ways of choosing which of the firm's own clients receive it: from the client list, from the clients' phone book, from a saved list, by task type, from client details imported from an Excel sheet, or typed in. A firm that has learned to choose recipients for an email already knows how to choose them for a message.
• Write once, send to everyone it applies toOne message, a saved recipient list and a send — for the announcements that do not warrant an email and would otherwise be typed out one client at a time.

What you can do here

• Task raised, task finished, invoice issued, estimate sent — the client is told each timeA client hears from the firm when a job is raised, when it is finished, when an invoice goes out and when an estimate is issued — without anybody writing a message. Most practices tell clients none of this, and then field the phone call asking.
• Each event sends from the number you chooseThe sending number is set per event, so job updates can come from the office line and dues reminders from somewhere else — or from the partner who actually chases them.
• Build a batch by hand, or let MyTask build itManual batches are precise and slow; auto-generated batches are quick and want reading before they are saved. The app says so itself rather than pretending the fast route is free, which is the right way round — 239 enabled batches in the demo firm would have been a month of typing.
• Clients, numbers and groups on one batchA batch carries its own clients, contact numbers and groups, previewed before the events are attached to it.

What you can do here

• Chase dues on your own intervalSet how many days apart the reminders go. A client is reminded steadily rather than on the day somebody happens to look at the ledger.
• And stop chasing below an amount you setReminders switch off once the outstanding falls under a threshold. Nobody wants the firm pursuing a client for fifty rupees, and a chaser that cannot be told when to stop is a chaser that gets switched off entirely.
• Dues reminders can go by SMS as wellThe one place a second channel is offered, because a payment reminder has to reach somebody who may not read anything else.

What you can do here

• Built into the reports where chasing actually happensOn a service dashboard, on the GST return status report, on the income tax portal screen — the reports a firm opens when it needs to push clients along carry the chase on the list itself, so the people to write to are the ones already in front of you.
• Select forty clients stuck on the same thing, and chase them at onceWork that has not started, work still pending, or work held up by a particular issue — pick the clients off the list and message all of them in one action instead of writing to each in turn.
• Each one still reads as though it were written for themClient name, service, financial year, period and task description are filled in per recipient, so a reminder sent to many clients does not read like a circular.
• The contact details come from the clients themselvesNo list to assemble and no addresses to look up — the recipients are whoever is on the report you are already looking at.
• Send it as a message or as an emailThe same selection works either way, so a firm can reach the clients who read email by email and the rest by message.

What you can do here

• Messages sync on your phoneEverything sent from MyTask shows up on the phone too, so the conversation carries on where the client already is — and a reply is not sitting somewhere nobody thinks to look.