Skip to main content
CoCounsel
Search
Search Indirect Tax Help and Support.

This article applies to:

  • Product: ONESOURCE Indirect Tax,ONESOURCE Sales and Use Tax Compliance

Tasks

This topic explains the Tasks view in the OSU CoCounsel Protocol Dashboard, covering the 3 task status categories: Actions Required, Ready to Process, and Completed.

Task categories and process steps

The
Tasks
 view is the default tab when customers open a protocol run. On the left-hand panel, tasks are grouped under the main process steps:
  • Import datasets
  • Review journal
  • Prepare tax binders
  • Review ledger
  • Prepare tax returns
  • Review and file returns
Within these steps, tasks represent either:
  • Action required
     – tasks that require customer review and/or approval
  • Routine automations
     – tasks that may still be reviewed for assurance (for example, reviewing import details, journals, ledgers, computes, or transfers.)
Tasks are broadly categorized into 3 status buckets:
  1. Actions required
     – tasks needing customer review and/or approval
  2. Ready to Process
     – tasks where customer review is complete, but compute and transfer is still required to update tax returns
  3. Completed
     – tasks fully processed, including all agentic actions and customer-driven updates

Actions required tasks

Review and approve or override OSU CoCounsel decisions. Key capabilities:
  • Approve tasks individually or in bulk
  • Open each task for details:
    • What the agent did
    • Why it took that action (clear explanation of the reasoning)
    • Recommendations
How OSU CoCounsel learns
OSU CoCounsel bases its actions on historical reporting patterns:
  • In Period 1 (no usable history), the default behavior is conservative:
    • The agent will suspend all unreported taxes and tax credits
    • Customers then review and decide whether to:
      • Report them now
      • Reclassify them
      • Continue to suspend for a future period
As history is built, OSU CoCounsel uses prior decisions to make more confident reclassifications and recommendations.
Overriding agent decisions
If customers disagree with an AI-proposed action, they can override it directly at the task level.
Example 1 – Unreported tax reclassification
  • The agent detects unreported tax for Calera and, based on prior periods, reclasses it to Birmingham.
  • During review, customers can instead select to:
    • Register Calera
       as a filing jurisdiction and begin reporting in Calera
    • Suspend Calera records
       in the current period, deferring reporting to a future period
    • Edit reclass
       to a different authority instead of the 1 the agent reclassed
Example 2 – New or missing entity or location
  • OSU CoCounsel identifies a potential new entity/location while processing the data.
  • It auto-adds the entity/location in OSU using smart rules.
  • On review, if customers determine it should map to an existing entity, they can:
    • Override the agent's action and map the transactions to an existing entity/location.
Example 3 – Tax Credit Resolution
  • The agent detects tax credits and automatically suspends or reclassifies (based on historical patterns) them.
  • During review, customers can select to:
    • Reclass
       the tax credits to a different tax authority or tax area and apply those credits toward tax amounts due there
    • Undo
       the agent's action and report the credits in the same reporting period
    • Edit reclass
       by assigning the credits to a different tax authority or tax area than the 1 selected by the agent
These overrides become part of the learning history for future periods.
Status transitions from Actions Required
When customers complete a review:
  • If customers approve the task as-is, it moves to
    Completed
    .
  • If customers override the agent's action, the task requires reprocessing and therefore moves to the
    Ready to process
     state.
Examples:
  • If customers override a suspension decision by reclassifying transactions to a different tax authority, the task goes directly to
    Ready to process
    .
  • If customers override a new entity or location by mapping to an existing entity, they'll need to update the task to
    Mark as ready to process
    . After updating, the task appears in the
    Ready to process
     tab.

Ready to process

Tasks that are reviewed and overridden by customers will remain in the
Ready to Process
 state so they can be recomputed and retransferred. This view lists all tasks that:
  • Have been reviewed and overridden
  • Still require recompute and retransfer to push updated data into the ledger tables and impacted tax returns
Key details:
  • Tasks are grouped by entity for efficient processing.
  • Customers can process the tasks for multiple entities simultaneously.
  • Processing can only be initiated for entities that have at least 1 task with status
    Ready to process
    .
Process behavior:
  • When customers initiate a task for an entity:
    • Task status changes from
      Ready to process
       to
      Processing
      .
  • If a task is already in
    Processing
     state for an entity:
    • The system prevents processing other tasks for the same entity while a task is already in progress.
Once the system finishes a processing job, all corresponding tasks move to
Completed
 state.

Completed

The
Completed
 view provides a full audit trail of AI actions and human review. This view lists all tasks that:
  • Have been reviewed by customers
  • Have had all the required recompute/transfer steps successfully completed
For each completed task, customers can refer to:
  • The original agent action
  • The final customer decision (approve vs override)
  • The activity log, including:
    • Who made each change
    • Timestamps for approvals, overrides, recomputes, and transfers
Example:
  • The agent detects unreported tax for Caldwell County and suspends the associated records.
  • Customers later decide to:
    • Register Caldwell County as a filing authority, and
    • Report the taxes to that authority.
The activity log captures:
  • OSU CoCounsel's initial suspension decision
  • Customers' decision to register and report
  • The customer ID and timestamp for each action

Routine automation tasks

The
Routine Automation Tasks
 view provides a consolidated list of routine, automated tasks for each protocol process step from
Import Data
 through
Review & File Returns
. These items are non-critical and don't require customer approval to proceed. However, customers may select to review them before advancing to subsequent steps.
note
Examples include Review import details, Review journals, Review ledgers, Review compute details, and Review prepayment details.
Selecting a hyperlink for any routine automated task will bring customers to the corresponding OSU screen, where they can review the underlying details as needed. For example:
  • If a customer selects
    Review Import Details
    , they'll be taken to the Work Area–level Import Dashboard.
  • If a customer selects
    Review Journals
     or
    Review Ledgers
    , they'll first be prompted to select an entity. Based on the selected entity, the system will open the binder.