Evidence the run may read
- Approved contract metadata
- Delivery and billing evidence
- Documented accounting policy
production blueprint · finance
Revenue close support agent blueprint.
Organize approved contract, delivery, and billing evidence into a reviewer packet without making accounting judgments autonomously.
Search intent: AI agent for revenue close support
Published by a2a cloudProduct-source methodology →
01 · the contract
Start from a bounded job, not a blank chat box.
trigger
A revenue population or exception enters close review.
owner
finance owner
agent stops at
A qualified revenue accountant decides treatment and approves any entry.
KPI · decrease
revenue exception aging (days). Measure exception opening to accountant-approved disposition.
outputs
Artifacts the run must produce
- Evidence completeness table
- Policy question list
- Reviewer-ready close packet
02 · topology
Small specialists. Named handoffs. One accountable decision.
Each stage produces an artifact another stage can inspect. The final node is a person, not an autonomous write to an external system.
- 01
intake
Validate and normalize the revenue close support inputs.
- 02
contract evidence extractor
Produce the evidence completeness table.
- 03
delivery evidence matcher
Produce the policy question list.
- 04
revenue accounting reviewer
Challenge the revenue close support result and prepare an approval packet.
- 05
finance owner
A qualified revenue accountant decides treatment and approves any entry.
intake→ validated input packet →contract-evidence-extractor
contract-evidence-extractor→ Evidence completeness table →delivery-evidence-matcher
delivery-evidence-matcher→ Policy question list →revenue-accounting-reviewer
revenue-accounting-reviewer→ approval packet with evidence references →human-approver
03 · authority
Grant the run only what this case needs.
Source material is read-only. Drafts land in a case-specific output path. Tools may read or propose; the human gate owns the external write.
case inputs
workspace/finance/revenue-close-support/inputs/**Read only the evidence attached to this workflow instance.
case outputs
workspace/finance/revenue-close-support/outputs/**Write drafts and evidence artifacts without modifying source records.
approved tools
finance:revenue-close-support:read-or-proposeInvoke only tools explicitly granted for this run; external writes remain gated.
04 · implementation
A private, bounded starting manifest.
The blueprint starts private, caps its DAG, disables replanning, and exposes no public endpoint. Add only the tools and data adapters this workflow has approved.
a2a.yamlsafe starting point
name: finance-revenue-close-support
version: 0.1.0
entrypoint: agent:BlueprintAgent
expose:
public: false
composition:
planning: deterministic_dag
max_nodes: 6
max_parallel: 1
max_replans: 005 · acceptance test
Pass only with evidence.
- 01
Evidence traceability
Every material conclusion cites an input artifact or a scoped tool result from this run.
- 02
The packet reports evidence and policy questions without substituting an unapproved accounting conclusion.
The packet reports evidence and policy questions without substituting an unapproved accounting conclusion.
- 03
Approval boundary
The run stops at a proposal and records the human decision before any external side effect.
failure containment
Stop small. Preserve the evidence.
Contract terms, delivery evidence, or applicable policy cannot be matched to the population.
Containment: Return a partial result with unresolved items; do not broaden scope or perform an external write.
Operator: Attach the missing evidence, narrow the brief, or explicitly approve a new scoped run.
A required input or tool grant is unavailable.
Containment: Stop the affected branch and preserve completed artifacts in the case output workspace.
Operator: Grant only the missing resource or continue with that branch marked out of scope.
06 · proof
Sign the run facts. Keep money in the billing ledger.
Current platform receipts sign caller identity or classification, skill, bounded input evidence, verified grant IDs when present, outcome or result preview, and timing. Optional file, tool, artifact, handoff, evaluation, and review fields require separate instrumentation and are not populated by default. Price, fees, payouts, and later human approvals remain separate platform records.
The example uses only fields populated by the current platform sealing paths. It is illustrative, not a record of a real customer run.
ExecutionReceipt · selected fieldsEd25519 token
{
"receipt_id": "rcpt_01J...",
"schema_version": 1,
"agent_name": "finance-revenue-close-support",
"caller": "user:workflow-owner",
"task_id": "case_revenue_close_support",
"skill_name": "revenue_close_support",
"input_hash": "4d7c...9a2f",
"grant_ids": [
"grt_case_inputs",
"grt_tool_propose"
],
"status": "ok",
"result_preview": "Output prepared: Evidence completeness table. Human decision remains separate.",
"elapsed_ms": 4218
}related blueprints
Keep the operating model consistent.
Finance
Invoice exception review
Compare an invoice exception with purchase, receipt, and policy evidence and prepare a resolution recommendation.
Finance
Expense policy review
Evaluate an expense packet against the applicable policy and prepare a cited decision for a human approver.
Finance
Month-end reconciliation support
Compare ledger and subledger evidence, identify unmatched items, and prepare a reconciliation packet for sign-off.
put the pattern to work
Start private. Scope the authority. Require the decision.
Deploy the workflow as a bounded internal agent, verify its outputs and the receipt fields actually emitted, then expand only the scopes your acceptance test proves it needs.