Importing Documents into Microix Workflow Modules Modern

Creation date: 3/18/2026 10:28 AM Updated: 3/18/2026 11:13 AM csv documents import

Overview

This article outlines the process for importing documents into Microix Workflow Modules (Modern UI). It includes required data structure, field definitions, and best practices to ensure a successful import.

Prerequisites

Access to Microix Workflow Modules (Modern version)
A properly formatted import file (based on Microix template which can be generated from the application)
Valid reference data in MIP/Microix (vendors, addresses, workflow IDs, etc.)

Import File Requirements

Use the provided Microix import template. Each row represents a document line, and multiple rows can belong to the same document.

Column Definitions & Requirements

Core Document Fields

Column Name	Description	Requirement
sDocPrefix	Document prefix (e.g., ENC, PO, API)	Must match configured prefixes
sDoctype	Document type	Static value: Use `API` for Invoices and `ENC` for Purchase Orders. For other document types (e.g., JV, CD, CR), either `API` or `ENC` can be used, depending on how you want the document to route through the approval workflow, as this field determines the approval processing behavior.
Status	Workflow status level	Static value: `0` (or desired workflow level)
Document No	Document Identifier	If you want Microix to automatically assign a document number, set this column value to "To Be Assigned". Otherwise, enter an alphanumeric number. (NOTE: Perform imports during off-hoursto avoid duplicate numbering conflicts)
Reason	Reason for document	Optional
Vendor Invoice No	Vendor invoice reference	Optional
Comments	Additional notes	Optional
Document Date	Date of the document	Required

Vendor & Address Fields

Column Name	Description	Requirement
Vendor ID	Vendor identifier	Must match a valid MIP Vendor ID
Check Address ID	Vendor Address	Must match MIP address ID (Default: `Main`)

Workflow & Ownership Fields

Column Name	Description	Requirement
Prepared By	Requester in Microix	Required
Workflow	Workflow ID	Must be a valid Microix Workflow ID
Bill To	Billing address code	Optional (must be valid if used)
Ship To	Shipping address code	Optional (must be valid if used)

Line-Item Fields

Column Name	Description	Requirement
Item No	Vendor UPC / Item code	Use `N/A` if not applicable
Qty	Quantity	Default to `1` if not applicable
Units	Unit of measure	Default to `EA`
Date	Transaction line date	Required
Item Description	Description of item/service	Required
Price	Line-item price	Required

Accounting Fields (COA Segments)

All remaining columns correspond to your Chart of Accounts (COA) segments.
These fields:

Should be populated if required by your organization
Can alternatively be completed within Microix after import

2. Data Validation

Before importing, verify:

Vendor IDs exist in MIP
Address IDs are valid
Workflow IDs are active
Required fields are populated

3. Default Values

Use the following defaults when data is not applicable:

Item No: N/A
Qty:1
Units: EA
Check Address ID: Main

4. Multi-Line Documents

Each document can have multiple rows (line items)
Ensure all rows for the same document share consistent header values (prefix, vendor, workflow, etc.)

Troubleshooting Tips

Issue	Likely Cause
Import fails	Missing required fields or invalid IDs
Vendor not found	Vendor ID does not exist in MIP
Workflow error	Invalid or inactive Workflow ID
Error with no message	Verify you import file do not contain any blank rows

Summary

Successful document import into Microix depends on:

Proper template formatting
Valid reference data (Vendor, Workflow, Addresses)
Correct use of static/default values
Performing imports during controlled time windows