Skip to main content
Question

Month end close, multi branch variances

  • August 10, 2026
  • 2 replies
  • 24 views

Hello,

We recently encountered an issue where production order variances are being attributed to the incorrect branch. Our current set up is a two tenant, two branch instance.

Our production orders for both sites are manually closed by a site admin, who has a profile at one branch but not both. In this case, the work order variances are being attributed to the branch the site admin’s profile belongs to. I’ve checked the warehouse profile and there are no GL accounts populated at all throughout the list. 

I guess the question is, will the user’s profile who is manually closing the orders play a role in determining what branch the variances are posted to? Especially if the warehouse profile GL accounts aren’t set up.

 

2 replies

Laura03
Captain II
Forum|alt.badge.img+20
  • Captain II
  • August 10, 2026

Hello,

One of our clients experienced the same results recently. Please vote for improvements here. (Link)

We worked around the problem by creating two automation schedules with filters by Branch, to close/release these transactions.


Kandy Beatty
Captain II
Forum|alt.badge.img+18
  • Captain II
  • August 10, 2026

Hello ​@bosborne 

Along with what ​@Laura03  said, here are some suggestions:

I would check:

  1. Branch on the Production Order

    • Open a production order from each site and confirm the Branch value.
  2. Branch on the Resulting GL Batch

    • Compare a correctly posted variance and an incorrectly posted variance.
    • Review the GL batch details to see which branch is assigned to the transaction lines.
  3. User Access

    • Does the site admin only have access to one branch?
    • Are they switching branches before closing orders?
  4. Production Order Type

    • Verify the WIP and WIP Variance account sources on the Production Order Type and Posting Class setup.