Add GL-001 OpenXML simulation outputs
This commit is contained in:
@@ -36,6 +36,7 @@ It is intended to prepare the future mapping with the target CTRM / ERP. The map
|
||||
| `counterparty` | Customer, supplier, broker or other party. | `GL-001`, `GL-002` |
|
||||
| `credit_base_currency` | Credit amount or movement in base currency. | `GL-001`, `GL-002`, `FIN-003`, `AR-001`, `AR-003`, `AP-001`, `AP-003` |
|
||||
| `credit_transaction_currency` | Credit amount or movement in transaction currency. | `GL-001`, `GL-002`, `FIN-003`, `AR-001`, `AR-003`, `AP-001`, `AP-003` |
|
||||
| `Currency_Rate` | FX rate applied to convert the transaction-currency amount to base currency for the GL-001 line. | `GL-001` |
|
||||
| `customer` | Customer account code. | `AR-001`, `AR-002`, `AR-003` |
|
||||
| `customer_name` | Customer legal or commercial name. | `AR-001`, `AR-002`, `AR-003` |
|
||||
| `customer_reference` | Customer reference or external customer document reference, when available. | `AR-003` |
|
||||
@@ -95,6 +96,7 @@ It is intended to prepare the future mapping with the target CTRM / ERP. The map
|
||||
| `settlement_status` | Open, partially settled, settled and reversed logic depends on the ERP subledger. |
|
||||
| `voucher_number` | Should be mapped only if it is distinct from `document_number`, `supplier_invoice_number`, customer references and payment references. |
|
||||
| `supplier_invoice_number` | May map to a vendor invoice number, supplier reference or AP invoice field depending on ERP terminology. |
|
||||
| `Currency_Rate` | GL-001-specific FX-rate field; mapping must confirm rate source, rate date, direct versus inverse convention, precision and naming convention. |
|
||||
| `purchase_invoice_number` | Should be mapped only if the ERP exposes a separate internal purchase invoice number. |
|
||||
| `customer_reference` | Should be mapped only if the ERP exposes a distinct customer-facing reference. |
|
||||
| `payment_reference` | Should be mapped only if payment references are stored separately from document references. |
|
||||
|
||||
@@ -19,6 +19,15 @@ These conventions define the default reporting vocabulary and presentation rules
|
||||
|
||||
There is no separate `reporting_currency` in the current reporting scope.
|
||||
|
||||
When a report exposes an FX rate between transaction currency and base currency, it should document:
|
||||
|
||||
- the rate source;
|
||||
- the rate date;
|
||||
- whether the rate is direct or inverse;
|
||||
- the number of decimal places preserved in the export.
|
||||
|
||||
`GL-001 General Ledger` currently defines the FX-rate field as `Currency_Rate`. This report-specific name should be preserved in GL-001 exports until the field naming convention is explicitly harmonized.
|
||||
|
||||
---
|
||||
|
||||
## Amount fields
|
||||
|
||||
Reference in New Issue
Block a user