ATS & CRM
Customers, workers, orders, and placements.
Najaxa Ontology
The shared definition of how your staffing business fits together.
Every customer, worker, placement, rate, hour, invoice, and journal belongs to a larger story. Najaxa Ontology connects that story, so Middle Office can run it, your data can report it, and AI can understand the business behind the rows.
One business. Many systems.
Your staffing business crosses every system you run.
The ATS knows the candidate and the placement. The VMS knows the submitted hours. Payroll knows the check. The ERP knows the invoice and the journal. Each system holds part of the truth.
Najaxa connects those parts through the language of staffing. This worker filled this placement for this customer. These rates governed these hours. Those hours became this pay, this bill, this invoice, and this journal. That connected meaning is the Ontology.
VMS & time
Hours, approvals, expenses, and purchase orders.
Payroll
Gross pay, checks, taxes, and payroll cost.
ERP & GL
Invoices, receivables, revenue, and journals.
The rest
Spreadsheets, client files, and the systems unique to your firm.
The staffing model
The relationships are the intelligence.
A table can hold a rate. The Ontology knows which placement it belongs to, when it applies, which hours it changes, how pay and bill differ, and where the result appears next.
Customer Who receives the work
Worker Who performs the work
Placement Where the customer, worker, rates, approvals, and invoice rules meet
Rate & rules What applies, and when
Time & expense What happened
Converted pay & bill What the hours became
Gross pay For payroll or AP
Invoice For the client
Margin & commission For the business
Journal For accounting
A shared vocabulary
The words mean the same thing wherever you use them.
Reports become dependable when the people, systems, and questions are working from the same definitions. These are some of the concepts that carry through the Najaxa model.
- Placement
- The point where the worker, customer, rates, approval path, pay codes, and invoice rules meet.
- Time
- What the worker did: hours, punches, expenses, and the client detail collected with them.
- Converted pay
- The pay result after the configured rules run over the time.
- Bill
- The client-side result produced from those same hours under its own configured rules.
- Invoice
- Bill lines grouped and presented in the format that client expects.
- Pay / bill margin
- The bill minus the converted pay on a finalized export.
From an hour to the books
Every number keeps the story behind it.
The value is not just one more total. It is the ability to follow the total back through the business decisions that produced it.
- 01
The placement carries the rules.
The worker, customer, pay rate, bill rate, approval path, purchase order, and invoice requirements meet in one operating context.
- 02
The hour keeps its meaning.
It arrives with the placement, pay code, date, approval, expenses, and client detail that explain what happened.
- 03
Pay and bill follow their own paths.
Configured rules turn that hour into a pay result and a bill result. The two can differ while staying connected to the same source.
- 04
The outcome stays traceable.
The invoice, margin, commission, export, and journal can all be followed back to the placement, rate, and time behind them.
How we deliver it
One body of staffing knowledge. Three ways to put it to work.
Najaxa Middle Office
The Ontology running in the center of operations.
Middle Office uses the relationships among placements, rates, time, pay, bill, invoices, and commissions to move transactions through the rules of your firm. The same model keeps every result connected to the work behind it.
See how Middle Office works →Implementation
The rules of your firm, learned and put into the system.
The people who learn your rates, invoice formats, and client rules are the people who configure them. They stay on the account after go-live.
See how implementation works →Najaxa Data
The Ontology assembled in an environment you own.
Najaxa Data maps the systems you already run into your staffing vocabulary. The result lives in your account and begins with customers, placements, time, pay, bill, invoices, and the relationships among them.
See the data practice →Questions with context
AI gets the business, not just the schema.
“What did this placement make?” sounds simple. The answer depends on which time was approved, which rate was effective, how the hours converted, what was billed, and which invoice carried the line.
The Ontology gives reports and AI-assisted questions those concepts and relationships. A question begins with the business meaning, then follows the records that support the answer.
Your firm’s version
The model follows how you operate.
Two staffing firms can use the same ATS and payroll provider and still define the business differently. What counts as a placement. Which rate applies. When time is ready to pay. How an invoice groups. What margin means in the room.
We map those definitions into your Ontology. When a system is added or retired, the shared business meaning remains. When a number changes, the relationships show why.
Your operating model
Bring the number your team keeps reconciling.
Tell us the systems you run and the figure that never quite matches. We will show how those pieces connect.