1. Tax Collection System
  2. Features
  3. Taxpayer Demands
Feature · Taxpayer Demands

Taxpayer Demands

Prepare demand, refund and adjustment documents for each taxpayer with line-level net and tax amounts.

OverviewPosted Demands
Tax Collection System · Taxpayer Demands

Posted Demands

Accounting documents

New
Record numberCounterpartyDocument typeGross amount USDPosting datePosted at
AD-28289BP-6129Invoice37012 Oct15 Oct
AD-48879BP-8073Credit93010 Oct15 Oct
AD-38798BP-6981Expense28010 Oct13 Oct
AD-26160BP-5316Adjustment42001 Oct05 Oct
AD-90543BP-5746Invoice47008 Oct10 Oct
6 of 6 records
BP-6129Accounting documents · AD-28289
Invoice
Gross amount USD370
Posting date12 Oct
Posted at15 Oct
Example screen with sample data

What you can do

Every amount owed starts as a document

A demand is an accounting document raised against a taxpayer. It carries a record number, subject, document date, document type, gross amount, the officer who owns it and its version. Invoices are demands, credits are refunds and abatements, and adjustments correct earlier figures. Each document has lines with a description, quantity, unit price, tax, net amount and the ledger account the line posts to.

Taxpayers are kept in one register with a code, contact, address, eligibility note and active flag, under the tax office that administers them. The officer picks the taxpayer and eligible ledger accounts, and the document’s net and gross are worked out from its lines.

How the work is organized

  • Draft, review, approve, post. A document is Draft while prepared, in Review once submitted, then Approved or Rejected, Posted to the ledger and, if corrected, Reversed.
  • Versions on every submission. Submitting raises the version and freezes it for the reviewer.
  • Lines carry the accounting. Each line names its ledger account, so posting knows where every amount goes.

What to agree during setup

Agree the demand types you raise and which ledger accounts each line type uses. Load the taxpayer register with stable codes. Decide how refunds and abatements are documented and who may prepare adjustments. Agree the evidence each demand needs before review.

Check the handoff on an actual case

A restaurant’s annual trade license is due. The Assessment Officer prepares an invoice for the restaurant with one line: license fee of $1,500 net to the license fee revenue account and a $150 levy as tax. The gross is $1,650. She attaches the inspection report and submits the document for review.

The Assessment Reviewer approves it. The officer posts it into the open period, and the restaurant’s demand appears on the posted list for collection. When the restaurant later downsizes mid-year and qualifies for a partial abatement, the officer raises a credit document for the abatement, which passes the same review and posting.

What your team sees

  • Draft Documents — Documents being prepared, with taxpayer, type, date and gross amount.
  • My Documents — The documents the signed-in officer owns.
  • Document Board — Every document grouped by status.

The Operations Overview page shows posted document value, the net ledger balance, pending reviews, failed operations and unposted documents by type.

Follow the work through

Review the implementation plan and the data model before importing open demands.

What it keeps track of

Data model
Accounting documents
Assessed accounting documents carrying lifecycle, counterparty and gross amount.
Document lines
Line detail for an accounting document with quantity, price, tax and net amounts.
Business partners
Taxpayers and counterparties assessed and collected against.
Ledger accounts
Chart of accounts used by journal lines.

Who uses it

Permissions
Assessment Officer
, Assessment Reviewer, Admin.
The Assessment Officer prepares documents.
The Assessment Reviewer decides them.
Admin
Keeps the taxpayer register 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