Drag and drop your Bill.com export file(s), or click to browse. CSV, XLSX, and XLS formats are accepted. You can upload multiple files in a single run — their columns are combined (duplicates removed) and all rows processed together.

Each file's headers, a sample row, and row count are detected automatically and feed the column pickers used in later steps.

Vendor ID

Choose how vendor IDs are handled for this transaction:

• No Vendor — No vendor required (e.g. Journal Voucher). Vendor validation is skipped.
• Use Bill.com as-is — The Bill.com file already contains a Vendor ID; no vendor file upload is needed.
• Validate & Populate Using MIP Vendor File — Upload your MIP Vendors export, match one or more Bill.com columns to MIP Vendors columns, and populate Vendor ID + 1099 + Address ID per row. Rows whose combined value isn't found in the vendor file are flagged.

When Validate & Populate Using MIP Vendor File is selected, upload the MIP Vendors file and match columns. Then choose which vendor file column holds the Vendor ID (populated into the output) and, optionally, which holds the Address ID.

1099 Handling

Choose whether 1099 information stays in Bill.com or is pulled from the MIP Vendors file:

• In Bill.com — 1099 information stays in the Bill.com file; nothing is pulled from the vendor file.
• In MIP — 1099 information is pulled from the MIP Vendors file and added to the output.

If In MIP is selected, indicate whether your Bill.com file contains 1099 information:

• Yes, it does — Match each 1099 field (Issue 1099, Form Type, Box Number) to a Bill.com column and a MIP Vendor column. Bill.com values are written to the output and validated against the vendor file; rows that differ are flagged.
• No, it doesn't — Select the 1099 columns from your MIP Vendors file. They populate the output by matching on the vendor key selected above. "Issue 1099" is an internal reference only — if a vendor's value is "No", that vendor's 1099 fields are left blank.

Optionally validate your data against MIP reference files. Each validation can be enabled or skipped independently.

MIP Chart of Accounts (COA)

Upload your MIP Chart of Accounts file, then pair one or more Bill.com columns to COA columns. Each pair is checked independently — a Bill.com value is valid if it appears anywhere in its paired COA column (no combination or row matching). A row is flagged whenever a selected Bill.com column has data and that value isn't found in the paired COA column, so you know the code needs to be added in MIP. Only the columns you select are checked.

MIP Account Code Combinations

Upload your Account Code Combination file and choose whether the combination strings in the file are Valid Strings (rows with codes NOT in the file are flagged) or Invalid Strings (rows with codes FOUND in the file are flagged). Column mapping is configured in the next step.

This step appears only when Account Code Combination validation is enabled. Map each Bill.com column to its matching Account Code Combination file column. The processor builds a compound key from these mappings to validate each row. Use Auto Match to fill pairs automatically by header name, then adjust as needed.

Session metadata

• Session ID (Import Batch Number) — Optional session identifier (the MIP import batch number) written to each output row.
• Session Date (Does Not Override the Effective Date) — An additional session date that does not override the row's Effective Date. Must be entered as mm/dd/yyyy (e.g. 09/17/2026). Any non-empty value that doesn't match this format is flagged and blocks processing.
• Session Description (Does Not Override Description) — An additional session description that does not override the row's Description. Written to each output row.

Field Length Validation (optional)

Optionally set a max length for a Document Number column and/or a Document Description column. Choose the column from the dropdown and enter the maximum character count. Values that exceed the limit are truncated in the Import tab and the row is flagged in the Errors tab as "Field Length". Leave both blank to skip this validation.

Check your own MIP database for the exact field length limits that apply to your setup. MIP's standard limits are 10 characters for Document Number and 50 characters for Document Description — use these as the max length values unless your database specifies otherwise.

Balancing

Choose how the entry balances in MIP:

• Use MIP Automatic Offsets — MIP handles balancing, or offsets are already in the file. No changes to the output.
• Manually Balance Output — A balancing row is inserted whenever the selected group column changes value. Configure the group/trigger column, the amount column (negated on the balancing row), the account/GL column (overwritten), and the GL account to balance to.
• Autofill Output — Empty cells in the selected column(s) are filled from the most recent non-empty value above them. No new rows are added — only existing empty cells are filled. Use this to carry values like vendor ID or account codes downward through rows that left them blank.

Review the summary of your selections, then click Validate & Preview. The tool processes all uploaded Bill.com rows, applies COA, Account Code Combination, Vendor, and 1099 validations, and shows a preview table.

Flagged rows are color-coded by exception type:

• COA Mismatch — a selected Bill.com code was not found in the paired COA column
• Account Code Combination — code combination failed validation
• Vendor Not Found — vendor not present in the MIP Vendors file
• 1099 Mismatch — Bill.com 1099 value differs from the MIP Vendor file
• Field Length — value exceeded the configured max length and was truncated
• Missing Required Field — column A (the first source column) is empty; this is a required field and must be filled before importing into MIP
• Missing Vendor ID — for invoice transaction types, the Vendor ID column is empty; invoices require a Vendor ID before importing into MIP
• Missing Invoice Number — for invoice transaction types, the Invoice Number column is empty; invoices require an Invoice Number before importing into MIP
• Missing Accounting Segment — a row is missing one or more mapped accounting segments (GL, Fund, Department, etc.); the specific missing columns are highlighted in amber and the row is excluded from the Import tab

You can edit any cell directly in the preview table before downloading. Invoice numbers and other key columns are exported as text to preserve leading zeros and prevent scientific notation.

Download

Click Download to export a three-tab workbook:

• Original — raw source rows in upload order, no added columns.
• Errors — only the flagged rows, each with an "Import Row" number (to locate it in the Import tab) and an "Error Type" column describing the exception.
• Import — the final, clean MIP-ready file. Only rows with no error flags are included; any flagged row is excluded (it lives on the Errors tab so you can fix it). Added columns (Vendor ID, 1099 Form Type, 1099 Box Number, Address ID, Session ID, Session Date, Description) appear after the source columns in a fixed order.