Healthcare Staffing Software.

Most healthcare staffing firms are not looking for a scheduling system. For 13-week travel nursing assignments, the facility manages the schedule once a nurse is placed. The agency’s job is placement, credentialing, contract billing, and pay package calculation — and that is precisely where 1Staff is built.

1Staff is a native part of the Microsoft architecture. Front office and back office are connected applications that stay in step as work happens — not separate systems syncing overnight.

Compliance and Credentialing

For travel and locum placements, credentialing is the placement. An expired license, a missed background check currency date, or a lapsed immunization record stops a worker going to site. 1Staff tracks credential requirements at three levels simultaneously: what the placement requires, what the specific facility requires, and what the individual worker currently holds.

Automated renewal reminders trigger before expiration. Credential workflows are configurable by placement type — a travel nursing onboarding package looks different from a locum physician engagement, which looks different again from an allied health credential set. eSign is embedded for onboarding documents. Role-based access keeps the compliance team’s data separated from billing and payroll. A full audit trail comes as standard.

Mixed Workforces: Locums, Travel, Allied, and Managed Programs

One platform, multiple workforce types

A firm may run locum physician placements alongside a travel nursing program and a growing allied health division — each with different billing structures, different credential requirements, and different payroll complexity. 1Staff handles all of this within a single Business Central environment. There is no second system for locums, no separate database for allied health.

Locum tenens complexity

Locum placements carry the highest per-placement financial complexity in staffing. Multi-state physician licensing runs three to six months and must be tracked against assignment start dates. Malpractice insurance must be allocated per contract. 1Staff’s rules engine handles pay and bill independently, so the pay structure for a locum physician arrangement can sit alongside a travel nurse contract in the same firm without cross-contamination of rules.

MSP supplier agility: turning assignments on a dime

For healthcare firms operating as MSP program suppliers, contract continuity is a live operational pressure. When a managed program renegotiates rate cards, restructures its supplier tiers, or moves VMS platforms — a pattern that has accelerated as enterprise health systems reassess their technology contracts — assignments need to be amended and workers need continuity. Payroll cannot gap. Invoicing must reflect the new terms from the amendment date.

1Staff’s assignment architecture supports mid-contract changes without requiring a worker to be offboarded and recreated. Rate amendments apply from a specified date. Billing rules update at the amendment point. The worker’s credential record, placement history, and payroll continuity are preserved.

“1Staff automated several key processes which allowed us to keep the same number of support staff as we grew 4x over three years.” - 1Staff Client

Pay and Bill: Independent Pipelines

Travel nursing operates under compliance rules that affect pay and bill differently. Daily overtime obligations apply to pay in certain states. Bill rates are typically weekly, contractually defined, and independent of how hours fall across the working week. These are not the same calculation, and running them through a single shared pipeline will get one of them wrong.

It is worth being direct about why 1Staff is the right answer for travel nursing specifically: the agency does not schedule shifts. Once a nurse is placed on a 13-week assignment, the hospital nurse manager controls daily scheduling. The agency’s job is placement, credentialing, pay package calculation, VMS billing, and financial management. That is the problem 1Staff is built to solve. No shift-scheduling capability is needed — and no competitor’s shift-scheduling capability changes the pay/bill calculation problem one bit.

1Staff runs pay and bill through independent pipelines. The rules engine processes each side separately — regular hours, overtime, double-time, holiday, shift differentials, and pay package components are all calculated against the correct rule set for each dimension. State compliance rules apply per assignment based on work location, not the agency’s home state.

VMS Reconciliation: 1Staff Streams

When the majority of revenue flows through managed programs, the reconciliation burden is material. The bill you submit to a VMS doesn’t come back in the same shape. Bill codes need mapping to internal pay types. Adjustment records need matching. The VMS may apply program fee deductions before transmitting data. All of this has to land correctly in the financial record.

1Staff Streams ingests VMS files through a validation pipeline. Bill codes map to internal pay types. Duplicates and corrected resubmissions are detected automatically. Exceptions are grouped and routed for resolution, and invoice batches are assembled from validated records. Pay rates always come from the assignment record — never from the VMS file. That boundary is enforced at the architecture level, not as a configuration choice.

Streams runs in two modes. Validated mode blocks import on any unmapped code or discrepancy — for environments where clean data is the rule. Permissive mode logs exceptions and continues — for high-volume operations where deferred resolution is the operational model. Both maintain a complete audit trail.

COMING SOON: Automated VMS receipt matching and rate discrepancy detection are in active development as the next layer of Streams capability — closing the gap between ingestion and full cash reconciliation.

On the Roadmap: SOW and Milestone Billing

Near-term roadmap — not current capability

SOW and milestone billing are in active development as a Business Central extension. If your firm manages fixed-fee project engagements, milestone-based invoicing, or retainage structures, speak to us about development timeline and fit for your business.

SOW now represents 35–39% of all MSP program spend. Healthcare firms with professional services or consulting-adjacent work are increasingly asked to invoice against deliverables rather than hours. Standard time-and-materials billing engines can’t handle this — the invoice trigger, the amount, and the supporting documentation requirements are structurally different. 1Staff is building this capability natively on Business Central.

The Platform

1Staff is a native part of the Microsoft architecture. Front office and back office are both Microsoft applications — connected, running in the same environment, with no third-party middleware between them. Power Platform connects both. Microsoft Copilot is available across the environment. One login, one security model, one audit trail — from first candidate touch to posted invoice.

Not every 1Staff client uses the full stack. Some come for the financial and billing layer behind an existing front office. Some come for compliance and credentialing. Some replace everything. The right starting point depends on where the pain is. If the pain is VMS reconciliation, margin visibility, or pay/bill complexity, that is where the conversation begins.

Find out how 1Staff brings recruiting, compliance, credentialing, pay/bill, and financials together on one Microsoft-powered platform.

Ready to simplify your healthcare staffing operations?

More from 1Staff Staffing Software

Frequently Asked Questions | FAQs