Evidence the run may read
- Invoice record
- Purchase and receipt evidence
- Vendor and exception policy
production blueprint · finance
Invoice exception review agent blueprint.
Compare an invoice exception with purchase, receipt, and policy evidence and prepare a resolution recommendation.
Search intent: AI agent for invoice exception handling
Published by a2a cloudProduct-source methodology →
01 · the contract
Start from a bounded job, not a blank chat box.
trigger
An invoice fails an approved validation or match rule.
owner
finance owner
agent stops at
An accounts-payable owner approves any posting, hold release, or vendor communication.
KPI · decrease
invoice exception cycle time (days). Measure exception creation to approved disposition.
outputs
Artifacts the run must produce
- Exception explanation
- Evidence comparison table
- Resolution recommendation
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 invoice exception review inputs.
- 02
invoice normalizer
Produce the exception explanation.
- 03
match analyst
Produce the evidence comparison table.
- 04
accounts payable reviewer
Challenge the invoice exception review result and prepare an approval packet.
- 05
finance owner
An accounts-payable owner approves any posting, hold release, or vendor communication.
intake→ validated input packet →invoice-normalizer
invoice-normalizer→ Exception explanation →match-analyst
match-analyst→ Evidence comparison table →accounts-payable-reviewer
accounts-payable-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/invoice-exception-review/inputs/**Read only the evidence attached to this workflow instance.
case outputs
workspace/finance/invoice-exception-review/outputs/**Write drafts and evidence artifacts without modifying source records.
approved tools
finance:invoice-exception-review: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-invoice-exception-review
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 recommendation reconciles amounts, entities, dates, and supporting evidence without inventing missing records.
The recommendation reconciles amounts, entities, dates, and supporting evidence without inventing missing records.
- 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.
A purchase, receipt, tax, or vendor record required for comparison is missing.
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-invoice-exception-review",
"caller": "user:workflow-owner",
"task_id": "case_invoice_exception_review",
"skill_name": "invoice_exception_review",
"input_hash": "4d7c...9a2f",
"grant_ids": [
"grt_case_inputs",
"grt_tool_propose"
],
"status": "ok",
"result_preview": "Output prepared: Exception explanation. Human decision remains separate.",
"elapsed_ms": 4218
}related blueprints
Keep the operating model consistent.
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.
Finance
Cash application review
Match a payment export to open receivables and prepare proposed applications with confidence and exceptions.
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.