Front office
ATS and CRM. Placements, workers, customers, and rates come in.
- Bullhorn
- Bullhorn One
- Bullhorn Back Office
- Salesforce
- Mercury
Integrations
Connect the systems you already chose.
You choose the front office and the back office. A firm with more than one ATS, or more than one payroll system or ERP, can keep them. Najaxa connects the systems you chose and handles the operational work: time, conversion, gross pay, invoices, purchase orders, and margin you can explain.
Systems we connect
The systems staffing firms run.
Each connection is configured for how that customer actually runs. If yours is not on the list and it has an API, a file, or a feed, we connect it.
Back office
ERP. Invoices, receivables, and journals go out.
- Business Central
- Dynamics GP
- NetSuite
- Acumatica
- Sage Intacct
- QuickBooks Online
Payroll and pay
Gross pay goes out in the file the provider already takes.
- ADP
- Tipalti
- Employdrive
- Greenshades
- Ceridian
- Paychex
- Paylocity
VMS
We capture VMS time and client orders, including from a system only that client uses.
- Beeline
- Fieldglass
- VNDLY
Straightforward
An integration project is straightforward.
A placement comes in. Time comes in. Gross pay goes to payroll. The invoice and the journal go to the ERP. That is the job, and in staffing it is the same job at every firm. The rules differ. The shape does not.
If you are being told it takes a year, a second integration platform, and a team of consultants to move placements and time, ask what you are paying for. Usually it is someone learning staffing data on your project. We already know it. A large share of the work is built into Middle Office, and the part that is yours is configuration, not a rebuild.
You should not need another license to make the connection. Imports and workflows are part of Middle Office. When a handoff is not there yet, we build it on the same platform and you use it.
The records
We know the staffing data and the key in each system.
A placement, a rate, a timesheet, a pay code, and an invoice are the same facts in the systems you chose. The IDs are what keep a worker, a customer, and a placement tied across those systems.
Front officePlacements, workers, customers, and rates from the ATS or CRM. Time from a VMS.
Middle OfficeTime is approved and converted. Pay and bill are calculated on the same hours.
PayrollGross pay in the format the provider takes. Payroll still runs payroll.
ERPInvoices, WIP, AR, and revenue journals. Accounting keeps the books.
One worker can carry a Bullhorn ID, a payroll ID, and an ERP customer number at the same time. Middle Office keeps every external ID on the record, so a firm that acquired a company on another system can run both.
How it goes
Four steps, the same people.
1. Map what you runEvery application, what was bolted on, and what people still do by hand.
2. Configure itImports, workflows, and exports in Middle Office. Most of the work is already built.
3. Prove itReal rows from your systems, and what happens when a row fails.
4. Stay on itThe people who built the connection support it after go-live.
How data moves
Imports, workflows, webhooks, and sync.
Imports
Map JSON, XML, CSV, Excel, or OCR-processed timecard images into placements, workers, purchase orders, payroll costs, and other configured records.
Workflows
Run configured jobs from record changes, events, schedules, REST hooks, or a completed export. Send the result over HTTP or into Azure storage.
Webhooks
Deliver configured business events over HTTP, SFTP, Azure Blob, or S3, with retry and a delivery log.
NMO Sync and APIs
Use the API for transactional work. NMO Sync copies NMO records to SQL, Fabric, or Snowflake.
Want an assistant on these same records? See Middle Office for agents →
Tell us what you run.
The ATS, the payroll provider, the ERP, and the file someone still moves by hand. We will tell you which parts are already built and what the rest takes.