Jev invoice issuer match

Match an invoice issuer to a known supplier

Provide invoice seller evidence and a supplier list with documented aliases. Compare the issuer with the bill-to customer, keeping outside or conflicting sellers unmatched.

invoice issuer matchLive API
Try an example

Bill-to text does not identify the seller.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original text demonstration adapts a decision in a repository linked by the cited X post. The examples and explicit uncertainty outcomes are ours. The post is a directory reference, not proof that its author built every linked project. No third-party benchmark, business outcome or external action is reproduced.

Select supplier A, B or C only when invoice seller evidence matches that supplied supplier, including explicitly documented aliases.

Decision rules and labels
ABCNoneUnclear
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

Supplier matching is a candidate-selection task after text extraction. It should not pick a familiar company merely because that name appears somewhere on the invoice; the name must occupy the issuer role.

None and Unclear preserve two different problems: a known issuer outside the list, and an unresolved issuer. Neither output creates a vendor, validates bank details or approves a payment.

This original text demonstration adapts a decision in a repository linked by the cited X post. The examples and explicit uncertainty outcomes are ours. The post is a directory reference, not proof that its author built every linked project. No third-party benchmark, business outcome or external action is reproduced.

Illustration of one spreadsheet row producing two separate classification results
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for invoice supplier matching.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Provide invoice seller evidence and a supplier list with documented aliases.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between A, B, C, None, Unclear. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Unclear before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Seller versus customerA100%
Documented trading nameB100%
Hosting invoiceC100%
Unknown issuerNone100%
Only bill-toUnclear100%
Contradictory sellerUnclear99.0%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

Invoice supplier matching: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Matching seller text to a reviewed supplier list
  • Separating buyer and seller roles
  • Preserving unknown vendors for manual review

Outside this demonstration

  • Creating suppliers or posting invoices
  • Approving payment instructions
  • Inferring aliases from brand familiarity
Example FAQ

Using this example

The input contract and these limits define what the result means.

How can I support trading names?

Provide a documented alias with the candidate. The demo must not assume that similarly named businesses are the same supplier.

Does a match verify bank details?

No. Seller matching and payment verification are separate tasks. This page returns only the supplier label.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.