Employee Statement Documentary Inconsistency Analysis

Skill: Employee Statement vs. Documentary Evidence Inconsistency Analysis

1. Subject-matter triage

• Treat the source set as a comparison exercise, not a generalized fraud narrative.
• First identify each declarant, each declaration, and each documentary source that bears on that declarant.
• If the materials include only one declarant or one event sequence, state that expressly before analyzing; otherwise enumerate the full set of declarants, time periods, and key document clusters before drawing conclusions.
• Separate sworn statements, interview notes, emails/messages, accounting records, audit materials, compliance logs, and board or management communications. Do not mix them unless the comparison requires it.

2. Failure modes the skill is correcting

• Providing a global credibility judgment instead of a declarant-by-declarant comparison anchored to specific statements and specific documents.
• Treating a mismatch as merely factual when it may also implicate sworn-statement exposure, financial reporting risk, or internal control deficiencies.
• Failing to distinguish direct contradictions from omissions, evasions, or statements that are technically true but misleading in context.
• Missing temporal sequencing: a statement may be false because later documents prove earlier knowledge, or because the declarant’s account is inconsistent with the contemporaneous record.
• Overlooking investigation inadequacy where the source set shows a cursory or incomplete internal review.
• Asserting legal consequences without naming the governing authority or practice standard that supports the characterization.

3. Legal frameworks / domain conventions that apply

• Compare declarations against contemporaneous documentary evidence using ordinary credibility principles: the most probative materials are those closest in time to the events and those created for business purposes rather than litigation posture.
• For sworn declarations, evaluate whether contradictions support potential false-statement exposure under the relevant perjury or false-declaration statute used in the source materials, or the generally applicable perjury framework if no statute is named.
• For financial reporting issues, assess whether the facts suggest improper recognition, misclassification, disclosure failure, or audit misrepresentation under the applicable accounting framework referenced in the source set, and note the downstream reporting consequence.
• For auditor-facing representations, assess whether management representations, certification language, or equivalent assurances are contradicted by the record and therefore may support misrepresentation or fraud theories.
• For internal controls, assess whether the record shows a breakdown in review, escalation, documentation, or investigation procedures; cite the internal-controls standard, policy, or control framework identified in the materials, or the generally recognized internal-control framework if none is specified.
• For investigation adequacy, use ordinary investigation practice standards: review of relevant documents, coverage of relevant witnesses, timing, and whether the inquiry was superficial relative to the issue.
• For any legal proposition stated in the memo, name the controlling authority, rule, statute, regulation, or generally recognized practice standard that supports it.

4. Analytical scaffolds

• Begin with an inventory of declarants and source documents. Then run the analysis once per declarant, not once per issue type in the abstract.
• For each declarant, list each material statement that can be tested against the record. For each statement, identify the exact contradicting document or documents, explain the conflict, and state whether the conflict is direct, contextual, temporal, or by omission.
• For each inconsistency, include three closing moves: the scale or significance of the point as shown by the source documents, the other document or record that interacts with it, and the downstream consequence for the investigation committee.
• Distinguish between:
  • a clear contradiction,
  • an incomplete or selective account,
  • a statement that is technically accurate but misleading in context,
  • and a statement that is unsupported but not yet disproved.
• When the materials include side arrangements, undisclosed understandings, or informal communications, test whether they negate a declarant’s professed lack of knowledge, lack of involvement, or completeness of disclosure.
• When the materials include revenue, returns, reserves, cut-off, or other accounting data, compare the asserted accounting treatment to the stated criteria in the record and note which criteria are implicated, not merely that the treatment seems wrong.
• When the materials include investigation logs or compliance notes, assess scope, witness coverage, duration, and document review; if the inquiry was narrow or perfunctory, characterize that as an internal-control concern.
• For each declarant, assign a severity level using a uniform ordinal scale defined once in the memo, and tie the severity to the number, specificity, and reliability of the contradictions.
• For each declarant, give a credibility assessment that reflects the pattern of inconsistencies, not just the loudness of the allegation.
• If the source set permits, cross-reference statements against emails, meeting notes, accounting records, audit materials, and compliance logs in that order of evidentiary strength, giving priority to contemporaneous business records.
• If a statement depends on a date, sequence, or knowledge state, test it against the timeline, not merely against a later summary document.

5. Vertical / structural / temporal relationships

• Track whether a contradiction is early, midstream, or post hoc. Earlier documents often show actual knowledge or intent; later declarations may show repair attempts or rationalization.
• Where the record shows an initial concern, a limited investigation, and then a contrary external representation, analyze the sequence as a possible concealment pattern, not as isolated events.
• If one declarant’s statement depends on another person’s account, identify the dependency and test both against the same record.
• Where multiple records describe the same transaction, document flow, or approval chain, show how the records fit together across time so the committee can see whether the inconsistency is isolated or systemic.
• If a prior investigation appears closed without meaningful review, connect that procedural defect to the substantive issue and explain why it matters for control effectiveness.

6. Output structure conventions

• Write as an investigation committee memorandum, not as a litigation brief.
• Use a short executive overview, then organize the body by declarant, and within each declarant by issue or statement.
• Give each entry a severity label from the uniform ordinal scale used in the memo, followed by the declarant’s statement, the contradicting document citation, and a concise explanation of the conflict.
• For each entry, state the legal or operational significance in plain terms and name the governing authority or standard relied on.
• Include a credibility section that summarizes the basis for each declarant’s assessment in one place.
• Include a legal exposure section grouped by category, such as false sworn statement exposure, financial reporting risk, auditor misrepresentation risk, and internal-control failure.
• End with a Recommended Actions block. Each recommendation should use an imperative verb, identify the responsible role or function, and include a timing anchor tied to the committee’s next step, investigation milestone, or filing/reporting deadline if one appears in the materials.
• Keep citations specific and document-based. Do not generalize across declarants where a document ties the issue to only one person.
• Do not rely on stylistic emphasis alone; the prose itself must make the contradiction and its significance clear.