1. [Bookkeeping] Account id has been replaced by account code in Net Loss Account and Net Profit Account in system configuration.
  2. [CAB] Display salary has been changed on salary list page. Salary amounts are right aligned and displayed in thousand separator and two decimal point format.
  3. [Expenses] Expense Category has been replaced by financial dimension and each expense form will be linked with one or more financial dimension. Upon adding expense, User should select unit for each dimension that is linked to expense form.
  4. [Invoicing] Upon creating/editing a new invoice, user is able to map financial units from different financial dimension to an invoice.
  5. [Invoicing] Invoice details page lists the mapped financial dimensions and corresponding units if any.
  6. [Invoicing] Upon creating journals if Bookkeeping module integration is enabled, it takes into consideration financial dimensions unit that used are mapped to invoice.
  7. [Invoicing] Upon adding new invoice/proforma, customer name autocomplete listed from customers and leads from contact module. Creating an invoice for a lead will convert it to a customer.
  8. [Invoicing] User is not allowed to map accounts that does not use base currency.
  9. [Invoicing] New invoice design page:
    • Rename Add new invoice section to basic info.
    • Add summary table on the top and bottom of the page.
    • Add invoice tab section that contains invoice details:
      • Item tab that contains all items rows.
      • Dimension tab, optionally if user integrates with BK module, it has some dimension units.
      • Payment section, when user create invoice in paid status this tab accepts payment details.
  10. [Invoicing] Upon creating/editing invoice, changing branch/customer while items already added to invoice may lead to:
    • Changes items prices.
    • Causes some items to be unavailable.
    System suggests to either keep the old options, or apply new ones and change price and remove unavailable items.
  11. [Invoicing] User can now link addition taxes to a liabilities account and deduction taxes to an assets account.
  12. [Organization] Enable user to easily enter branch location (latitude, longitude).
  13. [Personnel] Upon editing department changing attendance scheme/daily working hours, user is asked for:
    • Apply changes to new employee.
    • Apply changes to existing employee and user asked for apply date.
    • Apply changes on existing employees only have the default value from department and user asked for apply date.
  14. [System] System user level can now edit users’ password.

New Features

  1. [Personnel] Employees can sign-in/out with geolocation using GPS feature in their smart devices.
  2. [Bookkeeping] Introducing a new way to define financial dimension and unit for each dimension. User can link revenue or expense account with one or more financial dimension.
  3. [Bookkeeping] Upon creating/editing journal the UI should oblige user to select units for the financial dimensions attached to the selected account.
  4. [Bookkeeping] Organization locations have been linked with Branches dimension, where the dimension units are automatically updated when adding or editing locations.
  5. [CAB] Upon creating settlement, new field is introduced to let user choose between regular or irregular to annualize this settlement or not.
  6. [eInvoice] Introduced a new routine to periodically check out status of document on ETA and automatically update it on Modulus.
  7. [eInvoice] Introduced calculation the usage of E-Invoice Module.
  8. [Expenses] User can enable integration with Bookkeeping by defining basic accrual account, expense account and cash account by linking them with Bookkeeping accounts.
  9. [Expenses] Upon enabling integration with BK, user can link accrual account and expense account to each expense form. Basic account is used for non-linked forms.
  10. [Expenses] Upon integration with BK, user can link account to each payment method. Basic account is used for non-linked payment methods.
  11. [Expenses] Upon integration with BK, user can link finance book to each serial for both expenses and payments. Journals would not be created for expenses or payments that are not linked to finance books.
  12. [Expenses] Upon integration with BK, journal would be created when expense status has been changed to approved.
  13. [Expenses] Upon integration with BK, reverse journal would be created for accrual journal when expense status has been changed to cancelled.
  14. [Expenses] Upon integration with BK, Journal will be created along with adding payments on expense.
  15. [Invoicing] Enable user to create invoice in paid status and add payment using one or more payment method.
  16. [Invoicing] Upon creating invoice, only invoice supervisor can modify price of invoice items.
  17. [Invoicing] User is able to manage multiple price lists and link them to branches, also optionally can link price list to customer.
  18. [Invoicing] Introduce a new button in invoice details page to add payment to invoices with status sent or partially paid.
  19. [Invoicing] Listing proforma invoices can be now ordered by (Proforma number, Issue date, Expiry date, Gross amount and Status), Proforma number is clickable to redirect user to proforma invoice details.
  20. [Invoicing] Listing invoices can be ordered by (Invoice number, Issue date, Due date, Gross amount and status), Invoice number is clickable to redirect user to invoice details.
  21. [Invoicing] Upon integration with BK module. User can link customer to revenue account to use it in journal creation. Basic customer account will be used in case of customer has no linked account.
  22. [Invoicing] Upon integration with BK, user can link finance book to each serial of invoices or payments that use serials. Journals will not be created for invoices or payments with serials non-linked to finance book.
  23. [Items] Upon adding new item user would be asked if he likes to push item to CRM module or not.
  24. [Personnel] Introduce a new setup page “Attendance Logs” that allows user to assign permissions to Employee / Employee Personnel to access usage of attendance log feature:
    • Manual logs: user can sing in/out his attendance without recording his location.
    • GPS Logs: user can sing in/out his attendance with recording his location.
    • Both: user can sign in/out his attendance and if he grants GPS access to the browser then attendance log will save location automatically.
  25. [Personnel] Employee with user level Manual logs or GPS logs can access employee attendance logs page to sign-in/out and list attendance logs.
  26. [Personnel] Introduce new configurations to define the way employee manually signs-in/out via GPS:
    • Enable/Disable GPS Location.
    • Validation distance that defines the possible distance of sign in/out to nearest branch.
    Logs that have distance greater then “Validation Distance” to nearest branch will remain in “Hold” status.
  27. [System] Introduced pagination for Notification page and added new features:
    • Mark All notification as read/unread.
    • Delete all notification.
    • Mark selected notification as read/unread.
    • Delete selected notification.

Bug Fixes

  1. [Invoicing] Improper reports page permissions to relevant users.
  2. [REC] Upon sending proposal to candidate no email is sent.
  3. [System] Notification delete message is not localized.
  4. [System] Empty notification message when notification changed to Read / Unread is fixed.