Timastra Expenses
Separate project advances from expenses
Keep issued funds, supported spending and returned balances distinct so project reconciliation has a clear starting point.
Giving someone project funds does not tell you how those funds were spent. An advance, an expense and a returned balance represent different steps. Keeping them separate makes the later review easier to follow and avoids treating every fund release as completed spending.
Begin with a simple record of the advance: project reference, recipient, amount, release date, purpose and expected reconciliation date. Store the transfer or release evidence through your approved process. Limit access to people who need the financial information.
As expenses occur, record the date, supplier, purpose, amount and supporting receipt. Link the spending to the correct project and advance where appropriate. If evidence is missing, mark the issue clearly instead of filling the gap with a guessed description or an invented receipt.
In a fictional project, $500 is advanced, $320 has supported expense records and $180 remains to be reconciled. That remaining amount still needs an explanation: unspent funds, spending awaiting evidence, or a combination. It is not automatically available for another project.
At review time, compare the issued amount with accepted expenses, returned funds and unresolved items. Record the reviewer and the action needed for each exception. Keep corrections traceable rather than rewriting earlier history without an explanation.
Timastra Expenses supports project funds, receipts, approvals and reconciliation reports. Explore the workflow to assess its fit for your projects. Funds shown in the software are records; Timastra does not hold the money or provide a reimbursement service.