Page Comparison

Summary

We are excited to release USAS-R version 8.0.0.  With the addition of the new Accounts Receivable module USAS is moving from major release version 7 to 8.0.0.  This release contains bug fixes, reporting improvements and exciting new features as detailed in the release notes below.

Important Highlights

Please keep in mind these release notes only reflect the changes included in this release.  There are many other features of the software that were previously released that will not be reflected in these release notes.  General information about all of the features available in USAS-R can be found in our USAS-R Documentation.  There is a section in the documentation that also details the significant changes between USAS-R and classic USAS. 

New Features!

• The Accounts Receivable Module is now available in USAS-R.  To use, navigate to System/Modules and install the Accounts Receivable Module.  Please see the documentation for details on how to import your existing Classic ARF customers and transactions.

  • 
    

    Note
    title Important Note
    It is very important for any districts who have already migrated to Redesign, that are still using Classic ARF with the intention of importing their ARF data, to keep their vendors and accounts in sync with Redesign.  This means if they create a vendor or an account in Classic to use with ARF they also need to create the vendor or account in Redesign.

    
    

• The ability to import Receipts from a CSV file is now available from the Receipt grid via the Import button.  Please see the Receipt chapter of the documentation for details on import file specifications.  A template spreadsheet file is available in the documentation to use for importing Receipts.  Users with permission to create Receipts will see the import button from the grid.

Enhancements/Bug Fixes

• Corrected a problem with the Financial Summary by Fund and the Revenues and Expenditures by Fund reports.  Previously when running the reports with the option to exclude accounts with zero amounts the July 1 Balance could have been incorrect.  The method used to determine zero amounts was incorrectly totaling the amounts instead of checking each amount separately.  The problem was exposed when an account had an overall amount of zero because the transactions associated with the account netted zero.
• Refactored a service that is used in both the application and reports to pull total amounts that are stored when posting periods are closed.  
• Improved posting period related error messages to be consistent when creating or updating transactions.

Issues included on this release