Common analytics

Finance module

This unified layer is applied to general ledger accounts, typically from a software’s chart of accounts. Accounts are categorized at various granularities, such as Class, Balance or Income, Category, and Type. For more information on these categorizations, see the Common chart Unified Layer.

Accounts payable

This unified layer is applied to the Accounts Payable pipeline. Use this layer to map columns such as your vendors' AP balances, invoice due dates, and aged days.

It is assumed that all amount columns mapped to this unified layer are already currency converted to the Main currency. If amounts are not currency converted when they are mapped, cross-company reporting may not work as expected.

Accounts receivable

This unified layer is applied to the Accounts Receivable pipeline. Use this layer to map columns such as your customers' AR balances, invoice due dates, and aged days.

In order to take advantage of Collection effectiveness metrics, it is important to map the following CEI columns in the unified layer: AR paid after due month, AR paid before a due month but after posting, AR paid in the due month, AR pre-paid or paid in the posted month, Current not paid receivables, Sales, Total AR for future payments, Total AR for past payments, Total AR for unpaid open items.

Budget scenario

This unified layer is applied to general ledger budget pipelines which provide the list of budget scenarios. Depending on the ERP or accounting software, these may be referred to as Budget Types, Codes, Versions, or Models. The list of budget scenarios is used by the 'Ledger Actuals Budget' pipeline and can be used to compare actual with budget financial data.

Common chart

The purpose of this unified layer is to generically categorize the general ledger accounts of an enterprise application or accounting software into common classes, categories, and types. Each of these classifications has its own granularity which is useful in reporting and can make up a hierarchy of Class->Category->Type.

Tip

An account may be mapped to one of the following 'Common Classes': Assets, Liabilities, Equity, Revenue, Expenses, Other Income, Other Expenses.
An account may be mapped to a 'Common Category' such as Current Assets, Non-Current Assets, Current Liabilities, Non-Current Liabilities, General Expenses, etc.
An account may be mapped to a 'Common Account Type' such as Cash, Accounts Receivable, Inventory, Intangible Assets, Interest Payable, etc.

Debit/Credit

Flag indicating whether the transaction is a debit or a credit.

General ledger

The General ledger unified layer is applied to the pipeline that combines general ledger actual and budget data (if available). Use of this unified layer will allow seamless reporting across GL actuals and budgets for financial reporting across companies, charts of accounts, and segments, where applicable.

If Ledger Actual and Budget information is stored in different tables in the source, it is necessary to combine them into one table to make use of this unified layer. Ensure that the tables have at least the following columns in common before combining them (for example, using a union), to ensure the correct granularity: Account code, Common Account Type, Company, Date, Amount.

Inventory module

Inventory transactions

This unified layer is applied to the pipeline in the data model containing data from inventory movement tables. Map inventory quantities and valuation from here.

Stock in warehouse

This unified layer is applied to the pipeline which has information regarding on-hand quantities for inventory warehouses. Columns to be mapped here include the items or products, their quantities, units, and groups.

Units

The Units unified layer is applied to the pipeline containing information for units used in the ERP or accounting software transactions, eg Sales unit, purchase a unit, etc. The Units layer will map the unit and its grouping.

Procurement module

Purchase invoice lines

This unified layer is applied to the pipeline containing data for purchase invoice line transactions (also called Receipt lines). Purchase price variance (PPV), Purchase Invoice Amount, and Quantity can be mapped here.

Credit memos and return transactions should be included in the pipeline that is mapped to this layer.

Purchase order lines

The Purchase order lines unified layer is applied to the Purchase order lines pipeline, which contains information about purchase orders such as order amount, quantity, and dates. Delivery performance metrics can be derived from the columns in this unified layer.

Sales module

Sales invoice lines

This unified layer is applied to the pipeline containing data for sales invoice line transactions. Cost of Sales, Sales Invoice Amount, and Quantity can be mapped here, as well as any statuses. The Sales invoice lines unified layer also provides the opportunity to perform cross-ledger reporting with Sales budgets.

If Sales Actual and Budget information is stored in different tables in the source, it is necessary to combine them into one table to make use of this unified layer. Ensure that the tables have at least the following columns in common before combining them (for example, using a union), to ensure the correct granularity: Company, Date, Amount.