Consolidate GL-001 TradOn assessment decisions

This commit is contained in:
GiorgioCALLIGARO
2026-05-08 12:31:28 +02:00
parent 4ce9711c3f
commit c344be9dff
13 changed files with 918 additions and 396 deletions

View File

@@ -38,9 +38,9 @@ Standard parameters:
- `date_from`
- `date_to`
- `account`
- `currency`
- `currency` (transaction currency)
- `journal`
- `entity`
- `entity` (current TradOn company context for the first implementation)
Additional filter parameters out of scope for this report:
@@ -54,9 +54,9 @@ Additional filter parameters out of scope for this report:
- posting date between `date_from` and `date_to`;
- account or account range;
- currency;
- transaction currency;
- journal;
- entity;
- entity through the current TradOn company context;
- document number or voucher number, if available.
---
@@ -92,23 +92,20 @@ Totals should be displayed by:
- base currency;
- report total.
Optional grouping to confirm:
- entity.
Out of scope grouping:
- journal;
- entity;
- counterparty;
- analytic account;
- profit center.
Balance presentation:
- opening balance rows should be displayed by account and transaction currency;
- closing balance rows should be displayed by account and transaction currency;
- opening and closing balances should be shown in transaction currency and base currency;
- running balances should be calculated line by line between opening and closing balance rows.
- initial and ending balances should be displayed as rolling balances on each transaction line by account and transaction currency;
- initial and ending balances should be shown in transaction currency and base currency;
- transaction-line initial balances should represent the balance immediately before the transaction line;
- transaction-line ending balances should represent the balance immediately after the transaction line.
---
@@ -121,7 +118,7 @@ Required columns:
| `entity` | Legal entity or company code |
| `account` | General ledger account code |
| `account_name` | General ledger account name |
| `transaction_currency` | Original transaction currency |
| `transaction_currency` | Original transaction currency, defaulting to `base_currency` when no distinct transaction currency is stored |
| `base_currency` | Functional or company base currency |
| `posting_date` | Accounting posting date |
| `document_date` | Source document date |
@@ -137,13 +134,15 @@ Required columns:
| `reference` | External or source reference |
| `payable_qty` | Payable quantity for commodity-related postings only |
| `uom` | Unit of measure for payable quantity |
| `initial_balance_transaction_currency` | Rolling balance of the account and transaction currency immediately before the transaction line |
| `debit_transaction_currency` | Debit amount in transaction currency |
| `credit_transaction_currency` | Credit amount in transaction currency |
| `balance_transaction_currency` | Running balance in transaction currency |
| `Currency_Rate` | FX rate of the transaction |
| `ending_balance_transaction_currency` | Rolling balance in transaction currency immediately after the transaction line |
| `currency_rate` | FX rate of the transaction |
| `initial_balance_base_currency` | Rolling balance in base currency immediately before the transaction line |
| `debit_base_currency` | Debit amount in base currency |
| `credit_base_currency` | Credit amount in base currency |
| `balance_base_currency` | Running balance in base currency |
| `ending_balance_base_currency` | Rolling balance in base currency immediately after the transaction line |
| `entered_date` | Entry creation date |
| `entered_by` | User who created the entry |
| `modified_date` | Last modification date |
@@ -156,14 +155,26 @@ The report should display individual accounts only. Account hierarchy levels are
Amount sign convention for this report:
- debit amounts are displayed as positive amounts;
- credit amounts are displayed as negative amounts;
- running balances are calculated using this debit-positive and credit-negative convention.
- credit amounts are displayed as positive amounts, following the current Tryton convention;
- ending balances are calculated using this debit-positive and credit-positive convention;
- `ending_balance_transaction_currency` equals `initial_balance_transaction_currency` plus `debit_transaction_currency` minus `credit_transaction_currency`;
- `ending_balance_base_currency` equals `initial_balance_base_currency` plus `debit_base_currency` minus `credit_base_currency`.
Initial balance convention:
- for the first transaction line in each account and transaction-currency group, the initial balance date is the day before `date_from`;
- for balance sheet accounts, the first line initial balance should equal the account balance up to and including the day before `date_from`;
- for profit and loss accounts, the first line initial balance should equal the movement balance from the start of the fiscal year up to and including the day before `date_from`;
- balance sheet versus profit and loss classification should use the Tryton / TradOn account classification;
- for subsequent transaction lines, the initial balance should equal the previous transaction line's ending balance in the same account and transaction-currency group.
FX rate presentation for this report:
- `Currency_Rate` should display the FX rate used to convert transaction-currency amounts into base-currency amounts;
- for same-currency transactions, `Currency_Rate` should be either `1.000000` or blank according to the confirmed ERP export convention;
- the source of the rate, rate date, direct versus inverse convention and precision remain to be confirmed during mapping.
- `currency_rate` should display the stored accounting move line rate used to convert transaction-currency amounts into base-currency amounts;
- when the stored accounting rate is expressed as `1 accounting currency = x transaction currency`, `currency_rate` should display that rate;
- when the stored accounting rate is expressed as `x accounting currency = 1 transaction currency`, `currency_rate` should display the reverse stored accounting rate;
- for same-currency transactions, `currency_rate` should be either `1.000000` or blank according to the confirmed ERP export convention;
- the rate date and precision remain to be confirmed during mapping.
---
@@ -179,24 +190,29 @@ The report may contain a large number of accounting lines and should support exp
- CSV
- XLSX
- PDF, including all detail columns
Out of scope for the first implementation:
- PDF export
---
## 11 Controls / reconciliation rules
- Total debit and credit amounts should reconcile by selected period, account and transaction currency.
- For each account and transaction currency grouping, opening balance plus movements should reconcile to closing balance.
- For each account and transaction currency grouping, first-line initial balance plus cumulative movements should reconcile to the final line ending balance.
- The report total in base currency should reconcile with the trial balance for the same entity, period and account selection.
- For non-base-currency lines, transaction-currency amounts, `Currency_Rate` and base-currency amounts should reconcile within the agreed rounding tolerance.
- For non-base-currency lines, transaction-currency amounts, `currency_rate` and base-currency amounts should reconcile within the agreed rounding tolerance.
- Each line should retain enough audit references to trace back to the accounting document and source document where available.
- AP-related entries should be identifiable by both `document_number` and `supplier_invoice_number` when the supplier invoice number is available.
- Debit, credit and balance signs should follow the GL-specific convention defined in this report.
- Debit, credit, initial balance and ending balance signs should follow the GL-specific convention defined in this report.
---
## 12 Open questions
- Which source should be used for `document_number`, `journal_entry_number`, `voucher_number` and `reference` when several accounting or source-document references are available?
- Which source origin models should feed `document_date`, `document_type` and `supplier_invoice_number` in the first implementation?
- Should `posting_status` be displayed in the first implementation? This depends on the target ERP capabilities.
- Should `Currency_Rate` use the ERP stored accounting rate, a reporting FX rate, or a derived rate from transaction/base amounts?
- Should `Currency_Rate` remain capitalized as currently specified, or be renamed to `currency_rate` to match the wider field naming convention?
- Are `payable_qty` and `uom` mandatory for the GL-001 launch, or can they remain optional commodity extensions?
- Should the document or voucher number filter search only `document_number` and `voucher_number`, or also `journal_entry_number`, `reference` and `supplier_invoice_number`?