Skip to content
English
Sign in
  • There are no suggestions because the search field is empty.

How do I route projects to different Corfix accounts using Branches?

This article will summarize how to configure Branch settings in Acumatica to ensure your projects are sent to the correct Corfix account.

Note: If you are managing multiple Corfix accounts (e.g., different physical locations or entities) from a single Acumatica instance, you must define how each Branch connects to Corfix. Failing to do this may result in projects being sent to the wrong account by default.

Overview & Explanation

In Acumatica, a Branch often represents a specific office, region, or division. If your company uses separate Corfix accounts for these different divisions, you must "link" them manually.

How It Works (Step-by-Step)

  • Create a New Corfix Preference for each Branch For every unique Corfix account you have, you must create a corresponding entry in the Corfix Preferences screen.

    • Navigate to Corfix Preferences.

    • As shown in the configuration screen, you must enter the specific login credentials and API details for that destination account.

Note: If you want "Branch 1" "Branch 2" and "Branch 3" to all go to different Corfix accounts, you must have a preference saved for each one.

  • Assign the Branch to Your Project Open the Projects screen in Acumatica.

    • Ensure the Branch field on the project matches the location you configured in Step 1.

    • Check the Export to Corfix box on the project header.

 

Warning: If you uncheck this box later, you will see a warning that the link will be broken. Re-checking it later may create a duplicate project in Corfix.

  • Filter by Branch in Prepared Data When you are ready to sync, go to the Corfix Prepared Data screen.

    • Use the Branch ID filter to view only the projects belonging to a specific office (e.g., Milwaukee).

    • This ensures you are only processing data for the specific account you intend to update.

Understand the "Default" Rule If you attempt to process a project for a branch that does not have its own preference set up, the system will automatically send that data to your Default Preference account. Always double-check that a branch-specific preference exists to avoid sending data to the wrong office.

Use Cases and Benefits

  • Regional Management: Keeps your "Ottawa" project data completely separate from your "Vancouver" data for cleaner reporting.

  • Security: Ensures users in one Corfix account don't see projects belonging to a different business entity.

  • Automation: Once the branch preference is set, the system remembers where to send updates every time you click "Process," saving you from manual data entry.