A clear document request names the item, the reporting period, the format, the deadline and where to send it. If you are following up, list the items still missing. Making someone reread the original request usually adds work for both sides.
These six templates cover a reporting cycle from the first request to handover. Replace every bracketed field before sending. They work for internal finance teams and advisers collecting client records. The download is a plain-text file you can edit in any text editor.
In this guide
1. The first request
Subject: [Entity] records needed for [reporting period] by [date]
Hi [name],
We are preparing [report or review]. Could you upload the following records for [entity/site] and [period] by [date, time and timezone]?
| Request ID | Record | Period or scope | Format |
|---|---|---|---|
| [REQ-01] | [Electricity invoices] | [All accounts at Site A, September] | [Original PDFs] |
| [REQ-02] | [Meter/account list] | [Active and closed accounts during September] | [Spreadsheet] |
| [REQ-03] | [Allocation working] | [Shared meter E-01, September] | [Workbook with formulas] |
Please use [approved upload location]. If an item is unavailable, reply with its request ID, the reason and the date you expect it. Please also tell us who should handle any item that belongs to another team.
Thanks, [Name]
Why this works: the request IDs keep a reply attached to a specific item. A precise boundary makes “all records” less ambiguous. Choose a format that preserves the evidence you need, rather than asking for PDF by default.
2. A reminder for missing items
Subject: Two records still needed for [entity/period]
Hi [name],
Thanks for sending [items received]. We still need [REQ-02: item] and [REQ-03: item] to finish [specific review step].
Could you upload them to [approved location] by [date/time]? If that date will not work, please let me know the expected delivery date and any issue we can help resolve.
Thanks, [Name]
Use the actual count in the subject. Keep the received-item acknowledgement short, and remove anything already resolved. Avoid a threatening final notice when you only need a revised delivery date.
3. The file covers the wrong period
Subject: [REQ-01] replacement needed for [correct period]
Hi [name],
The file [filename] covers [received period]. Our request is for [required period] at [entity/site/account]. Could you send the matching record to [approved location] by [date]?
If the supplier has not issued it yet, please tell us. We will keep that gap open rather than treating the earlier file as the requested record.
Thanks, [Name]
State what you received before stating what you need. That makes the problem easier to fix and avoids implying the colleague did not respond.
4. The number arrived without supporting records
Subject: Supporting records for [figure or request ID]
Hi [name],
Thank you for the [figure] for [period]. To complete our review, could you send [source record], [calculation working] and [method or allocation explanation]?
We need to understand how the reported value follows from those records. If an estimate was used, please identify the estimate and explain its basis.
Upload the files to [approved location] by [date], or let us know what is unavailable.
Thanks, [Name]
5. A revised file has been received
Subject: Confirming the replacement for [request ID]
Hi [name],
We received [new filename/version] on [date]. Please confirm that it replaces [earlier filename/version] for [period and purpose], and briefly describe what changed.
We will retain the earlier copy with its superseded status and send the replacement for review. This message confirms receipt only. Approval will be recorded separately.
Thanks, [Name]
6. Final handover with open items
Subject: [Entity/period] handover and remaining questions
Hi [name],
The handover files are in [approved location]. The index identifies the version and review status of each item.
The following questions remain open: [request ID, issue, owner and expected date]. Please confirm who will decide how these affect [reporting or review milestone].
If a file changes after this handover, please provide the replacement version and a short explanation. We will update the index and route the change for review.
Thanks, [Name]
Keep the request list and the conversation connected
| Event | Update the tracker |
|---|---|
| Request sent | Owner, request date and due date |
| File received | File reference, received date and version |
| Problem found | Specific question and person resolving it |
| Replacement received | New version and relationship to the old one |
| Review completed | Decision, reviewer and supporting record |
The free PBC tracker gives those fields a home. For suppliers, attach a short ESG data questionnaire only where its questions fit the request.
Choose the delivery method before sending
Use your organisation's approved document-sharing method and check recipient access. Avoid asking someone to put credentials, full personal identifiers or sensitive records in an ordinary reply when a restricted upload location is available. US tax practices should consult the IRS's Publication 4557 for their specific safeguarding responsibilities. Other teams should follow the rules that apply to their own records and jurisdiction.
Prepared with AI assistance using the linked sources and original worked examples. Illustrative records are fictional. No customer results, independent specialist review or hands-on software testing are claimed.