Browse articles
- Getting started
- Project finances
- Billing by the hour
- Practice finances
- Grouping fees
- Budgeting project costs
- Claim an expense
- Recording revenue entries
- Recording project expenses
- Purchase orders
- Approving expenses
- Going further
- Construction cost fees
- Recurring fees
- Billing expenses
- Contingencies and discounts
- Billing progress claims
- Project templates
- Overheads
- Getting started
- Billing milestones
- Sending an invoice
- Billing logged time
- Month-end invoicing
- Fee proposal templates
- Writing a fee proposal
- Getting a proposal signed
- Link invoices that are already in Xero
- Going further
- Payments and overdue invoices
- Connect your accounting system
- Fee groups on invoices
- Tax codes and accounts
Expense claims access
Separate no access to claims, supplier invoices and direct costs from access that lets a person add and change them.
What you'll achieve
Set and verify Hidden or Edit access to expenses and claims.
You'll end up with: Marcus Webb has Team member access and can submit and change claims.
Before you start
The claims ledger is an account capability
The Expenses group of the Account level has three switches:
- Expense claims covers staff claims, supplier invoices and direct costs, including rows with no project. Hidden removes the area. View allows inspection. Edit adds submitting and changing.
- Approve expense claims approves or rejects claims when the practice requires approval. A person with it can approve their own claims.
- Mark claims paid marks claims as paid.
Approve expense claims and Mark claims paid need Expense claims Edit. With Expense claims at View or Hidden, the two rows stay on the screen, greyed out, with the reason under their names.
This differs from project Expenses. A project access level controls project cost visibility. The account capability controls the expense ledger itself. Linked expense rows may require both.
Build a clear Hidden case
None of the other built-in levels combines all the exact restrictions needed for this contrast, so the tutorial creates Claims Hidden. A new custom account level begins with every switch Hidden, apart from Projects View.
- 1
Go to Team › Access levels. Click New access level, then Access level. Type the name Claims Hidden and click Create access level.
- 2
Go to Team › Team members and open Marcus Webb's page. Click Profile, then the Access section. Choose Claims Hidden and click Save.
- 3
Click Preview and confirm Expenses is absent from the navigation.
- 4
Click Exit on the Preview banner. Choose Team member, click Save, then click Preview again.
- 5
Open Expenses and confirm the claims list shows New expense.

The final check is the claims list with New expense, which proves Team member has Expense claims Edit. A person with Expense claims View sees the list without New expense.
Redacted expense values must be absent or shown as an em dash. Monument must not replace a protected amount with zero because that would invent a financial fact.
Troubleshooting
- Expenses appears because Operational is allowed. Practice finances separately controls operational expenses. Check the specific Claims surface and switch.
- New expense is missing. The person has Expense claims View, not Edit. Team member has Edit.
- Approve is missing for a person with Approve expense claims. Check that their Expense claims is Edit, and that the practice requires approval.
- A linked project expense is missing. The person also needs project Expenses access on the admitted project branch.
Where this fits next
Continue with Reports, where base-entity access still controls what a visible report can disclose.
Related articles
Search Monument help
Search help articles and open a result.