> For the complete documentation index, see [llms.txt](https://finspectors.gitbook.io/finspectors-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://finspectors.gitbook.io/finspectors-documentation/audit-modules-auditor-view/execution/test-of-details.md). # Test of Details ## **Overview** The Test of Details module helps auditors validate sampled transactions against supporting evidence and predefined testing rules. The process is divided into three stages: 1. Input 2. Source 3. Rules Fins AI Brain then processes the data and generates validation results with direct evidence linkage for auditor review. *** ## **Step-by-Step: Test of Details** *** ## **1. Input** The first step is selecting the transaction data to be tested. Auditors can choose from multiple input methods: #### **Populate from Sampling** Automatically loads transactions selected during the sampling stage. This is commonly used for sampled audit testing. *** #### **New Dataset** Upload a separate dataset for testing using the predefined template. Useful when testing external extracts or additional populations. *** #### **Manual Copy-Paste** Auditors can directly paste tabular data into the testing grid. This is useful for quick validations or smaller datasets. *** ### **Input Configuration** Auditors can also: * Select the data range * Define the header row * Review imported transaction data before validation *** ## **2. Source** The next step is uploading or selecting supporting evidence documents. #### **Supported evidence types** Examples include: * PDF * Excel * Word documents * Images * CSV files *** ### **Purpose of Source Documents** These documents act as audit evidence used to validate: * Invoice details * Dates * Vendor names * Amounts * PO numbers * Supporting references The uploaded evidence becomes the basis for automated verification. *** ## **3. Rules** The Rules section defines how the validation should be performed. Auditors can choose between: *** ### **Custom Setup** Manually define: * Fields to validate * Data types * Validation logic * Extraction prompts *** ### **Template-Based Setup** Use predefined templates for commonly used testing procedures. This helps standardize testing across engagements. *** ## **Field Configuration** For each column or field, auditors can define: * Operation type * Verify * Retrieve * Field type * Text * Date * Currency * Percentage * Boolean * Rule logic * AI extraction prompts *** ## **Running Validation** Once configuration is complete: * Click **Run Validation** * Fins AI Brain processes: * Transaction data * Source documents * Validation rules The system then generates testing results automatically. *** ## **Validation Output** The output displays: * Matched values * Exceptions * Differences * Validation status * Review indicators Examples: * Pass * Needs Review * Mismatch This helps auditors quickly identify exceptions requiring attention. *** ## **Evidence Linking & Drill-Down** One of the key capabilities of Test of Details is direct evidence linkage. Auditors can: * Click on any output cell * Open the related source document instantly * View the exact supporting evidence * See the matched value highlighted within the document This provides: * Faster verification * Better audit traceability * Improved reviewer confidence * Easier investigation of exceptions *** ## **Review & Confirmation** After reviewing the results: * Auditors can investigate exceptions * Add notes or observations * Review linked evidence * Confirm the testing output The finalized results then become part of the engagement workpapers. *** ## **How Test of Details Supports the Audit** The module helps auditors: * Validate sampled transactions efficiently * Reduce manual verification effort * Improve consistency in testing * Maintain strong evidence linkage * Increase confidence in audit conclusions It converts transaction testing into a structured, evidence-backed workflow. {% embed url="" %}