TASS
      Back to home
      1. Knowledge Base
      2. Integration
      3. TASS

      Alii - TASS API Integration

      The Alii onboarding team will need access to TASS (THE ALPHA SCHOOL SYSTEM) API’s per below.

       

      Please provide details for Api Licence code for:

      • Application Code for API06: Accounts Payable Automation (No security role is allowed for this api as it is a level 2)
      • Application Code for API22: General Ledger Analytics (A security role must be applied to this API as it is a level3, please ensure that all read only permissions are assigned against accounts payable and general ledger to the security role. Alii only uses this API to get the full year budget and spend amounts of the glcodes)
      • Token Key must be provided in txt format to eliminate errors in copying.
      • Your TASS API URL
      • Your TASS Company Number

      It is also preferable to supply a screen shot of the API setup in TASS so that we can identify any anomalies. Please note you will need to organise Api licences with TASS if you have not prior.

      Please see image below to “view” the api , you will also need to access logs, if permission issues are encountered

      If there are any specific system integration requirements you need, please provide us sufficient details as part of the implementation process. It is important to understand any integration requirements early in the process to ensure a smooth transition and migration to Alii. Please note Alii will create users based on TASS GLcode Purchasing rights , level 2-8 . If this is not maintained you will need to create users manually

      With Alii-TASS clients, there are several options that are available and should be considered:

      1. GL Code structure: with the initial sync of glcodes, Alii uses the two standard elements from TASS to create potential ongoing synched department\business unit combinations.
        • The first two digits (Some clients may use this as an entity identifier, others as division of single campus junior\senior school etc). Please advise the name of that is used at your college.
        • The 9 and 10th digit (Most TASS clients use that as a potential department\sub name)
        • The combinations of the two for the Business Unit structure. Please note it is a high likelihood that this sync will be turned off as data has to be perfectly aligned (This will be discussed as project task)
      2. Users are created from TASS GL Code purchasing permissions (User’s identified from level 2 to 8, please ensure there is an email address in the users’ employee record in TASS) Level 1 will need to be added manually.
      3. The associated GL Codes from point 2, provide core permissions in Alii for these users (A hybrid model is possible through adding an entire business unit access)
      4. Budget number: Please advise what you use for each current college financial year. Please note Alii reflects 12 months of data current school year
      5. GLCodeType : By default, we synchronise all gl codes, if you require specific types, please advise the specific GLCode Type: code
      6. Suppliers: We can synchronise Teacher Kiosk preferred supplies if preferred
      7. Due Date: If you have non-numerical payment terms, Alli can send invoice data whereby TASS sets the due date. If you prefer Alii to perform, then all payment terms need to be numerical (I.e. 7\14\30 etc, if we cannot calculate it will default to 30)      

                          

      Note in some circumstances please ensure that you whitelist the TASS server in the authentication table (different to an IP routing whitelist) so that the server can access the internet without authentication