Ason is a 100% API product. Features are generic - Regulations are the content.
Tenant (one per company customer)
Payroll (a company within the Tenant, with its own regulations)
Best Practices
Do
- βStart with Quickstart, then Case Data - especially if your platform already holds a lot of employee data
- βThe frontend covers every feature - use, adapt or replace it
- βAson should be the source of truth for anything payroll-relevant.
Don't
- βDon't create an Ason User per end user - your backend authenticates as one System User
- βDon't put more than one company in a Tenant - only one Payroll per Tenant is supported today
- βDon't treat documents shown before Close as final - they're provisional until the period closes, see Payrun Periods
