Attach a receipt to an expense
Upload supporting evidence and keep the file linked to the expense record. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goExpense → Attachment
Before you startThe screen or action may be hidden when your role lacks permission, the related module is inactive, or a required setting has not been configured. Ask an administrator to review access rather than using another person’s account.
What you’ll accomplish
Upload supporting evidence and keep the file linked to the expense record. Britixo CRM keeps the result connected to the relevant customer, staff member and operational history where the feature supports those relationships. That connection is important for search, reporting, client portal visibility and future automation.
Follow these steps
- Go to Expense → Attachment and select the relevant record or setup list.
- Use search, filters or status tabs to confirm you are working on the intended item.
- Check linked records, activity and permissions before changing status, ownership or visibility.
- Use the available edit, status, reorder, attach, copy or delete action as required.
- Complete any confirmation dialog carefully; destructive actions may be restricted when linked data exists.
- Check the updated state in the list and record view.
- Check downstream client portal, reporting or automation effects where applicable.
Fields and decisions to review
CategoryCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Date and amountCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
TaxCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Payment modeCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Customer or projectCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Billable and receipt settingsCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Checks before you finish
- Attach evidence where required.
- Mark billable only when the customer should be charged.
- Check currency and tax before saving.
- Check whether the result should be visible to a customer contact or only to staff.
- Confirm the final status, activity entry, generated document or notification before leaving the record.
Permission and data safetyDeletion, refunds, signature clearing, module changes, payment configuration and privacy actions can affect linked records or legal history. Use the least destructive action available and follow your organisation’s approval process.
Browse connected topics:invoicepaymentexpensechecktaxcurrencyapprovalserviceclient portalnotificationscustomers
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.