Invoice Processing Pipeline

End-to-end invoice verification: extract structured data from the invoice, validate the vendor's VAT number, verify the payment IBAN, and convert currency if needed. Returns everything an AP automation agent needs.

4 steps x402 eligible invoice-process

What it runs

Invoice and Receipt Extraction
Source: Claude API (document analysis and data extraction)
EU VAT Validation
Source: VIES (EU VAT Information Exchange System, European Commission)
IBAN Validation
Source: Algorithmic validation (ISO 13616 IBAN standard + bank registry)
Currency Converter
Source: European Central Bank daily reference rates

The answer returns every step’s result, so your agent can show or check each one.

Inputs

Field	Type	Required	What it is
`text`	string	Yes	Invoice text or OCR output
`target_currency`	string	No	Convert amounts to this currency (optional)

How to call it

# Needs an API key. The whole check is charged once, at the listed price.
curl -X POST https://api.strale.io/v1/solutions/invoice-process/execute \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "inputs": {
      "text": "Invoice #2024-001\nFrom: Acme Ltd, VAT: GB123456789\nIBAN: GB82WEST12345698765432\nTotal: €1,250.00",
      "target_currency": "SEK"
    },
    "max_price_cents": 50
  }'

# No account. The first request answers 402 with the price in USDC;
# an x402 client pays it from your wallet and repeats the request.
curl -i -X POST https://api.strale.io/x402/v2/solutions/invoice-process \
  -H 'Content-Type: application/json' \
  -d '{
    "text": "Invoice #2024-001\nFrom: Acme Ltd, VAT: GB123456789\nIBAN: GB82WEST12345698765432\nTotal: €1,250.00",
    "target_currency": "SEK"
  }'

The bundle’s published example input.

Limitations

Best results with standard invoice layouts — handwritten invoices or heavily stylised designs may have lower accuracy
From step: Invoice and Receipt Extraction
What to do instead: For non-standard formats, use pdf-extract for raw text and apply custom parsing rules
AI extraction from invoice documents — line item totals and tax calculations should be verified against source
From step: Invoice and Receipt Extraction
What to do instead: Validate that extracted line items sum to the total amount and cross-check VAT calculations before booking
Documents supplied by URL or base64 are refused above 8 MiB of decoded data, with a caller_input error naming the input field and no charge. Reduce the document size or split it before submitting.
From step: Invoice and Receipt Extraction
VIES can be unavailable or throttle requests under unpublished per-member-state limits. Transient faults are retried, and cached results, including older fallback results, can be returned during outages.
From step: EU VAT Validation
What to do instead: Lookups within 48 hours can use cached results; if VIES is unavailable and no cached result exists, retry later.
Results can be cached for 48 hours, and national registry changes can take a further 24 hours to appear in VIES. Check the national tax authority directly for same-day registration or deregistration confirmation.
From step: EU VAT Validation
What to do instead: For real-time same-day verification, contact the national tax authority directly.
Swiss UID validation returns valid or invalid only, without a company name or address. This tool does not perform the separate enrichment lookup, whose public service is limited to 20 requests per minute.
From step: EU VAT Validation
What to do instead: For Swiss company name + address, call the swiss-company-data capability.
GB VAT numbers return a credentials-pending error when the HMRC connection is not configured.
From step: EU VAT Validation
What to do instead: Use vat-format-validate for GB format checks; it does not confirm VAT registration.
Validates structure and checksum only — does not confirm the account is open or active
From step: IBAN Validation
What to do instead: Use a SEPA test transaction (€0.01) or bank account verification API to confirm the account is live before large transfers
Covers all SEPA-zone IBANs. Non-SEPA country IBANs validated structurally but bank lookup may be incomplete
From step: IBAN Validation
What to do instead: For non-SEPA IBANs, cross-reference the bank code portion against SWIFT's IBAN Plus directory
Uses mid-market exchange rates — actual conversion rates from banks and payment processors include spread and fees
From step: Currency Converter
What to do instead: Apply your payment processor's typical markup (0.5-3%) to the converted amount for realistic cost estimates