No — this is build-to-order, not an AppSource one-click install. After a short scoping call to confirm your operating states, bank ACH spec and benefit plans, a typical build, install and validation runs about 4 to 7 weeks depending on the number of states, mid-year cutover needs and self-service scope. We install it as a published per-tenant extension on your Business Central environment and validate a parallel pay run before go-live.

ECOSIRE supports the extension after delivery. Tax-table refreshes can run automatically via Job Queue, and we issue updates when the IRS/SSA change form layouts or e-file formats (e.g., annual W-2 and ACA revisions) under your support agreement. You also receive the AL source repository, so you are never locked out of your own payroll logic.

Yes. Each pay run creates standard G/L entries and vendor liabilities through Business Central journals, mapped to your chart of accounts during setup. Payroll expense, tax withholdings and net pay reconcile inside BC with no CSV imports from an outside payroll provider.

Yes. Each employee can be assigned per-jurisdiction withholding configuration, and the tax engine applies the correct federal, state and local rules per pay period. SUTA/SUI rates are configured per state. Reciprocity and local taxes are handled where applicable based on the jurisdictions in scope at build time.

The extension builds 1095-C records from your benefit-eligibility and coverage data tracked in Business Central, generates the 1094-C transmittal, and produces IRS AIR-conformant XML for electronic filing. Employee 1095-C copies are generated for distribution, and the data ties back to the same employee records used for payroll.

Payroll runs inside your own Business Central tenant — data does not leave to a third-party payroll cloud. Access is governed by dedicated permission sets (Payroll Admin, Process, View) for least-privilege segregation of duties, and all pay-run and setup changes are captured in the Business Central change log for audit.