This article explains how Microix (Modern Version) validates account code entry, determines required segments, and checks budgets during document entry and submission. The rules described below apply specifically to account code segment behavior and validations performed during data entry and during submit/approve.
Workflow Budget Segments are used to determine which account segments Microix should evaluate when checking for an existing Budget in MIP’s Ledger.
This rule ensures that users can only enter account code combinations that MIP recognizes as valid.
This rule controls which segments are required during data entry and submission, based on segment type and GL account type.
The segment title will turn Green only for segments of type:
During data entry, Microix requires only the segments of type:
GL / FUND / BAL
Other segment types may appear on the screen, but they are not required during entry unless additional MIP configuration exists (see Section 3.4).
When the document is submitted or approved, Microix performs a second validation based on the GL account type used on each line.
All segments are required.
Then segments of type GL / FUND / BAL are required.
If the customer has configured Required Segments in MIP for GL Types (NBAL/RES), then Microix will:
Treat those segments as required during data entry, even if the segment is associated with RES/NBAL type accounts.
Additionally:
When Microix applies offset entries, it will populate these segments even if the offset line is a RES/NBAL type account.
| Rule | When it Applies | What it Does |
|---|---|---|
| Workflow Budget Segments | Budget lookup logic | Not required for entry; used only for budget check targeting |
| Enforce MIP Account Code Combination | Data Entry | Blocks invalid MIP account combinations |
| Required Account Codes (GSID 69) | Entry + Submit/Approve | Requires GL/FUND/BAL during entry; may require all segments at submit depending on GL type |
| Prevent Account Codes at Level 0 | N/A | Deprecated |