For CPA Firms

Inquiry channels — Client Tasks (external) vs Review Points (internal)

Local Check does not have a separate "clarifications" feature; instead it splits inquiries into two purpose-built channels — Client Tasks (anything the client must answer) and Review Points (internal CPA workpaper notes).

7 min readUpdated 19 April 2026

Naming note

Many engagement teams use "clarification" loosely to mean any question raised during fieldwork. Inside Local Check, that intent is served by either a Client Task (when you need something from the client) or a Review Point (when the conversation is between CPA team members).

When to use each channel#

AspectClient TaskReview Point
AudienceExternal — assigned to a Client UserInternal — between CPA team members
Visible to the client?Yes — appears in the Client PortalNo — confined to the CPA workpaper
Typical useProvide data, upload evidence, sign / review a document, answer a questionReviewer-to-preparer notes, points to revisit, items to escalate to partner
Lifecyclepending → in_progress → submitted → approved / rejected (rework) / cancelledprepared → updated → reviewed → resolved
Real button label (CPA UI)Request from Client (also: Request Evidence)New review point (within the inspector panel)

Where you can raise a Client Task#

The platform exposes the Request from Client action on every section that drives the LCGPA model: Income lines, Labor (employee rows), Goods & Services (supplier rows), Capital Expenditure (asset rows), Depreciation, Capacity Building (Training, Providers, R&D), and AUP procedures. Opening the modal pre-fills the title bilingually based on context (e.g. Provide Invoice — [supplier name]).

Task type drives the form#

When you open the Request from Client modal you pick a task type — provide_file, add_employees, add_suppliers, update_company_data, review_document, sign_document, provide_information, answer_query, or other. The chosen type controls which fields appear, what file labels the client may attach (e.g. Employee ID, Bank Statement, GOSI Certificate, Highest Invoice, Random Invoice), and how the response is later verified by the auditor.

Modal fields (Request from Client)#

  • Assign to Client — required dropdown of the engagement's client users.
  • Title — Arabic & English — both required. Pre-filled when launched from a row.
  • Description — Arabic & English — optional clarifying note.
  • Template file — optional attachment for review_document / sign_document / template-based requests.
  • Priority — low | medium | high | urgent.
  • Due date — optional; drives the reminder schedule.
  • Submit button label: Create Task.

Status lifecycle (Client Task)#

StatusMeaningWho acts next
pendingCreated and assigned, not yet opened by the client.Client.
in_progressClient opened it; may upload, edit, or add notes.Client.
submittedClient uploaded the files / data and submitted.CPA — verify or reject.
approvedAuditor verified the evidence (per verify-evidence API).—
rejectedReturned to the client with reviewer notes; the client may resubmit.Client.
cancelledTerminal status — the task is no longer required.—

Review Point (internal channel)#

Review Points live entirely inside the CPA workpaper. They are scoped to a section of the report (Labor, Suppliers, AUP procedure, etc.) and carry comment threads, attachments, and a four-stage workflow recorded as prepared → updated → reviewed → resolved. Each stage stores who marked it and when, providing a clean review trail for the manager and partner.

  • Open the inspector panel on the relevant row → New review point.
  • Severity is implicit in the workflow stages; review points are not surfaced to the client.
  • All open review points must be resolved before partner sign-off.

Decision rule

If the answer must come from the client (a file, a number, a confirmation, a signature) → use Request from Client. If the conversation is between CPA staff (a reviewer note, a partner comment, an item to revisit) → use a Review Point.