Imports
Map JSON, XML, CSV, Excel, or OCR-processed timecard images into placements, workers, purchase orders, payroll costs, and other configured records.
You should not need a second integration product.
Firms that buy one spend thousands of dollars and an immense amount of time configuring it. Integrations are built into Najaxa Middle Office. We make them fast, efficient, and correct. Placements, time, pay, and invoices move from here. A large share of that work is already built. When a handoff still needs to be built, we build it and you use it. If there is an API, we can call it.
The other product
Thousands of dollars. An immense amount of time.
A separate integration product is another license and another project. Someone has to learn it, map every field, and keep it running. Workato, Power Automate, or a tool beside the staffing system is where that money and that time go, before a placement or a timesheet has moved.
Imports and workflows are how Najaxa Middle Office does that work. Nested loops, conditions, matching against records you already have, schedules, and calls out over HTTP. We build the connection on the same system you use for time, pay, and bill. We check the source, the destination, and what happens when a row fails, and we call it ready when it is correct. If your ATS, CRM, payroll provider, ERP, or VMS handoff is already in the product, you use it. If it is not, our team builds it and you use it.
Import the file or feed you already receive.
JSON, XML, CSV, Excel, or a photograph of a paper timecard read by OCR. Import recipes support nested loops, conditions, and matching against existing records. Placements, workers, purchase orders, payroll costs, and other configured records can arrive this way. Time often arrives as a file, a feed, a VMS report, or an API.
Review incomplete placement data before time entry.
When a front office ATS or CRM record arrives without required billing data, the import can wait in review. An internal operator fills in what is missing and approves it, or rejects it with a reason. Worker entry can be blocked on that placement until it is ready.
Pay data and bill data leave separately.
A workflow is a record you create. Format, filters, revenue treatment, numbering, and a legal transaction date. Output as CSV, Excel, PDF, HTML, or Word. A configured payroll export can make gross pay eligible on submission, while a configured billing export can require approval before the invoice is created.
Webhooks send configured events when they happen.
Webhooks deliver supported events over HTTP, SFTP, Azure Blob, or S3, with retry and a delivery log. Workflows can also start from schedules, record changes, REST hooks, and completed exports.
Use your configured sign-in.
NMO supports OIDC single sign-on and customer-signed JWTs. Provider setup and login behavior are configured for each tenant.
How data moves
Imports, workflows, webhooks, and sync.
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.
The sync
Report from SQL, Fabric, or Snowflake.
NMO records placements, timesheets, pay, bill, invoices, and purchase orders. NMO Sync copies supported records to SQL, Fabric, or Snowflake.
1. Work happens hereTime, pay, bill, invoices, and purchase orders in Middle Office.
2. Changes are recordedSupported new rows and updates enter the sync feed.
3. Records copy outSQL, Fabric, or Snowflake.
4. You use the dataReport from the destination you chose.
If you still need the warehouse built, Najaxa Data can scope that work.
Where NMO sits
Front office integrations and back office.
Front office integrations
ATS and CRM. Candidates, orders, and placements stay there. Time and billing data come in through a configured import, API, or workflow.
Back office
Payroll and ERP. Gross pay goes to the payroll file the provider already takes. Invoices and journals go to the ERP. Payroll still runs payroll. Accounting keeps the books.
Najaxa Middle Office handles the connection.
ATS, CRM, payroll, ERP, and VMS. The import, the workflow, the webhook, and the export live in the product. We review the source data, where it has to land, and what happens when a row fails before we call a connection ready. You should not need a second system to move it. If there is an API, we can call it.
Current systems
Front office and back office stay
See what Middle Office takes when the ATS, CRM, payroll provider, and ERP stay where they are.
See the features →Your stack
The file or feed you already receive
If a file, a feed, or a step still happens by hand, we will show which import, workflow, webhook, or export fits.
Request a demo →Bring the file you already use.
A payroll file, a client invoice, or a feed your team still handles by hand. We will show where it enters Middle Office and where it comes back out.