Mileage Records

Mileage Records

Purpose and when to use this record

BriskDocument storesbusiness vehicle mileage recordsfor asa partspecific ofdate so reimbursable or deductible travel can be supported.

At a glance

• Identify it by: Expense Date.

• Check its business context: Vehicle.

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

Create a recordMileage Record

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

1. Select the business context first: Vehicle.

2. Enter the required identifying and operational values: Beginning Miles, Ending Miles, Expense Date, and Vehicle.

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

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

After saving: Use Vehicle to interpret this Mileage 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 a Mileage Record

Delete this Mileage 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 Mileage Records list and make sure only the intended Mileage Record was removed.

ViewReview recordMileage Record details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Mileage Record currently means. Verify Expense Date before relying on it for a decision.

Follow Vehicle to determine whether the issue is on this Mileage Record or on one of those linked records.

Next check: Use Vehicle to interpret this Mileage Record. If it records a failure or exception, correct the source process and sourcecreate locationa fornew successful event rather than rewriting the audit trail.

Edit an existing Mileage Record

Edit this action.Mileage ConfirmRecord user-facingto stepscorrect beforeor approvingcomplete 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 Vehicle with the supporting document or approved request.

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

After the change: Use Vehicle to interpret this page.Mileage 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 mileage records

The evidence packet identifiesUse the viewMileage 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 Vehicle.

Open the Mileage 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.Mileage 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-facingstepsbeforethispage.

Delete a record

user-facingstepsbefore

Field	Required	What it controls
Beginning Miles	Yes	The evidencebeginning packetmiles identifiesvalue the view and source locationrecorded for this action.mileage Confirmrecord.
Ending approvingMiles	Yes	The evidenceending packetmiles identifiesvalue the view and source locationrecorded for this action.mileage Confirmrecord.
Expense approvingDate	Yes	Date recorded for expense date on this page.mileage record.
Vehicle	Yes	The vehicle associated with this mileage record.
Memo	No	Record notes about this mileage record.

What happens next

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

Common mistakes and troubleshooting

• The record will not save: Recheck Beginning Miles, Ending Miles, Expense Date, and Vehicle 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 Vehicle from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.