Fix formats before data moves anywhere.
Trims, standardizes case, strips invalid characters, and fixes formats, such as phone numbers, SSNs, and ZIP codes.
Every payroll, HRIS, pension, and carrier system expects data in its own layout, and every vendor change can mean rebuilding an extract. BAS converts, validates, and securely transfers complex data between those systems, whether it supports programs BAS administers or runs on its own as a system-to-system service.
WHAT BAS HANDLES
Data Conversion Services Scope
Conversions rarely fail on the big picture. They fail on a date format, a code value, or a field one character too short, and the cost lands on payroll, HR, and IT teams downstream.
Every file follows the same path: secure intake, conversion, one validated data set in MyEnroll360, then use or export. MyEnroll360 is owned, developed, maintained, and operated by BAS, so the team that converts your data is the same team accountable for the system it moves through. Data Conversion Services is part of BAS Specialized Program Administration.
The rules that turn raw client data into clean, usable data run automatically on every file. Multi-field calculations, eligibility rules, code translation, and record splitting are standard here, not custom projects.
Fix formats before data moves anywhere.
Trims, standardizes case, strips invalid characters, and fixes formats, such as phone numbers, SSNs, and ZIP codes.
Convert between text, number, date, and boolean types.
Changes types and formats to match the target, such as MMDDYYYY to YYYY-MM-DD.
Map your codes to BAS codes, and BAS codes to partner codes.
Translates code values in both directions, such as a plan code to a carrier plan ID.
Validate values against reference tables.
Confirms values exist and are allowed, such as state, plan, and coverage level codes.
Derive a new value from one field.
Calculates what the target needs from what you send, such as annual salary to a per-pay-period amount.
Combine several fields into one result.
Builds values from multiple inputs, such as a deduction from rate, hours, and pay frequency.
Split or join fields and records.
Restructures data to fit the target, such as a full name into first, middle, and last.
Fill blanks and apply if-then rules.
Applies agreed business rules, such as a default pay frequency by employee class.
A conversion-only feed between two payroll platforms. The data is not used by any other BAS service. BAS restructures the layout, data types, field sizes, and codes so the file one system produces is a file the other system accepts.
Sample data for illustration only. No actual employee information is shown.
Mix and match intake paths across your data feeds. Whichever path a file takes, it enters the same pipeline, runs through the same rules, and lands in the same validated data set. BAS adapts to your file. You never adapt to ours.
INTAKE PATHS
One pipeline behind every path
Log in to MyEnroll360 and upload through the Super Importer. Results and errors appear on screen. Best for ad hoc loads, corrections, and hands-on control.
Drop files in your dedicated BAS SFTP folder. BAS picks them up, processes them, and notifies you of the results. Best for recurring feeds such as payroll deductions and eligibility.
Hand the file to BAS. Our staff run the import, resolve exceptions with you, and confirm the final load. Best for conversions, onboarding, and complex or irregular files.
Each field in your file is mapped to the matching BAS data element, whatever the layout, delimiter, header, code values, or date formats.
BAS data is mapped to each recipient's specification, down to field order, lengths, padding, and code tables.
Maps are saved per client and per feed, so repeat files process the same way every time with no rework.
When you or a partner change a layout, BAS updates the map and tests it before the next production run.
Built Around Your File. BAS builds the template around your specific file and owns the mapping on both sides, so your team never rebuilds an extract because a vendor changed a specification.
Some data only has to leave one system and arrive in another in the right shape. BAS restructures the file layout, field order, data types, and field sizes and delivers a file the target system accepts. Conversion-only feeds require no other BAS services.
If BAS Also Administers Your Programs
One load can feed many destinations. These are optional and never required for conversion-only clients.
Eligibility, elections, and life-event data feed enrollment administration without re-keying.
Imported rates, deductions, and census changes drive invoicing and reconciliation through premium billing.
Payroll, HRIS, pension, carriers, and other vendors receive their exact layouts, on their schedule.
Two systems can both carry a "hire date" and mean different things by it. A gap found in discovery is a question. Found in production, it is a correction, a rerun, and a call to everyone downstream. That is why BAS and your data owners settle each detail, field by field, before production.
Walk through sample files and target specifications with the data owners.
Write down every field-to-field requirement. The client signs off.
BAS builds the template and map for this specific file.
Run real sample files. Review every failure and warning together.
The receiving system accepts the output. The client approves go-live.
Files run on schedule. Layout changes are re-vetted and tested first.
Five things from your team make discovery fast and accurate. During discovery we also settle each feed's intake path, schedule, file-level controls, duplicate and reload handling, partial-file rules, and access and delivery.
Sometimes security is the whole job. The conversion itself may be simple; the reason to route it through BAS is that sensitive data stays under these controls from the moment it leaves your system until it arrives in the next.
BAS undergoes independent annual SOC 1 Type 2 and SOC 2 Type 2 examinations, maintains privacy and security practices aligned with applicable HIPAA requirements, and maintains a security program aligned with NIST standards. Each plan sponsor remains responsible for its own HIPAA compliance obligations. Learn more about BAS security and compliance.
How Each Finding Is Handled
The whole file is stopped before load and you are notified. Triggered by a wrong layout, missing header, record count or control total mismatch, or duplicate file.
The record is held with a message naming the file, row, field, and reason. Good records continue or hold, per your rule. Examples: a missing required field, invalid SSN format, duplicate key, or invalid code.
The record loads and the warning is logged for your review or BAS review. Examples: an out-of-range value, an unusual change from the prior file, or an auto-corrected field.
When records carry a unique, stable key, a record that arrives twice is applied once. Without one, each file updates the stored data as a new version or by overwriting the most current one. Corrected records can be resubmitted without reloading the full file.
Payroll, HRIS, pension, and carrier data arrive in different shapes. Full-population conversions, recurring scheduled feeds, and single-record corrections all run through the same pipeline.
An extract from one payroll platform is converted into the input file the other platform requires, including layout, codes, and data types.
Automated SFTP pickup and saved maps process each scheduled file under the same rules, with results reported back to your team.
Payroll, HRIS, pension, and carrier recipients each receive data mapped to their specification, down to field order, lengths, padding, and code tables.
BAS-processed imports handle conversions, onboarding, and complex or irregular files, with BAS staff resolving exceptions alongside your team.
When you or a partner change a layout, BAS re-vets the requirement, updates the map, and tests it before the next production run.
Even a simple conversion benefits when data stays off email, access is role-based, and every file, correction, and export is logged.
BAS converts, validates, and securely transfers complex data between payroll, HRIS, pension, carrier, and benefits administration systems. You send data the way your systems already produce it. BAS maps it, validates it, cleans it, and delivers it in the exact format each receiving system requires. Conversion can support programs BAS administers, or run on its own as a system-to-system service.