Search Results

Consolidated Accounts Purpose and when to use this record Define the common reporting accounts that receive mapped balances from individual stores. At a glance Identify it by: Code, and Name. Why care: Consolidated results are only as reliable as store con...

Adjustment Entries Purpose and when to use this record Record a dated topside or elimination adjustment used only in consolidated reporting. At a glance Identify it by: Name, and Entry Date. Why care: Consolidated results are only as reliable as store conn...

Sync Runs Purpose and when to use this record The Sync Runs overview screen in the Brisk documentation demo. The Sync Runs overview screen in the Brisk documentation demo. The Sync Runs overview screen in the Brisk documentation demo. The Sync Runs overview sc...

Reporting Stores Purpose and when to use this record Configure a participating store’s reporting endpoint, timezone, currency, transport safeguards, and synchronization health. At a glance Identify it by: Name. Why care: Consolidated results are only as re...

Store Account Maps Purpose and when to use this record The Store Account Maps overview screen in the Brisk documentation demo. Map or intentionally ignore a store-level account when rolling balances into the consolidated chart. At a glance Identify it by: Co...

Consolidation Consolidation overview The Consolidation workspace related to this reference article. Consolidation—shown in Brisk as Multi-Store Reporting—collects reporting data from participating stores, maps their local accounts into a common chart, and prod...