<< All versions

Skill v0.1.0

currentAutomated scan96/100
ghost1034/cpaautomation/audit-pbc-coordinator
──Details
PublishedNovember 17, 2026 at 05:21 AM
Content Hashsha256:7ebe335a0e2041ba...
Git SHAadbaea7eddad
──Files
Files (1 file, 5.5 KB)
SKILL.md5.5 KBactive
SKILL.md · 143 lines · 5.5 KB

name: audit-pbc-coordinator description: Track PBC requests with dependency-aware status reporting and burn-down version: 0.1.0 metadata: hermes: tags: [accounting, audit, pbc] category: accounting required_environment_variables:

  • name: CPAA_ACTIVATION_KEY

prompt: CPAAutomation.ai activation key required_for: premium skill access


Audit Prepared-by-Client (PBC) Coordinator

Ingest an audit-request tracker, normalize delivery statuses against an “provided/completed/delivered” vocabulary, quantify completeness, surface pending and overdue items against an --as-of cut-off, aggregate backlog by owning preparer, and publish an XLSX status dashboard suited to audit coordination stand-ups.


Overview

Target userInternal Audit Liaison, Controller’s office, External audit PBC coordinator
MaturityProduction for operational tracking via ./scripts/pbc_tracker.py; legal sufficiency / audit assertions remain with owners
What it doesValidates required columns; computes % complete, overdue sets, aging by owner averages, writes multi-tab workbook
What it does NOT doHost evidence securely; certify audit readiness; automate confirmation letters; substitute for auditor’s PBC portals

When to use

  • Weekly steering calls with external auditors through busy season
  • Cross-functional visibility when dozens of numbered requests flood email
  • SLA tracking by functional owner (“AP”, “Treasury”) with escalation messaging
  • Go / no-go check before commencing fieldwork tranche

When NOT to use

  • Substantive testing or sampling design
  • Sensitive evidence distribution (move to guarded sharepoint workflows)
  • Real-time syncing with ticketing tools without export discipline

Authoritative sources

  • PCAOB AS 2110, AS 2301 — nature and timing of audit evidence expectations
  • PCAOB AS 2201 — audit documentation completeness themes
  • COSO IC — reliance on completeness and timeliness monitoring controls

Inputs

PBC tracker CSV/XLSX — --tracker <path> (required)

Columns lowercased on read.

ColumnTypeRequiredNotes
request_idstringYStable ID from auditor numbering
descriptionstringYWork request description
ownerstringYResponsible internal party
due_datedateYParsed by pandas (YYYY-MM-DD recommended)
statusstringYMatching to provided set is case-insensitive after trim
prioritystringNDefault Normal if absent

Provided / complete statuses counted as fulfilled: `provided`, `complete`, `delivered` (status_norm ∈ PROVIDED_STATUSES).

Parameters

FlagRequiredDescription
--trackerYSource listing
--as-ofYEvaluation date YYYY-MM-DD
--outputYDestination XLSX
--quietNReduce logging chatter

Pending = rows whose normalized status ∉ provided set.

Overdue = pending rows with due_date < as-of (exclusive of same-day completeness logic — confirm policy if borderline).

Exit codes: 0 clean (no overdue); 2 if any overdue rows exist; 1 ingestion failure.

Workflow

1. IMPORT auditor PBC list + internal supplements into tracker template.
2. NORMALIZE statuses to consistent vocabulary (“In Progress”, “Provided”, etc.).
3. RUN coordinator with weekly as-of cadence snapshot.
4. REVIEW Pending & OwnerSummary tabs → assign escalation owners.
5. CLEAR Overdue BEFORE next auditor touchpoint OR document blocker narrative.

Edge cases

ScenarioHandling
Malformed datesParsed to NaT → may distort overdue logic; fix upstream rows
Status synonyms like “Uploaded”Not counted as provided unless renamed or mapping extended in code
Past-due completed itemMoves out of overdue because status now in PROVIDED_STATUSES
Owner churnConsolidate owner strings before rollup to prevent split metrics

Anti-patterns (DO NOT)

  • DO NOT mark “Provided” before files exist in auditor workspace
  • DO NOT ignore exit code 2; treat overdue as escalation signal automatically
  • DO NOT delete historical rows unless auditor agrees PBC versioning scheme
  • DO NOT use dashboard alone as SOC / SOX evidence without backing logs

Outputs

SheetContents
SummaryCounts & percent complete vs total
PendingOpen items with engineered days_overdue scalar
OverdueStrict subset overdue vs as-of snapshot
OwnerSummaryPending counts + average overdue days grouped by owner
AuditTrailTimestamp
SignOffAudit Coordinator / Controller / External Auditor scaffolding

Quality gates

  1. [ ] Tracker row count matches auditor master list version ID
  2. [ ] Every pending item has target delivery date and named backup
  3. [ ] Overdue lines include documented mitigation (data dependency, system outage, etc.)
  4. [ ] Sign-off occurs only after evidence drop confirmation for material items
  5. [ ] Archival copy of weekly dashboard stored in audit evidence tree

Worked example

From audit-pbc-coordinator/:

bash
python scripts/pbc_tracker.py \
--tracker examples/pbc_tracker.csv \
--as-of 2024-05-15 \
--output /tmp/pbc_status.xlsx

If any pending request predates 2024-05-15, expect exit 2 to trip automation alerts.

References

  • AICPA — Audit documentation & PBC best practice updates
  • Big 4 — Audit delivery center toolkits (align naming with vendor portal exports)
All versions