Jev receipt expense category

Assign a receipt to an internal expense category

Supply purchased items and their business purpose to compare software, travel, office and meal categories. Keep mixed or unsupported purchases for review rather than deciding tax treatment.

receipt expense categoryLive API
Try an example

The service description identifies a software subscription.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Classify the supplied receipt by its stated purchased items and business purpose: Software for hosted software services or software subscriptions; Travel for transport or accommodation; Office for physical office supplies; Meals for food or drinks.

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

The taxonomy is intentionally small. A receipt can be authentic and still fall outside the four named expense categories. Review covers mixed receipts and missing purchase descriptions instead of guessing from a merchant.

The demo returns a proposed internal category. Amount parsing, currency conversion, accounting rules and ledger writes remain outside the model request. No tax or financial treatment follows from the label.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

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 expense category matching.

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

    Add the information to check

    Supply purchased items and their business purpose to compare software, travel, office and meal categories.

  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 Software, Travel, Office, Meals, Review. 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 Review 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
Hosted databaseSoftware100%
Train to meetingTravel100%
Printer paperOffice100%
Team lunchMeals100%
Unknown orderReview100%
Mixed receiptReview83.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

Expense category 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

  • Testing a small internal expense taxonomy
  • Checking when merchant-only receipts need more context
  • Routing mixed-category receipts to a person

Outside this demonstration

  • Tax deductibility or accounting advice
  • Extracting or changing currency values
  • Posting expenses to a ledger
Example FAQ

Using this example

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

What happens to receipts with several categories?

This example returns Review. A separate line-item workflow could classify each item, but the current input receives one label.

Can I add another expense category?

Yes. Update the rule and choice list together, then replay representative receipts. A label that lacks a clear definition can make the result harder to interpret.

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.