1. Tax Collection System
  2. Features
  3. Review Queue
Feature · Review Queue

Review Queue

Record an independent reviewer's decision on the exact version of each document and assessment.

OverviewDocuments in Review
Tax Collection System · Review Queue

Documents in Review

Accounting documents

New
Record numberSubjectCounterpartyDocument typeGross amount USDRevision
AD-70430Review ad-277BP-2507Invoice140800
AD-32531Review ad-669BP-1755Credit79030
AD-59604Review ad-546BP-6626Expense430860
AD-79159Review ad-745BP-4573Adjustment850580
AD-43999Review ad-369BP-4584Invoice470720
6 of 6 records
Review ad-277Accounting documents · AD-70430
Invoice
CounterpartyBP-2507
Gross amount USD140
Revision800
Example screen with sample data

What you can do

Decide the version that was submitted

No demand reaches the ledger on one person’s word. A review decision records the outcome (Approve, Reject or Return), the reason, the reviewer, the time and the version it applies to. The reviewer is a different team member from the officer, in the same tax office.

If a document changes after submission, the earlier decision no longer applies and the new version waits for its own review. The same queue handles demands, refunds, adjustments, assessments and compensating corrections to posted documents.

How the work is organized

  • Approve. The document moves to Approved and can be posted; an assessment moves to Approved and Completed.
  • Return. The work goes back to the officer with a reason for a revised version.
  • Reject. The work stops, with the reason recorded.

What to agree during setup

Name reviewers and deputies and confirm nobody reviews their own work. Agree review limits by document type and amount. Agree what a reviewer checks: taxpayer, lines, accounts, tax amounts and evidence. Decide the turnaround for reviews before demand due dates.

Check the handoff on an actual case

An officer submits a refund of $900 to a shop that overpaid last year. The Assessment Reviewer opens Documents in Review and sees no evidence of the overpayment attached. She returns it with that reason. The officer attaches the receipt history showing the double payment and resubmits.

The reviewer approves the new version, and the decision records the version, reason and time. When a colleague later asks why the refund took two days, the decision log shows the return and its reason.

During the pilot, have each reviewer return at least one document and approve its revised version. Check that the earlier decision stays on record, that a decision on the old version is refused, and that an officer cannot open their own document in the review queue.

What your team sees

  • Documents in Review — Submitted documents with taxpayer, type, gross amount and version.
  • My Review Decisions — The decisions the signed-in reviewer recorded.
  • Review Decisions Log — Every decision with reason, reviewer and version.

Follow the work through

Rehearse access with an officer account before go-live.

What it keeps track of

Data model
Review decisions
Independent reviewer decisions recorded against a document revision.
Accounting documents
Assessed accounting documents carrying lifecycle, counterparty and gross amount.
Tax assessments
Authority tax assessments reconciled against supporting evidence.
Team members
Staff membership linking an authenticated platform user to an organization and role.

Who uses it

Permissions
Assessment Reviewer
, Assessment Officer, Admin.
The reviewer decides.
The officer prepares and resubmits.
Admin
Keeps team members and their office current.

Set up Tax Collection System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started