The end of the receipt-chasing email
The single most repetitive email a tax advisor writes is "please send me the receipt for this payment." In TaxItEasy that email is one click. You stay in the work queue, the client gets a precise, actionable notification on their phone, and the paper trail writes itself.
You'll find the button in two places: as the primary action on any transaction in the Needs receipt bucket, and behind the R shortcut in the invoice workbench when an invoice is missing its document (that's also the one-click path the UI offers when the receipt gate blocks an approval).
What one click actually does
The request is a single atomic operation — all four parts happen together or not at all:
- The transaction is set to a waiting/query status — it moves out of your open work and into the Waiting bucket.
- An append-only comment is posted on the transaction. The default text is "Please upload the invoice or receipt for this bank transaction." — you can edit it before sending. Like all comments, it can never be edited or deleted afterwards, so the request is part of the permanent record.
- Every owner and admin of the client company is notified — an in-app notification plus email and push, each according to that person's own notification preferences. The title reads "Receipt requested by your tax advisor".
- An audit entry is written.
Privacy detail worth knowing: the notification body deliberately contains no counterparty and no amount. A push notification on a lock screen never leaks who your client paid or how much — the details are only visible after signing in.
Built-in safeguards
- Idempotent for 10 minutes — the identical request (same advisor, same text) within 10 minutes is recognized as a duplicate and creates nothing twice. A double-click, an impatient retry, or a flaky connection can never spam your client with repeat notifications.
- Honest delivery status — the response tells the UI whether anyone was actually notified. If every recipient has notifications switched off, you'll know to contact the client directly instead of assuming the request landed.
The loop closes itself
When the client attaches the document, the open query resolves automatically — the document is the answer, so nobody has to click "resolved". The transaction flips from Waiting back to your open queue for a quick re-confirm.
And it often goes further: once the linked invoice is approved with a usable document, the auto-clear loop books the transaction for you — approved invoice, matched payment, receipt on file, cleared. On a good day, "request receipt" is the last manual touch a transaction ever needs.
Where this fits in period close
Open queries are checklist item number 8 on the period checklist — a period isn't ready to attest while queries are outstanding. The Waiting bucket gives you a live view of everything you're blocked on, which turns the classic month-end receipt scramble into a list you can check twice a week.
Related
- Why VAT bookings need a receipt — the rule that makes the request necessary
- The transaction work queue, explained — Needs receipt and Waiting in context
- The VAT workbench: reviewing client invoices — the R shortcut on the invoice side
- Period checklist and VAT return prep — open queries as a close blocker