CustomBooks™ Release Notes | Labrador 2026.06.09

CustomBooks™ Release Notes | Labrador 2026.06.09



Welcome to the CustomBooks™ Release Notes for the Labrador 2026.06.09 update. This release focuses on enhancing system transparency, streamlining your daily workflows, and delivering deeper financial insights. Key improvements include a more robust Audit Log for tracking administrative changes, universal Cloud Payroll Sandbox access for risk-free testing, and a new Cash-Basis View directly within the General Journal. Alongside smarter account validation, automated credential formatting, and upgraded Budget vs. Actual reporting, these enhancements are designed to make your accounting experience more intuitive, accurate, and reliable.


Improvements


Audit Log


Log Update for Admin Panel Changes

What’s Updated
We have introduced a robust tracking system for changes made within the Admin Panel and Settings forms. Previously, administrative adjustments were not fully captured in the system's history; this update ensures that manual modifications to global parameters are recorded in the Audit Log.

How It Works
The system now monitors key settings forms to capture manual inputs and updates:
  1. Manual Entry Tracking: The Audit Log specifically records values that are changed manually within the settings forms.
  2. Form-Specific Versioning: If a setting (such as a default account) exists in multiple locations, the version update is recorded in the specific form where the edit occurred. For example, a change made in "Accounting Settings" will update the value in "Sales Settings," but the audit trail will be stored under the Accounting form.
  3. Feature Safeguards: High-risk options that could cause system-wide "chaos" or data inconsistency have been hidden from the interface to ensure a more stable administrative environment.
How It Helps
  1. Administrative Transparency: Admins can now review a clear history of manual configuration changes, identifying who made an update and when.
  2. Risk Mitigation: By removing unstable options and tracking changes at the form level, we’ve reduced the potential for accidental misconfigurations.
  3. Data Reliability: This creates a reliable trail for troubleshooting, though users should note that automated changes—such as those made via API or data conversion—are not captured in this specific versions list.

Documents

Consignment Document Error Message Accuracy

We have corrected a labeling issue in the error reporting system that occurred when consignment-related documents failed to post. Previously, the system would default to generic document names (like "Warehouse Transfer") in error messages instead of using the specific consignment terminology applicable to the document in use.

The system's error management logic has been updated to recognize and display customized document presentations accurately during the posting process:
  1. Consignment Transfers: If a Warehouse Transfer is marked as a Consignment Transfer and fails to post (e.g., due to insufficient inventory), the error message will now correctly state: Failed to post: "Consignment Transfer"!
  2. Consignment Sales: Similarly, if a Cash Sale is marked as a Consignment Sale and encounters a posting error, the message will now accurately read: Failed to post: "Consignment Sale"!
  3. New Document Handling: This fix specifically addresses instances where new documents failed their initial posting before being saved in the database.
How It Helps
  1. Reduces Confusion: Users no longer have to guess which document the system is referring to when multiple transfer or sale types are being processed.
  2. Faster Troubleshooting: Accurate error messages allow staff to immediately identify that an inventory issue is occurring within a consignment workflow rather than a standard warehouse transfer.
  3. Interface Consistency: The error messages now match the labels and headers used within the document forms, providing a more cohesive user experience.

Bank/Credit Card Register

Enhanced Deletion Warning Messages

We have improved the user messaging system within the Bank Register specifically for instances when a user attempts to delete a reconciled transaction. Previously, the system would display a helpful accounting warning followed by a confusing, technical system-level error message. This update removes the technical jargon and replaces it with a clean, user-friendly notification.

The system now filters out "system-level" code errors during the deletion process:
  1. Accounting Validation: When you attempt to delete a reconciled transaction, the system still provides the critical warning that doing so may cause imbalances in future reconciliations.
  2. Simplified Error Notification: If the deletion fails, the system now displays a straightforward message: "Failed to delete [Transaction Name] #[Number] [Date]!".
  3. Removal of Technical Jargon: Technical details—such as errored line numbers, code snippets, or context method errors—are now hidden from the end-user interface.
How It Helps
  1. Reduces User Confusion: By removing unexpected system-level messages, the software provides a more professional and less intimidating experience.
  2. Clear Actionable Steps: The remaining warning clearly explains why the transaction cannot be modified (it is reconciled) and how to proceed (exclude it from the Bank Rec document first).

Cloud Payroll

Expanded Sandbox Access

We have updated the provisioning logic for Cloud Payrol to ensure that the Payroll Sandbox is available in all Production Sandboxes. Previously, access to the Payroll Sandbox was restricted to users who already had Payroll active in their live production tenant.

How It Works
The system now treats the Sandbox environment as a universal testing ground, independent of your live subscription status:
  1. Universal Availability: The Payroll module will now appear and be functional in your Sandbox environment regardless of whether you have "Live" Payroll enabled.
  2. Independent Configuration: Users can now set up pay schedules, work locations, and employee details in the Sandbox to explore the feature before committing to a live rollout.
  3. Gusto API Integration: The connection to the Gusto Sandbox remains robust, allowing you to simulate payroll runs, tax filings, and onboarding tasks in a risk-free environment.
How It Helps
  1. Risk-Free Exploration: You can now fully test the Payroll workflow—including complex tasks like identifying >2% shareholders or setting up sick time policies—without affecting your live financial data or subscription billing.
  2. Better Implementation Planning: Teams can use the Sandbox to train staff and refine their internal payroll processes before going live, ensuring a smoother transition for the entire company.
  3. Eliminates Setup Blocks: By removing the requirement for a live payroll license to access the sandbox, we’ve made it easier for you to evaluate if Cloud Payroll is the right fit for your business needs.

Accounting

Intelligent Default Account Requirements for Business, Startup, and Writeup Editions

We have refined the account validation logic for our Business, Startup, and Writeup editions. Previously, these smaller editions sometimes required users to specify default accounts for high-level features (like Advanced Inventory) that were not even available in their current plan. This update ensures the system only prompts for accounts that are truly necessary for your specific edition to function.

The system now intelligently distinguishes between core required accounts and advanced feature accounts:
  1. Dropship Integration: The "Inventory Shipped Not Yet Invoiced" account has been added specifically to the "Dropship" functional option. It is now recognized as a requirement only when Dropship functionality is active, preventing posting failures during Dropship deliveries and invoices.
  2. Edition-Specific Filtering: In the Business edition and lower, the Accounting settings will no longer search for or require accounts related to disabled features, such as advanced inventory tracking.
  3. Resolved Configuration Errors: We have eliminated the "Object Field Not Found" errors that occurred when users were redirected to specify accounts that their edition did not support.

Paya Integration

Automated Credential Formatting

We have improved the Paya integration connection process by implementing an automatic "trim" feature for security credentials. The system now proactively cleans credential data during the integration setup:
  1. Automatic Character Removal: Insignificant characters—such as spaces, paragraph signs, or new lines—are automatically stripped from the beginning and end of input fields.
  2. Targeted Credential Fields: This logic applies specifically to the UserID, UserApiKey, UserHashKey, and LocationID fields.

General Journal

Cash-Basis View for General Journal

We have introduced a Cash-Basis View directly within the General Journal. Previously, the General Journal only displayed accrual records, forcing users to navigate into individual transactions or run specialized reports to see cash-basis entries. This update brings cash-basis transparency to your primary day-to-day accounting view.

How It Works
A new interactive toggle has been added to the General Journal window:
  1. Accounting Method Toggle: You can now switch instantly between Accrual and Cash options.
  2. Dynamic Data Refresh: Changing the toggle value automatically updates the records in the list to display the respective accounting entries based on your selection.
  3. Source Integration: The Cash Basis mode pulls data directly from the CashFlowData register, ensuring that what you see in the journal matches your official cash-basis financial reports.
  4. Visual Indicators: The user interface has been updated with a clear command bar style to indicate which accounting method is currently being displayed.
How It Helps
  1. Faster Analysis: You no longer need to perform multiple clicks to verify how a transaction posted to your cash books; the data is now available in one central location.
  2. Simplified Reconciliation: By viewing cash entries alongside document dates and types, you can more easily troubleshoot discrepancies and reconcile accounts.
  3. Improved Consistency: This update aligns the General Journal with other document-level views, providing a more predictable and uniform experience across the software.

Reports

Budget vs. Actual: Enhanced Drilldown & Comparative Reporting

We have significantly upgraded the Budget vs. Actual reporting suite to provide deeper insights into your financial performance. This update focuses on "Comparative" features, allowing users to analyze budget variances across different time periods and administrative settings with greater precision.

How It Works
The Budget vs. Actual report now includes expanded navigation and filtering capabilities:
  1. Enhanced Drilldown: Users can now click directly into report totals to drill down(double click) into the General Ledger. This allows you to immediately see the specific transactions (Journal Entries, Invoices, Expenses) that make up a budget variance.
  2. General Settings Integration: New comparative features have been added to the General Settings tab of the report. You can now toggle specific parameters to compare performance across different Projects, Classes, or Locations.
  3. Presentation Options: We have improved how accounts are displayed. You can now choose to show/hide accounts with zero amounts, inactive accounts, and customize the account hierarchy for a cleaner, more readable report.
  4. Unified Account View: The report now supports a consistent account presentation, allowing you to view accounts by Code, Name, or a combination of both across the comparative view.
How It Helps
  1. Instant Reconciliation: When you see a budget "Over" or "Under" amount, the new drilldown feature saves you time by taking you straight to the underlying data without needing to run a separate General Ledger report.
  2. Strategic Comparisons: The comparative features make it easier for department heads to see how their specific "Class" or "Project" is performing against the budget compared to previous periods or other departments.
  3. Cleaner Financial Reviews: By filtering out zero-balance or inactive accounts, management can focus on active financial drivers during board meetings or internal reviews.

    • Related Articles

    • CustomBooks™ Release Notes | Labrador 2026.04.02

      The Labrador 2026.04.02 release introduces key enhancements to financial accuracy and workflow control within CustomBooks™. This update features a new integration toggle for Avalara AvaTax to prevent duplicate records, refined UI visibility for ...
    • Reconciliations (Bank & Credit Card)

      Reconciliations Reconciling your bank or credit card account serves several important purposes. First, it helps you identify and correct any discrepancies between your internal records (your accounting software, CustomBooks™ ) and the bank's records. ...
    • CustomBooks™ Release Notes | Labrador 2025.11.20

      We're excited to announce the release of CustomBooks™ Labrador 2025.11.20, bringing a new feature and several improvements to your experience! This update includes: A major New Feature to enhance Cloud Payroll management. Key Improvements in ...
    • CustomBooks™ Release Notes | Labrador 2026.04.28

      Welcome to the CustomBooks™ Release Notes for the Labrador 2026.04.28 update. This release brings a variety of feature enhancements and workflow improvements across Cloud Banking, Document Emailing, Audit Logs, and more. Review the details below to ...
    • Budget vs. Actual Report

      Overview The Budget vs. Actual Report will show budgeted amounts for each account included in the budget along with actual account totals for comparison purposes. This reports on Budgets that have been pre-created in Accounting --> Budgets. Click ...