BotCurrent↗
← Back to examples

Official recipe

Check payable documents for approval-policy exceptions

A correct invoice total can conceal unsupported charges, altered payment details or conflicting contract terms.

Read original recipe
Suggested result

Document-level findings, an independently checked calculation and a consolidated unresolved-issue queue.

What you need: Source-named agent: OpenAI Agents API. Suggested inputs: Document copies; Review policy. Keep inputs read-only and use a new output directory. Require one report per source and reconcile the batch manifest. Workflow costs and current compatibility remain unverified.

Proposed: Payments, accepting terms, supplier contact or changing authoritative records.

Official recipe. BotCurrent has not independently tested this workflow.

Setup and access

Proposed inputs

  1. Name

    Document copies

    Owner

    Accounts payable owner

    Minimum scope

    Two fictional invoices and one related agreement

    Quality check

    Keep distinct filenames and source-page references.

  2. Name

    Review policy

    Owner

    Procurement owner

    Minimum scope

    A short invented approval policy with an effective date

    Quality check

    Identify exceptions and the person who decides them.

Access and setup — proposed or unknown

Proposed minimum

  1. Keep inputs read-only and use a new output directory.

  2. Require one report per source and reconcile the batch manifest.

Compatibility unknowns

  1. Unknown: runtime availability, document coverage and organization-specific approval controls.

External actions requiring approval

  1. Payments, accepting terms, supplier contact or changing authoritative records.

Detailed steps and output format

At a glance

Suggested result
Document-level findings, an independently checked calculation and a consolidated unresolved-issue queue.Suggested; untested.
Tool
OpenAI Agents APISource-named; check current access.
Suggested inputs
Document copies; Review policyProposed; access notes below.
Human review
Proposed: Payments, accepting terms, supplier contact or changing authoritative records.Suggested boundaries; source approvals below.
Setup notes
Keep inputs read-only and use a new output directory. Require one report per source and reconcile the batch manifest.Guide notes; proposed setup untested.
Cost
Workflow cost not established. Check current tool pricing, setup and human review costs before trying it.No measured cost or time added.
Content depth
Source-linked example · suggestions untestedDepth does not establish successful execution.
Check source evidence and limits ↓

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

A correct invoice total can conceal unsupported charges, altered payment details or conflicting contract terms.

Suggested task · untested

Proposed: Prepare a payable-document exception packet for an authorized reviewer.

What you could produce

Document-level findings, an independently checked calculation and a consolidated unresolved-issue queue.

Where these suggestions come from
  • Core problem: Our suggestion; no result reported by the source
  • Agent job: Our suggestion; no result reported by the source
  • Expected output: Our suggestion; no result reported by the source
  • Relevant job roles: Our suggestion; no result reported by the source
  • Benefit type: Our suggestion; no result reported by the source
Suggestions and their limits

Describes the proposed purpose and review output; measured benefit and successful delivery are not established.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Before you try it · suggestions untested

Original decision guidance and first check are proposals. The source supports the attributed task; this guidance has not been executed.

Read the attributed source evidence and original caveats below ↓

Why use this

  1. Separate calculation errors from approval questions.

  2. A common findings format supports batch review.

Why an agent / simpler alternative

Useful judgment

Connect unclear terms to approved rules.

Simpler alternative

Use accounting-system matching and deterministic totals for standard invoices with complete purchase records.

Unsuitable when

No authorized policy exists or legal interpretation would determine binding terms.

Expected deliverable and review checks

Proposed artifact

Document-level findings, an independently checked calculation and a consolidated unresolved-issue queue.

Critical checks

  1. Account for every document.

  2. Check amounts against source pages.

  3. Identify the applicable policy version.

Missing output evidence

Unknown: no independently inspected run artifact or live outcome.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Two invented invoices, one with a duplicated line, and a related agreement whose effective date falls after the billed period.

Acceptance checks

  1. Reconcile every document.

  2. Expose the duplicated line.

  3. Leave policy timing unresolved for the owner.

Stop conditions

  1. Requests to pay, accept terms or decide an unclear legal obligation.

Tasks: Documents & filesSecurity & complianceMoney & accounting

Useful for: General use

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.
OpenAI Agents APIIndependent testing: No
Failure handling, costs and limits

Failure signals and proposed responses

  1. Signal

    Correct total from misread lines

    Why it matters

    Arithmetic checks can pass an incorrect extraction.

    Proposed response

    Compare each disputed line with the source image.

  2. Signal

    Policy versions mixed

    Why it matters

    A valid rule may not apply to this document.

    Proposed response

    Pause and ask the policy owner to identify the controlling version.

Effort and cost — unknown

Setup work

  1. Define document IDs, calculation checks and the exception-review template.

Ongoing review

  1. Resolve commercial questions and verify changed payment details independently.

Unknowns

  1. Unknown: implementation effort, review time, usage charges and error frequency. No savings estimate established.

Limits

  1. This exercise checks review traceability, not payment validity or legal enforceability.

Full source evidence

Official recipe · Tool workflows

Original task title: Check payable documents for approval-policy exceptions

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://github.com/openai/openai-cookbook/blob/main/examples/agents_api/apps/document_review/README.md ↗

Attributed to: OpenAI

Official recipe
Original action type
tool_action
What the source reports
Delegates document reviews using a shared policy and writes individual and consolidated reports; application code separately checks extracted invoice arithmetic.
Source outcome limits
Synthetic examples; arithmetic validation cannot establish faithful extraction. No completed review run inspected. No independent execution test.
Evidence attribution caveat
This official recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description
The agent may recommend; people retain payment approval and contract acceptance.
Named tools
OpenAI Agents API
Model or version
gpt-5.6-luna, as specified in the recipe
Publication date
Unknown
Source last checked
2026-10-14
Demonstrated in Canada
Unknown
Canadian availability
Unknown
Proposed Canadian adaptation
Proposed: an authorized local owner must verify availability, privacy, policy and professional-review requirements. Canadian execution is unknown.
Recommended approval boundaries
Proposed: Payments, accepting terms, supplier contact or changing authoritative records.