Consolidated Accounts

Consolidated Accounts

Purpose and when to use this record

BriskDefine storesthe consolidatedcommon 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 partreliable as store connectivity, account mapping, currency/timezone setup, and the status of the consolidationlatest module.run.

  This
generated
• reference

  Why care: Availability and publication flags affect future use without erasing history. Prefer disabling an obsolete setup record when existing transactions still refer to it.

Before you begin

You need the Brisk permission for the action you are taking on consolidated accounts. If a Create, Edit, or Delete control is awaitingabsent, workflowdo review.not work around it with another user’s account; ask an administrator to review your role.

Create a recordConsolidated Account

TheCreate evidencea packetConsolidated identifiesAccount after searching for the viewperson, organization, item, location, or resource under alternate names and sourceidentifiers. locationMerge or correct an existing master record instead of creating a duplicate.

1. Select the business context first.

2. Enter the required identifying and operational values: Code, Name, and Statement Type.

3. Review Statement Type, and Active deliberately; these choices control availability or workflow rather than merely describing the record.

4. Save the Consolidated Account, then confirm Code, and Name on its detail page before continuing.

After saving: Verify this Consolidated Account in Adjustment Lines, Adjustment Snapshot Lines, General Ledger Snapshot Lines, and General Ledger Snapshot States, plus the remaining screen fields before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Delete a Consolidated Account

Delete this Consolidated Account only if it is an unused duplicate or setup mistake. Once other records refer to it, preserve that history and make the value inactive when the screen provides that option.

If the record is merely obsolete, use Active to remove it from future use while preserving existing references.

Before confirming, check for thisrelated action.Adjustment ConfirmLines, user-facingAdjustment stepsSnapshot beforeLines, approvingGeneral Ledger Snapshot Lines, General Ledger Snapshot States, and Store Account Map Snapshots, plus the remaining screen fields. Brisk may refuse deletion when another record depends on this page.one; resolve the duplicate or use the supported correction workflow instead of breaking the trail.

On the confirmation page, verify Code, and Name. After confirmation, return to the Consolidated Accounts list and make sure only the intended Consolidated Account was removed.

ViewReview recordConsolidated Account details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Consolidated Account currently means. Verify Statement Type, and sourceActive locationbefore relying on it for thisa action.decision.

Confirm

Compare user-facingthe stepsConsolidated Account with its source document or approved setup request before approvingdeciding that it needs correction.

Next check: Verify this Consolidated Account in Adjustment Lines, Adjustment Snapshot Lines, General Ledger Snapshot Lines, and General Ledger Snapshot States, plus the remaining screen fields before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Edit an existing Consolidated Account

Edit this Consolidated Account to keep the same real-world party, item, location, or resource accurate. Do not repurpose it for a different entity after activity is attached.

1. Open the detail page. Compare Code, and Name with the supporting document or approved request.

2. Recheck Statement Type, and Active. These values are most likely to change store mapping and consolidated statement results.

3. Save the change, return to the list, and confirm that the Consolidated Account now appears under the expected Statement Type, and Active.

After the change: Verify this Consolidated Account in Adjustment Lines, Adjustment Snapshot Lines, General Ledger Snapshot Lines, and General Ledger Snapshot States, plus the remaining screen fields before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Find and review recordsconsolidated accounts

The evidence packet identifiesUse the viewConsolidated Accounts list to find the correct record before opening or changing it. Compare Code, and sourceName. locationCompare the full identifier rather than relying on a similar name.

• Keyword search checks Code, Name, Statement Type, and Section.

• The initial order emphasizes Statement Type, Section, Code, and Name. Select a column heading when you need a different comparison.

Open the Consolidated Account whose Code, and Name match the task. If it is missing, clear the list filters and recheck Statement Type, and Active rather than creating a replacement immediately.

Fields and business rules

Brisk stores 5 user-relevant fields for this action.Consolidated ConfirmAccount, user-facingincluding steps0 beforelinked-record approvingselections and 1 controlled-choice field. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

The

evidencetheviewandsourcelocation user-facingstepsbeforethispage.

Delete a record

Field	Required	What packetit identifiescontrols
Code	Yes	Short code used to identify this consolidated account.
Name	Yes	Human-readable name for this action.consolidated Confirmaccount.
Statement approvingType	Yes	The evidencestatement packettype identifies the view and source locationrecorded for this action.consolidated Confirmaccount. user-facingAvailable stepsvalues: Balance Sheet, Profit & Loss.
Section	No	The section recorded for this consolidated account.
Active	No	Whether this consolidated account is active and available for use.

What happens next

Verify this Consolidated Account in Adjustment Lines, Adjustment Snapshot Lines, General Ledger Snapshot Lines, and General Ledger Snapshot States, plus the remaining screen fields before approvingstaff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Common mistakes and troubleshooting

• The record will not save: Recheck Code, Name, and Statement Type and any message beside the field. A required related record may also be inactive or unavailable to your role.

• The record saved but is not available where expected: Recheck Statement Type, and Active, then clear the filters on the destination list. A saved record can still be inactive, unpublished, locked, unapproved, or in the wrong workflow state.

• The values look right but the result is wrong: Compare this page.Consolidated Account with the source document or approved setup decision, then check the downstream screen where it is used.