In this article
Explain the work connection in a short, specific note while keeping categories, attendees and allocation details consistent.
“Business expense” tells a reviewer what you hope the purchase will be treated as. It does not explain the work it supported. A useful purpose note gives enough context for someone who was not there to understand the connection and apply the employer’s policy. It should be specific, factual and proportionate to the purchase.
Build the note from three parts
Start with the activity, add the work objective, and identify the relevant project, meeting or destination using approved internal terms. A practical formula is: “Purchase or activity for work objective, connected to project or event.” Add dates, participants or an exception explanation only where needed for clarity or policy.
This formula is our editorial writing aid, not an Emburse-required sentence structure. Professional’s non-receipt mobile expense guide identifies its Reason field as a place for business purpose. Other products or employer configurations may use different field labels and requirements.
Three fictional improvements
- Vague: “Lunch.” More useful: “Lunch during the on-site Atlas implementation workshop; project team attendees recorded in the attendee fields.”
- Vague: “Taxi for work.” More useful: “Transfer from the rail station to the customer training venue for the scheduled afternoon session.”
- Vague: “Office stuff.” More useful: “Replacement presentation adapters for the branch training room after the existing set failed.”
These examples illustrate structure only. They do not establish that the purchases are eligible or that a particular meal, transport mode or replacement was authorized. Use the facts of your own expense. Do not copy a convincing example if it describes a purpose that did not occur.
Use the other fields for their own jobs
The note should complement structured information rather than conceal missing data. Professional’s expense-type guide describes different fields for different categories, including meal attendees, lodging dates and travel locations. Check the fields shown for the selected category and any employer-required custom fields.
If attendees belong in an attendee field, enter them there. If a project or department must be selected, a project name buried in the narrative may not allocate the expense correctly. If the category seems unsuitable, resolve that choice instead of trying to explain around it. For Enterprise, the product description specifically notes configurable fields and routing; a coworker’s screen may differ because their work has different requirements.
Separate purpose from payment and approval
“Paid personally” describes who funded the purchase. “Approved by Sam” describes an earlier decision. Neither independently explains why the purchase served work. Keep the business purpose, payment classification and any pre-approval reference distinct, even if your interface displays them together.
Similarly, charging a client is a different question from reimbursing the employee. A detailed purpose can support review without determining either classification. Our card and reimbursement guide explains how to avoid conflating these dimensions.
Explain exceptions with facts
When the expense appears unusual, state the relevant circumstance and point to the approved exception process. For example, a fictional note might say that the planned train was cancelled and the traveler used the transport option authorized by the duty manager. That is useful only if those events and authorization actually occurred.
Avoid defensive essays, guesses about policy, or claims that “everyone does this.” State what happened, identify the supporting record and ask for the specific decision if eligibility is unresolved. A truthful short explanation is easier to review than a long argument with unclear evidence.
Protect sensitive context
Do not include health details, confidential deal terms or personal information unrelated to the review. If a purchase involves a sensitive matter, ask the policy owner which approved project identifier or restricted channel to use. Privacy should be handled through the appropriate process, not by substituting a false purpose.
Before submitting, ask a colleague-free test: could an authorized reviewer who did not attend the event understand what happened and why it relates to work? Then check that the note agrees with the receipt using the evidence checklist. If a reviewer still needs clarification, respond to that specific question and preserve the history through the approval handoff process.