Context
- Customer: Leaseplan Digital
- Project: External Reporting Data Quality
- Technologies: SAP HANA (native), SAP BW on HANA, DENODO
- Time: 2021
Requirement summary
To comply to the BCBS 239 standard, FinRep reporting must be based on transaction-level data, instead of stand-alone balances.
For this purpose, transaction data of sub-administrations must be reconciled with formal reported GL balances, and differences must be accounted for.
Solution summary
Sub-administration data is loaded into the SAP BW data warehouse on transaction-level, on a monthly basis. It comprises lease contract data, accounts receivables data, customer data.
The values in the sub-administration drive balances of specific general ledger accounts.
The GL account balances are acquired from the reporting and consolidation application (SAP BCS).
Comparing sub-administration with GL balances
In the solution, the monthly sub-administration data is compared to the specified GL account balances for the month, by re-applying account assignment logic on the sub-administrations data.
Differences are compensated for by generating identifiable surrogate sub-administration records, with attribute values that comply to the account assignment logic (for example, surrogate overdue invoice balance references a surrogate customer record which is tagged “in arrears”).
Reporting attributes
Surrogate transaction- and customer attributes is completed with (default) FinRep-properties, to support all required breakdowns. These properties are supplied by the business and fed into the BW system via flat files.
The generated surrogate transactions are combined with the original transactions, and supplied to the FinRep reporting solution via the DENODO application.
