Infor Lawson is an ERP platform widely used in healthcare, public sector, and nonprofit organizations, covering HR, payroll, financials, and supply chain. Originally Lawson Software, it was acquired by Infor and now runs on the Infor ION integration layer, making it accessible through the same .ionapi credential flow as other Infor products.
Pull active employees with hire date, department, job classification, and pay grade. Write back updated position assignments or status changes when your product triggers an HR action.
Read the chart of accounts, cost center hierarchy, and fund structure. Useful for financial analytics products that need to map transactions to the customer's account structure without manually re-entering it.
Read pay period data, earnings codes, and deduction records. Askel respects the service account's data-access restrictions so only the payroll data the customer explicitly grants is returned.
Pull open requisitions, approved POs, and receipt confirmations from the Lawson supply chain module. Useful for procurement analytics or approval-routing products.
Read vendor master data, payment terms, and 1099 classification. Write back updated vendor information from your product's supplier-management workflow.
Read approved budgets, encumbrance balances, and year-to-date actuals by cost center and account. Healthcare and government customers rely heavily on this data for spending-control dashboards.
Meridian Regional Health Network uses Infor Lawson for HR and payroll across 12 facilities and 6,400 employees. They are rolling out your workforce-scheduling platform and need active employee records, job classifications, and department assignments from Lawson to appear in the scheduling system before nurses and technicians can be assigned to shifts.
Meridian's Infor system administrator logs into the Infor OS Portal, creates a service account scoped to the HR and Payroll ION endpoints, and exports the .ionapi JSON file. Their IT change-management team approves the credential provisioning request before the file is handed to Meridian's implementation lead.
Meridian's implementation lead uploads the .ionapi file into the Askel setup screen inside your scheduling product. Askel parses the token endpoint, client credentials, and tenant routing fields, then confirms connectivity by fetching a sample employee record.
Askel reads the Lawson HR and Payroll objects accessible to the service account, including Employee, Department, JobCode, and PayGrade records, along with any custom fields Meridian has defined. Your CS team sees a mapping draft within minutes.
Meridian uses a custom Lawson field to track nursing license type. A CS rep maps this field to the scheduling platform's credential attribute so schedulers can filter by license. A dry-run against all 6,400 employee records confirms the data lands correctly.
The nightly employee sync is enabled. Active employees appear in the scheduling platform the following morning with correct department, job classification, and license data. When Lawson processes a new hire or a termination, the change propagates to the scheduling system overnight.
The customer's Infor OS Portal admin creates a service account and exports a .ionapi JSON file containing the ION OAuth token endpoint, client ID, client secret, and tenant routing data. Askel parses this file, requests a Bearer token from the ION gateway, and refreshes it automatically. No user passwords are stored.
© 2025 Askel.ai. All rights reserved.