Skip to main content

​
Overview

A Business Unit (FCORE_PAY__Business_Unit__c) represents a single “selling entity” or financial division inside your Salesforce org. Each Order, Financial Event, and GL Account (a general-ledger account record) is tagged with a Business Unit. This lets one org run several separate “books” — for example, a foundation and an association — each with its own revenue, taxes, write-offs, and adjustments tracked independently. fusionCore does not post journal entries or debits and credits itself. Instead, it organizes the financial data — by Business Unit — that your general-ledger system uses to do its own posting. A Business Unit is the top-level container that keeps that data separate. A Business Unit also carries:
  • Branding and contact details — a logo, email, phone, website, and billing address. The billing address feeds the financial documents you generate.
  • Default accounting configuration — the default GL Accounts and tax product used when money moves, plus the accounts used for transfers between Business Units.
  • Automation settings — whether write-off and adjustment transactions post automatically or wait for manual review.
Why Business Units help:
  • Clear data organization. Each Business Unit keeps its GL Accounts, Payment Types, Products, Orders, and Financial Events separate, which is helpful when you analyze performance for a specific division.
  • Tailored reporting. You can build reports scoped to a single Business Unit without unrelated data getting in the way.
  • Access control. Business Units are one of several tools administrators use to control which end users see which records.
fusionCore does not post journal entries or debits and credits itself. It records the financial data — tagged by Business Unit — that your general-ledger system uses to post. Keeping Business Units separate is what keeps those books separate.

​
The Default Business Unit

You can flag one Business Unit as the org-wide default by checking Is Default (Is_Default__c). Only one Business Unit can be the default at a time. If you try to mark a second one as default, fusionCore blocks the save with an error. To change which Business Unit is the default, clear Is Default on the current default first, then set it on the new one.

​
Working with Business Units

Creating a Business Unit

Create a Business Unit record, fill in its branding and contact details, and set its default accounting configuration.

Uploading an Image to the Business Unit

Add a logo to a Business Unit and store its URL on the record.

Configuring Automatic Write-Offs and Adjustments

Choose whether write-off and adjustment Financial Events post automatically or wait for manual review.

General ledger (GL) accounts

Each Business Unit’s default accounts point at GL Accounts, and every GL Account belongs to one Business Unit.

Payment Types

Payment Types are configured per Business Unit and deposit into that unit’s GL Accounts.

Taxes

A Business Unit’s Default Tax Product must be an active product marked as taxable.

Writing off an Order

A write-off uses each Business Unit’s Default Write-Off Account, set on the Business Unit.

​
Notes about Business Units

  • One Business Unit per GL Account. A GL Account can belong to only one Business Unit. The default-account lookups on the Business Unit are filtered to show only GL Accounts tied to that same Business Unit.
  • Default accounts can disappear silently. If you delete a GL Account that a Business Unit uses as a default account, the Business Unit’s reference to it is cleared automatically rather than blocking the delete. The default-account field goes blank without warning, so check your defaults after removing any GL Account.
  • A write-off needs a Default Write-Off Account. A write-off fails if the Business Unit involved has no Default Write-Off Account set. This check runs against each order item’s Business Unit, not just the Order’s header, so confirm every Business Unit in play has a Default Write-Off Account before writing off an Order.
  • Default Tax Product rules. The product you choose as Default Tax Product must be active, must be marked as a tax product, and must not have a pricing condition configured. Otherwise the save is blocked.
  • The only-one-default-Business-Unit rule cannot be turned off in Setup. The single-default limit is enforced by fusionCore automation, not by a standard validation rule, so an administrator cannot toggle it off.