Product guides

Flagging reimbursable spending with a rule

Work costs paid from your own pocket can be flagged as reimbursable automatically. Build a rule that marks them so claims are not forgotten.

Editorial illustration for Flagging reimbursable spending with a rule

People who occasionally pay for work from their own account share a common headache: remembering which payments are owed back. Waiting for memory to supply the list at month end usually means missing a few. The rule editor includes an action to mark transactions as reimbursable, which turns that memory task into a standing instruction.

What the flag means

The reimbursable flag marks a transaction as money you expect to recover from someone else, such as an employer or a client. The rule editor offers both reimbursable and not reimbursable choices, plus leaving the setting as it is. Marking something reimbursable does not itself request payment; it makes it visible and countable so that a claim can be put together.

Because it is an attribute of the transaction, you can later filter or report on everything flagged, giving you a ready list for a claim.

Which payments qualify

Only you know your arrangement. The flag should reflect what you have agreed with whoever repays you, and what the relevant policy allows. Where the rules are unclear, ask the person who approves claims rather than guessing. For tax questions that touch reimbursements, check an official source or a qualified professional.

Typical candidates are travel for work, client meals, software bought for a project, and courier costs. The common thread is that someone else owes you the money.

Designing the rule

The cleanest triggers are those that identify work spending without ambiguity.

  • A dedicated account or card used only for work expenses.
  • A category such as work travel that you already use consistently.
  • A merchant you only use for work.
  • A tag you add when paying.

If you use a dedicated account, one condition on the account catches everything, which is the simplest design. If you use categories, a rule that flags anything in the work travel category is just as easy.

Timing matters

The editor notes that the reimbursable flag is applied as new transactions arrive. It is not retroactive in the way category changes can be, so a new rule will protect future payments rather than rescuing past ones. For the existing backlog, flag the entries by hand or with a bulk selection, then let the rule handle the rest.

Linking to receipts

Claims nearly always need proof. Combining the reimbursable flag with the receipt condition is powerful: you can see which reimbursable payments still lack a receipt and chase them before the claim date. Sorting by reimbursable and no receipt gives a short list of exactly what to find.

Closing the loop

A flag is only useful if you act on it. Set a monthly moment to review flagged transactions, gather their receipts, and submit the claim. When repayment arrives, record it so that the books show the money back, and so the next review begins with a clean list.

StageWhat to do
Payment madeRule flags it reimbursable
Receipt scannedAttach to the transaction
Month endReview flagged items, assemble claim
Repayment receivedRecord it and clear the cycle

Reimbursable income side

When repayment arrives, it appears as money in. Treat it as a repayment rather than ordinary income, so earnings reports are not inflated. Matching the repayment to the claim, even by a note, shows that the cycle is complete and prevents the same payments from being claimed twice in a later round.

One thing to avoid

Do not flag personal purchases by mistake. A rule with a loose condition might sweep ordinary spending into the claim list. Preview carefully, and keep the condition tied to something that really does identify work spending.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports