Import without CaseMan delivers the data you have. It can't deliver what Ason asks for next - that depends on the data itself. So even if your HR system feels complete, Ason opens cases after the import, and they're resolved through CaseMan.
What an import can't know
Which fields are required is decided by rules over data that's already there: company setup and earlier answers. A new employee - German, lives in Switzerland, married, spouse also employed:
| Step | You deliver | Ason reacts |
|---|---|---|
| 1 | Personal data, Swiss address, marital status, hire date, wage | Not Swiss - case "Record residence category" |
| 2 | Residence category B | Withholding tax liable - withholding tax data required |
| 3 | Withholding tax data with code C (married, both earning) | Code C - partner data required |
| 4 | Partner data (personal data, address) | Partner's employment missing - case "Record partner employment" |
| 5 | Partner's employment | Complete - cases close, the employee is payable and ready for ELM submission |
None of these steps can be mapped in advance: what's needed next only emerges from the previous answer.
Even complete data opens cases
| Trigger | Example |
|---|---|
| Company setup | Cost centers switched on (also later) - a cost center is required for every employee. No UVGZ or KTG insurance - those cases never appear |
| Earlier answers | Not Swiss - residence category. Category B - withholding tax data. Code C - partner data |
| Changes over time | Wage type changes from monthly to hourly - every value the hourly wage needs is required. Child data changes - confirm or correct the withholding tax code |
| Recurring checks | Hourly wage - record hours every period, or confirm "none". Monthly wage deviates from the previous month - confirm or correct |
Recurring checks aren't gaps in your data, and no import can answer them in advance. Unresolved Missing Data and Payroll Control cases also block closing the Payrun Period.
Two example imports
EMPL1 - French national, lives in France, works in Geneva. The import delivers nationality FRA, residence FRA (with "75" in the canton field - a French département number), work location GE, married, 90 % workload, withholding tax location GE, exit 31.10.2026. Empty: residence permit, partner data, withholding tax status.
| # | Case Ason opens | Why |
|---|---|---|
| 1 | Record residence category | Not Swiss, permit missing (probably cross-border permit G) |
| 2 | Record withholding tax data | Location GE delivered, status and tariff missing |
| 3 | Record type of stay | Residence abroad and withholding tax liable - unless a cross-border commuter |
| 4 | Record partner data | Married, partner data empty - mandatory for code C |
| 5 | Check additional employment / replacement income | 90 % workload, withholding tax liable |
| 6 | Check exit | Exit in the open period (if that Payroll Control check is switched on) |
EMPL2 - German with B permit, hourly wage, Geneva. The import delivers nationality DEU, permit B, married (partner not employed), 1 child, hourly wage, withholding tax location GE. Empty: withholding tax status and tariff - although everything the tariff needs is there (married, sole earner, 1 child).
| # | Case Ason opens | Why |
|---|---|---|
| 1 | Record withholding tax data | B permit means withholding tax liable, status and tariff missing |
| 2 | Record hours (every period) | Hourly wage - record hours or confirm "no hours" |
| 3 | Check withholding tax code (ongoing) | Whenever child data changes |
Data that looks complete still opens 6 and 3 cases - and in the second example, two of them recur.
Resolve through Build, not around it
Missing Data and Payroll Control are Cases too. Resolving one goes through Build, then Report - and Ason re-checks, which can open the next case. That loop is what CaseMan runs.
- Skipping Build risks missing newly required fields
- Your own UI works if it runs the same loop on the same calls - a CaseMan equivalent, not a fixed import mapping