Revenue Recognition Qa
Use when QAing revenue recognition schedules, deferred revenue, performance obligations, SSP assumptions, contract modifications, and close-period revenue exceptions.
Install
$ agentstack add skill-loopfour-finance-skills-revenue-recognition-qa ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-loopfour-finance-skills-revenue-recognition-qa) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Revenue Recognition QA
Use this skill to review revenue recognition support and surface issues for controller review.
Inputs
- Revenue schedule or subledger export.
- Contract/order form terms and performance obligation notes.
- Billing data, start and end dates, delivery dates, and usage data if relevant.
- Accounting policy excerpts for recognition method, SSP, materiality, and modifications.
Workflow
- Identify the revenue model: ratable subscription, usage-based, services, milestone, hybrid, or other.
- Tie revenue schedule inputs back to contract and billing source data.
- Check core fields: customer, contract ID, performance obligation, start date, end date, total consideration, deferred balance, recognized amount, and remaining obligation.
- Review high-risk areas: nonstandard terms, discounts, credits, cancellations, upgrades, downgrades, renewals, multi-element arrangements, and services bundled with software.
- Classify each issue as policy question, data quality issue, schedule math issue, or missing support.
Output
Return:
- QA summary with pass, pass with notes, blocked, or controller review required.
- Exception table with issue, source evidence, financial impact, suggested owner, and recommended next step.
- Close-period risk notes.
- Questions for controller, auditor, legal, sales, or billing.
Guardrails
- Do not provide final accounting conclusions when policy is missing or ambiguous.
- Do not cite ASC 606 or IFRS 15 as a final answer without matching the user's policy and source facts.
- Keep recommendations review-oriented: flag, reconcile, document, or escalate.
- Separate revenue recognition issues from cash collection issues.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: loopfour
- Source: loopfour/finance-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.