Agency finance operations workshop / 5 MIN READ
Connect the expense to its purpose and approval before claiming it
Prepare project-expense records that distinguish spending evidence, employee reimbursement and client recharge approval.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
A receipt shows a transaction, but it does not by itself settle who should pay for it. A reliable expense record links the business purpose, relevant approval and correct accounting route while keeping personal information and duplicate claims under control.
What you will leave with: A reconciled project-expense packet ready for authorized review.
Use this when
- Staff incur approved costs during client work.
- Project expenses may be reimbursed internally and separately recharged to a client.
This is not tax advice, authority to spend or reimburse money, or a guarantee that an expense is contractually recoverable from a client.
Identify the expense and its business purpose
Harvest’s expense documentation distinguishes receipt records from a billable setting. Start with the actual transaction and why it was needed for the project, rather than assuming every project-related purchase is automatically chargeable.
Record the date, merchant, amount, currency and relevant project using the approved system. Link the applicable prior authorization where required. Explain the purpose briefly enough for a reviewer to understand it without including unrelated attendee or personal details. Separate several different purchases when they have different purposes or approval treatment, instead of hiding them inside a vague combined description.
Check the evidence and payment route
Attach the required readable evidence through the approved process and confirm that it corresponds to the claimed item. Distinguish a receipt, booking confirmation, unpaid invoice and card statement; they may establish different facts. Ask finance what is acceptable when normal evidence is missing.
Record whether the cost was paid personally, by a company card, directly by the client or through another approved route. Check for duplicate entry or a cost already settled elsewhere. Do not submit a personal reimbursement claim for a company-paid item. Protect unnecessary card or account details and do not alter original evidence to make it appear that a different purchase occurred.
Separate reimbursement from client recharge
Have the authorized internal reviewer determine whether the expense meets the organization’s policy and approval conditions. Separately check whether the client agreement permits recharge and whether additional client approval is required. These are related but distinct decisions.
A legitimate employee reimbursement may still be an agency cost that cannot be passed to the client. Equally, a tool’s default billable flag should not decide the matter. Route uncertain taxes, currency conversion, allowances or markup treatment to finance and the commercial owner. Do not invent a conversion rate or round a cost to match a remembered budget when the approved method requires something else.
Resolve exceptions and keep the final status clear
Submit the packet for the appropriate review and answer factual questions with supporting evidence. If an item is declined or needs correction, preserve the reason and use the approved adjustment process. Avoid submitting a slightly renamed duplicate to get around the decision.
Track reimbursement and client billing status separately so neither is mistaken for the other. If a booking is refunded or an expense changes, alert finance and the project owner so the related records can be reconciled. Retain documentation under the applicable policy. The completed packet should make the actual cost and its approved treatment understandable without requiring a reviewer to reconstruct the trip or event from scattered messages.
Make the reasoning concrete.
A fictional account manager buys event supplies on a company card and later includes the receipt in a personal expense claim. The project system also marks the item billable to the client by default.
Approve from the receipt alone
Opening: Treat proof of purchase as enough for both reimbursement and recharge.
Hypothesis: The packet moves through quickly.
Risk: The employee could be paid for an item already paid by the company, and client billing may be unauthorized.
Reconcile payment and approval routes
Opening: Confirm the company-card payment and check the separate client recharge terms.
Hypothesis: Each financial action can use the correct evidence.
Risk: The record needs correction before approval.
Finance removes the duplicate personal claim through the approved process and reviews the client-billing status separately. The original transaction remains accurately recorded against the event.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Purpose
Why was this cost necessary for the project?
Evidence
What proves the transaction and relevant details?
Payment route
Who actually paid, and has it already been claimed?
Approvals
What governs internal reimbursement and client recharge separately?
Changes
What refund or correction must update the final record?
Watch for the wrong conclusion.
- Treating a receipt as proof of every approval.
- Claiming a company-paid expense as a personal reimbursement.
- Letting a default billable flag decide the client’s obligation.
Your next action
Reconcile one project expense from purchase through payment route and separate approval states before it reaches reimbursement or invoicing.
Sources & scope
The workflow, worksheets and hypothetical examples are original editorial analysis. Sources support only the identified principles. No measured business results or named human reviewer are claimed.
- Harvest Help Center: Tracking expenses →Primary product documentation · Supports: Expense records can include receipts and a separate billable setting; the reconciliation and approval exercise is original editorial analysis.