Skip to main content

Credit Card Charges

Credit Card Charges

Purpose and when to use this record

Record a card purchase or credit, its vendor, statement-clearing state, amount, and transaction date.

At a glance

  • Identify it by: Reference #, and Charge Date.

  • Check its business context: Vendor, and Card Account.

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

  • Why care: Treat posted, processed, paid, reversed, and edit-locked states as controls—not ordinary descriptive fields. Confirm the source transaction before changing any state that the screen permits you to change.

Before you begin

You need the Brisk storespermission for the action you are taking on credit card chargescharges. asIf parta ofCreate, theEdit, accountingor module.Delete 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 Vendor, and Card Account records ready first. Those selections determine where this Credit Card Charge belongs and which later screens can find it.

Create a recordCredit Card Charge

Brisk Credit Card Charges create screen displayed with fictional documentation-demo data.
The Credit Card Charges create screen in the Brisk documentation demo.

TheCreate evidencea packetCredit identifiesCard Charge 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: Vendor, and Card Account.

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

  3. Review Transaction Type, Cleared, and Edit Locked deliberately; these choices control availability or workflow rather than merely describing the record.

  4. Save the Credit Card Charge, then confirm Reference #, and Charge Date on its detail page before continuing.

After saving: Open Credit Card Reconciliation Information, Expense/Asset Categories, and Transactions and confirm the Credit Card Charge 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 Credit Card Charge

Delete this page.Credit Card Charge 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 Credit Card Reconciliation Information, Expense/Asset Categories, 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 Reference #, and Charge Date. After confirmation, return to the Credit Card Charges list and make sure only the intended Credit Card Charge was removed.

ViewReview recordCredit Card Charge details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Credit Card Charge currently means. Verify Amount, Charge Date, Transaction Type, Cleared, and sourceEdit locationLocked before relying on it for thisa action.decision.

Confirm

Follow user-facingVendor, stepsand beforeCard approvingAccount to determine whether the issue is on this Credit Card Charge or on one of those linked records.

Next check: Open Credit Card Reconciliation Information, Expense/Asset Categories, and Transactions and confirm the Credit Card Charge 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 Credit Card Charge

Edit this Credit Card Charge 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 Vendor, and Card Account with the supporting document or approved request.

  2. Recheck Vendor, Card Account, Amount, Charge Date, Transaction Type, and Cleared, plus the remaining screen fields. 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 Credit Card Charge now appears under the expected Transaction Type, Cleared, and Edit Locked.

After the change: Open Credit Card Reconciliation Information, Expense/Asset Categories, and Transactions and confirm the Credit Card Charge 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 recordscredit card charges

Brisk Credit Card Charges list screen displayed with fictional documentation-demo data.
The Credit Card Charges list screen in the Brisk documentation demo.

The evidence packet identifiesUse the viewCredit Card Charges list to find the correct record before opening or changing it. Compare Reference #, and sourceCharge locationDate. Records with similar names or numbers can still belong to different Vendor, and Card Account.

  • Keyword search checks Memo.

  • Narrow the list with Vendor filters.

Open the Credit Card Charge whose Reference #, and Charge Date match the task. If it is missing, clear the list filters and recheck Vendor, Transaction Type, Cleared, and Edit Locked rather than creating a replacement immediately.

Fields and business rules

Brisk stores 9 user-relevant fields for this action.Credit ConfirmCard user-facingCharge, stepsincluding before2 approvinglinked-record selections and 1 controlled-choice field. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

The

evidence stepsbeforeapproving record

stepsbeforeapproving
Field Required What packetit identifiescontrols
VendorYesPlease select the view and source locationvendor for this action.credit Confirmcard user-facingcharge.
Card AccountYesThe card account associated with this page.

credit

Deletecard acharge.

AmountYesThe evidenceamount packetvalue identifies the view and source locationrecorded for this action.credit Confirmcard user-facingcharge.
Reference #NoThe reference number for this page.transaction.
Charge DateNoDate that the card was charged.
Transaction TypeNoDetermines whether this credit card transaction is a charge or a credit. Available values: Charge, Credit.
ClearedNoRecords whether or not this transaction has cleared on a credit card statement.
MemoNoThe memo recorded for this credit card charge.
Edit LockedNoWhether the edit locked option applies to this credit card charge.

What happens next

Open Credit Card Reconciliation Information, Expense/Asset Categories, and Transactions and confirm the Credit Card Charge appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

Common mistakes and troubleshooting

  • The record will not save: Recheck Vendor, Card Account, and Amount 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 Transaction Type, Cleared, and Edit Locked, 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 Vendor, and Card Account from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.