How Nimbello Uses A/R/N Logic to Keep Your GL Coding Clean, Fast, and Accurate
If your organization sends GL master data to Nimbello using an Access Rules–based file structure, this article is for you.
Why This Structure Matters
Using Access Rules (A = Accessible, R = Required, N = Not Available) provides two major advantages:
-
Faster, more efficient GL coding — Nimbello guides users to the correct segments automatically.
-
Better accuracy and control — Consistent rules prevent invalid combinations and reduce coding errors across all tenants.
How It Works
Each GL Account number is paired with a set of letters that represent how each GL segment can be used inside Nimbello:
A — Accessible
Users may select this segment when coding invoices.
R — Required
Users must select this segment. It cannot be left blank.
N — Not Available
Users cannot select this segment. Nimbello blocks it from use.
Example Configuration
A Unit Code may be marked R (required), meaning users must choose one.
Other segments—such as Department, Location, Product Line, etc.—may be marked A (accessible) so they can be selected when needed.
Every GL account can have its own unique combination of A, R, and N. Because of this, correct setup in your ERP is crucial.
Where These Rules Come From
These designations (A, R, N) are defined in your company’s ERP, not in Nimbello.
If you need to change a segment that’s currently marked N (Not Available) to make it selectable:
-
Update the segment access rules in your ERP.
-
Wait for the next masterfile transfer job to send the updated rules to Nimbello.
Once the data transfers, Nimbello immediately begins enforcing the new access logic.
If you’d like help reviewing or confirming how your Access Rules are configured in Nimbello, feel free to reach out!