Expense Records

Expense Records

Purpose and when to use this record

BriskRecord storesa dated business expense recordswith asits partamount, ofretailer, category, and supporting memo.

At a glance

• Identify it by: Expense Date.

• Check its business context: Category.

• 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 expense records. 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 Category records ready first. Those selections determine where this Expense Record belongs and which later screens can find it.

Create aan recordExpense Record

TheCreate evidencean packetExpense identifiesRecord only after confirming that the viewsource document or operational event has not already been entered.

1. Select the business context first: Category.

2. Enter the required identifying and operational values: Amount, Expense Date, and Category.

3. Review Retailer, and Memo against the source locationdocument or approved setup decision.

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

After saving: Use Category to interpret this Expense Record. If it records a failure or exception, correct the source process and create a new successful event rather than rewriting the audit trail.

Delete an Expense Record

Delete this Expense Record 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 thisa action.real Confirmevent user-facingthat stepslater beforechanged.

approving

On thisthe page.confirmation page, verify Expense Date. After confirmation, return to the Expense Records list and make sure only the intended Expense Record was removed.

ViewReview recordExpense Record details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Expense Record currently means. Verify Amount, and sourceExpense locationDate before relying on it for thisa action.decision.

Confirm

Follow user-facingCategory stepsto beforedetermine approvingwhether the issue is on this Expense Record or on one of those linked records.

Next check: Use Category to interpret this Expense Record. If it records a failure or exception, correct the source process and create a new successful event rather than rewriting the audit trail.

Edit an existing Expense Record

Edit this Expense Record 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 Category with the supporting document or approved request.

2. Recheck Amount, and Expense Date. 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 Expense Record now appears under the expected Expense Date.

After the change: Use Category to interpret this Expense Record. If it records a failure or exception, correct the source process and create a new successful event rather than rewriting the audit trail.

Find and review expense records

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

Open the Expense Record whose Expense Date match the task. If it is missing, clear the list filters and sourcerecheck locationthe identifying information shown on the screen rather than creating a replacement immediately.

Fields and business rules

Brisk stores 5 user-relevant fields for this action.Expense ConfirmRecord, 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

user-facingstepsbefore

Field	Required	What it controls
Amount	Yes	The evidenceamount packetvalue identifies the view and source locationrecorded for this action.expense Confirmrecord.
Expense approvingDate	Yes	Date recorded for expense date on this page.expense record.
Category	Yes	The category associated with this expense record.
Retailer	No	Record the business where this purchase was made.
Memo	No	Record notes about this expense record.

What happens next

Use Category to interpret this Expense Record. If it records a failure or exception, correct the source process and create a new successful event rather than rewriting the audit trail.

DeleteCommon mistakes and troubleshooting

• The record will not save: Recheck Amount, Expense Date, and Category 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 Category 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.