Jev is a decision model with a fixed version, called through a software interface (API) to choose an allowed evidence lookup, while code controls access and calculations and sends low-confidence or out-of-scope requests for review.
Billed positions
200,000
Plus one pricing and one cost record per position; 1,000 materials.
Data processing
2.48 s
Parse, join, validate, hash and aggregate 91.3 MB of local exports.
Full live run
15.2 s
Includes generation, both routing decisions and the explanation draft.
Decision model context
1.4–1.5 KB
Per decision request. Two decision-model calls reported US$0.00005237; the drafting model's per-run cost is unavailable, so the full workflow cost is unknown.
Three isolated Node runs per data size on the same local machine. Processing includes file parsing, joins, validation, hashing and aggregation; it excludes source generation and model calls. Filesystem caching was not controlled.
- 60,000 export rows (20,000 billed positions): 0.28 seconds mean processing time, three runs.
- 300,000 export rows (100,000 billed positions): 1.24 seconds mean processing time, three runs.
- 600,000 export rows (200,000 billed positions): 2.54 seconds mean processing time, three runs.
Each decision-model (Jev) request is under 1.5 KB. The drafting model receives a 6.2 KB evidence prompt with sixteen representative billed positions, rather than the full export. Its usage includes runtime context beyond that prompt, and its per-run cost is unavailable, so the complete workflow cost is unknown.
A separate six-question holdout matched all labels for both Jev and a simple keyword router, with no wrong high-confidence lookups. This is a small test set. Jev adds API latency; these results do not establish a speed or accuracy advantage over rules.
EUR only. Generated billing is fully recognized in its labelled period. No taxes, returns, foreign exchange or material entry/exit are modeled. Pricing and allocated-cost rows are custom projections; a real SAP adapter and recognition mapping need separate validation.
Missing costs, duplicate keys, foreign currency, inconsistent amounts and unsupported document citations block a confident draft. Vague questions and outbound requests require review. No client savings or production throughput are measured.
SAP references: Margin Analysis and Billing Document Item.