> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inyett.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Screen supplier payments to identify anomalies & deviations, errors and misstakes and fraud and sanctions.

# **Why you'd use it**

Catches double payments, sanctioned payees and changed bank accounts while you can still stop them. The single highest-value use case in the API.

# **How it behaves**

Asynchronous: POST the batch, then poll the warnings endpoint until AnalyzeStatus is Done. 31 indication rules run per transaction. No webhook — polling only.

# Use cases

<Card title="Screen Supplier Payments" href="https://docs.inyett.com/use-cases/supplier-onboarding-and-kyc" cta="Set it up!">
  <Badge color="white">Fraud</Badge>

  Screen supplier payment batches prepared to be sent by the ERP. Fetch a list of warnings connected to the payments. Hold the risky ones, and release the rest.
</Card>

## Warning lifecycle

```mermaid theme={null}

stateDiagram-v2
    [*] --> NotProcessed: Warning raised

    NotProcessed: NotProcessed
    note right of NotProcessed
        Raised but nobody
        has looked at it yet.
    end note

    Active: Active
    note right of Active
        Open and unresolved —
        the payment should be held.
    end note

    Completed: Completed
    note right of Completed
        Reviewed and
        dismissed as acceptable.
    end note

    CompletedWithAction: CompletedWithAction
    note right of CompletedWithAction
        Reviewed and something was
        actually changed or stopped.
    end note

    NotProcessed --> Active: Picked up for review
    Active --> Completed: Dismissed as acceptable
    Active --> CompletedWithAction: Payment changed or stopped

    Completed --> [*]
    CompletedWithAction --> [*]
```
