Party-name lookup at Create & Reconcile previously used a strict (strip-only) key, so a Bank Transaction whose bank_party_name differed in casing from the registry record would never resolve a party. Now: - 'Ignore Case in Party Matching' Check on Bank Integration (default ON) sets the global behaviour: party names are indexed under both their strict and lowercase forms, and the lookup tries both. - 'Case Mode' Select on each Customer / Supplier Mapping row overrides the global for that specific party — blank inherits, "Ignore Case" / "Case Sensitive" forces the mode regardless of the global setting. Honours the established "row > global" priority pattern used elsewhere. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| jey_erp | ||
| .gitignore | ||
| BANK_INTEGRATION_PLAN.md | ||
| README.md | ||
| TASK_CONTEXT.md | ||
| license.txt | ||
| pyproject.toml | ||
README.md
Jey Erp
Azerbaijan localization for JeyERP
License
unlicense