NetLease - Troubleshooting the "- None -" Line on G/L Reports

Overview

The - None - line on G/L reports shows transactions that are booked to lease-related accounts but are missing a lease tag. This article provides a guide to understanding why transactions appear on the - None - line and how to identify and resolve the underlying issues.

Understanding the - None - Line

Before troubleshooting the - None - line, it's important to understand how the system determines which transactions appear there.

Transactions appear on the - None - line when they meet both of these criteria:

  • The transaction is missing a lease tag (i.e., the NetLease Lease field is blank)
  • The transaction is booked to an account that is mapped to a lease type

Example Causes of - None - Line Transactions

  • Manual journal entries posted to lease-mapped accounts without a lease tag
  • Go-live manual entries that reverse pre-existing lease balances were not properly handled
  • System-generated transactions that failed to tag properly due to data issues
  • Non-lease transactions posted to accounts that are incorrectly mapped to lease types

Filtering Reports for Troubleshooting

Viewing Transaction Detail

Transaction detail only displays for transactions in the activity columns of the G/L report. To view the transactions comprising the beginning balance, filter to earlier accounting periods to ensure all relevant transactions appear in the activity columns.

Recommended Filtering Approach

Filter the G/L report from the original go-live date to the present date. This should display transaction detail for all - None - line activity since going live with NetLease. At the original go-live date, the beginning balance of the - None - line should match the lease balances that existed before implementing NetLease.

To filter the report:

  • Navigate to NetLease > Reports > G/L & Recon Reports, and open the desired G/L report
  • Locate the Filters section at the bottom of the report
  • Set the From Date to the NetLease go-live date
  • Set the To Date to the current date (or the end of the reporting period)
  • Set the Export Level to Full Hierarchy
  • Click Preview to refresh the report

Troubleshooting Common - None - Line Issues

Incorrectly Mapped Accounts

Verify that accounts are mapped to the correct lease types. Review transactions on the - None - line to identify whether any originate from accounts that should not be mapped to lease types.

Example: If non-lease accounts are accidentally mapped to a lease type, unrelated transactions will be pulled into the G/L report and appear on the - None - line, creating an unexpected balance.

Resolution: Navigate to the lease type setup and verify account mappings are correct. Remove any incorrectly mapped accounts from the lease type configuration. Once corrected, the - None - line balance attributable to the non-lease transactions will resolve.

Missing Lease Tags

Review transactions on the - None - line to identify any that should be tagged to a specific lease. Transactions may appear on the - None - line if:

  • Manual journal entries were posted to mapped accounts without tagging a lease
  • Transactions were created through integrations or imports that did not include lease references
  • System-generated transactions failed to properly tag due to data issues

Go-Live Entry Issues

Unexpected - None - line balances often stem from improperly configured go-live entries. The manual entry recorded at go-live should reverse the amounts that existed on the balance sheet on the day before the go-live date.

Critical Note: The manual go-live entry should NOT be an exact reversal of the NetLease system-generated go-live entries. The manual entry must reverse the pre-go-live balance sheet amounts, which may differ from the NetLease system-generated go-live entries due to timing/rounding differences or adjustments.

To validate go-live entries:

  1. Review the balance sheet on the day before the go-live date
  2. Verify the manual go-live entry reverses these specific amounts
  3. Confirm the net effect of the manual entry and system-generated go-live entries results in the correct beginning balances
Was this article helpful?