Help

Run your first invoice review in the browser, connect the API, or work through a result that needs attention. New accounts start free; no credit card is required.

Run your first review

Create an account with an emailed code. You will arrive in the console with a synthetic supplier invoice and its context already loaded. Read the example, then select Run verification. Nothing runs automatically, and you do not need an API key.

The sample totals $24,800 but lacks the purchase-order reference required above $1,000. Look for the false verdict and failed po_present check. This gives you a specific finding to follow from the submitted record to the result.

Read the verdict together with its failed or undecided assertions. A completed review can be true, false or uncertain; uncertainty is a result that needs a next step, not a failed request.

Follow the console guide for JSON, importing CSV or XLSX files, batch progress and downloading your results.

Manage access and usage

Your account page shows today's usage and the API keys used by your integrations. The free allowance is 5,000 items and 1,000 model questions per UTC day, with 60 authenticated API requests per rolling minute. The question allowance counts questions asked by single verifications; batches add no question usage.

If either daily allowance is exhausted, new submissions wait until 00:00 UTC. You can still retrieve existing results, subject to the request-rate limit. See Pricing for the free plan and Limits for counting and reset details.

Account and API-key help covers sign-in, replacing a key, shared account quotas and choosing the correct account for existing audits.

Resolve a problem

If an upload is rejected, identify the field or format the message names. If a result is uncertain, inspect the missing evidence or unqualified question. If a batch is still running, keep its audit id and check progress before submitting it again.

Troubleshooting helps distinguish input problems, access problems and review outcomes. Developers can use the error reference for status codes and retry behavior.

Connect the API

For an integration, create a key on the account page, then follow the quickstart. It includes a complete invoice request and commands for sending it. You can download the JSON example or import the Postman collection.

The API guides explain authentication, single-record verification, reading results and batch audits.

Before expanding a review, confirm the input schemas and evidence scope, plan for limits, and decide who will resolve exceptions. The review-marks guide explains how to record a completed audit's human review.

Understand the result and the data boundary

How it works explains the checks, model qualification and verdict rules. Evaluations describes what has been measured. The privacy notice covers data retention, and security explains account and request controls.

The OpenAuditor blog explores practical review problems and recorded experiments. Start with 99.5% of which decisions? to understand why a requested target is different from measured certainty, or the batch review workflow to plan complete result retrieval and follow-up.

Contact ERP.AI

For an issue these guides do not resolve, use the ERP.AI contact page and identify OpenAuditor as the product. Include the page or endpoint, approximate time, the visible error and a request or audit id if available. Share a small sanitized example when needed; leave API keys, sign-in codes and confidential records out of the initial message.

Plans and billing

Check Pricing for available plans and included usage. The billing guide covers upgrades, payment confirmation, invoices and cancellation when paid subscriptions are available.