Skip to main content

Tally Definitions

Tally Definitions

Purpose and when to use this record

Define a recurring countable agency activity used in logs and performance reporting.

At a glance

  • Identify it by: Name.

  • Check its business context: Category.

  • Why care: Use the agency’s approved terminology and access policy. Preserve dates, responsible personnel, case links, and audit history because these records may support official reporting or custody review.

  • 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 storespermission for the action you are taking on tally definitionsdefinitions. asIf parta ofCreate, theEdit, lawor enforcementDelete module. This generated referencecontrol is awaitingabsent, workflowdo review.not work around it with another user’s account; ask an administrator to review your role.

Have valid Category records ready first. Those selections determine where this Tally Definition belongs and which later screens can find it.

Create a recordTally Definition

Brisk Tally Definitions create screen displayed with fictional documentation-demo data.
The Tally Definitions create screen in the Brisk documentation demo.

TheCreate evidencea packetTally identifiesDefinition only when the viewexisting choices do not represent the policy or classification you need. Near-duplicate setup values split reporting and sourcemake locationlater selection harder.

  1. Select the business context first: Category.

  2. Enter the required identifying and operational values: Category, and Name.

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

  4. Save the Tally Definition, then confirm Name on its detail page before continuing.

After saving: Open Tallies and confirm the Tally Definition appears with the intended label and availability. Keep the old value for thishistorical action.records Confirmwhen user-facingchanging stepsit beforewould approvingsplit or relabel prior reporting.

Delete a Tally Definition

Delete this page.Tally Definition 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 related Tallies. Brisk may refuse deletion when another record depends on this one; resolve the duplicate or use the supported correction workflow instead of breaking the trail.

On the confirmation page, verify Name. After confirmation, return to the Tally Definitions list and make sure only the intended Tally Definition was removed.

ViewReview recordTally Definition details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Tally Definition currently means. Verify Active before relying on it for a decision.

Follow Category to determine whether the issue is on this Tally Definition or on one of those linked records.

Next check: Open Tallies and sourceconfirm locationthe Tally Definition appears with the intended label and availability. Keep the old value for thishistorical action.records Confirmwhen user-facingchanging stepsit beforewould approvingsplit or relabel prior reporting.

Edit an existing Tally Definition

Edit this Tally Definition when the underlying policy or classification changed. First determine whether historical transactions should retain the old value; if so, deactivate the old choice and create a new one.

  1. Open the detail page. Compare Category with the supporting document or approved request.

  2. Recheck Active. These values are most likely to change case history, custody, dispatch, official reporting, or audit review.

  3. Save the change, return to the list, and confirm that the Tally Definition now appears under the expected Active.

After the change: Open Tallies and confirm the Tally Definition appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

Find and review recordstally definitions

Brisk Tally Definitions list screen displayed with fictional documentation-demo data.
The Tally Definitions list screen in the Brisk documentation demo.

The evidence packet identifiesUse the viewTally Definitions list to find the correct record before opening or changing it. Compare Name. Records with similar names or numbers can still belong to different Category.

Open the Tally Definition whose Name match the task. If it is missing, clear the list filters and sourcerecheck locationActive rather than creating a replacement immediately.

Fields and business rules

Brisk stores 5 user-relevant fields for this action.Tally ConfirmDefinition, user-facingincluding steps1 beforelinked-record approvingselection and 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

FieldRequiredWhat it controls
CategoryYesThe category associated with this tally definition.
NameYesSets the name of this tally.
Sort OrderNoSets the order that this tally appears within its category.
CurrencyNoIf enabled, this field will report a dollar amount on reports.
ActiveNoIf this field is unchecked, this definition will no longer appear in reports.

What happens next

Open Tallies and confirm the Tally Definition appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

EditCommon anmistakes existingand troubleshooting

  • The record

    Thewill evidencenot packetsave: identifiesRecheck Category, and Name and any message beside the viewfield. andA sourcerequired locationrelated record may also be inactive or unavailable to your role.

  • The record saved but is not available where expected: Recheck 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: Open Category from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for this action. Confirm user-facing steps before approving this page.it.

    Delete

  • a
record

The evidence packet identifies the view and source location for this action. Confirm user-facing steps before approving this page.