# Checkpoint 334 — Saudi Arabic bank CSV import parsing

**Date:** 2026-10-27  
**Story:** BE-080 — Reconcile bank payments and receipts (**PARTIAL**)

## Change

Accounting KSA's configurable CSV bank-statement parser now normalizes Arabic-Indic and Persian digits, Arabic decimal and thousands separators, bidirectional marks and the Unicode minus sign before interpreting amounts and dates. The bank's column map remains authoritative for column selection and decimal convention; the parser does not infer a bank layout or connect to a bank API.

## Verification

- Added tests for Arabic column headers, Arabic/Persian date digits, Arabic separators, signed payments, and separate debit/credit columns.
- Ran the complete Accounting KSA `TestCsvParser` class on a disposable clone of `namaa_ksa`: **10 tests passed, 0 failures/errors**.
- Disposable database `be_ksa_arabic_bank_csv_5678f439` was dropped after QA; the shared demo database and its business rows were unchanged.
- Evidence: [machine-readable isolated QA](KSA_ARABIC_BANK_CSV_QA.json), [parser](../../addons/accounting_ksa/features/bank_import/parsers/csv_file.py), and [CSV tests](../../addons/accounting_ksa/features/bank_import/tests/test_parser_csv.py).

## Remaining acceptance

BE-080 remains PARTIAL. Saudi bank-specific layouts still require an approved sample/export and a reviewed column map; this change does not provide direct bank connectivity. Banking-role UAT, other tax/write-off policies, broader duplicate/company-boundary cases and full A1–A4 acceptance remain open.
