SAP Invoice Health Check
Invoice and tax reconciliation – diving into the SAP edifice
Stability, depth but complexity
SAP is of course everywhere. However, a quick internet search gives consistent feedback: complexity. And this complexity is not just the implementation and day to day use, it’s reporting and diving into that complexity.
Our data analytics tools proved to be well positioned to enter this world, with their ability to tie together the myriad of tables, look for data inconsistencies and perform analysis at the most granular level before aggregating upwards.
CPRA’s SAP invoice health check

CPRA’s invoice VAT analysis application detects anomalies and potential invoice inaccuracies in SAP invoice data. It’s a line by line bottom up reconciliation analysis and tax data quality check. In general, identifying and correcting any tax issues yourself leads to a far better outcome than the tax authority discovering anomalies via a random audit.
SAP Aggregation levels and Tables
The data structure sometimes does not help, record sets often consist of line items which contain different depths of data: a field which is relevant for all lines in a record set may only by populated for one line item. So data needs to be cascaded (where appropriate) across the line items.
And the data is a mix of line detail, subtotal and grand totals, so even summing across rows is not possible.

Consistency and a Framework
On the other hand, SAP provides structure: consistency of fields names, consistency of flags and metadata. To the extent that SAP has been somewhat conventionally implemented then analysis can become plug and play but we also retain the flexibility to adapt to any client customisation or combine other data sources.
Related Topics
Related case Studies
Inventory Data
Cleaning and consolidating product lines by description and attributes: but it’s not easy if there is no data standardisation
P&L attribution
Delta 1 products can still present a data challenge due to the number of rules involved