In this article
For each expense, keep a short connection between the event, the supporting file and the request you actually submitted. The useful unit is one identifiable claim, not a camera roll full of receipts. A receipt-to-request crosswalk helps you answer “Which item does this belong to?” without reconstructing a shoot day from memory.
Start with the production’s requirements, then organize your own evidence around them. This article proposes a private working method for a production worker. It is not a reimbursement policy, and completing the method does not mean an expense has been accepted or will be paid.
Official context
Wrapbook’s expense-documentation guide tells workers to confirm the evidence required by their production administrators. It describes separate submissions, explanatory notes and digital supporting files. The personal crosswalk below is an independent organizational method; it does not establish eligibility, calculate an allowance or replace the production’s instructions.
Begin with the question the evidence must answer
Before choosing a filename, identify the uncertainty. A parking receipt may need to be connected to a particular workday. A purchase may contain both project and personal items. A journey may need an explanation of its purpose. Those situations call for different context, even when each produces a document that looks like a receipt.
Write a brief description in ordinary language: the event, the relevant date and why you believe it belongs to this production. Keep uncertain information visibly uncertain. If you cannot remember which project a purchase served, label the question and resolve it rather than assigning it to whichever project is easiest to open.
Use a crosswalk with six fields
A small table can connect records without copying every detail into a second database. Use a private location appropriate for your own records. The table is a navigation aid, so a reference to a file is often more useful than embedding a large image in every row.
- Personal reference: a simple label such as EXP-04 that you can recognize later.
- Project and event: enough context to distinguish this item from similar work.
- Evidence location: the filename or private folder containing the supporting material.
- Amount under discussion: the amount you intend to ask about, clearly separated from the entire receipt total when they differ.
- Submission connection: the reference, date or other detail that identifies your actual request.
- Open question: anything that still needs clarification and the person or channel you have asked.
Do not invent an official request number. A personal reference belongs to your notes; a reference issued by a production system belongs to that system. Label each so a reader can tell them apart. The project record index can point to this crosswalk without duplicating its contents.
Preserve the original; explain the difference separately
Keep the original evidence intact where appropriate. If only part of a purchase is relevant, write a separate explanation of the proposed portion. Changing a receipt image to make it resemble the requested amount can destroy the distinction between what happened and what you are asking the production to consider.
Review readability before relying on a file. Check that the relevant date, description and amount are legible, that the file opens, and that several pages have not been mistaken for separate transactions. If the original is incomplete, say so. An honest description of missing evidence is more useful than a confident filename attached to an unreadable image.
Fictional example: one purchase, two contexts
A crew member working on the fictional project Harbor buys several items during a day that also includes personal errands. The receipt total is $48, but the worker believes $19 relates to the project. Their crosswalk records the full receipt as evidence and lists $19 as the amount being discussed, with a note describing which items they mean.
The worker asks the production how to handle the mixed receipt before treating the request as complete. The example does not establish that the $19 qualifies for reimbursement. Its purpose is to preserve the relationship between the source document, the worker’s explanation and the eventual production decision.
Check for duplicates by event, not filename
A phone photo, a downloaded merchant receipt and a forwarded email can all describe the same purchase. Different filenames do not make them different expenses. Compare the event date, merchant description and amount before creating another crosswalk row. If two files support one item, connect both to the same personal reference.
Also distinguish a correction from a new request. When you supply a clearer image or answer a question, record that it supplements the earlier item. Avoid silently creating another claim simply because the first file was hard to read. If you do not know how to update the existing request, use a focused help question to ask for the appropriate route.
Close the evidence loop without guessing the outcome
Once an answer arrives, add the outcome to the relevant row and retain the source of that answer. “Clarification sent” and “request accepted” describe different events. A separate payment observation belongs in your payment records; do not replace the request history with a single optimistic “done.”
During your weekly project review, look for three practical gaps: evidence without a known request, a request without identifiable evidence, and a question without a recorded answer. Resolve those connections rather than rebuilding the entire table. The result should be a small, explainable trail that lets you identify one item accurately when someone asks about it later.
Source & scope
Official documentation checked October 25, 2026. The organizational methods and fictional examples are independent editorial analysis, not an official procedure or a private-account test. This article does not determine pay, benefits, tax treatment, contractual rights or record-retention obligations.