Every reimbursement moves through a set of statuses, and once transactions are linked to a reimbursement, Inn-Flow limits what you can change. This article explains the lifecycle and the difference between voiding and deleting.
Reimbursement Status
A reimbursement moves through the following statuses:
Draft – while you are creating it
Unpaid – created and posted, but not yet paid
Paid – payment recorded
Void – reversed while unpaid (voiding backs out the posting so it no longer affects the books)
Editing Transactions Linked to a Reimbursement
Reimbursements enforce transaction integrity – once a transaction is part of a reimbursement, you cannot quietly change it:
Situation | What's allowed |
Transaction linked to a paid reimbursement | Cannot be edited. Void the reimbursement first. |
Transaction linked to an unpaid reimbursement | Cannot be edited. Delete the reimbursement first. |
Transaction split that has not yet been reimbursed | Can be edited normally. |
This prevents the classic audit problem where the underlying transactions of a posted reimbursement could be silently modified after the fact.
Voiding vs. Deleting
Void reverses a paid reimbursement and unmaps the included transactions so they can be reimbursed again later.
Delete removes a reimbursement that has not yet been paid and returns the transactions to unmapped status.