1. Tax Collection System
  2. Features
  3. Activity and Evidence
Feature · Activity and Evidence

Activity and Evidence

Keep evidence files on each document and a receipt of every guarded action and its outcome.

OverviewOperation Exceptions
Tax Collection System · Activity and Evidence

Operation Exceptions

Operation receipts

New
ParentActionOperation keyResult stateOccurred atFailure reason
AD-41540ACT-373OK-413Pending03 OctCut to length
AD-92697ACT-651OK-770Failed09 OctWeld frame
AD-72175ACT-116OK-321Needs review12 OctDrill and tap
AD-98861ACT-821OK-892Pending26 OctDeburr
AD-65286ACT-607OK-955Failed20 OctAssemble
6 of 6 records
ACT-373Operation receipts · OR-48613
Pending
ParentAD-41540
Operation keyOK-413
Occurred at03 Oct
Failure reasonCut to length
Example screen with sample data

What you can do

Keep the proof with the demand

Evidence files, such as assessment orders, inspection reports, taxpayer returns and correspondence, are attached to the document they support. Each file has a title, an evidence type, the uploader, the upload time and a visibility of Internal or Shared.

Every guarded action, such as approving a document, posting a journal, applying a receipt or approving an assessment, leaves an operation receipt with the action, a unique operation key, the version it expected, the outcome, the time, any external reference and the failure reason. Outcomes are Pending, Completed, Failed or needs review. A repeated action with the same key returns the original receipt.

How the work is organized

  • Evidence where the reviewer looks. Files sit on the document, so reviewers and auditors find them together.
  • Receipts for guarded actions. Each receipt shows what was expected and what happened.
  • Exceptions in one list. Pending, Failed and needs review receipts wait for the Revenue Accountant.

What to agree during setup

Agree the evidence types you attach and which may be shared with taxpayers or auditors. Decide who reviews operation exceptions and how quickly. Set the schedule for the routine receipt reconciliation.

Check the handoff on an actual case

An officer posts a batch of demands just as the connection drops. One posting leaves a Pending receipt. When the officer retries, the same operation key returns the existing receipt, and the demand is not posted twice. The routine reconciliation finds the journal and its lines recorded and marks the receipt Completed.

Another receipt, for a cash application the bank later reversed, does not match the recorded effects. It is marked needs review with the discrepancy, and the Revenue Accountant follows up with the Collections Officer.

During the pilot, interrupt one posting and one cash application on purpose. Confirm the retry returns the original receipt, the reconciliation marks each receipt correctly, and every demand under review carries the evidence its reviewer needs.

What your team sees

  • Operation Exceptions — Receipts waiting for review, with action, outcome and failure reason.
  • Active Taxpayers — The taxpayer register with contacts and eligibility notes.

Follow the work through

Map the source records before importing history.

What it keeps track of

Data model
Record attachments
Evidence files attached to an accounting document.
Operation receipts
Idempotent operation receipts recording guarded action outcomes.
Accounting documents
Assessed accounting documents carrying lifecycle, counterparty and gross amount.
Organizations
Tax administration organizations that own assessments, documents and ledger scope.

Who uses it

Permissions
Revenue Accountant
, Assessment Officer, Admin.
Officers attach evidence.
The Revenue Accountant resolves receipts.
Admin
Maintains organizations and the taxpayer register.

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