Eden field notes / Expense reports

Expense report automation
with room for a human decision.

Collect each claim once, flag missing facts, and send the right report to the right reviewer.

Start with the claim.

Record the employee, date, merchant, amount, currency, purpose, project, and receipt. Keep the original file with the claim. Ask which fields your accounting team actually needs before building a form.

Let exceptions interrupt the route.

Imagine a team that receives expense sheets and receipt photos by email. A workflow could group each submission, then flag a missing receipt, a repeated merchant and amount, or a claim outside the team's stated policy.

This is an illustrative design, not a delivered client result. A flag asks for review; it does not prove that a claim is wrong. Keep a person responsible for resolving unclear items.

Keep approval and payment separate.

Send the checked report to its named approver. Record the decision, the reason for a rejection, and any corrected version. Only approved items should move to accounting. A payment or reimbursement still follows the organization's own controls.

Test the awkward cases.

Try a duplicate submission, a missing receipt, two currencies, and an absent approver. Agree who fixes each case and how the claimant hears back. If your existing expense tool already covers these steps, use it. Eden can scope custom connections when several systems leave gaps.