How beres learns

Why the second month is much less work than the first — and why it's worth correcting documents properly rather than working around them.

What gets learned

Every time you confirm something during review, it's saved and reused.

Supplier matches. Pick the supplier for "SYARIKAT MAKANAN SB" once and the next document showing that name matches automatically. It also recognises variations — the same supplier printed slightly differently on a different document form.

Item and account codes. Confirm that "Ayam Segar 1kg" is item code AY-001 and later documents carry that code without being asked.

Unit prices. Confirmed prices are remembered per item. When a later document's rate can't be read, the known price fills in — you'll see a flag like "No rate read — using AY-001's known price 12.50; verify". Always verify it. Supplier prices change, and a stale learned price is exactly the kind of quiet error worth catching.

Your corrections beat imported data

Master data comes in two kinds: rows you imported or synced, and rows created when a person confirmed a code during review.

Re-importing refreshes names but never overwrites a code a person confirmed.

So you can re-import your supplier list whenever it changes in your accounting system without undoing your accountant's decisions. Human confirmations stay authoritative.

What this means in practice

Review carefully in the first few weeks. Early documents are where the learning happens. A supplier matched properly once is matched forever; a supplier you skip past keeps costing you time on every document.

Correct rather than work around. If a line's item code is wrong, fix the code — don't edit the description to something that happens to match. The fix teaches; the workaround doesn't, and you'll do it again next week.

Use apply-to-group. Setting a code across every matching line at once teaches once and saves the clicks.

Import master data before you start. Learning fills the gaps in your master data; it isn't a substitute for having it. Starting with a good supplier and item list means far fewer documents need a human at all. See Import your master data.

What it doesn't do

It doesn't invent codes. If a supplier isn't in your master data, beres will not create one — it asks you, because a made-up code fails at import anyway.

It doesn't learn across organizations. Your matches are yours alone.

It doesn't stop asking about genuinely ambiguous cases. When two suppliers have near-identical names, you'll be asked each time — which is correct. Guessing between them silently is exactly the error you'd want caught.