Nothing proposed a kontering for a document. The receipt hunt attaches
paper and stops; "klart att bokföra" existed only as an idea. The right
pane had extracted fields and no answer to the question the user is
actually there to settle.
POST /items/:id/suggest-booking answers it, read-only. The lines come from
buildTransactionEntryLines, the same function the commit path and the
pending-operations preview use, so what is shown cannot drift from what
gets posted. That is the whole reason to compose the existing chain rather
than write a second one.
Derived on demand rather than stored on the row. A stored proposal goes
stale against a corrected amount, a re-matched transaction or a template
the company taught itself yesterday. The hunt deliberately does not
compute it either: the nightly run is already at its time ceiling and a
proposal nobody opens is wasted work.
Five honest outcomes instead of one optimistic guess:
- already_booked, checked against the transaction and not only the inbox
row. Booking from Transaktioner, bulk-book or MCP stamps the transaction
and leaves the inbox row untouched, so trusting the row alone proposed a
second verifikat for money that already had one.
- no_transaction, because without one there is no trusted amount, no
settlement account and no learned counterparty.
- no_mapping, which now includes the engine's own 6991 placeholder at
confidence 0.1. Rendering that dressed "no idea" up as an answer one
click from the ledger.
- currency_unsupported on a foreign row matched by a mapping rule.
mapping-engine's rule branch computes VAT from the transaction's own
currency while every other line is SEK, so 100 EUR at 11.5 shows 20 kr
of moms instead of 230. The entry balances, so nothing downstream
catches it. The counterparty and static-template paths convert properly
and are not withheld.
- a proposal, with the provenance named correctly: template_id marks a
static library template, and a learned konteringskarta match sets
neither field. Read the other way round, the company's most trusted
suggestion was labelled 'default', the same word the placeholder gets.
The entity type is now resolved and passed. Left undefined it silently
proposed enskild-firma accounts to aktiebolag. The settlement account is
no longer applied twice, since evaluateMappingRules applies it on every
return path and a second pass rewrote a legitimate 1930 leg. Both queries
report a database failure as a failure instead of as "Posten hittades
inte".
Twenty-one tests, mostly about what the route must not do. Every guard was
removed in turn to confirm a test fails without it.
Co-authored-by: Jakob Wennberg <311770904+jakobwennberg-oss@users.noreply.github.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Jakob Wennberg
8b1e90abcc