Auto-coding purchase invoice lines with Jev
Moneyby FlyingDutchGeek2026-09-19
Auto-coding purchase invoice lines with Jev
We run a Dutch accounting SaaS. When an invoice arrives from a supplier we've never booked before, the GL account field is simply empty — every first invoice is hand-coded. Jev now proposes one from that client's own chart (~1,000 eligible accounts).
What actually moved the numbers:
• Candidates in state, bare ids as Choice options. Putting the descriptions in criteria instead was ~8pp worse.
• Two rounds — category, then account. Not a design choice: 1,000 accounts don't fit in 255 options.
• One category question per invoice, not per line. The lines of one invoice usually belong together. 28% fewer calls, and it fixed a case we couldn't crack otherwise: our chart has two accounts literally both named "Brandstof machines" (machinery fuel) in different sections. Per line it picked the wrong one at 0.79; with the whole invoice as context, the