# GL-001 Tradon Development Backlog

Disposable draft created from `Assessments/Tradon/GL_001/`.

This file is a working conversion layer between the documented GL-001 gaps and future development tickets. It is intentionally conservative: items remain `Blocked` where mapping, business or architecture decisions are still open.

## Traceability sources

| Type | Reference |
| --- | --- |
| Target report | `Reports/GL/GL_001_general_ledger.md` |
| Assessment | `Assessments/Tradon/GL_001/` |
| Gap mapping | `Assessments/Tradon/GL_001/gap_mapping.md` |
| Open points | `Assessments/Tradon/GL_001/open_points.md` |
| Decisions | `Assessments/Tradon/GL_001/decisions.md` |
| Retained source | `Assessments/Tradon/GL_001/source_documents/general_ledger_gap_analysis.md` |

## Summary

| ID | Priority | Status | Theme | Depends on |
| --- | --- | --- | --- | --- |
| DEV-GL001-001 | High | Blocked | Flat detailed GL dataset | GL001-PD006 |
| DEV-GL001-002 | High | Blocked | Transaction-currency grouping and balances | GL001-PD002, GL001-Q009 |
| DEV-GL001-003 | High | Blocked | Opening and closing rows | GL001-PD006, GL001-Q009 |
| DEV-GL001-004 | High | Blocked | Document and reference mapping | GL001-PD001 |
| DEV-GL001-005 | High | Blocked | Source document metadata | GL001-PD004 |
| DEV-GL001-006 | Medium | Blocked | Transaction-currency debit and credit split | GL001-PD002 |
| DEV-GL001-007 | Medium | Blocked | GL sign convention transformation | GL001-PD003 |
| DEV-GL001-008 | Medium | Blocked | Audit metadata columns | GL001-PD007 |
| DEV-GL001-009 | Medium | Blocked | CSV and XLSX export | DEV-GL001-001 |
| DEV-GL001-010 | Low | Blocked | Commodity quantity fields | GL001-PD005 |

## DEV-GL001-001 Flat detailed GL dataset

| Field | Value |
| --- | --- |
| Source gap | Build or expose a flat detailed GL dataset matching `GL-001`, not only account summary plus drill-down |
| Linked questions | GL001-Q008 |
| Linked decision | GL001-PD006 |
| Priority | High |
| Status | Blocked |

Development scope:

- Provide one export-ready GL-001 dataset that combines account context and detailed move lines.
- Include one row structure capable of representing opening rows, movement lines and closing rows.
- Support the target GL-001 ordering: account, transaction currency, posting date, document number.

Out of scope:

- Final source table or SQL design until GL001-PD006 is confirmed.
- Commodity-specific fields, handled by DEV-GL001-010.

Acceptance criteria:

- A consumer can retrieve all required GL-001 output columns from one logical dataset or service.
- Account summary and line drill-down no longer have to be manually combined outside the reporting layer.
- Dataset rows can be typed as opening, movement or closing without ambiguous interpretation.

Validation:

- Compare base-currency movement totals with existing Tryton general ledger totals for the same period and account selection.

## DEV-GL001-002 Transaction-currency grouping and balances

| Field | Value |
| --- | --- |
| Source gap | Add transaction-currency grouping, filtering and running balances |
| Linked questions | GL001-Q004, GL001-Q009 |
| Linked decisions | GL001-PD002 |
| Priority | High |
| Status | Blocked |

Development scope:

- Add transaction currency as a grouping key for GL-001.
- Add transaction-currency filtering where supported by the selected implementation design.
- Calculate or expose `balance_transaction_currency`.

Out of scope:

- Deciding whether empty `second_currency` means company currency; this is GL001-PD002.

Acceptance criteria:

- GL-001 can be grouped by account and transaction currency.
- Running transaction-currency balances are available for movement rows.
- Base-currency lines have a documented transaction-currency fallback or exclusion rule.

Validation:

- For each account and transaction currency, opening plus movements equals closing once DEV-GL001-003 is available.

## DEV-GL001-003 Opening and closing rows

| Field | Value |
| --- | --- |
| Source gap | Add opening and closing rows by account and transaction currency |
| Linked questions | GL001-Q009 |
| Linked decisions | GL001-PD006 |
| Priority | High |
| Status | Blocked |

Development scope:

- Add explicit opening balance rows by account and transaction currency.
- Add explicit closing balance rows by account and transaction currency.
- Ensure movement rows sit between opening and closing rows in the exported ordering.

Out of scope:

- Storage versus reporting-layer calculation decision for transaction-currency opening balances.

Acceptance criteria:

- Each account and transaction-currency group has an opening row when relevant.
- Each account and transaction-currency group has a closing row when relevant.
- Opening, movement and closing row types are machine-readable in the dataset or export.

Validation:

- Opening balance plus period movements reconciles to closing balance for each account and transaction currency.

## DEV-GL001-004 Document and reference mapping

| Field | Value |
| --- | --- |
| Source gap | Define mapping for `document_number`, `journal_entry_number`, `voucher_number` and `reference` |
| Linked questions | GL001-Q001, GL001-Q002, GL001-Q003 |
| Linked decision | GL001-PD001 |
| Priority | High |
| Status | Blocked |

Development scope:

- Implement confirmed mappings for the GL-001 document and reference fields.
- Preserve enough information to trace each line back to the accounting document and source document.

Out of scope:

- Choosing the final business meaning of each reference field.

Acceptance criteria:

- `document_number`, `journal_entry_number`, `voucher_number` and `reference` follow the confirmed decision.
- Fields are populated consistently for accounting moves and AP-originated entries.
- Empty optional values are intentionally blank, not silently overloaded.

Validation:

- Sample accounting entries can be traced from GL-001 output back to the accounting move and, where available, source invoice.

## DEV-GL001-005 Source document metadata

| Field | Value |
| --- | --- |
| Source gap | Normalize source document metadata: document type, document date and supplier invoice number |
| Linked questions | GL001-Q006, GL001-Q012 |
| Linked decision | GL001-PD004 |
| Priority | High |
| Status | Blocked |

Development scope:

- Populate `document_type`, `document_date` and `supplier_invoice_number` according to confirmed origin-model rules.
- Support AP-related entries where supplier invoice information is available.

Out of scope:

- Commodity quantity mapping, handled by DEV-GL001-010.

Acceptance criteria:

- GL-001 exposes normalized source document metadata for confirmed origin models.
- AP-related entries include `supplier_invoice_number` when available.
- Non-AP entries follow a documented fallback or blank rule.

Validation:

- Review a sample containing AP invoices, manual journal entries and other available origin types.

## DEV-GL001-006 Transaction-currency debit and credit split

| Field | Value |
| --- | --- |
| Source gap | Split `amount_second_currency` into debit and credit transaction-currency columns |
| Linked questions | GL001-Q004 |
| Linked decision | GL001-PD002 |
| Priority | Medium |
| Status | Blocked |

Development scope:

- Derive `debit_transaction_currency` and `credit_transaction_currency` from signed transaction-currency amounts.
- Apply the same transaction-currency fallback rule used by DEV-GL001-002.

Out of scope:

- GL credit sign convention, handled by DEV-GL001-007.

Acceptance criteria:

- Debit and credit transaction-currency columns are populated deterministically.
- Zero, blank and base-currency-only cases follow documented rules.

Validation:

- Transaction-currency debit and credit totals reconcile to movement totals by account and currency.

## DEV-GL001-007 GL sign convention transformation

| Field | Value |
| --- | --- |
| Source gap | Decide and implement GL sign convention transformation for credit columns |
| Linked questions | GL001-Q005 |
| Linked decision | GL001-PD003 |
| Priority | Medium |
| Status | Blocked |

Development scope:

- Apply the confirmed GL-001 display convention for debit, credit and balances.
- Ensure base-currency and transaction-currency amounts use consistent signs.

Out of scope:

- Changing Tryton accounting storage or standard UI conventions.

Acceptance criteria:

- `debit_*` amounts are positive.
- `credit_*` amounts follow the confirmed GL-001 convention.
- Running balances are consistent with the exported debit and credit signs.

Validation:

- Sample entries reconcile between source Tryton amounts and GL-001 export amounts after documented transformation.

## DEV-GL001-008 Audit metadata columns

| Field | Value |
| --- | --- |
| Source gap | Add audit columns `entered_by`, `entered_date`, `modified_by` and `modified_date` |
| Linked questions | GL001-Q010 |
| Linked decision | GL001-PD007 |
| Priority | Medium |
| Status | Blocked |

Development scope:

- Expose creation and modification metadata for GL-001 rows where available.
- Use consistent user and timestamp formatting across the report.

Out of scope:

- Defining shared audit mappings for all accounting reports unless GL001-Q010 is resolved that way.

Acceptance criteria:

- GL-001 includes `entered_by`, `entered_date`, `modified_by` and `modified_date`.
- Missing metadata is handled consistently and visibly.

Validation:

- Compare exported values against source record creation and modification metadata for a sample of move lines.

## DEV-GL001-009 CSV and XLSX export

| Field | Value |
| --- | --- |
| Source gap | Add dedicated CSV / XLSX export target |
| Linked dependency | DEV-GL001-001 |
| Priority | Medium |
| Status | Blocked |

Development scope:

- Provide CSV and XLSX exports for the GL-001 flat dataset.
- Preserve column order from `Reports/GL/GL_001_general_ledger.md`.

Out of scope:

- Wide PDF export unless separately prioritized.

Acceptance criteria:

- CSV export includes all required GL-001 columns.
- XLSX export includes all required GL-001 columns.
- Column names match the report specification.

Validation:

- Exported row counts and totals match the underlying GL-001 dataset for the same parameters.

## DEV-GL001-010 Commodity quantity fields

| Field | Value |
| --- | --- |
| Source gap | Add `payable_qty` and `uom` for commodity-related postings using Tradon lot, invoice or fee links |
| Linked questions | GL001-Q007, GL001-Q013 |
| Linked decision | GL001-PD005 |
| Priority | Low |
| Status | Blocked |

Development scope:

- Populate `payable_qty` and `uom` for commodity-related postings if retained for first implementation.
- Document blank behavior for non-commodity postings.

Out of scope:

- Making commodity fields mandatory for all GL-001 rows.

Acceptance criteria:

- Commodity-related GL rows expose payable quantity and unit of measure when source data is reliably available.
- Non-commodity rows remain blank or follow a documented rule.

Validation:

- Review a sample of commodity AP postings against source invoice, lot or fee evidence.