Skip to main content

Deposits

Deposits

Purpose and when to use this record

BriskMove storesundeposited depositsfunds asinto parta ofbank account and create the accountingbalancing module.detail Thisfor generatedthe referencewarehouse and work period involved.

At a glance

  • Identify it by: Deposit Date.

  • Check its business context: Bank Account, Source Account, Warehouse, and Work Period.

  • Why care: Dates, accounts, amounts, posting state, and period locks can change financial reports. Verify them against the source document before finalizing the record.

Before you begin

You need the Brisk permission for the action you are taking on deposits. 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.

Have valid Bank Account records ready first. Those selections determine where this Deposit belongs and which later screens can find it.

Create a recordDeposit

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

TheCreate evidencea packetDeposit identifiesonly after confirming that the viewsource document or operational event has not already been entered.

  1. Select the business context first: Bank Account, Source Account, Warehouse, and sourceWork locationPeriod.

  2. Enter the required identifying and operational values: Bank Account, and Amount.

  3. Review Dispersal Method, and Enable Splits deliberately; these choices control availability or workflow rather than merely describing the record.

  4. Save the Deposit, then confirm Deposit Date on its detail page before continuing.

After saving: Compare the saved deposit with the bank deposit record, then include it in the next reconciliation for thisthe action.selected Confirmbank user-facingaccount.

steps

Delete beforea approvingDeposit

Delete this page.Deposit only when it was entered by mistake and no downstream history depends on it. Use a reversal, void, credit, counter-adjustment, or status correction for a real event that later changed.

Before confirming, check for related Bank Information, Deposit Balancing Transactions, Sheriff Bank Deposits, and Transactions. 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 Deposit Date. After confirmation, return to the Deposits list and make sure only the intended Deposit was removed.

ViewReview recordDeposit details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Deposit currently means. Verify Amount, Deposit Date, and sourceDispersal locationMethod before relying on it for thisa action.decision.

Confirm

Follow user-facingBank stepsAccount, beforeSource approvingAccount, Warehouse, and Work Period to determine whether the issue is on this Deposit or on one of those linked records.

Next check: Compare the saved deposit with the bank deposit record, then include it in the next reconciliation for the selected bank account.

Edit an existing Deposit

Edit this Deposit to correct or complete the same source document or operational event; use the supported reversal or follow-up workflow when the business event itself changed.

  1. Open the detail page. Compare Bank Account, Source Account, Warehouse, and Work Period with the supporting document or approved request.

  2. Recheck Bank Account, Source Account, Warehouse, Amount, Deposit Date, and Dispersal Method. These values are most likely to change account balances, financial periods, and statement results.

  3. Save the change, return to the list, and confirm that the Deposit now appears under the expected Dispersal Method.

After the change: Compare the saved deposit with the bank deposit record, then include it in the next reconciliation for the selected bank account.

Find and review recordsdeposits

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

The evidence packet identifiesUse the viewDeposits list to find the correct record before opening or changing it. Compare Deposit Date. Records with similar names or numbers can still belong to different Bank Account, Source Account, Warehouse, and sourceWork locationPeriod.

Open the Deposit whose Deposit Date match the task. If it is missing, clear the list filters and recheck Dispersal Method rather than creating a replacement immediately.

Fields and business rules

Brisk stores 9 user-relevant fields for this action.Deposit, Confirmincluding user-facing4 stepslinked-record beforeselections approvingand 1 controlled-choice field. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

The

evidence Confirmuser-facingstepsapproving

Delete

arecord

Confirmuser-facingstepsapproving
Field Required What packetit identifiescontrols
Bank AccountYesSelect the viewbank andaccount to which this deposit will be made.
Source AccountNoSelect the source locationof undeposited funds.
WarehouseNoAssociates this deposit with a system warehouse.
AmountYesThe amount value recorded for this action.deposit.
Deposit beforeDate NoDate recorded for deposit date on this page.

deposit.
Memo NoThe evidencememo packet identifies the view and source locationrecorded for this action.deposit.
Dispersal beforeMethod NoRecords how this page.deposit was made. Available values: ACH/Bank Transfer, Bank Deposit, Mobile Deposit, ATM Deposit, Other.
Work PeriodNoOptionally link this deposit to a work period.
Enable SplitsNoEnable split balancing transactions for this deposit. Enabled by default, but disabled in specific circumstances.

What happens next

Compare the saved deposit with the bank deposit record, then include it in the next reconciliation for the selected bank account.

Common mistakes and troubleshooting

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

  • The values look right but the result is wrong: Open Bank Account, Source Account, Warehouse, and Work Period from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.