audit-trail-verifier
Verifies financial data against source documents, bank statements, contracts
Best use case
audit-trail-verifier is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Verifies financial data against source documents, bank statements, contracts
Teams using audit-trail-verifier should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/audit-trail-verifier/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How audit-trail-verifier Compares
| Feature / Agent | audit-trail-verifier | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Verifies financial data against source documents, bank statements, contracts
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Audit Trail Verifier ## Overview The Audit Trail Verifier skill provides systematic verification of financial data against source documentation during due diligence. It traces reported metrics back to bank statements, contracts, and other primary sources to validate accuracy and identify discrepancies. ## Capabilities ### Bank Statement Reconciliation - Match reported revenue to bank deposits - Verify cash balance accuracy - Reconcile payment timing differences - Identify unexplained discrepancies ### Contract Verification - Match revenue recognition to contract terms - Verify pricing and payment terms - Check contract status and renewal dates - Validate customer counts against contracts ### Invoice and Payment Tracking - Trace invoices to payments received - Analyze days sales outstanding (DSO) - Identify collection issues - Verify accounts receivable aging ### Expense Verification - Match expenses to supporting documentation - Verify vendor contracts and commitments - Check employee payroll against records - Validate equity compensation records ## Usage ### Verify Revenue ``` Input: Reported revenue, bank statements, contracts Process: Trace revenue to sources, reconcile differences Output: Verification report, discrepancy list ``` ### Reconcile Cash ``` Input: Reported cash, bank statements Process: Compare balances, identify differences Output: Cash reconciliation, unexplained items ``` ### Verify Contracts ``` Input: Customer list, revenue claims, contract files Process: Match contracts to revenue, check terms Output: Contract verification summary, issues found ``` ### Audit Expenses ``` Input: Expense reports, supporting documentation Process: Sample and verify expenses, check approvals Output: Expense audit results, policy compliance ``` ## Verification Categories | Category | Key Verification Points | |----------|------------------------| | Revenue | Bank deposits, contracts, invoices, recognition timing | | Cash | Bank statements, reconciliations, restricted cash | | Receivables | Aging, collectability, concentration | | Payables | Vendor agreements, payment terms, accruals | | Payroll | Employment records, compensation agreements | ## Integration Points - **Financial Due Diligence**: Core verification for financial DD - **Financial Model Validator**: Validate historical data accuracy - **Legal Due Diligence**: Coordinate contract reviews - **Financial Analyst (Agent)**: Support verification work ## Red Flags - Revenue not matching bank deposits - Large reconciling items without explanation - Significant revenue concentration in month-end - Missing or incomplete contract documentation - Unusual related party transactions - Unexplained cash movements ## Best Practices 1. Request direct bank feeds or certified statements 2. Sample test across periods, not just recent 3. Focus on material items and unusual patterns 4. Request management explanations for discrepancies 5. Document verification trail thoroughly
Related Skills
trail-effects
Trail renderer skill for motion trails.
medical-coding-audit
Review clinical documentation and assigned codes for accuracy, compliance, and optimization, identifying documentation improvement opportunities and coding errors
accessibility-compliance-auditing
Evaluate learning materials and technology for WCAG, Section 508, and accessibility compliance with remediation recommendations
optimization-correctness-verifier
Verify correctness of compiler optimizations using formal methods
energy-auditor
Process energy audit skill for consumption analysis, benchmarking, and efficiency improvement identification
quality-auditor
Internal quality audit skill with planning, execution, findings documentation, and corrective action tracking
five-s-auditor
5S workplace organization audit skill with scoring, photo documentation, and sustainability tracking
freight-audit-validator
Automated freight bill validation skill with discrepancy detection and payment processing automation
audit-workpaper-generator
Automated audit workpaper preparation skill with PBC list management
audit-sampling-calculator
Statistical and non-statistical audit sampling skill with sample size determination and evaluation
sandbox-entitlements-auditor
Audit and recommend minimal sandbox entitlements for secure desktop applications
qt-widget-accessibility-audit
Audit Qt Widget applications for accessibility compliance using QAccessible interface and platform accessibility APIs