# Finance Documentation Lifecycle > Controls the lifecycle of finance and accounting documentation after or alongside content authoring: intake, metadata, review, approval, publishing, access, version control, retention, revision, retirement, and audit evidence. Use when users need ISO 9001:2015 clause 7.5-aligned document governance for SOPs, control procedures, reconciliation guides, reporting documentation, data definitions, analytics documentation, or work instructions. For drafting the document content itself, use the more specific SOP, procedure, policy, glossary, metadata, metric, dashboard, or analytics skills first. - Skill: `bkjohn2018/finance-documentation-lifecycle` (Agent Skill, multi-file: 11 files) - Install (CLI): `npx skillmds@latest add bkjohn2018/finance-documentation-lifecycle` - Raw SKILL.md: https://api.skillmd.com/api/skills/bkjohn2018/finance-documentation-lifecycle/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Data & Analytics - Author: bkjohn2018 (https://skillmd.com/u/bkjohn2018) - Updated: 2026-09-21 - Page: https://skillmd.com/skills/bkjohn2018/finance-documentation-lifecycle --- # Finance and Accounting Documentation Lifecycle **Customer**: Finance and accounting team **Product**: Controlled, auditable, usable documentation **Framework**: ISO 9001:2015 clause 7.5 (Documented information) + customer feedback + PDCA + risk-based thinking This skill guides you through the complete documentation lifecycle so your finance and accounting team receives accurate, current, usable, protected, traceable, retained, and auditable documentation. The product itself is documentation—SOPs, control procedures, reporting guides, data definitions, reconciliation procedures, analytics documentation, and work instructions. **ISO 9001 Principle**: Clause 7.5 informs this skill but does not dictate the user-facing workflow. Documentation is organized by process and user task, not ISO clause structure, to ensure usability for finance and accounting stakeholders. --- ## When to Use - **Govern** a new or existing SOP, process narrative, control procedure, reconciliation guide, reporting template, or data definition through its controlled lifecycle - **Structure lifecycle metadata** so documentation has owner, audience, version, status, review cadence, approval evidence, and retention requirements - **Review** documentation for accuracy, compliance, and clarity before approval - **Approve** documentation through proper authority and record the decision - **Publish/Store** documentation so it's discoverable, retrievable, and protected - **Use** documentation while tracking how it performs in practice - **Revise** documentation when processes change, risks emerge, or users identify gaps - **Retire** documentation when it's no longer needed, archiving evidence as required Use specialized authoring skills for the document body before applying this lifecycle skill: - `sop-writing` for SOP content - `process-and-procedure-writing` for operational procedure content - `policy-and-standard-writing` for policy or standard content - `metric-governance`, `business-glossary-management`, and `metadata-and-lineage` for governed definitions and metadata --- ## Quick Lifecycle Checklist Use this checklist to guide any documentation task: - [ ] **Prepare**: Define purpose, owner, audience, scope, initial risk/compliance drivers - [ ] **Structure**: Organize content for your audience; include metadata (owner, version, date, approval) - [ ] **Review**: Check for accuracy, completeness, clarity, compliance with standards and process - [ ] **Approve**: Obtain sign-off from authorized owner/manager; document approval date and authority - [ ] **Publish/Store**: Place the controlled copy in a discoverable authoritative location; restrict changes; record access rules - [ ] **Use**: Monitor effectiveness; capture finance/accounting customer feedback, exceptions, gaps, and nonconformities - [ ] **Revise**: Update when processes change, customer feedback shows gaps, nonconformities occur, or risks evolve; maintain version history - [ ] **Retire**: Archive with retirement date and reason; retain review, approval, revision, retirement, and exception evidence per policy --- ## The Eight Lifecycle Phases Each phase aligns to ISO 9001's **process approach** (plan → do → check → act), **customer focus** (finance/accounting users can rely on the documentation), and **risk-based thinking** (identify what could go wrong, take proportionate action). ### 1. Prepare – **Plan & Risk Identify** Define the documentation need before you write. Identify purpose, owner, audience, process scope, compliance drivers, and known risks. **See**: [./references/01-prepare.md](./references/01-prepare.md) ### 2. Structure – **Plan & Create** Organize content so users can find and understand it. Establish metadata standards (identification, description, format, media). **See**: [./references/02-structure.md](./references/02-structure.md) ### 3. Review – **Check** Verify accuracy, completeness, clarity, and compliance. Identify gaps and nonconformities before approval. **See**: [./references/03-review.md](./references/03-review.md) ### 4. Approve – **Check & Act** Obtain sign-off from authorized manager/owner. Document approval decision and date; record who approved and why. **See**: [./references/04-approve.md](./references/04-approve.md) ### 5. Publish/Store – **Do** Place documentation in its authoritative location. Ensure access control, discoverability, and protection from unintended alteration. **See**: [./references/05-publish-store.md](./references/05-publish-store.md) ### 6. Use – **Do & Check** Release and monitor. Track how finance/accounting team uses documentation; log exceptions, user questions, process deviations. **See**: [./references/06-use.md](./references/06-use.md) ### 7. Revise – **Check & Act** Update when processes change, nonconformities emerge, or users identify gaps. Maintain version history and document reasons for change. **See**: [./references/07-revise.md](./references/07-revise.md) ### 8. Retire – **Act** Discontinue when no longer needed. Archive with retirement date and reason; retain per policy; dispose per retention schedule. **See**: [./references/08-retire.md](./references/08-retire.md) --- ## ISO 9001:2015 Alignment: Clause 7.5 Documented Information This skill applies the core control requirements from **ISO 9001:2015, clause 7.5** (Documented information) to finance and accounting documentation. The standard requires: | Control Requirement | How This Skill Applies | |---|---| | **7.5.1 General**: Maintain documented information required by the standard and by the organization | Phases 1–2: Define what documentation you need; structure it properly | | **7.5.2 Creating and updating**: Ensure identification, description, format, media, review, approval | Phases 2–4: Structure with metadata; review for completeness; obtain approval | | **7.5.3 Control**: Ensure documented information is available, suitable, protected from loss/alteration; manage distribution, storage, retrieval, preservation, version control, retention | Phases 5–7: Publish with access controls; protect from change; track versions; update when needed | **Key ISO principle**: Documentation must be controlled not because the standard says so, but because **inaccurate, outdated, unclear, inaccessible, or uncontrolled documentation creates risk**. Finance and accounting teams depend on current, accurate documentation to execute controls, support audit readiness, and prevent errors. --- ## Acceptance Criteria for Documentation Quality Documentation is considered complete and usable when it meets these criteria: - **Accurate**: Reflects current processes, systems, roles, and compliance requirements - **Current**: Approved version is the most recent; no outdated information - **Approved**: Formally signed off by authorized owner/manager; approval decision documented - **Accessible**: Stored in discoverable location; access control allows appropriate users to view/download - **Usable**: Clear, plain language; organized for user tasks; includes examples and decision points - **Protected**: Controlled copies only; protected from unauthorized alteration; version control in place - **Traceable**: Metadata includes owner, version history, approval dates, change reasons - **Retained**: Evidence of review, approval, revision, retirement decisions retained per policy Do not treat a document as ready for release until these criteria are met or an authorized exception decision is recorded with owner, approver, reason, risk, expiration date, and follow-up action. --- ## Controlled vs. Uncontrolled Copies - **Controlled copies**: Official, authoritative versions stored in designated locations (e.g., Sharepoint, Wiki). Marked with metadata (version, approval status, effective date). Only controlled copies are valid for use. - **Uncontrolled copies**: Unofficial versions (e.g., emailed attachments, printed copies, personal drives). Clearly marked "UNCONTROLLED COPY – FOR REFERENCE ONLY" with date printed. Not valid for official use; users must refer to controlled copy for current information. **Why this matters**: Prevents use of outdated or unauthorized versions that could lead to errors or compliance gaps. --- ## Evidence Retention Retain evidence for key decisions to support auditability and continuous improvement: - **Review evidence**: Review findings, meeting notes, reviewer sign-offs - **Approval evidence**: Approval forms, emails, signatures, conditional approvals - **Revision evidence**: Change logs, revision requests, impact assessments - **Retirement evidence**: Retirement notices, archive records, disposal confirmations - **Exception decisions**: Temporary use approvals, conditional approvals, variance approvals, nonconformity resolutions, corrective actions, and waiver expiration dates **Retention period**: Typically 3–7 years per SOX, tax, or organizational policy. Store with documentation or in audit trail folder. --- ## Customer Feedback from Finance and Accounting Users Since finance and accounting teams are the customers, monitor their perception and usage: - **Feedback mechanisms**: Surveys, user interviews, helpdesk tickets, process variance logs - **Key metrics**: User satisfaction (e.g., "Is this procedure clear?"), usage frequency, error rates tied to documentation - **Customer requirements**: Documentation must be accurate, current, accessible, and usable to meet customer needs - **Feedback integration**: Use in Phase 6 (Use) and Phase 7 (Revise) to identify improvement opportunities - **Feedback evidence**: Retain survey summaries, interview notes, ticket extracts, usage issues, and owner responses as lifecycle records --- ## Nonconformity Handling When documentation is inaccurate, outdated, missing, unclear, or not followed: - **Identify nonconformity**: Log as nonconformity (e.g., "Procedure missing Step 5; user deviated") - **Assess impact**: Determine if it caused errors, audit findings, or control weaknesses - **Document root cause**: Why did the nonconformity occur? (e.g., process change not reflected, unclear language) - **Take immediate action**: Clarify with users, provide workaround, or issue temporary guidance - **Escalate if needed**: Notify owner/manager; may trigger revision or corrective action --- ## Corrective Action Workflow for Recurring Documentation Issues For recurring issues (e.g., same procedure repeatedly unclear): 1. **Identify pattern**: Review nonconformity logs; note recurring themes (e.g., "GL codes outdated annually") 2. **Root cause analysis**: Investigate why issues recur (e.g., lack of annual review, poor user feedback capture) 3. **Develop corrective action**: Implement fix (e.g., add annual review trigger, improve feedback mechanism) 4. **Implement and verify**: Apply fix; monitor for recurrence 5. **Document and retain**: Record corrective action plan, implementation, and effectiveness check Recurring documentation nonconformities should not be handled as isolated edits. Treat them as signals that the documentation lifecycle, review cadence, ownership model, storage control, or customer feedback process may need correction. --- ## Governance Elements Covered Each phase captures governance metadata so documentation is traceable and auditable: - **Document owner**: Who is responsible for accuracy and updates - **Customer/audience**: Finance team, audit team, compliance team, data users - **Approval status**: Draft, approved, superseded, retired - **Version history**: Track each revision and reason for change - **Review cadence**: How often to formally review (e.g., annually, per regulation, per process change) - **Storage location**: Where authoritative copy lives (Sharepoint, wiki, database, repository) - **Access control**: Who can view, download, modify (role-based or user-specific) - **Change log**: What changed, when, why, who approved - **Review evidence**: Records of review meetings, sign-offs, approvals - **Risks and opportunities**: What could go wrong if documentation is weak; what could improve - **Nonconformities**: Documentation gaps, user questions, audit findings - **Corrective actions**: How you addressed documentation weaknesses - **Retirement criteria**: When to discontinue (e.g., process redesigned, regulation changed, merged with another doc) --- ## Supported Documentation Types This skill applies to all finance and accounting documentation: - **Standard Operating Procedures (SOPs)** – Step-by-step instructions for recurring processes - **Process Narratives** – High-level flow and context for a finance function - **Control Documentation** – How a control operates, its risk, frequency, evidence - **Reconciliation Procedures** – Steps to reconcile accounts, variance limits, approval levels - **Data Definitions** – Metadata, calculation formulas, data lineage, ownership - **Reporting Guides** – How to prepare reports, interpret data, meet deadlines - **Work Instructions** – Detailed task guides for specialized roles - **Finance Analytics Documentation** – Data dictionary, source systems, refresh schedule, assumptions --- ## Core Principles (Process Approach + PDCA + Risk-Based Thinking) 1. **Process approach**: Treat documentation as part of your finance process, not as an administrative burden. Poor documentation breaks the process. 2. **PDCA cycle**: Plan documentation needs → Do (create/update) → Check (review, use feedback) → Act (approve changes or retire). 3. **Risk-based thinking**: Identify risks that weak documentation creates (errors, audit findings, compliance gaps); take proportionate action (governance level, review cadence, access control). 4. **Customer focus**: Stakeholder is the finance/accounting team. Documentation is usable when it answers their questions and supports their work. --- ## Quick Start **Use the skill when you need to:** 1. Establish lifecycle controls for a new finance SOP or control procedure 2. Manage an existing document revision, approval, publication, or retention decision 3. Review documentation for lifecycle readiness, governance evidence, or ISO 9001 clause 7.5 alignment 4. Retire outdated documentation with archive and evidence requirements 5. Establish governance for a suite of finance procedures **For each task, follow the relevant phases** from the checklist above, and refer to the phase-specific guides. **For governance templates and examples**, see the `./templates/` folder. --- ## Next Steps for Your Team 1. **Review** [./references/01-prepare.md](./references/01-prepare.md) to understand how to scope a new documentation task 2. **Identify** which finance documentation currently lacks governance (missing owner, approval, version control, retirement criteria) 3. **Prioritize** by risk: high-risk controls (fraud, misstatement, audit findings) first; lower-risk reference documents second 4. **Apply the lifecycle** to each priority, phase by phase 5. **Track governance** in a documentation register or inventory --- ## References - [ISO 9001:2015 Clause 7.5: Documented Information](https://www.iso.org/standard/62085.html) – The authoritative source - Each phase guide in `./references/` – Deep-dive into plan, do, check, act - Templates in `./templates/` – Metadata sheets, approval forms, version history logs **Remember**: Documentation is your finance team's guide to how work gets done. Invest in its quality; your audit readiness and error prevention depend on it.