Features

• Counterpart map per account — account.account.l10n_ro_counterpart_id is a many2many to itself through account_counterpart_rel, listing every account that the selected account can be balanced against in a Romanian journal entry.
• Bundled Plan de Corespondență — data/plan_corespondenta.csv ships the official prefix-based mapping for the Romanian Chart of Accounts (e.g. 103 → 101|501|643|665|765); accounts are matched by code_store.startswith(prefix).
• Stored computed counterpart on each line — account.move.line.l10n_ro_counterpart_id and l10n_ro_counterpart_line_id are computed and stored, depending on parent_state and the account's counterpart list. Only posted lines on Romanian companies are populated.
• Sign-based pairing — for each posted line, the compute picks opposite-sign lines on the same move and keeps the one whose account is in the counterpart list. This handles two-leg entries (cash receipts, bank statements) and multi-line entries (purchases with tax) consistently.
• Pre-init hook for fast install — pre_init_hook adds the two columns directly via SQL so the install does not trigger a full ORM-side recomputation on existing databases.
• One-click loader — Accounting → Configuration → Settings → Load Romanian Counterpart Accounts parses the CSV and inserts the pairs directly into account_counterpart_rel (raw SQL, no per-record write).
• Recompute server action — Action → Recompute Romanian Counterparts on the journal-item list, scoped to account.group_account_user.

Configuration

You need accounting manager rights (account.group_account_manager) and an installed Romanian Chart of Accounts.

1. Load the counterpart accounts map

1. Open Accounting → Configuration → Settings.
2. Find the Load Romania Account Counterparts setting block and tick Load Romanian Counterpart Accounts.
3. Save the settings.

The save triggers _add_l10n_ro_account_counterparts(), which reads data/plan_corespondenta.csv, matches each row by code prefix against your company's accounts, and inserts the pairs into account_counterpart_rel using raw SQL — no recompute is triggered during the import.

Run this on a fresh database whenever possible. If you install on an existing live database, the field is computed lazily on each subsequent posted move; you can also batch-refresh historical lines from the action below.

2. Adjust the map per account (optional)

Open Accounting → Configuration → Chart of Accounts, then open any Romanian account. Under the Accounting page, the Romania - Counterparts many2many tag widget lets you add or remove counterpart accounts for that account.

These per-account changes take effect on new posted journal items immediately. To refresh historical lines, see step 3.

3. Recompute counterparts on existing lines

From any journal-item list (Accounting → Journal Entries → Journal Items), filter the lines you want, then click Action → Recompute Romanian Counterparts. The server action is available to users in the Accounting / Billing group (account.group_account_user).

Only Romanian posted lines without a counterpart are reprocessed.

4. Multi-company

The loader is scoped per company (comp_accounts = … .with_company(self) filtered by company_ids). Re-run the toggle in each company's settings if you need the map loaded everywhere.

How it works

Once the counterpart map is loaded, every Romanian posted journal item gets its counterpart account and counterpart line filled in automatically. There is no UI flow to run by hand — the fields are stored on account.move.line and update as you post entries.

Where you see counterparts

• Journal Items list (Accounting → Journal Entries → Journal Items) — a new Romania - Counterpart Account column.
• Journal Item form — the counterpart account and counterpart line appear next to the regular Account field.
• Pivot / search / group-by — both fields are indexed and can be used as group-by axes (e.g. cash account by counterpart) or as a filter (e.g. bank account 5121 grouped by counterpart account).

Counterpart selection logic

For each posted line on a Romanian company:

1. Look at the other lines on the same move.
2. Keep the ones with opposite sign on amount_currency.
3. Among those, keep the line whose account_id belongs to the account's l10n_ro_counterpart_id list.
4. The first match wins; both the account and the specific line are stored.

For balanced two-leg entries (typical for bank statements, cash receipts, manual journal vouchers) the counterpart is unambiguous. For multi-line entries (e.g. a vendor bill with VAT) the result is the counterpart account that matches the bundled plan_corespondenta.csv, so the cash-book / journal-book reports group lines on the right column.

Refreshing existing data

If you change the per-account counterpart list, run Action → Recompute Romanian Counterparts on the journal-item list to refresh the lines you just modified. Only lines whose l10n_ro_counterpart_id is empty are recomputed, so the action is safe to run repeatedly.

Versions

19.0.0.1.0 (2026-05-24)

• Changelog tracking starts at this release.