# Invoice Decision — Preflight & 3-Way Matching API (`tryva/invoice-decision-api`) Actor

Validate invoices and match them against purchase orders and goods receipts. Get an auditable MATCH, REVIEW or REJECT decision with evidence.

- **URL**: https://apify.com/tryva/invoice-decision-api.md
- **Developed by:** [smile flow](https://apify.com/tryva) (community)
- **Categories:** Business, Automation
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $500.00 / 1,000 invoice matches

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Invoice Decision — Preflight & 3-Way Matching API

Validate invoices and match them against purchase orders and goods receipts. Get an auditable `MATCH`, `REVIEW` or `REJECT` decision with reasons and evidence.

This is not merely an OCR/parser: extracted or structured invoice data is normalized and evaluated by a deterministic business engine. V1 supports one invoice, at most one PO and one receipt. Ambiguous multi-document allocation returns `REVIEW` in the production roadmap.

Modes: `preflight`, `match`, and `batch` (maximum 100 independent cases). Structured JSON bypasses Docling. Document mode accepts a single HTTPS/HTTP URL, with SSRF protection, 15 MB limit, no redirects, and PDF/PNG/JPEG content types. Unknown fields remain `null`; confidence describes extraction/coverage/matching quality, never fraud, legal compliance, or payment safety.

### Local development

```bash
pip install -r requirements.txt
python -m pytest -q
python -m app.main < example.json
```

### Buyer terms

invoice validation · invoice matching · 3-way matching · 2-way matching · accounts payable automation · AP automation · purchase order matching · invoice exception management · goods receipt matching · invoice preflight · batch invoice validation

### Pricing

Pay per event is declared for successful results only: `invoice-preflight` $0.20 and `invoice-match` $0.50. No synthetic events; actor start and default dataset items are not billed.

### Document benchmark gate

`benchmarks/` contains the gate definition and fixture manifest. Publication must remain blocked unless text-native PDF, table PDF, scanned invoice, PO, and goods receipt fixtures meet field-level extraction thresholds. PaddleOCR is intentionally not a default dependency.

# Actor input Schema

## `mode` (type: `string`):

preflight, match, or independent batch

## `invoice` (type: `object`):

Optional structured Invoice object.

## `invoice_url` (type: `string`):

Optional HTTP(S) URL to a PDF, PNG, or JPEG invoice.

## `purchase_order` (type: `object`):

Optional structured PurchaseOrder object.

## `purchase_order_url` (type: `string`):

Optional HTTP(S) URL to a PDF, PNG, or JPEG purchase order.

## `goods_receipt` (type: `object`):

Optional structured GoodsReceipt object.

## `goods_receipt_url` (type: `string`):

Optional HTTP(S) URL to a PDF, PNG, or JPEG goods receipt.

## `items` (type: `array`):

Up to 100 independent invoice cases.

## `tolerances` (type: `object`):

Percentage tolerances used by the deterministic matching engine for price, quantity, and total comparisons.

## Actor input object example

```json
{
  "mode": "preflight",
  "tolerances": {
    "price_percent": 2,
    "quantity_percent": 0,
    "total_percent": 1
  }
}
```

# Actor output Schema

## `results` (type: `string`):

Explainable invoice preflight, two-way, and three-way matching decisions from the Actor default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("tryva/invoice-decision-api").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("tryva/invoice-decision-api").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call tryva/invoice-decision-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tryva/invoice-decision-api"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/55rmE2xxr8jl6QUGS/builds/ITFhix2nQqENy2Tw1/openapi.json