Jev financial document kind

Classify a financial document by its stated purpose

Paste readable document text to compare bank and card statements, paystubs and company financial reports. A filename alone cannot establish the document type.

financial document kindLive API
Try an example

The fields describe a deposit account.

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.

Identify the document purpose: Bank for a deposit-account statement with balances and transactions; Card for a credit-card statement with a card balance and payment terms; Paystub for employee earnings and deductions for a pay period; Financials for a company balance sheet, income statement or cash-flow statement.

Decision rules and labels
BankCardPaystubFinancialsOther
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

Several documents use similar words such as balance and statement. The distinguishing evidence is their purpose and field relationships: wages and deductions differ from deposit transactions or a company balance sheet.

This demo receives text you already have. It does not perform OCR, open a PDF, verify authenticity or assess creditworthiness. Redact personal and account details before testing a real excerpt.

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 financial document types.

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

    Add the information to check

    Paste readable document text to compare bank and card statements, paystubs and company financial reports.

  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 Bank, Card, Paystub, Financials, Other. 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 uncertain or unexpected results 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
Deposit transactionsBank100%
Card payment termsCard100%
Payroll recordPaystub100%
Company reportFinancials100%
Invoice insteadOther100%
Filename onlyOther96.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

Financial document types: 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

  • Sorting already-extracted document text
  • Testing a clear intake taxonomy
  • Separating filename hints from content evidence

Outside this demonstration

  • PDF or image extraction
  • Credit, tax or financial advice
  • Authenticity or fraud verification
Example FAQ

Using this example

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

Why are invoices labeled Other?

This example focuses on account statements, payroll records and company reports. The separate invoice-text example covers payment requests, receipts and quotes.

Does a recognized type prove the document is genuine?

No. It only means the supplied text resembles that type. Authenticity checks require a different process.

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.