1. Tax Collection System
  2. Features
  3. Tax Assessments
Feature · Tax Assessments

Tax Assessments

Record each authority assessment against its demand and approve it only against the attached evidence.

OverviewAssessments Awaiting Approval
Tax Collection System · Tax Assessments

Assessments Awaiting Approval

Approval conditions

New
ParentJurisdictionAssessment dateAssessed USDAuthority referenceRevision
AD-19382JRS-99014 Oct720AR-284720
AD-18828JRS-49826 Oct80AR-543540
AD-77914JRS-23612 Oct150AR-875580
AD-50234JRS-91606 Oct130AR-530630
AD-47450JRS-54426 Oct130AR-97290
6 of 6 records
JRS-990Tax assessments · TA-47418
ParentAD-19382
Assessment date14 Oct
Assessed USD720
Authority referenceAR-284
Revision720
Example screen with sample data

What you can do

Tie the authority's figures to the demand

An assessment records what the authority assessed: the jurisdiction, the assessment date, the assessed amount and the authority reference, such as an order or notice number. It belongs to the demand document it supports and to the tax office.

The Assessment Officer submits the assessment. Its submitted version is frozen, and the jurisdiction, date, amount and reference are checked against the evidence attached to the same document. An Assessment Reviewer independent of the officer records the decision. Only then is the assessment Approved and Completed. A rejected assessment stays on record with the reason.

How the work is organized

  • Evidence on the demand. The assessment order, notices and calculations are attached to the demand document.
  • Independent approval. The reviewer is never the officer who submitted the assessment.
  • Assessments by jurisdiction. Jurisdiction lets the office report assessed amounts by ward, district or zone.

What to agree during setup

Agree how jurisdictions are written so they group correctly. Decide what evidence an assessment needs: the signed order, a calculation sheet, an inspection report. Agree who may submit assessments and who reviews them, and how a disputed assessment is handled.

Check the handoff on an actual case

The restaurant’s license demand has an authority assessment for Ward 12 dated 3 April for $1,650, with the order number as the authority reference. The officer attaches the signed order to the demand and submits the assessment. The reviewer compares the order with the assessment and the demand and approves it; the decision date is recorded and the assessment is completed.

A second assessment for a bakery shows $2,400 while its signed order says $2,040. The reviewer rejects it with that reason. The officer corrects the amount and submits a new version, which is approved.

During the pilot, compare the assessed totals by jurisdiction with the authority’s own register for the same dates. Any assessment without a signed order attached should be found before it reaches the reviewer.

What your team sees

  • Assessments Awaiting Approval — Submitted assessments with demand, jurisdiction, date, amount, reference and version.
  • Tax Assessment Register — Every assessment by status with amount, reference and decision date.

Follow the work through

Check reviewer access before go-live.

What it keeps track of

Data model
Tax assessments
Authority tax assessments reconciled against supporting evidence.
Accounting documents
Assessed accounting documents carrying lifecycle, counterparty and gross amount.
Record attachments
Evidence files attached to an accounting document.
Review decisions
Independent reviewer decisions recorded against a document revision.

Who uses it

Permissions
Assessment Officer
, Assessment Reviewer, Revenue Accountant.
The officer submits assessments.
The reviewer approves them.
The Revenue Accountant reads assessed totals by jurisdiction.

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