Improvements

Sales Settings

Default Credit Application Controls for Sales Invoices

1. New Global Admin Configuration Toggle: Inside the Admin Panel ➔ Sales Settings, users will find a new default dropdown selection framework labeled "Default Credit Application on Sales Invoices". Administrators can choose from three operational defaults:
   
1. Apply Automatically: Preserves the legacy behavior where the engine automatically clears balances against open unapplied customer cash.
   
2. Do Not Apply Automatically: Completely halts automatic allocation. Credits remain safely unapplied on the client profile until manual reconciliation takes place.
   
3. Prompt on Save (Default Setting): Dynamically flags matching credit options at the exact moment of initial document validation.
   
2. Dynamic Save-Time Modals: When your operational workflow is set to Prompt on Save, creating and saving a brand new Sales Invoice for a customer with open cash balances triggers an interactive modal prompt: "This customer has $X.XX in unapplied credits. Would you like to apply them to this invoice?". Users can choose to instantly Apply credits, Leave unapplied, or Cancel save.
   
3. Real-Time UI Indicator Banners: To ensure visible credits are never overlooked, clear text banners display directly on the Sales Invoice form interface:
   
1. Displays Available to apply: $X.XX if matching overpayments are open but unlinked.
   
2. Displays $X.XX Applied if credits have successfully bonded to the active document balance.
   
4. Uniform Data Import Integration: Invoices introduced into the application via the Data Import Wizard will systematically follow the active global default option selected inside your Sales Settings, preventing unlinked cash allocations from occurring silently during batch operations.
   

1. Eliminates Manual Rework: Staff members no longer have to waste billable hours reverse-engineering automated credit settlements, resetting invoice lines, or clearing unintended data pairings manually.
   
2. Maintains Strategic Billing Intent: Accounts Receivable teams can now cleanly enforce distinct payment terms for individual contracts or internet sales accounts without background allocations clouding specialized ledger metrics.
   
3. Maintains Flawless Audit Trails: When a credit option is executed via the save prompt or autofill matrix, the background engine automatically spawns a dedicated Apply Customer Credit sub-document as a child record cleanly linked directly to the parent invoice, preserving bulletproof trace accounting.
   

Lists

Payment Terms: Discount Percentage Validation Restrictions

1. Strict Upper Bound Ceiling: The underlying database variable for DiscountPercent has been hard-coded to a maximum allowable constraint value of 100%.
   
2. Real-Time Input Sanitization: If a user types or uses the calculator tool to input an invalid discount percentage value of $100.01% or higher, hitting Enter or attempting to save will instantly block the execution.
   
3. Automated Value Restoration: Upon triggering the block, the system completely cancels the input, restores the field back to its previously saved legitimate percentage, and fires a dedicated pop-up error prompt: "Discount percent cannot exceed 100. Value will be restored."

1. Protects Sub-Ledger Math: Hard-capping discount values eliminates the possibility of downstream transaction records calculating negative payment distributions or over-allocated credit reductions.
   
2. Guarantees Accounting Accuracy: Restricting discount metrics ensures that your journal entries for automated invoice settlements remain strictly aligned with compliant business standards.
   
3. Speeds Up Form Setup: Clear pop-up error notifications provide instant clarification to accounting operators during early-payment incentive definitions, preventing accidental typos from creating corrupted rules.
   

Documents

Closed Period Optimization: Manual Status Updates for Sales and Purchase Orders

1. Standardized Warning Toggles: Changing document indicators inside a closed book interval now cleanly triggers the active "Closed period notification" dialog window.
   
2. Override Confirmations: If a user possesses the necessary administrative data write authorizations, they can select "Yes" inside the modal prompt to successfully save and post the status adjustments without interrupting core platform configurations.
   
3. Read-Only Lock Status: Orders toggled to Cancelled or Manually Closed correctly shift down into a safe, non-editable read-only configuration, preventing accidental ledger discrepancies.
   

1. Preserves Book Closures: System administrators no longer face the disruptive administrative task of temporarily shifting back fiscal closure dates just to complete order status edits.
   
2. Eliminates Processing Blocks: Resolves a major operational issue where background posting procedures (OrderClosing background commands) failed to execute because they were missing implicit permission parameters.
   
3. Unified Workspace Behavior: Brings consistency across different document menus by matching the user experience of Sales Orders and Purchase Orders with our existing Sales Quotes setup.
   

Sales Invoice: Validation and Sign Auto-Correction for Negative Discounts

1. Automated Sign Inversion: If a user types a negative discount parameter in either the global document header or a specific transaction line, hitting Enter or saving the document triggers an auto-correction script. The application instantly flips the mathematical sign from a negative to a positive integer (e.g., transforming -50.00% directly into 50.00%).
   
2. Dynamic Recalculation: Immediately following the sign inversion, the row formulas recompile the subtotal fields, subtracting the discount from the gross asset lines correctly.
   
3. Calculation Consistency: For example, a quantity of 10 items priced at $5 each generates a $50 subtotal. Entering a value of -5% will now automatically save as 5%, adjusting the total due down to exactly $47.50 rather than scaling it up to $52.50.
   

1. Protects Accounting Integrity: Auto-correcting negative parameters safeguards your financial reports from carrying unintentional hidden revenues or irregular transaction balances.
   
2. Standardizes System Behavior: This patch aligns data fields directly with true operational intent: discount fields are locked strictly to price reductions. Extra fees or processing surcharges must be added intentionally as distinct line items.
   
3. Improves Fast Data Entry: Staff members who mistakenly include a negative dash while copying over external contract values or processing swift adjustments are protected by immediate field correction.
   

Sales Invoice:  Structural Editing Restrictions for Paid and Voided Invoices

1. Paid Invoice Safeguards: When an invoice is tied to an active payment (such as a posted Cash Receipt), editing controls lock automatically. A prominent banner appears in the header warning: "This Invoice is paid. To make changes, you must first void the associated payments".
   
2. Cascading Read-Only Field Restrictions: While an invoice is flagged as paid or voided, the layout locks the following modules from user interaction:
   
1. All inventory parts, item descriptions, and item grid quantities.
   
2. Global header elements (such as customer matching fields and overall total-affecting variables).
   
3. Footer discount rates, shipping costs, and the Sales Tax parameters tab.
   
3. Grayed-Out Void Protections: To maintain consistent sequential validation, the command function "Void the Invoice" is completely grayed out and disabled for paid records. Users must actively cancel the matching Cash Receipt first before the invoice can be voided.
   
4. Flexible Field Exclusion: Secondary tracking fields that do not alter tax bases, item counts, or total customer balances remain available for administrative mapping.
   

1. Prevents Financial Discrepancies: Freezing lines ensures that transactions with clear audit paths cannot be edited by accident, protecting your core ledger.
   
2. Enforces Clean Reconciliations: Restricting structural edits on settled documents ensures that accounts receivable balances match customer payments flawlessly without silent data drift.
   
3. Standardized System Behavior: This update coordinates code rules across overlapping features, seamlessly integrating with changes implemented for paid asset editing.
   

Sales Order: Data Locking and Validation Controls for Shipped Orders

1. Systemic Line-Grid Lockout: Once an order changes to a status of "Shipped" or "Partially Shipped", the application instantly restricts modifications across the core line item grid. All data rows including Item selection, Quantity fields, Unit Pricing, Line-Item Discounts, and Tax Codes transition automatically into a non-editable, read-only configuration.
   
2. Real-Time Validation Safeguards: If an integration command or an edge-case configuration attempts to force a change onto a shipped order's discount value or calculation type, the system rejects the input. It completely rolls back the entry to its previous value, leaves totals un-recalculated, and flashes descriptive validation warnings in the message panel:
   
1. "Discount percent cannot be changed, because the Order has been shipped."
   
2. "Discount type cannot be changed, because the Order has been shipped."
   
3. Standardized In-App Workflow Routing: To change pricing or apply retroactive allowances after an inventory shipment has been dispatched, operators must select from the following authorized accounting options:
   
1. Adjust parameters directly on the unposted Sales Invoice before sending it to the client.
   
2. Generate an explicit, separate Credit Memo to cleanly trace and track the credit adjustment.
   
3. If an explicit order edit is mandated, an authorized manager must completely Unship the fulfillment record, modify the open Sales Order, and then Reship the log.
   

1. Secures Revenue Integrity: Locking calculations prevents warehouse personnel or accounting clerks from accidentally altering historical contract numbers that have already physically moved out of delivery bays.
   
2. Eliminates Ledger Variance: Restricting late changes guarantees that your upstream sales order contracts remain in absolute alignment with your inventory allocations and shipment summary logs.
   
3. Establishes Clear Process Paths: Forcing price adjustments into Credit Memos or Invoice screens ensures your internal team members abide by clear, standardized accounting and audit compliance strategies.
   

Assembly Builds FIFO Costing Engine Calculation Fix

1. Disassembly Handling & Error Validation
   
1. Edge-Case Fix: A crash issue ("Cannot convert value to Numeric") was discovered and fixed when posting a Disassembly document dated prior to an inventory adjustment on a zero-quantity layer.
   
2. Clean Error Messaging: Rather than throwing a technical processing exception, the system now properly validates stock chronology and displays a clear error message (e.g., "There is an insufficient balance of [X] at [Location] on [Date]. Failed to post Disassembly...").
   
2. Multi-Item Assembly & Disassembly BOM Support
   
1. Expanded BOM Testing: The costing engine logic was updated and verified to ensure that when an assembly (or disassembly) contains multiple component items, the 50/50 (or proportional BOM ratio) cost allocation split remains accurate across all active materials.
   

Time Tracking

Document Print Forms

Multi-Level Sub-Assembly Explosion/Expansion for Print Forms

1. Reconfigured Setup Toggle: Under Admin Panel ➔ Print Form Settings, the configuration option for the Assembly List template has been precisely renamed to "Explode Sub-assemblies" (replacing the generic "Explode Assembly BOM" checkbox). This update accurately reflects its function, since top-level Bill of Materials lines already render on manufacturing records by default.
   
2. Cross-Document Standardization: To maintain engineering symmetry across operational workflows, these multi-tier structural calculations simultaneously apply to both Assembly Build Print Sheets and standard Sales Invoice Templates.
   
3. Consistent Decimal Precision: A structural layout bug has been resolved so that all deep-tier exploded material quantities strictly inherit and match the numerical formatting rules and decimal precision configurations of parent lines.
   
4. Continuous Data Retention: Inherited fields such as Location and Qty Needed map and print continuously across cascading component branches rather than leaving blank layout gaps during multi-level generation.
   

1. Streamlines High-Volume Picking: Shop floor managers and assembly technicians can view a complete, expanded structural layout of all nested component requirements on a single pick sheet without needing to toggle through cross-referenced item screens.
   
2. Optimizes Inventory Planning: Keeping Qty Needed vs. Qty On Hand decimal values cleanly aligned across all multi-level sub-components makes it simple to identify raw material deficits prior to starting a production run.
   
3. Standardizes Billing Records: Sales Invoices containing multi-level manufactured items now show clear, formatted component breakdowns, ensuring transparent communications for complex client deliveries.
   

Bank Reconciliation

Standardized Page Setup and Print Settings

1. Enabled Page Setup Button: The primary page configuration buttons on the print preview form—which were previously greyed out—are now fully unlocked and interactive.
   
2. Standard Document Formatting: When launching the print preview from either the Reconciliation List or a specific Reconciliation form, clicking Page Setup opens standard document adjustments:
   
1. Paper Size Selection: Adjust your layout across universal dimensions.
   
2. Margin Parameters: Explicitly define independent layout boundaries for Left, Right, Top, and Bottom margins in inches.
   
3. Page Mechanics: Configure horizontal and vertical Header/Footer spacing variables, paper orientation (Portrait or Landscape), and color scale options (Color vs. Black & White).
   
4. Dynamic Scaling: Control multi-page layouts using custom percentages of normal size, Fit to Width, or Fit to Page variables.
   

Audit Log

Tracking for Merged Catalog Items

1. Dedicated Log Entries: A new predefined action classification called "Merged" has been added to the system-level user event monitoring variables.
   
2. Traceable Reference Notes: When duplicate items are consolidated, the system automatically writes an archive trace with detailed descriptions explaining exactly where the records went. The description log is saved using a standardized text structure: Merged into: [Target Record Info].
   
3. Pre-Deletion Snapshots: The background application mapping components ensure this tracking trace entry is permanently committed to your ledger records immediately prior to clearing out the secondary entries.
   

1. Trace Historical Mappings: Internal administration and accounting staff will no longer lose visibility into where data vanished during cleaning sessions. You can filter changes by date or entity types to verify if missing records were manually scrubbed or consolidated.
   
2. Provides Definitive Audit Trails: If a transaction history looks modified due to changes in linked item codes, auditing teams can check the target references to confirm data authenticity without parsing unlinked files.
   
3. Maintains Stable System Indexes: Secondary references are tracked clearly while preserving data performance across your primary operations.
   

Cloud Payroll

Embedded Payroll + Gusto Integration: Optimized GL Account Mapping Screen Layout

1. Three-Column Matrix Layout: The G/L mapping data fields are now organized cleanly across three distinct, balanced columns.
   
2. Alphabetical Row Ordering: To make asset mapping faster, configuration options sort systematically in alphabetical order from left to right, and wrap down continuously from top to bottom.
   
3. Responsive Vertical Scrolling: Instead of letting expanding fields stretch out past window bounds horizontally, the interface anchors to a standardized horizontal layout format matching the rest of the application. Large datasets are now handled using clean vertical scroll controls.
   

1. Eliminates Screen Distortion: Standardizing input fields prevents large payroll matrices from bleeding over and corrupting the sizing parameters of other integration tabs.
   
2. Improves Account Accessibility: On wide monitors, fields are no longer cut off on the left or stretched out to extreme margins on the right, keeping your chart of accounts readable and within view.
   
3. Intuitive Navigation: Sorting complex state employer taxes (e.g., FUTA, Medicare, and varied SUI/SUTA premium lines) alphabetically within three structured fields minimizes human error when linking tax obligations to expense accounts.
   

Data Import Wizard

Data Import Wizard: Zero-Quantity Assembly Component Validation

1. Staging Error Flagging: Any imported Assembly Build containing components with a quantity of zero is flagged with a staging error. The side panel will display the warning: Line #[X]: please adjust zero quantity.
   
2. Resolution Hyperlinks: To eliminate manual cleanup of text or spreadsheet data, the error interface in the side panel includes two actionable options:
   
1. Remove Zero-Quantity Lines: Clicking this link automatically strips all zero-value component lines from the staging record, instantly clearing the error state so you can commit the clean record.
   
2. Import As-Is: Clicking this option bypasses the safety error block, clearing the flag and allowing you to force-import the Assembly Build exactly as structured in the source document.
   
3. Manual Editing Option: Users can still double-click the staging record card to open the document and manually adjust the quantities to a valid non-zero number before saving and pushing to production.
   

1. Reduces Post-Import Cleanup: Users who maintain legacy or inactive inventory items with zeroed out rows in their Excel source files can now drop those lines automatically during staging.
   
2. Guarantees Production Readiness: Enforcing component quantity checks at the import stage guarantees that every active Assembly Build created in the system can be executed immediately without manufacturing delays.
   
3. Protects Workflow Integrity: Restricting incomplete builds prevents broken lines and data mismatches from leaking into your core inventory and production sub-ledgers.