Improvements

Reports

Budget vs. Actual Report: Customizable Report Periods

1. Arbitrary Date Ranges: Users can click the calendar button to select a customized period (e.g., a single month or a specific quarter) that falls within the established budget's date range.
   
2. Automatic Data Recalculation: The report automatically calculates both Actual and Budget values to match only the selected period.
   
3. In-Period Validation: If a selected period falls outside the overall budget range, the system will provide a notification or automatically return to the initial valid budget boundaries.
   
4. Precise Drilldown: Performing a drilldown (double-click) on an amount in the "Actual" column now correctly opens the General Ledger report filtered specifically for the customized period you are viewing.
   

1. Eliminates Manual Workarounds: Users no longer need to export entire years to Excel just to isolate a single month’s performance, nor do they need to create multiple separate budget documents for different timeframes.
   
2. Improved Presentation: You can now present month-to-date (MTD) or quarter-to-date (QTD) performance to stakeholders with a few clicks, showing only the columns relevant to your current meeting.
   
3. Faster Troubleshooting: By aligning the drilldown logic with your customized view, you can jump directly from a specific budget variance to the underlying transactions for that exact timeframe without manually resetting General Ledger filters.
   

Balance Sheet Report (Standard and Comparative): Drill-Down Accuracy Improvements

1. Double-clicking on any numeric value in the Balance Sheet now reliably opens a detailed view of the transactions that make up that balance.
   
2. Drill-down results now follow proper accounting logic, ensuring that the displayed transactions fully and accurately support the selected amount.
   
3. Date filtering between the Balance Sheet and the General Ledger drill-down has been aligned, eliminating discrepancies between report totals and transaction details.
   

1. Previously, users could encounter mismatched totals when drilling down from the Balance Sheet due to inconsistent date ranges applied in the General Ledger view. This has been corrected.
   

Integrations

Stripe: Enhanced Webhook Diagnostic Logging

1. User Message Processing: Added a dedicated processing layer to the HandleIncomingWebhook function to capture detailed error descriptions.
   
2. Event Log Integration: All diagnostic information is now automatically stored in the Event Log, allowing technical teams to review exactly what occurred during a webhook event.
   
3. Response Body Transparency: The response body now includes a "Messages" section that explicitly lists error types—such as "Object field not found"—and points to the exact line in the module where the exception was raised.
   
4. Stripe Automation Support: This fix directly relates to improving the auto-generation of Bank Deposits from Stripe, ensuring that payouts are tracked accurately.
   

1. Faster Root Cause Analysis: Technical support and development teams no longer have to guess why a webhook failed; the specific technical reason is now preserved in the log.
   
2. Improved Integration Stability: By identifying missing object fields or configuration gaps in the Stripe payout flow, we can more effectively ensure that your bank deposits remain in sync with your payment processor.
   
3. Reduced Data Gaps: Detailed logging helps prevent "silent failures," where a transaction might be missed without notifying the user or administrator.
   

Documents

Sales: Statements: "Open AR Snapshot" Customer Statement Option

1. Itemized Outstanding Balances: Instead of showing a "Balance Forward" summarized line, the statement now itemizes every individual transaction (Invoices, Credits) that contributes to the current total.
   
2. Exclusion of Payments: To reduce clutter and confusion, payment line items are excluded from the view, as their impact is implicitly reflected in the remaining invoice balances.
   
3. Enhanced Aging Logic: The report features a new Due Date column and calculates aging buckets (Current, 1-30, 31-60, 61-90, 91+) based on the Statement Date vs. the Invoice Terms or manually entered due dates.
   
4. Snapshot Accuracy: The statement reflects a true "run-time" snapshot of the account, ensuring that even historical credits from years prior appear with their original dates if they remain open.
   

1. Reduces Support Inquiries: By providing customers with a clear list of "what is owed" rather than a complex transaction history, you reduce the time spent explaining statement activity to clients.
   
2. Faster Collections: The inclusion of a clear Due Date and Aging breakdown directly on the statement helps your customers prioritize their payments to you.
   
3. Versatile Printing Options: You can now choose between the traditional "Activity-Based" statement for detailed audits or the "Balance-Based" snapshot for quick collection reminders, available directly from the Customer Card or Customer List.
   

Apply Customer Credits: Improved Credit Application Logic: Future-Dated Payment Validation

1. Future-Dated Restriction: Cash Receipts or Bill Payments dated in the future will no longer appear as available credits if the Apply Credit document date is set to "today".
   
2. Real-Time Visibility: Available credits are now dynamically filtered based on the document date. If you change the date of the "Apply Credit" form to a future date, those future payments will then correctly become visible for application.
   
3. Consistent Line Filling: We have resolved an issue where transaction lines would intermittently appear or disappear when toggling between "New," "Draft," or "Saved" states. The grid now populates consistently regardless of the document's save status.
   

1. Maintains Financial Integrity: By preventing future payments from affecting past records, we ensure your historical aging reports and customer/vendor balances remain accurate.
   
2. Eliminates UI Confusion: Users will no longer experience the frustration of "disappearing lines" upon reloading a document, providing a more stable and predictable data entry experience.
   
3. Standardized Behavior: This logic is applied uniformly across both Sales (Apply Customer Credits) and Purchases (Apply Vendor Credits) modules.
   

Data Conversions

QBO Conversion: Improved Journal Entry Data Integrity

1. Automated Setting Adjustment: During the import of General Journal entries from QBO, the system now automatically unchecks the "Line-Based Reconciliation" flag.
   
2. Prevention of Empty Child Records: By disabling this flag during conversion, the system prevents the creation of "empty" child journal entries that would previously trigger errors because their records were incorrectly linked only to the parent entry.
   
3. Data Consistency: This change ensures that all imported bank transaction data remains accurately housed within the primary Journal Entry, mirroring the source General Ledger exactly as it exists in QBO.
   

1. Eliminates Conversion Errors: Users will no longer encounter "further processing" errors that occurred when the system tried to reconcile converted entries that lacked properly distributed child records.
   
2. Streamlined Migration: By handling the technical complexities of reconciliation flags behind the scenes, we have provided a more stable and predictable path for Professional and Partner-tier firms moving data from QBO.
   
3. Reliable Audit Trails: Your converted General Ledger will now accurately reflect your historical QBO data without unnecessary technical artifacts causing friction in your new environment.