Debit Cards

Debit Cards

Purpose and when to use this record

BriskIdentify storesthe debit cards asand partbank-payment ofmethods available when recording withdrawals from a bank account.

At a glance

• Identify it by: Bank Account, Card Holder, Identifier, and System Generated.

• Check its business context: Bank Account.

• Why care: Dates, accounts, amounts, posting state, and period locks can change financial reports. Verify them against the accountingsource module.document Thisbefore generatedfinalizing referencethe record.

Before you begin

You need the Brisk permission for the action you are taking on debit cards. 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 debit card belongs and which later screens can find it.

Create a recorddebit card

TheCreate evidencea packetdebit identifiescard 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: Bank Account.

2. Enter the required identifying and operational values: Bank Account, Card Holder, and Identifier.

3. Review System Generated deliberately; these choices control availability or workflow rather than merely describing the record.

4. Save the debit card, then confirm Bank Account, Card Holder, Identifier, and System Generated on its detail page before continuing.

After saving: Open Payment Cards and confirm the debit card 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 debit card

Delete this page.debit card 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.

Before confirming, check for related Payment Cards. 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 Bank Account, Card Holder, Identifier, and System Generated. After confirmation, return to the Debit Cards list and make sure only the intended debit card was removed.

ViewReview recorddebit card details

The evidence packet identifiesUse the viewdetail page as the shared record of what this debit card currently means. Verify Bank Account, Card Holder, Identifier, and sourceSystem locationGenerated before relying on it for thisa action.decision.

Confirm

Follow user-facingBank stepsAccount beforeto approvingdetermine whether the issue is on this debit card or on one of those linked records.

Next check: Open Payment Cards and confirm the debit card appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

Edit an existing debit card

Edit this debit card 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 Bank Account with the supporting document or approved request.

2. Recheck Bank Account. 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 debit card now appears under the expected the identifying information shown on the screen.

After the change: Open Payment Cards and confirm the debit card 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 recordsdebit cards

The evidence packet identifiesUse the viewDebit Cards list to find the correct record before opening or changing it. Compare Bank Account, Card Holder, Identifier, and sourceSystem locationGenerated. Records with similar names or numbers can still belong to different Bank Account.

Open the debit card whose Bank Account, Card Holder, Identifier, and System Generated match the task. If it is missing, clear the list filters and recheck the identifying information shown on the screen rather than creating a replacement immediately.

Fields and business rules

Brisk stores 4 user-relevant fields for this action.debit Confirmcard, 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.

Editanexistingrecord

The

evidence

Field	Required	What packetit identifiescontrols
Bank Account	Yes	Connects this debit card to the viewbank andaccount sourceit locationdraws from.
Card Holder	Yes	Enter the name of the card holder on this account.
Identifier	Yes	Enter some identifying information for this action.card, Confirmsuch user-facingas stepsits beforelast approving4 thisdigits page.or a shorthand nickname.
System Generated	No	Represents payment by bank without debit card for use by checkbook system.

What happens next

Open Payment Cards and confirm the debit card appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

DeleteCommon mistakes and troubleshooting

• The record will not save: Recheck Bank Account, Card Holder, and Identifier 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 from the detail page. Correct the specific relationship that is wrong instead of forcing a recordtotal

  Theor evidencestatus packetto identifies the view and source locationcompensate for this action. Confirm user-facing steps before approving this page.it.