Overview
Xenett analyzes your general ledger and automatically creates monthly, vendor-level summaries, making it easy to review how transactions are coded.
Based on historical coding patterns, Xenett builds a configuration for each vendor and continuously monitors new entries against it. If a transaction is coded differently than expected, Xenett flags it for review.
This allows you to focus only on vendors with discrepancies, eliminating the need to manually check transactions that are already coded correctly.
Video Tutorial
How Configuration Works
When a client is first connected, the system scans past general ledger transactions and identifies consistent coding behavior for each vendor. It then builds an internal configuration based on these patterns.
Example:
If Verizon has historically been coded to Telephone & Internet, the system saves that expectation. Any future Verizon posting coded to another account is flagged as inconsistent.
You can add new valid accounts or correct errors, and the system updates its configuration accordingly.
How to Fix GL Discrepancy (Coding error)
A GL highlighted in red indicates an inconsistency, meaning the transaction does not match the configured GL for that vendor.
To correct this, click the Reclassify icon next to the GL and select the suggested GL account.
If the suggested GL is not appropriate, select Choose Another GL and manually select the correct account.
Resolving a False Inconsistency Flag
If Xenett flags a GL as inconsistent but the coding is correct, you can add it to the vendor’s configuration to remove the red flag. To do this, click the Add to Config icon next to the GL. Xenett will update the configuration, clear the current flag, and ensure that future transactions coded to this GL are no longer flagged.
Adding GL Consistency Review to the Close Process
This review point is included by default in the close template provided by Xenett.
If it is missing:
Open the close workflow.
Click New.
Select Add Task.
Choose Review Point.
Select GL Consistency Review and add it to the close checklist.
This ensures that the consistency review is completed as part of the monthly close.
Explaining Different Filters in GL Consistency Review
All : Shows all the vendors.
Inconsistency : Shows only vendors where configuration exists and the current coding does not match expectations. These items require correction or confirmation.
New Vendors : Shows vendors appearing for the first time. Review their coding and set configuration so future transactions are monitored automatically.
Matched : Lists vendors whose transactions match the configured expectations exactly. These require no action.
Not Configured : Shows vendors without stable patterns (e.g., coded across many accounts). Use this list for manual review. You may add a manual config too.
Multiple GLs : Displays vendors coded to multiple accounts. Useful for quickly spotting unexpected variety in postings.
Additional Features
Vendor Ledger Access
Hover over any vendor to preview recent ledger activity. Click to open the full ledger and review or edit all historical transactions.
Drill-down on Amounts
Click any summarized amount to view underlying transactions. You can adjust individual entries directly from the drill-down window.
Configuration Settings
Within Config, you can customize the review environment by:
Hiding selected vendors
Excluding transaction types such as payroll or journal entries
Hiding accounts
Adding additional months for comparison
These options help tailor the review based on your workflow.
Alternative “By GL” View
This view organizes activity by account first and lists vendors under each account.
It works like a summarized general ledger, making unusual vendor-to-account relationships easy to spot.
Note:
This view does not use configuration rules and does not display flags or consistency filters. It is an informational report.
Monthly Best Practices
Start with the Inconsistency filter and resolve all flagged items.
Review New Vendors, confirm their coding, and establish configuration.
Review Not Configured vendors for additional oversight.
Optionally scan Multiple GLs for unexpected account usage.
Ensure the review point is included in your close checklist so the process is completed every month.
Class Inconsistency
Class Inconsistency works exactly the same way GL Inconsistency works. Just like GL Inconsistency highlights coding issues with GL, it highlights the Class Coding issues in this review point