In short: Collect one claim, check the fields your policy requires and route it to a manager who is not the claimant. A clearer photo must not create a second reimbursement. Paying the claim is a later, separate handoff.
An expense claim workflow can collect receipts, check required fields and route a claim to the right manager. It should not decide that every receipt is reimbursable, and it should not decide tax treatment. Those decisions sit with the company’s policy and with whoever is responsible for the accounts.
This is staff claims, not supplier bills. Supplier invoices belong in invoice approval. The records question, once a receipt contains personal data, belongs in retention.
One claim, one identity
Create a claim id that does not change when the employee uploads a better photo. Store employee, employing entity, expense date, category, merchant if known, original currency, amount, the policy version and a link to the receipt file. Keep the file in a library finance can open. Do not paste the image into a chat that the whole company can see.
Reimbursement policy is not GST treatment and it is not income-tax deductibility. If a GST-registered business is keeping the receipt because it supports a GST entry, IRAS’s record-keeping guidance requires GST records to be kept for at least five years from the end of the accounting period. That citation is about those source records. It is not a rule to keep every rejected draft, and it is not a retention period for unrelated HR data. Agree the schedule with finance and, where personal data is involved, with the person who advises on the PDPA.
Flags are review tasks
Rules that are worth automating are the ones you can explain:
- no receipt, or a file that will not open;
- the same employee, amount and date already on another claim;
- a claim older than the policy’s window;
- an amount above the category limit;
- a category the employee’s role does not use.
A flag opens a review. It is not a finding of fraud. Wording in the task should say “outside the written rule”, not “suspicious employee”.
Routing, and the manager who is also the claimant
Route to the manager, then to finance if your policy says so. Delegation is explicit. Self-approval is forbidden or limited in writing. The acceptance test is a manager submitting their own claim: the flow must choose the next role, not the claimant.
Record the policy version, the approved amount (which may be less than the claimed amount) and the person who decided. A later policy edit does not rewrite that row.
Versions, splits and currency
Handle these as data, not as a second claim:
| Situation | What the record should do |
|---|---|
| A clearer photo of the same receipt | Replace the draft file on the same claim id. Do not create a second payable claim |
| A personal portion | Split the line. Only the approved business amount is payable |
| Foreign currency | Store the original currency and the rate basis finance accepts. A corrected rate updates the version and needs the same approval level as the amount change |
| A rejected line | Stays rejected. A resubmission is a new version or a new line, not a silent copy of the old approval |
| Two versions open | Only one version is payable. The other is superseded |
Microsoft’s error-handling guidance is relevant when the payment handoff times out. Retrying a post without a claim id and a payment reference is how a reimbursement runs twice.
Reimbursement is not the approval
Approval means “this version may be reimbursed”. The payment itself is a later step in payroll or accounts, with its own control. Write the payment reference back to the claim. If the accounting system accepts the posting and the workflow does not hear about it, the operator looks up the claim id before trying again. A blind replay is a duplicate payment.
Receipts often show a person’s name, a card number fragment or a home address. The PDPC’s Key Concepts guidelines expect reasonable security arrangements for personal data the organisation holds. Limit who can open the file. Do not copy the whole receipt into an alert.
Tests and procurement questions
Witness a duplicate receipt, a claimant who is also the manager, and a foreign-currency line whose rate is corrected after submission. Ask whether finance can approve line by line, how the policy version is stamped, and what prevents two reimbursements of one claim.
Illustrative scenario, not a client engagement: an employee submits a meal receipt and later uploads a clearer photo. The new file replaces the evidence on the same claim. Finance checks the policy version and the amount before anything is handed to reimbursement. The workflow never marks the meal as tax deductible.
This is an operational design guide, not tax advice, and FYAdvisers is not a law firm or a tax agent. To separate the claim record from the payment, use the contact form or WhatsApp +65 9071 3976 (chat).
Frequently asked questions
Can finance approve some lines and reject others?
The design should allow it. A claim with a meal and a personal item is two decisions. Approving the header must not force every line to the same result, and the rejected line must not be payable on a resubmission of the whole claim unless it is a new line with its own decision.
How should policy changes be versioned?
Stamp the policy version on the claim when it is submitted. A later change to the limit applies to later claims. It should not rewrite a decision already recorded, unless finance explicitly reopens that claim.
What stops the same receipt being paid twice?
A claim id that survives resubmission, plus a duplicate check on employee, date, amount and a hash or supplier reference from the receipt. Reimbursement reads the approved amount on the current version only, and the payment reference is written back once.
Does an approved claim mean the expense is tax deductible?
No. Company policy and tax treatment are different questions. The workflow can collect the fields finance asked for. It should not label a receipt as deductible.
