Control test records

Assessment tests gives the team a dated record beneath an assessment. A test row carries a line number, revision, optional provider event reference, tested date, amount, evidence type and a Yes or No verification value. That is enough to distinguish an observed check from a narrative in the assessment subject. It also lets a reviewer ask which check supports a decision without searching an unrelated folder.

Use the evidence type that matches the source material: Statement, Confirmation, Settlement or Correction. A confirmation should not be labeled a settlement merely because it arrived later. Attach the underlying document to the parent assessment, give it a clear title and decide whether its visibility is Internal or Shared. The attachment records upload time and uploader. The tester and owner can then explain why a checked line was marked verified and which document was available at review time.

• Parent context. Every test belongs to an assessment, so its date and amount are read with the assessment’s period and owner.
• Observed check. Evidence type, verification value and provider event reference describe what was checked.
• Supporting file. An attachment retains title, upload identity, visibility and evidence type under the same parent assessment.

Agree what a line number means within an assessment and how revision changes are handled when a test is corrected. Define when the tester uses Verified Yes and who may change that value. A No value belongs in a follow-up queue; it should not disappear simply because the assessment has moved forward. Decide which evidence types correspond to the team’s actual source documents and how files will be named.

The app also has risk-linked Controls with effective date and financial ledger and available amounts. Use those records only for the financial context they actually hold. The team should agree which outside source owns the values and provider snapshot reference. Keep a test’s assessment parent clear even when the same provider event is being discussed elsewhere.

An Assessment Tester receives a statement for the period under review. They open the correct assessment, create a test line with the tested date, choose Statement, enter the relevant amount and provider event reference, and attach the file to the parent record. The Control Owner checks that the file title and visibility are appropriate. A reviewer sees the test line and attachment under the same assessment and can return the review with a reason if the check is still unverified. The owner can then find the exact line needing follow-up.

• Assessment Test Evidence — Find test lines still marked unverified with their parent and evidence type.
• Shared Attachments — Inspect files prepared for wider review under an assessment.

Use assessment preparation to place checks in context. The evidence and reconciliation process shows how reviewers follow an exception.