An audit software vendor's SLA matters less for its headline uptime percentage and more for three specific clauses: whether the support-response-time commitment is stated in hours with a number, not 'promptly,' and whether that number is the same during February-March as the rest of the year; whether the uptime commitment is measured and reported in a way the firm can actually verify rather than self-reported after the fact; and what the vendor's contractual remedy is when the SLA is missed, because an SLA with no stated consequence for a miss is a statement of intent, not a commitment.
Why uptime percentage alone is the wrong headline number
A 99.9% uptime commitment allows for roughly 8-9 hours of downtime a year. If that downtime happens to fall in a quiet month, it costs a firm almost nothing. If it falls during the last week of March, when audit files across the firm are being finalised against a statutory deadline, the same 8-9 hours can be genuinely damaging. The percentage doesn't tell a firm when the downtime happens, only how much of it is allowed — which is why the percentage alone is not the useful number to evaluate.
The support-response clause worth checking
| SLA language | Why it matters or doesn't |
|---|---|
| "We respond promptly to all support requests" | Not a commitment — no number, no consequence for being slow |
| "Initial response within 4 business hours, 9am-6pm Mon-Fri" | A real number, but check whether 'business hours' shrinks the firm's actual coverage during a season when it's working evenings and weekends |
| "Priority support with 1-hour response during March 1-31, including weekends" | A commitment that actually accounts for when the firm needs it most — the specific test of a usable SLA |
| "Best-effort support" | Explicitly no commitment at all — worth noticing when a vendor states this plainly rather than vaguely implying more |
Questions to ask specifically about busy season
- Does the support-response commitment change (for better or worse) during February-March, and is that stated in the contract, not just assumed?
- Does the vendor staff up support during this period, or does the same small team handle a seasonal spike in every client's volume at once?
- What's the vendor's own track record of planned maintenance or deployments during this window — do they freeze changes during peak season, or keep shipping?
- Is there a status page or outage history the firm can check independently, rather than relying on the vendor's own account of past incidents?
What happens when the SLA is missed
- 01Ask what the stated remedy is for a missed SLA — a credit, an extension, something elseAn SLA with no remedy clause is effectively just a description of intent, however precisely worded.
- 02Ask how a miss is verified — does the firm have to prove it, or does the vendor self-report and credit automaticallyA clause that requires the firm to file a formal claim within a tight window to get any remedy is less useful in practice than it looks on paper.
- 03Ask for the vendor's actual incident history for the last 12 months, including datesA vendor confident in its own record will usually share this; reluctance to share it is itself informative.
Common practice, not a requirement
Asking during the trial or RFP stage what the vendor's support load looked like last March specifically — not 'how is your support generally' — tends to get a more honest answer than a general support-quality question, because it forces a specific memory rather than a general impression.
A vendor whose SLA document is silent on seasonal variation in an India-focused audit tool has probably not thought hard about the one period of the year when a firm actually needs the commitment to hold.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- Technology, data & AI in auditAudit software security questionnaire: a buyer's checklistThe questions a firm's own IT or compliance reviewer raises before sign-off, listed so they can be answered before the vendor call, not during it.
- Technology, data & AI in auditRFP questions for an audit automation vendor: a template to sendA document a firm can send to three vendors at once and get back answers that are actually comparable, not three different sales decks.
- Technology, data & AI in auditWhat to ask an audit software vendor's reference clientsA reference call that only asks "are you happy with it" gets a polite yes almost every time. Here's what actually surfaces the real answer.
- Technology, data & AI in auditChoosing an audit automation vendor: a checklistThe questions that separate a vendor worth trusting with client data from one that merely demos well: security, what's computed versus generated, exit terms, pricing, and India-specific fit.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- GSTR-2B reconcilerMatches your purchase register against GSTR-2B — missing invoices either side, amount mismatches.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.