Matching learns from your corrections

When you fix booking accounts or BU codes on invoices, Cortena can turn repeated corrections into tenant-specific matching rules merged into your matching guidelines, so the next similar invoice matches correctly without manual edits.

1. What counts as a correction

Learning focuses on supervised changes you make to match data, typically:

• Booking account on header or line items
• BU code (business unit) where used

Automatic agent proposals you accept without change are not corrections. Repeated manual fixes on the same supplier, wording, or line pattern signal that a rule should exist.

2. How learning reaches matching

When tenant feature Invoice matching learned guidelines (auto) is enabled:

1. Cortena collects eligible corrections over time.
2. Similar edits are clustered into candidate rules (supplier + line context → account / BU).
3. A scheduled sync merges vetted rules into the tenant’s learned guidelines document (Google Doc) used during matching.
4. The payables matching agent reads those rules alongside your Chart of Account Matching Guide and chart spreadsheet.

Provisioning may create the learned doc when the feature is first enabled for a new workspace.

Pair with Instructing Cortena Agents for booking accounts for manual rules, and Matching correction for one-off automated fixes on a single invoice.

3. What improves for AP

Over time you should see:

• Fewer Needs review invoices for repeat suppliers you already corrected
• More stable first-pass booking on line descriptions you fixed before
• Clearer Ready to sync when invalid matches are resolved

Learning does not replace strong rules in the Matching Guide. Promote recurring learned lines into explicit guide text when they are business policy, not one-off exceptions.

4. Tips and limitations

• Feature must be enabled per tenant (Invoice matching learned guidelines (auto)).
• Learning runs on a schedule. Expect days, not minutes, before new corrections appear in matching.
• Noisy corrections (one-time projects) may produce rules you should delete from the learned doc or override in the Matching Guide.
• BU and account learning respects tenant matching policy; disabled features or stripped match fields are not learned.
• Super-admin / admin sync tools may force a guidelines refresh after large correction campaigns.

Quick reference