TAG LINE
TAG LINE
SMALL TITLE
BUTTON
Product Overview
Becoming familiar with the foundational concepts of LogiSense billing
Introduction
Product Vision
Usage Billing Challenges
LogiSense Billing UI Walkthrough
Terminology
Quick Start Guide
Release Notes
- LogiSense Billing 10.4.x Release Notes
- LogiSense Billing 10.5.x Release Notes
- LogiSense Billing 10.6.x Release Notes
- LogiSense Billing 10.7.x Release Notes
Accounts
Adding all of your customers and their products to the system
Account Overview Screen
Account Packages Screen
- Account Package Example
- Billing an Account Example
Account Settings Screen
Account Credits Screen
- Adding and Disbursing a Credit Example
Account Transactions Screen
- Adding a Transaction Example
Account Notes Screen
Account Contacts Screen
- Adding Account Contacts Example
Creating a New Account Screen
- New Account Creation Example
- Child Account Creation Example
Admin - Configuration
Configure all your system settings and user permissions
Owner Configuration Screen
- Financial Settings Example
- Password Policy Example
- Branding Example
- Automatic Naming Example
- Locales Example
- Payment Types Example
SMTP Settings Screen
- SMTP Example
Account Types Screen
- Account Types Example
Account Status Types Screen
- Account Status Types Example
Contact Types Screen
- Contact Types Example
Users and Roles
Users Screen
- User Example
Roles Screen
- Role Example
Role Groups Screen
- Role Group Example
Billing - Configuration
Group your customers into groups that bill in a similar fashion
Bill Runs Screen
- Bill Run Example
- Bill Run Auto-Pay Example
Bill Run History Screen
Bill Groups Screen
- Bill Group Example
General Ledger Codes Screen
- General Ledger (GL) Code Example
Contracts & Commitments
Ensure you are enforcing the contract commitments from your customers
Account Contracts Screen
- Commitments and Ramp Up Periods
- Early Termination
- Account Contract Example
Account Contract Status Types Screen
- Account Contract Status Types Example
Package Contracts Screen
- Package Contract Example
Customer Experience
Provide the best posssible experience from your billing touchpoints
Customer Portal
Email Templates
- Dunning/Payment Overdue Email Template Example
Dunning & Collections
Automate your collections and notification processes
Accounts Receivable Terms Screen
- Accounts Receivable Terms Example
Payment Terms Screen
- Payment Terms Example
Dunning Rules Screen
- Dunning Rules Example
Extensibility
Configure extra custom fields to cover unique scenarios
Custom Fields Screen
Custom Fields Layouts Screen
Importing & Exporting Data
Perform transforms on data that you wish to import into the system
Archiving Data
Data Imports
- Data Profiles
- Mapping
- Transforms
- Validations
- Debugging
Data Profiles Screen
Data Imports Screen
Invoicing & Credit Notes
Design your invoice templates and manage account invoices and credit notes
Account Invoices Screen
- Invoice Management Example
Account Credit Notes Screen
Invoice Delivery Screen
- Invoice Delivery Example
Invoice & Credit Notes Templates Screen
- Word Invoice Template Mail Merge Tips
- Embedding Reports in Invoice Templates
- Invoice Template Example
Rounding Behavior
Notifications & Events
Subscribe to different system events to trigger integration workflows
Available Events
Available Event Tokens
Notifications Screen
Payments
Record automatic payments or manually disburse amounts
Account Payment Methods Screen
Account Payments Screen
- Payments Example
Payment Gateway Screen
- Payment Gateway Example
Pricing
Explore different pricing options and customer specific catalogs
Account Price Plans Screen
Tiered Monthly Recurring Charge
Tiered Usage
Counting Rules for Tiered Pricing
Price Book Regions Screen
Price Books Screen
Product Catalog
Add all of our products and services to the product catalog
Services Screen
- Service Example
Service Status Screen
- Service Status Example
Service Transitions Screen
- Service Transitions Example
Service Types Screen
- Service Type Example
Packages Screen
- Recurring and One Time Charges Package Example
- Global Add-on Package Example
- Toll Free & Trunk Groups Products Use Case
Package Frequencies Screen
Package Status Screen
- Package Status Example
Counting Rules Screen
Promo Codes Screen
Regional & Currency Settings
Setup all of your regonal settings including multiple currencies
Configuring Countries
- Regional Settings Example
Configuring State/Province
Multi-Currency
Currency Exchange Screen
- Currency Exchange Example
Exchange History Screen
Reporting & Analytics
Dig into your billing data for the analytics you need
Charts & Dashboards
Generating, Viewing and Downloading Reports
Filtering, Generating and Downloading Reports Example
Revenue Recognition
Recognizing the monetary value of a transaction or contract over time
Revenue Recognition Configuration
IFRS 15 and ASC 606
Salesforce Integration
Connect LogiSense Billing to Salesforce to automate your quote-to-cash
Salesforce Admin Guide
- LogiSense Billing Configuration
- Salesforce (Pre App Installation Process)
- Salesforce (app installation)
- Connecting Salesforce to LogiSense Billing
- Account Field Mapping
- Package Field Mapping
- Contact Field Mapping
- Order Product Field Mapping
- Order Product Service Field Mapping
- Account Invoice List
- Importing and Syncing Data
- LogiSense Requests (API Logs)
Salesforce User Guide
Sales Orders
Combine multiple products into a single order for an account
Account Orders Screen
Share Plans
Configure share plans to share usage across multiple services
Account Share Plans Screen
Share Plans Screen
Share Plan Buckets Screen
Single Sign On
Single Sign On Configuration
Taxes
Manage your tax setup and integration with 3rd parties
Tax Codes Screen
Tax Vendor Screen
- LogiSense Tax Example
Tax Rates Screen
Service Tax Categories Screen
Account Tax Categories Screen
Usage & Rating
Create flexible usage pricing and transform event data
Usage Rate Groups Screen
Usage Rates Screen
Usage Rate Plans Screen
Usage Classes Screen
Usage Class Types Screen
GeoTree Screen
Rounding Rules
Time Periods Screen
Location Groups Screen
Mediation
Usage Data Feeds
Import Usage by API
Billing Activation Rules
Dynamic Usage Classes Screen
Usage Exceptions
- Exceptions Screen
- No UDR Usage Identifier match
- UDR time does not match time period of UDR Usage Identifier
- Usage Rate matching UDR not found
- Usage Rate Group matching UDR not found
- Usage Rate Plan not defined
- Final Usage Bill issued
- Software System Error
Use For Cost Configuration
Usage Buckets
Create definitions of usage inclusions that can be used in plans
Base Buckets Screen
Usage Buckets Screen
Developer
Information for those looking to integrate with the billing system
API Platform
Developers - Getting Started
- Tokens & Authentication
- PATCH, POST, PUT & DELETE
- Search Requests
- Deep Search - Related Objects
- v2/v3 GET Filters
- Update Requests
- Response Data
- LogiSense Tools
- API Logging
Developer - Data Views
- Creating a Database View
- Configuring your DataSource
Eventing System
- Events
- Notifications
Architecture
Explore the logical, delployment and functional architecture of LogiSense Billing
Logical Architecture
- Web Client
- Rating & Mediation Scaling
- Usage Aggregation and Scaling
- Billing Scaling
- Database
Deployment Architecture
- Overview
- Single Node
- Upgrade Strategy
Functional Architecture
- Module Descriptions
- Adjunct Rating & Charging
Security
Controlled Flexibility
Search

Revenue Recognition Configuration

Last Updated: Tue Apr 02 2024

Overview

This article provides an overview on how revenue recognition is configured in LogiSense Billing.

Prerequisites

In order to determine the proper revenue recognition implementation we will work with you to evaluate your current systems and how to integrate them with LogiSense Billing. Some key aspects of this are:

  • If a CPQ/CRM system in use and if it's applicable to the revenue recognition configuration

  • What ERP is in use and what automation capabilities are available

  • What are the reporting levels and field mapping requirements within the ERP

  • Determining if there are any custom revenue recognition rules that are required outside the standard rules provided in LogiSense Billing

Configuration Process

In this document we will focus on the three standard report types provided when revenue recognition is configured in LogiSense Billing:

  • Recognized Revenue

  • Deferred Revenue

  • Accrued Revenue

Additional customizations are available to these reports and additional custom reports can be setup for revenue recognition purposes if required. The standard frequency for these outputs is scheduled monthly or at the end of your fiscal month.

Reports can be accessed in the Admin Portal (LogiSense Billing User Interface), delivered to a transfer location that you specify (S3 bucket/SFTP), or directly accessed by API integration with your ERP.

LogiSense Billing Configuration

Within the LogiSense Billing application you can define how revenue is recognized for every service configured in the system using revenue recognition rules (detailed below). How revenue is recognized for one service can differ from another service based on the rule you define.

Revenue Recognition Rules

Revenue Recognition Rules are configured through extended fields in the system and allow you to define how revenue should be recognized according to your needs. The extended field is configured on the product sold (service).

Standard rules required, plus any custom defined rules from prerequisite discussions, will be configured ahead of time before the report configurations are finalized.

image-20240327-135457.png

Available Rules:

  • Evenly Distributed: this option will take the total price for the service and divide it evenly across the length of the term/contract period. For example, an annual product with a price of $120 would be recognized at 1/12th ($10) per each fiscal month

  • At Invoice Creation: service revenue is deferred until the first invoice is generated. Once the invoice is generated the revenue is recognized. Typically, this would be used when finalizing a shippable product or switching from a trial service

  • At Charge Period Start: recognizes revenue when the service’s effective date is reached. When the effective date is reached even if the service has not yet been billed it will be recognized. Until the service’s effective date is reached it will remain as deferred

  • At Charge Period End: recognizes revenue when the service’s period end has been reached. The period end is determined by the billed invoice item or the end of the contract associated with the charge/term of the service fee

  • At Charge Date: revenue is recognized when the service is charged (billing is run)

  • Milestone Event: This option leverages additional custom fields or status changes (service status change, some other entity’s status changes, etc.) to know when a key deliverable event has been reached. Our implementation team will work with you to determine the best configuration to enable the system to track your milestone events

Standalone Selling Prices

To determine the standalone selling price (SSP) the pricing configured in the LogiSense Billing Product catalog is used. Specifically, the pricing set the package frequency level. If a discount were to be applied to a service the SSP would still be calculated using the prices defined in the catalog, unless custom revenue recognition rules were defined or a reporting process was configured to exclude this.

Revenue Recognition Reports

Numerous custom reports can be configured in LogiSense Billing to suit your needs, below the standard revenue recognition reports are described.

Recognized Revenue Report: displays revenues from the period that are associated with GL accounts for Recognition. The format of this report is dependent on each customer's specific needs

Deferred Revenue Report: displays any new deferred revenue based on sales orders/contracts within the fiscal month as well as any adjustments to deferred revenues related to recognition and or pricing/cancellation adjustments

Accrued Revenue Report: any non-contractual accrued revenue such as revenue for usage will be summarized and outlined on this report

Auditing

All changes to pricing, contracts, service state and invoicing are all traceable and reportable for auditing purposes in the Audit Log found in the Operations menu. For example, our audit log can show who changed pricing on a contracted service and to what value from its initial state.

Event showing a service price being created with a value of $9.99

image-20240403-003510.png

Event showing the same service price being updated to $7.99

image-20240403-003702.png