Jobs & Workflows

Workflow Software for Accounting Firms Every engagement runs the same way, every time.

Build engagements from reusable workflow templates. Stages advance only when every mandatory task is complete, so nothing ships half-finished and no review step gets skipped under deadline.

Book a DemoSee Pricing

How an engagement actually runs

A job is not a to-do item with a due date. It is an instance of a process your firm defined, and the platform holds it to that process.

  1. Stage 01

    Template

    Your firm defines the workflow once — its stages, the tasks in each, which are mandatory, which role each is assigned to, and what job status a stage maps to.

  2. Stage 02

    Instantiate

    Creating a job for a client builds every stage and task from that template and generates a unique job code in the form entity-jobtype-yearmonth-sequence.

  3. Stage 03

    Assign

    Jobs and individual tasks are assigned to partners, managers and accountants, and each assignee is notified. Tasks can also be assigned to the client.

  4. Stage 04

    Gate

    The stage advances only when every mandatory task in it is complete. Optional tasks are guidance and never block progress.

  5. Stage 05

    Wait on client

    Assigning a task to the client moves the job to Waiting on Client automatically. It returns to In Progress the moment no client tasks remain.

  6. Stage 06

    Complete

    A completed job locks against changes. Only a Manager or Administrator can reopen it, and the reopening is written to the audit log.

What you can build into a workflow

Workflow templates are entirely yours to define — the platform ships the mechanism, not an opinion about how a corporate return should be prepared.

Stages and tasks

Any number of stages, each with its own task list, ordered the way your firm actually works.

Mandatory flags

Mark the tasks that must be complete before the stage can advance. Everything else stays advisory.

Assignee roles

Each task carries the role responsible for it, so assignment is a property of the process rather than a habit.

Role-restricted completion

Lock a task so only a specific job role or an administrator can tick it off — review steps stay real.

Status mapping

Map each stage to a job status, so the pipeline view reflects where work genuinely is.

Client tasks

Tasks assigned to the client surface in their portal and move the job to Waiting on Client.

Recurrence

Monthly, quarterly or annual recurrence raises the next instance from the same template.

Dependencies

A job can be blocked until a prerequisite job is complete — self-reference and simple cycles are rejected.

Cancellation with cause

Cancelling requires a reason. A job that never started is removed; anything further along is retained for the record.

The rules the platform will not let you break

These are enforced by the application rather than written in a procedures document nobody opens.

  • A stage cannot advance while any mandatory task in it is incomplete.

  • A completed job is locked against changes; only a Manager or Administrator can reopen it.

  • A job that depends on another cannot start until the prerequisite job is complete.

  • A job cannot depend on itself, and simple circular dependencies are rejected at creation.

  • Cancelling a job requires a reason. A job that has not started is removed entirely; any other job is retained for history.

  • A task restricted to a job role can only be completed by that role or an administrator.

  • A recurring job must specify a frequency and a next date no earlier than tomorrow.

Frequently Asked Questions

Frequently asked questions

What stops a job from skipping a review step?

The stage gate. A job cannot advance to the next stage until every mandatory task in the current stage is complete. Optional tasks never block, so you decide at template level which steps are genuinely required and which are guidance.

Can a task be reserved for a specific role?

Yes. A task can be restricted so that only a specific job role — or an administrator — is able to complete it. A junior cannot tick off the partner review.

How do recurring engagements work?

A recurring job carries a frequency of monthly, quarterly or annually and a next date that must be tomorrow or later. The platform raises the next instance from the same workflow template, so the process does not drift between periods.

What happens when a job is complete?

It locks against further changes. If something genuinely needs revisiting, a Manager or Administrator can reopen it — nobody else — and the reopening is recorded.

Can one engagement depend on another?

Yes. A job that depends on another cannot start until the prerequisite is complete. A job cannot depend on itself, and simple circular dependencies are rejected rather than silently accepted.

Can we set jobs up in bulk at the start of a season?

Yes. Bulk creation runs across up to 500 clients at a time, bulk reassignment across up to 500 jobs, and bulk recurrence changes across up to 100 jobs — all processed in the background so the workspace stays usable.

Explore the platform

See Praxio on your own engagements.

Book a walkthrough and we'll configure it around the way your firm actually works — your engagement types, your review steps, your billing model.

Book a DemoSee Pricing