Skip to main content

​
Overview

A Business Unit is a configuration record that represents one selling entity or financial division inside your fusionCore org. Its API name is FCORE_PAY__Business_Unit__c. Every order, financial event, and GL Account (a general-ledger account record) is tagged with a Business Unit. This lets one org keep several sets of books — for example, a foundation and an association — with their own default accounts, tax handling, and document branding. A Business Unit also carries contact details, a billing address, and a logo that appear on financial documents.
Create your GL Accounts and tax products after you create the Business Unit. A GL Account must reference a Business Unit, and a Business Unit’s default-account lookups only show GL Accounts already tied to that same Business Unit. Set up the Business Unit first, then come back to fill in its default accounts.

​
Prerequisites

  • You need the FC_Commerce_Manage_Config_Data permission set. This is the only permission set that lets you create, edit, or delete Business Units.
    • This permission set can be found in the Admin and Accounting User PSGs
  • Create your GL Accounts (GL_Account__c) and any tax products after you create the Business Unit. A GL Account requires a Business Unit, and the account and tax-product lookups on the Business Unit only show records already tied to it.

​
How to Create a Business Unit

1

Open the Business Units tab

Click the App Launcher, type Business Units, and select it.
App Launcher search showing the Business Units result

App Launcher with Business Units

2

Click New

At the top right, click New.
3

Enter the basic details

Give the Business Unit a Business Unit Name (for example, Foundation).Optionally fill in the contact and branding fields that appear on financial documents:
  • Email (Email__c)
  • Phone (Phone__c)
  • Website (Website__c)
  • Billing Address (Billing_Address__c)
4

(Optional) Set this as the org default

Check Is Default (Is_Default__c) if this should be the org-wide default Business Unit. Only one Business Unit can be the default. If another record is already the default, the save is blocked with an error — clear the other record’s Is Default first.
5

Set the default financial configuration

In Default Financial Configuration, set the default GL Accounts and tax handling. These lookups only list records already tied to this Business Unit, so create those records first (see Prerequisites).
  • Default Credit Account (Default_Credit_Account__c) — a GL Account.
  • Default Write-Off Account (Default_Writeoff_Account__c) — a GL Account. Required to write off orders for this Business Unit (see Limitations and common pitfalls).
  • Due From Account (Due_From_Account__c) and Due To Account (Due_To_Account__c) — GL Accounts used for transfers between Business Units.
  • Default Tax Product (Default_Tax_Product__c) — an active product (Product2) marked as a tax product and tied to this Business Unit.
  • Auto-Update Write-Off FE To Succeeded (Auto_Update_Write_Off_FE_To_Succeeded__c) and Auto-Update Adjustment FE To Succeeded (Auto_Update_Adjustment_FE_To_Succeeded__c) — see Configuring Automatic Write-Offs and Adjustments. Both are checked by default.
  • Summary Taxes (Summary_Taxes__c).
6

Save

Click Save.
7

Add a logo

After saving, add a logo to the record. See Uploading an Image to the Business Unit.
Only one Business Unit can be assigned to a GL Account.

​
Limitations and Common Pitfalls

  • Auto-succeed is enabled by default. Auto-Update Write-Off FE To Succeeded and Auto-Update Adjustment FE To Succeeded are both checked when a Business Unit is created. While checked, write-off and adjustment Financial Events post as Succeeded as soon as they fire. Uncheck a field to hold those events for manual review.
  • Zero-dollar transactions auto-succeed regardless. A $0 write-off or adjustment posts as Succeeded even when the matching auto-update field is unchecked.
  • A write-off needs a Default Write-Off Account. If the Business Unit on an order item has no Default Write-Off Account, the write-off fails. The check runs against each order item’s Business Unit, not just the order header.
  • Only one default, enforced in code. The one-default rule is enforced when you save the record, not by a Salesforce validation rule you can switch off in Setup. To change which Business Unit is the default, clear Is Default on the current default first.
  • GL Account / Business Unit mismatch blocks the save. A chosen Default Credit Account or Default Write-Off Account must belong to this Business Unit. The lookup filters enforce this in the UI, but records loaded by data import bypass the filter and hit the same error on save.
  • Default Tax Product rules. The product must be active, marked as a tax product (Is_Tax__c = true), tied to this Business Unit, and must not have a condition configured. Otherwise the save is blocked.
  • A write-off or adjustment rejects a pending Financial Event. A Financial Event whose status is Pending cannot be written off or adjusted. These checks run before the auto-succeed step.
  • Deleting a GL Account silently clears the default. If you delete a GL Account that a Business Unit uses as a default account, the Business Unit’s field is cleared rather than blocked — a default account can disappear without warning.