AC-GL-RT1 - Profit and Loss Summary

Applies to

• Product version: Velixo NX,
• ERP: Acumatica
• Functional area: Financials, Other
• Template type: Production Report template

TABLE OF CONTENTS

• Applies to
• Description
• Coverage
• Typical audience
• Features
• Preview
• Download this template
• Documentation
  • Filters
  • P&L structure
• User Guide
  • Using the report
  • Using the As of (Period) filter and understanding Time calculations
  • Using the Control report
  • Understanding the Report Formula
• Customizing the template
  • Reviewing the Options sheet
  • Managing Account Structures
• Version history

Description

Please see Introduction to Report Templates for information about Samples, Demos, and Production Templates and the differences between them.  You many also want to refer to How to Modify Velixo Sample Reports.

The Profit & Loss Summary report is considered a key component in the month-end reporting process and is often used by managers and executives to analyze revenues, expenses and profitability across the business.

This report provides monthly, quarterly and year-to-date variances to both budget and last year’s actuals, enabling the user to easily compare amounts across time. The chart of accounts structure of this report is based on generic account classes which make sure the report is generic, dynamic and consistent with Acumatica. However, you may have changed those account classes or created new ones, and they must be reviewed.

Users can drill down on any cell of the report to analyze the value and see the accounts and transactions that make up the number of each cell.

Coverage

This workbook includes the following sheets:

• Profit & Loss: the Profit & Loss report, at the granularity of account classes, and reporting and Actuals and Budget data across MTD, QTD, YTD and Prior Year YTD.
• Control: a control report that can be used to confirm that the data is accurate and balances.
• Options: the report's settings sheet that used for data validation lists and various lookups and configurations.
• Information: the information sheet of the report, used for storing useful details about the report such as: code, version, article link in order to keep track of the origin of the report.

Typical audience

The typical users of this type of report are Finance professionals: Accountants, CFOs, Controllers 

Features

The following features are used by this report. To use this report, please ensure that your Velixo license includes all of them, (or contact Support or Sales):

• Financial functions
• List functions

Preview

Download this template

Download

Documentation

Navigating and utilizing the Velixo AC-GL-RT2 Profit and Loss Summary report is an intuitive process, designed for simplicity, genericity and efficiency. The template comes pre-configured with generic account classes streamlining the reporting process with minimal user effort.

Filters

Located in the upper left of the sheet, the filters include:

• Branch: lists all the Branches present in Acumatica Instance including any custom group defined in the options sheet. For ease of use, Velixo shows you the Branch ID that you may be familiar with along with the Branch name. This Display name is configurable in the Options sheet.
• As of (Period): a date field. Please use the last date of a financial period/month 
• Include unposted transaction: an option for user to include unposted transactions

These filters are seamlessly linked to the data on the Options tab.

P&L structure

Sections: Velixo has thoughtfully structured the P&L using multiple common sections that should be generic, by default. 

The following sections are used by default and can be customized in the options sheet:

• Revenue
• Cost of Goods Sold
• Operating Expenses
• Non-Operating Expenses
• Other Income
• Other Expenses
• Tax

Generic Account Classes: To enhance the report's usability, Velixo has incorporated a set of predefined account classes. Users have the flexibility to either utilize them as is or tailor them to align with their specific reporting needs.

Metrics: The report includes the following metrics :

• On rows
  • Gross Profit Margin %
  • EBITDA / EBITDA Margin %
  • Net Profit Margin %
• on columns:
  • MTD / QTD / YTD / Prior Year YTD
    • Actual:  the turnover from the beginning of the period up to the date specified in the "As of" filter
    • % of Rev: the share of revenue of the current row (compared to Total (Gross) revenue).
    • Budget: the budget amount from the beginning of the period up to the date specified in the "As of" filter.
  • MTD/QTD/YTD Variance 
    • Var $: The amount difference between the Budget amount and the Actual amount for the period.
    • Var %: The variance ratio between the Budget amount and the Actual amount for the period.
  • Prior YTD YTD
    • Var $: The amount difference between the Prior Year YTD Actual amount and the YTD Actual amount
    • Var %: The variance ratio between the Prior Year YTD Actual amount and the YTD Actual amount 

User Guide

Using the report

Now that we've covered the report overview, let's dive into a step-by-step guide on effectively utilizing the report.

• Set the Connection Name on the Options Sheet - crucial for all processes, set the Connection Name on the Options sheet by updating cell A2. Ensure it matches the name used during Velixo application login.

• Update the Options Sheet: As the foundation for filters on the Profit and Loss report sheet, keep the Options sheet up to date. It should always and automatically capture the latest dimensions and structures from your Acumatica instance; however, you can also customize it.

• Choose Desired Filters - After updating the Options sheet, select desired filters for the report:
  • Branch / Company
  • As of
  • Include unposted transactions

• Automatic Report Update - Selecting any filter will automatically update report balances. Begin analyzing the report with the latest data.

• Validation and analysis: ensure accuracy by verifying balances in the Control sheet. Confirm that differences for each total are zero.

• Variances Investigation: if discrepancies arise between data extracted at the account classes and account code levels, conduct a thorough investigation to resolve any differences.

Using the As of (Period) filter and understanding Time calculations

MTD (Month-To-Date) amounts:

• Returns the movement for the current month up to the specified as-of-date.
• For example, if a user selects January 31st, the returned balance is from January 1st to January 31st.

QTD (Quarter-To-Date) amounts:

• Returns the movement for the current quarter up to the specified as-of date.
• For instance, if a user selects February 28th, the balance returned spans from January 1st to February 28th.
• To obtain the full quarter balance, one would specify the last date of the quarter (e.g., 3/31, 6/30, 9/30, 12/31).

YTD (Year-To-Date) amounts:

• Returns the movement for the current year up to the specified as-of date, using the Fiscal start of year as defined in the Options sheet.
• For example, if a user selects 6/30/2019, and the specified Fiscal start month is April, the returned balance spans from April 1st, 2019, to June 30th, 2019.
• To obtain the full year position, one would specify the last date of the fiscal year.

Prior Year YTD amounts:

• Returns the YTD movement for the corresponding period in the prior year.
• For instance, if a user selects 6/30/2019 with a Fiscal Start Month set to January, the balance returned spans from 1/1/2018 to 6/30/2018.
• Similar to the current month, this does not represent a year-to-date balance but captures only the movement for the specified month.

Using the Control report

Committed to upholding data integrity across the report and Acumatica, the Control sheet serves as a supplementary component to the primary Profit and Loss sheet. Its purpose is to validate the data extracted by Velixo on an account category basis by cross-referencing it with the extracted balances at the account code level.

Given that the balances of the account codes aggregate to the account classes, the Control sheet ensures the absence of discrepancies in the total for each account type. This verification process enhances the reliability and accuracy of the overall financial reporting template.

The Control sheet is divided into three sections:

• Account Code Balance Check: Extracting balances at the account code level to guarantee accurate capture and reconciliation of P&L balances with the account classes listed on the Profit and Loss tab. The Account code series is highly flexible, and users may adjust the settings to match their specific requirements at any time.
• P&L Balances: Displays total balances from the Profit and Loss tab for reconciliation with the Account Code balance section.

Differences: Highlights reconciliatory differences between the Account code and account category sections, marked in red font for investigation

In this P&L summary report, it is crucial that the total balance matches the closing retained earnings for the chosen period. Also, we check for any differences at the overall P&L level, comparing it to the detailed account codes.

If any discrepancies in the report are displayed, it could be caused by a custom structure on the Profit and Loss tab, missing account classes, renamed account classes or any user customizations. 

Understanding the Report Formula

Velixo created the template using a combination of Excel functions and Velixo functions for Profit and Loss report. The report incorporates two primary formulas on the Profit and Loss tab:

• Account Class Validation
  1. In Column A, a validation formula was used to verify if the account category in Column B exists in Acumatica
  2. Invalid values (not in Acumatica) return as blank
  3. Ensure continuous use of this formula for any category additions or name changes; a correctly populated formula ensures accurate transaction amounts.

• Transaction Amount formula
  1. Used in all Actual and Budget columns, this formula’s primary objective is to extract balances for the account class from Acumatica ERP
  2. Velixo function, specifically ACCOUNTTURNOVER, power these columns
  3. To facilitate flawless execution of Velixo functions, an IF statement is strategically placed. 
  4. In the account class validation formula, any invalid classes yield blanks. The IF statement distinguishes whether the class is valid; if not (blank in Column A), the transaction amount formula sets the amount to blank. On the other hand, if the class is valid, it extracts the balance using the Velixo function.

Customizing the template

Reviewing the Options sheet

The Options tab comprises Acumatica dimensions, and other attributes and structures used in the report. This information updates in real-time with Velixo app refresh, facilitating immediate integration of newly added ERP data into the report as filters.

This includes:

• Connection Name
• Branch
• Company
• Quarter

The Connection Name is subject to variation depending on the user input provided through the Velixo login portal. For convenience, users may add the connection name used on cell A2. This cell has been designated as a named range (Connection), ensuring its automatic application to all formulas throughout the sheet.

Users can also customize Branch by adding their preferred custom values, using a list and ranges as described in this article.

To do so:

1. collapse the column groups for the Branch.
2. then simply input the desired values in the Group formula and Custom group name columns, highlighted in light blue for quick identification.

Managing Account Structures

As outlined earlier in this document, users have the flexibility to tailor this report to their specific needs. This is especially useful when the pre-defined account classes do not quite fit the requirements.

• Adding New Account sections

If users desire a structure beyond the pre-defined account classes, they can leverage account classes set up in their ERP instance.

Users have two options when adding new account classes:

1. Re-purposing an existing pre-defined account class:

• Rename an existing account class, replacing it with the desired custom account class.

2. Adding a Row in the Required P&L Section:

• Use Excel functions to add a new row in the desired section.
• Be cautious with formulas in newly added rows; copying from existing rows in the same section ensures accurate results.

• Removing an Account class

Removing a pre-defined account class is not really necessary as the report makes use of Velixo’s automatic hiding of rows with zero values, which has been configured on the Year-to-Date (YTD) Actual values.

This feature eliminates the need for manual deletions of account class rows and ensures the report remains fully dynamic should usage of account classes change over years or transactions get created against new account classes.

However, if an account class should really be deleted:

• Utilize Excel's delete row function for removal, followed by thorough data validation and reconciliation on the report.
• Always validate data accuracy using the Control sheet.

• Grouping Accounts Classes

If needed, the user can group multiple account classes into one and create a summary account class. Velixo enabled this feature so that user can consolidate similar account classes into one and present them in the Profit and Loss as one.

• On Column B of the Profit and Loss tab, user can list all the account groups and using the semi-colon ( ; ) delimiter to grouped them.
• If needed, rename the pre-defined account class on Column D showing the consolidation of the account classes listed on Column B.

• Using of Account Code/Range

As an additional feature, Velixo added the ability to use Account Code or Account Code ranges to extract the balance for the account class.

• On Column C of the Profit and Loss tab, users can list all the account code or ranges they wanted to use or consolidate. Same as account classes, the semi-colon delimiter should be us as well for the groupings.
•  If needed, rename the pre-defined account class on Column D showing the consolidation of the account classes listed on Column B.

Please note that Account Class and Account Code cannot be used at the same time. Doing so will result in calculations errors for the transaction balances. If a structure is not used, make sure to leave them blank to not cause any errors.

Version history