Preparing an invoice becomes harder when the project record is scattered. The agreed work lives in a message, the delivered files are in a folder, and a receipt image has a name that means nothing. Before thinking about document layout, gather enough context to explain what the work record actually contains.
FreelanceFlow organizes clients, projects and receipts, with a Hebrew-focused workflow for freelancers on iPhone and iPad. This article describes a preparation routine you can use alongside it. It is about organizing records; it does not establish which charges, invoice format or tax treatment are appropriate for your business.
Give the project one clear identity
Choose a project name that distinguishes it from other work for the same client. “North Studio website, October content update” is more useful than “website.” Keep the agreed scope and the latest relevant approval easy to find.
Write a short summary in your working notes:
- Which client and project does this record cover?
- What was agreed for this phase?
- Which deliverables have been sent, and when?
- Which questions remain unresolved?
These are suggested record headings, not promises of particular app fields. Use the format that lets you follow the story later. If a file name differs from the project name, add a clear connection rather than relying on memory.
Separate delivery from assumptions about billing
List the completed work in language someone outside your daily workflow can understand. “Revised the homepage introduction and delivered three image captions” is clearer than “content fixes.” Link or identify the version that was actually delivered.
Keep a later request separate from the original scope until its status is clear. A request appearing in a chat does not, by itself, tell you whether it was approved as additional work or included in an existing agreement.
For a fictional content project, the record might show that the first draft was delivered on Monday, revisions were delivered on Wednesday, and a new landing page was requested afterward. Keep the landing-page question visible rather than quietly merging it into completed agreed work.
If you need clarification, prepare one precise question referencing the work and agreement. Resolve consequential billing decisions through your usual client process before relying on them in a final document.
Review work notes before adding totals
If your arrangement uses time records, check entries for date, project and a meaningful description. Look for duplicated sessions, missing end times or work accidentally assigned to another client.
Suppose your notes contain 2 hours of drafting, 1.5 hours of revision and 0.5 hours preparing the delivery. That is 4 hours recorded. Whether all four hours belong on an invoice depends on the actual agreement; the arithmetic alone does not answer that question.
Do not invent precision when reconstructing missing records. Mark an uncertainty in your working notes and check the available source, such as the relevant work log. Keep a remembered estimate distinct from a recorded duration. If the project uses a fixed price, retain useful work context without converting every note into an hourly charge.
Compare receipt details with the original
FreelanceFlow's product page describes receipt organization and reviewing extracted details. Extraction can save retyping, but review is still part of the process. Open the original image and compare the date, supplier, amount and currency with any extracted values.
- Is the receipt readable, including its edges?
- Has the same purchase been added twice?
- Does the date belong to the project period you are reviewing?
- Is the amount a total or a different figure printed on the receipt?
- Does this receipt belong to this project at all?
For example, a receipt dated 6 October and one dated 10 June can be confused when a numeric date is interpreted in the wrong order. Resolve the date from the original document and its context. Keep the original available after correcting your working record.
Attaching a receipt does not establish that it should be charged to a client or treated in a particular way for accounting purposes. Keep that decision separate and follow the appropriate professional process when needed.
Create a small readiness check
Before preparing the final invoice in your chosen system, review four things: correct client, agreed work, supporting records and unresolved questions. A working note saying “ready for document preparation” should mean that the inputs are checked, not that an invoice has been issued or payment received.
Keep “delivered,” “approved,” “invoiced” and “paid” distinct in your own records. They describe different events. Record each only when you have the corresponding information. Before sending supporting files to a client, remove unrelated client details and check the intended recipients.
Try the routine with a sample project
Start with a fictional project and a non-sensitive sample receipt. Compare any extracted details with the original, then see whether you can retrieve the project context without hunting through several places. The FreelanceFlow edition page describes the iPhone and iPad app and its Hebrew-oriented workflow.
For a broader selection guide, read the freelancer client and project tracker guide. Review the official App Store listing for current availability and purchases. Check the app’s supported interface languages before choosing it.
Common questions
Should every receipt be linked to a client invoice?
No. First establish which project it relates to and whether it is relevant under the agreement. Receipt organization and billing decisions are separate tasks.
What if an extracted amount looks plausible?
Compare it with the original anyway. A plausible figure can still be a subtotal or a misread value.
Do I need hourly records for a fixed-price project?
You may find work notes useful for context. They do not change the agreed billing model by themselves.
Does this checklist make an invoice legally compliant?
No. It organizes the inputs. Use an appropriate invoicing process and qualified guidance for requirements that apply to your business.