Use cases
Put a review where the decision happens.
Check an expense before reimbursement, an invoice before payment, or an AI action before execution. OpenAuditor returns the checks, evidence and unresolved questions your reviewer needs to decide what happens next.
Choose the workflow below to see its supported records, required context, recorded example and evaluation results. Each use case checks the evidence you supply; your application keeps responsibility for approvals, payments and other business actions.
Finance & internal audit
Financial audit
Review an expense awaiting reimbursement, an invoice ready to pay, or a payment release against the records and authority behind it. Check amounts, dates, duplicate criteria, supplied receipt status, recorded bank details and applicable approvals; keep questions about business purpose visible for review.
Start with one transaction family and its approval policy. Supply the employees, vendors, reference limits and comparison history those checks need. A transaction and its approval are separate review items, so a valid amount does not establish that the right person approved it.
Explore the finance workflowClaims operations
Insurance claims
Bring the policy, loss description and claim history into one review. Check the policy period, stated peril, reporting window, item totals and limits, then inspect the questions that remain about how the narrative and claimed items fit together.
Begin with a claim and the structured policy terms that applied on the loss date. Review a later payment separately against its assessed amount, payee and approval. The result supports your claims process; it does not retrieve policy documents or make a settlement decision.
Explore the claims workflowProcurement & accounts payable
Contract compliance
Put the applicable contract beside a service or usage invoice. Verify line arithmetic and labor rates, then review invoice totals, billing periods, caps and service credits. Send scope and reimbursement questions to the contract owner with the relevant clause and finding.
Start with one contract and one billing period, including effective rate changes, invoice lines and relevant billing history. Header and line checks cover different requirements. Checking a line alone does not establish that the invoice total, cap or credits are correct.
Explore the contract workflowDocument & AI workflows
AI output verification
Review an extracted field or generated sentence before it enters a business record or customer-facing answer. Locate values, numbers and quotations in the supplied text, check declared types and totals, and keep semantic support separate from a simple text match.
Start with a high-impact field or sentence and its source text. Include a quote or byte locator where available. OpenAuditor checks the text you send; it does not fetch a document from its URL or establish that an upstream scan was transcribed correctly.
Explore the output-review workflowAgent & platform teams
Agent actions
Review a proposed tool call against the agent's grant, resource permissions, argument limits and required approval. Inspect whether the action serves the user's instruction and whether relevant input came from the user or from a document, email or tool response.
Start in observation mode with a small set of consequential operations. Supply the action, grant, session context and your approval policy. Your application must call the API before execution and enforce its own handling of failed or uncertain results; OpenAuditor does not intercept or undo tool calls.
Explore the agent-action workflowStart with a result your team can review.
Choose one workflow, assemble its records and policy, and compare a small sample with your reviewers' findings. Include ordinary cases, known failures and incomplete evidence. The next step is to establish how your process handles each result: continue, investigate or request more information.
Use the console to run a supplied example without writing code. For an integration, start with the documentation and the API reference.
Know what each result establishes.
A verdict covers the applicable, unskipped checks and supplied evidence. Missing records and unqualified judgment questions remain visible; a decisive failure can produce false while other checks remain unresolved. A true result does not establish source authenticity or completeness outside the submitted population. The published evaluations use synthetic populations and do not establish performance on your organization's records.
Read how verdicts are reached, inspect the evaluation evidence, and review data handling before expanding a trial.
Research and practical guides
The OpenAuditor blog connects these workflows to inspectable examples and review decisions. Start with the bank-account investigation to see what matching records leave unresolved, or read how to verify agent actions before execution for grants, amount limits and required approval.