5c1aa03270b8a9c0d84004e6f0165a8fbc787dd4
Analyzed Invoice-4302486921-26_650869002_000.pdf text structure. Three cases: 1. FUEL (fields[4] = numeric tx-nr): km+product merged in fields[5], unit in fields[6]. Already working; no change. 2. EV CHARGING (fields contains "DDDD KWH" or "DDDD MIN" unit): column layout shifts — no km field, station+ort sometimes merged in fields[1]. Detected by regex on unit field; kwhIdx drives relative offset for menge/netto/brutto. Ort extracted from fields[2] (kwhIdx>=5) or fields[1] (kwhIdx=4, compact). Kilometerstand = 0 (EV chargers don't record odometer). 3. SERVICE ROWS (e.g. "DKV Analytics Premiu"): appear inside a VEHICLE: block but fields[4] is non-numeric (product description, not a transaction number). These were being parsed as fake vehicle transactions producing wrong ort/km values. Now filtered out (return null). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Description
Tessera - Modulare Workflow-Automatisierung und Tool-Integration
Releases
14
Tessera 1.9.1
Latest
Languages
TypeScript
90.3%
JavaScript
5.6%
Rust
1.5%
HTML
1.1%
Shell
0.6%
Other
0.8%