Data Conversion Services

Your Data. Any Format. Ready for What's Next.

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.

Send data the way your systems already produce it
Every file checked before any data is used
Delivered by secure upload or SFTP, never by email

WHAT BAS HANDLES

Data Conversion Services Scope

  1. Secure Intake Self-service upload, automated SFTP pickup, or BAS-processed import
  2. Field Mapping Inbound and outbound maps built around your specific files
  3. Transformation Cleansing, code translation, calculations, and data type conversion
  4. Validation File-level stops, failures, and warnings caught before any load
  5. Secure Delivery To BAS services, partner systems, or a conversion-only target
35+ Years Benefits administration and data-management experience
SOC 1 & 2 Type 2 Independently examined controls, every year
3 Intake Paths One pipeline, one validated data set
Built Around Your File BAS builds the template to fit your data
Why BAS

Stop Rebuilding Extracts Every Time a Specification Changes.

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.

Without BAS Spreadsheets and One-Off Extracts Every vendor change becomes an internal project
  • Each payroll, HRIS, pension, or carrier recipient needs its own hand-built extract
  • A vendor specification change forces your team to rebuild and retest the file
  • Gaps surface in production, where each one means a correction, a rerun, and a call downstream
  • Recurring files are reformatted by hand, cycle after cycle
  • Files travel through email, with no reliable record of what loaded, when, or what changed
With BAS One Accountable Conversion Partner BAS owns the mapping, validation, and delivery
  • Less manual reformatting. One source file maps to every recipient's exact layout, on their schedule
  • Less disruption from vendor changes. BAS updates and tests the map before the next production run
  • Fewer file errors. Every field is vetted in discovery, and every file is checked before any data is used
  • Reusable mappings. Maps are saved per client and per feed, so repeat files process the same way with no rework
  • Secure, traceable transfers. Data moves only through secure upload or SFTP, never email, and every file and correction is logged
MyEnroll360 In Action

One Pipeline for Every File, Whatever Its Source or Shape

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.

  • Secure intake: self-service upload, automated SFTP pickup, or a BAS-processed import
  • Convert and validate: field mapping, error trapping, data cleansing, calculations, and type conversion on every file
  • Use or export: BAS enrollment, billing, and compliance services, partner exports in each recipient's layout, or a conversion-only delivery
Transformation Rules

Data Transformation, Built In

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.

Field Cleansing

Fix formats before data moves anywhere.

Trims, standardizes case, strips invalid characters, and fixes formats, such as phone numbers, SSNs, and ZIP codes.

Data Type Conversion

Convert between text, number, date, and boolean types.

Changes types and formats to match the target, such as MMDDYYYY to YYYY-MM-DD.

Code Translation

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.

Lookups and Checks

Validate values against reference tables.

Confirms values exist and are allowed, such as state, plan, and coverage level codes.

Single-Field Calculations

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.

Multi-Field Calculations

Combine several fields into one result.

Builds values from multiple inputs, such as a deduction from rate, hours, and pay frequency.

Splitting and Combining

Split or join fields and records.

Restructures data to fit the target, such as a full name into first, middle, and last.

Defaults and Conditions

Fill blanks and apply if-then rules.

Applies agreed business rules, such as a default pay frequency by employee class.

Illustrative Example

One Payroll Row In. Two Payroll Input Lines Out.

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.

As received: source payroll extract

1 row, comma-delimited
  • Associate ID K7Q2M9X4T
  • Payroll Company Code R4N
  • Tax ID (SSN) ***-**-4471
  • Home Department Code 004100
  • Pay Frequency Code B
  • Period Beginning Date 11/01/2026
  • Period Ending Date 11/14/2026
  • Regular Hours 80
  • Regular Pay Rate Amount 37.5000
  • Deduction Code MED
  • Deduction Amount $100.00

As delivered: target payroll input

2 lines
  • Line 1 · Earning
  • Batch ID BAS-R4N-20261114-01
  • Employee ID 104482
  • Start Date / End Date 2026-11-01 / 2026-11-14
  • Earning Code REG
  • Hours / Rate 80.00 / 37.50
  • Cost Center CC-4100
  • Ongoing Input / Currency N / USD
  • Line 2 · Deduction
  • Employee ID 104482
  • Deduction Code MED_PRETAX
  • Amount 100.00

What BAS Did to Each Field

  • Source field: Associate ID
    BAS conversion rule: Lookup. Matched to the target worker ID; unmatched IDs are held.
    Target field: Employee ID
  • Source field: Period Beginning Date, Period Ending Date
    BAS conversion rule: Data type conversion. MM/DD/YYYY text converted to ISO dates.
    Target field: Start Date, End Date
  • Source field: Regular Hours, Regular Pay Rate Amount
    BAS conversion rule: Type and size. Hours padded to two decimals; rate cut from four decimals to two.
    Target field: Hours, Rate
  • Source field: Deduction Code
    BAS conversion rule: Code translation. Source code mapped to the target's code table.
    Target field: Deduction Code
  • Source field: Deduction Amount
    BAS conversion rule: Field cleansing. Currency symbol and separators stripped.
    Target field: Amount
  • Source field: Home Department Code
    BAS conversion rule: Code translation. Leading zeros dropped; mapped to the target cost center.
    Target field: Cost Center
  • Source field: (one row)
    BAS conversion rule: Splitting. One row becomes an earning line and a deduction line.
    Target field: Two input lines
  • Source field: (not in source)
    BAS conversion rule: Defaults and conditions. Regular hours default to earning code REG; one-time input and currency set by rule; batch ID built from company code, period end, and run number.
    Target field: Earning Code, Ongoing Input, Currency, Batch ID
  • Source field: Tax ID (SSN), Pay Frequency Code
    BAS conversion rule: Not forwarded. Not needed by the target layout, so not sent.
    Target field: None
  • File-level check Row count and deduction total reconciled, file in to file out.
  • Duplicate protection With a unique, stable key, a resent record is applied once.
  • Secure both ways Received and delivered by secure upload or SFTP. Never by email.
  • Reusable map Saved per feed, so every later file converts the same way.
Flexible Intake

Three Ways In. Choose a Path for Each Feed.

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

  • Self-Service Upload

    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.

  • Automated SFTP Pickup

    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.

  • BAS-Processed Import

    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.

  • Inbound Mapping

    Each field in your file is mapped to the matching BAS data element, whatever the layout, delimiter, header, code values, or date formats.

  • Outbound Mapping

    BAS data is mapped to each recipient's specification, down to field order, lengths, padding, and code tables.

  • Reusable Maps

    Maps are saved per client and per feed, so repeat files process the same way every time with no rework.

  • Maintained Maps

    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.

Conversion-Only Service

When Data Only Needs to Move, Conversion Stands on Its Own.

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.

  • System-to-system conversion, such as an extract from one payroll platform converted into the input file another platform requires
  • The same discovery, validation, exception handling, and traceability as every file BAS processes
  • Full-population conversions, recurring scheduled feeds, and single-record corrections through the same pipeline
  • Sometimes security is the whole job: sensitive data stays under BAS controls from your system to the next

If BAS Also Administers Your Programs

One load can feed many destinations. These are optional and never required for conversion-only clients.

BAS Enrollment

Eligibility, elections, and life-event data feed enrollment administration without re-keying.

BAS Billing

Imported rates, deductions, and census changes drive invoicing and reconciliation through premium billing.

BAS Compliance

The same data supports COBRA, ACA, and other compliance workflows.

Partner Exports

Payroll, HRIS, pension, carriers, and other vendors receive their exact layouts, on their schedule.

Discovery to Production

Every Field Vetted Before the First File Runs.

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.

  1. Step 1

    Discover

    Walk through sample files and target specifications with the data owners.

  2. Step 2

    Specify

    Write down every field-to-field requirement. The client signs off.

  3. Step 3

    Build

    BAS builds the template and map for this specific file.

  4. Step 4

    Test

    Run real sample files. Review every failure and warning together.

  5. Step 5

    Approve

    The receiving system accepts the output. The client approves go-live.

  6. Step 6

    Produce

    Files run on schedule. Layout changes are re-vetted and tested first.

What We'll Need to Get Started

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.

  • Sample files in the real layout, including the awkward cases.
  • The target specification from the receiving system or vendor.
  • Code tables for both sides, current and complete.
  • A decision-maker who can answer field questions and sign off.
  • A test window in the receiving system to confirm the output is accepted.
What Gets Vetted for Every Field-to-Field Requirement 8 questions BAS confirms with your data owners, with example answers
  • Question: Meaning
    What BAS confirms: What the source field holds and which target field it feeds
    Example answer: Deduction Amount → Amount
  • Question: Type and size
    What BAS confirms: Data type, length, and decimal places on both sides
    Example answer: text, 12 → number, 9.2
  • Question: Format
    What BAS confirms: Date and number formats, padding, alignment, delimiters
    Example answer: $1,250.00 → 1250.00
  • Question: Code values
    What BAS confirms: Every code the source can send and its target equivalent
    Example answer: MED → MED_PRETAX
  • Question: Required or optional
    What BAS confirms: Whether a blank is allowed, and the default if it is
    Example answer: required; no default
  • Question: Rule or calculation
    What BAS confirms: Any derivation, split, combination, or condition applied
    Example answer: none; pass through
  • Question: Validation
    What BAS confirms: What makes a value invalid, and whether it is a Failure or a Warning
    Example answer: negative = Failure
  • Question: Sign-off
    What BAS confirms: Who on the client side confirms the requirement is right
    Example answer: payroll manager
Validation + Security

Every File Checked Before Any Data Is Used. Every Transfer Kept Off Email.

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.

  • No data by email. Client files are never sent, received, corrected, or delivered by email.
  • Private, secure login. Self-service uploads happen only inside an authenticated MyEnroll360 session.
  • Dedicated SFTP folders. Automated feeds use a folder dedicated to each client, with files encrypted in transit.
  • User groups and roles. Only authorized users can upload files, see results, or work exceptions.
  • Full traceability. Every file, error, warning, correction, and export is logged, so you can always answer what loaded, when, and what changed.

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

File-Level Stop

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.

Failure

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.

Warning

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.

Duplicates and Reloads

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.

Common Use Cases

Data Conversion in Action

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.

Payroll Platform Changes

Move between payroll platforms without rebuilding files by hand.

An extract from one payroll platform is converted into the input file the other platform requires, including layout, codes, and data types.

Recurring Feeds

Run payroll deduction and eligibility feeds the same way every time.

Automated SFTP pickup and saved maps process each scheduled file under the same rules, with results reported back to your team.

Partner and Carrier Exports

Give every partner the exact layout it requires.

Payroll, HRIS, pension, and carrier recipients each receive data mapped to their specification, down to field order, lengths, padding, and code tables.

Onboarding and Full Loads

Load a complete population when systems change.

BAS-processed imports handle conversions, onboarding, and complex or irregular files, with BAS staff resolving exceptions alongside your team.

Vendor Specification Changes

Absorb a layout change without an internal rebuild.

When you or a partner change a layout, BAS re-vets the requirement, updates the map, and tests it before the next production run.

Sensitive Data Transfers

Move sensitive data between systems under documented controls.

Even a simple conversion benefits when data stays off email, access is role-based, and every file, correction, and export is logged.

Common Questions

Data Conversion Services — Frequently Asked Questions

  • 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.

Data Conversion Services

Ready to Retire the Spreadsheets and One-Off Extracts?

Tell BAS where your data comes from and where it needs to go. We'll walk through your sample files and target specifications with your data owners, then build the conversion around them, whether or not BAS administers your benefits programs.