finance-operations-review

Finance Operations Review

Outcome

Coordinate Billing Operations Coordinator and Finance Analyst to review current billing exceptions and explain their finance impact. Add close or payables specialists only when a distinct owner or access boundary needs them.

When to use

Use for a small B2B subscription business that needs a repeated, owned finance review across Crews. For one Crew's weekly brief, use that Crew's schedule.

Discovery and user direction

Inspect existing Crews, selected skills, setup evidence, source access, current Automation, and policies. Propose a concrete team, handoff, first result, cost, and blockers. Selection is a proposal; save decisions in SETUP.json after verification.

Required inputs

Resolve entity, period, currency, timezone, billing and finance source of truth, named owner, invoice/refund/contact policies, metric definition, and approval boundaries. Authorized exports support the first route; live connectors are optional.

Plan and AgentWorks tools

Use two distinct ready Crews: billing-operations-coordinator produces billing-exception-queue/v1; finance-analyst receives only the validated queue and authorized source references and produces finance-impact-readout/v1. Reuse suitable Crews. After review, create missing ones with create_crew and stable idempotency keys; never pass their local skill names as global skill selections. Put the relevant contract fields and output path in each Crew step instruction so the Crew need not access the Workflow's installed Playbook files. Add blocking validator steps before consumers. Optional close/payables routes require their own artifact checks before activation.

Knowledge and persistence

Save source/account scope, metric and policy decisions, Crew IDs, artifact paths, validator results, run IDs, and stable case/action IDs. Re-read current provider state before repeating a case; deduplicate events and avoid a second customer contact for the same case.

Validation and reporting