2.2 KiB
Reporting Standards
These conventions define the default reporting vocabulary and presentation rules. A report may define a specific exception when its functional layout requires it.
Date fields
posting_datevalue_datedocument_date
Currency fields
transaction_currencybase_currency
There is no separate reporting_currency in the current reporting scope.
Amount fields
debitcreditbalance
When currency-specific amount fields are required, use the suffix:
_transaction_currency_base_currency
Examples:
debit_transaction_currencycredit_transaction_currencybalance_transaction_currencydebit_base_currencycredit_base_currencybalance_base_currency
Posting status
When exposed by the ERP, reports should include posting_status as an informational field.
The field should identify whether the source transaction is posted, non-posted, reversed, cancelled, pending or another ERP-specific status.
posting_status is not a standard filter by default. Each report should keep an open question until the target ERP confirms whether this field is available and which status values should be mapped.
Sign conventions
General financial statement sign conventions:
- Assets: positive debit
- Liabilities: positive credit
- Revenue: positive credit
- Expenses: positive debit
These sign conventions apply to financial statement presentation and summary reports. Detail ledger reports may define their own sign convention when required.
For GL-001 General Ledger, debit amounts are positive and credit amounts are negative, as specified in the report definition.
Sorting conventions
Default sorting for accounting detail reports:
accounttransaction_currencyposting_datedocument_number
Drill-down conventions
Summary reports should define the expected drill-down path from summarized balances to supporting detail.
Default drill-down path:
- summarized balance or statement line;
- underlying account, customer, supplier or open item movements;
- accounting document or journal entry;
- source document, when available in the ERP.