How to run a gifting approval workflow finance can sign off on

The problem is not the gift, it is the trail

When gifting is spread across HR, marketing and five regional offices, nobody owns the total. Each order looks reasonable on its own, and the annual figure surprises everyone. Finance then asks for a reconciliation nobody can produce, because the spend sits in fourteen vendor invoices with different line-item conventions.

Corporate gifting runs like an operation. It needs roles, limits and a single record — the same things any other recurring spend gets.

Three roles are enough

• Requesters — HR business partners and managers who raise a gifting request against a program.
• Owners — the budget holder for that program. Owners approve the spend; requesters never approve their own.
• Finance — read access to every program, its caps and its consolidated invoice. No approval clicks, full visibility.

Set caps before the first request

Per employee and per team caps prevent overspending far more reliably than a policy document. A request above the cap does not fail silently — it routes to the owner with the overage shown, so the exception is a decision rather than a discovery.

• Per-employee cap by occasion: onboarding, festive, milestone, exit.
• Per-team annual cap, visible to the team as it depletes.
• An explicit exception path with a named approver and a reason field.

Close the loop with one invoice

One catalogue, one platform, one GST invoice per cycle, with line items that map to programs and cost centres. That is what makes gifting reviewable — and it is the difference between a spend finance tolerates and gifting that finance can sign off on.