# What to Collect Before Sending an Invoice Before an invoice is prepared, collect the administrative details the billing owner needs and link them to the approved project or service record. Mark information as confirmed, missing, or awaiting clarification, and keep a source reference for each decision. This checklist does not define legal invoice requirements, tax treatment, or what a client owes. A fictional studio has completed a design milestone and the billing owner is preparing an invoice draft. The client record contains a billing contact, a project reference, and a note about a purchase order, but one item still needs confirmation. A short intake register lets the team resolve that gap before sending a draft to the client. All client names, billing contacts, references, purchase order values, and invoice states in the example are fictional. Canonical: https://areinum.com/guides/collect-invoice-details-before-sending/ Language: en Updated: 2026-10-31 ## Collect details from an approved project record Begin with the accepted proposal, project record, or other source your business already treats as authoritative for the agreed work. Record the project name or reference, the deliverable or milestone being billed, and the billing trigger described in that source. Copy the amount and currency only from the approved record; this guide does not calculate a price or decide when a charge is due. For the recipient, use the organization and contact details supplied or confirmed by the client. If the customer has provided a purchase order number or routing reference, record it alongside the source where it came from. If a field is not relevant to this transaction, mark it not supplied or not applicable according to your own process instead of inventing a value. ## Keep confirmed details separate from questions A missing field should have a named owner and a next action. If the project reference is unclear, the account owner can confirm which accepted proposal or milestone the billing draft should cite. If a PO reference was expected but has not been supplied, ask the client or the internal contact who requested it. Do not infer a reference from a previous invoice unless the current project record confirms it. The status of a detail is different from the status of the invoice. A recipient may be confirmed while the amount still awaits an internal check. A complete administrative handoff means the billing owner can prepare a draft from identified records; it does not mean the invoice has been reviewed, sent, paid, or legally sufficient. A fictional studio checks invoice inputs against the source for each detail. - Detail: Recipient; Example source: Client record updated by account owner; Administrative state: Confirmed for draft; Next action: Use the confirmed recipient in the draft - Detail: Project reference; Example source: Accepted proposal PROP-CL-08 v2; Administrative state: Confirmed; Next action: Carry the reference into the draft - Detail: Purchase order reference; Example source: Client note mentions a PO but gives no number; Administrative state: Needs clarification; Next action: Ask the client contact whether a reference was issued - Detail: Billing trigger; Example source: Approved milestone note; Administrative state: Internal confirmation pending; Next action: Billing owner to compare the draft with the approved record ## Check routing and billing context An invoice may be addressed to a named organization but routed through a particular contact or internal process. Record the contact or mailbox the client has supplied, the relevant project reference, and any agreed billing cadence or milestone that appears in the approved record. These are administrative prompts for the billing owner, not a universal list of mandatory invoice fields. Some invoice tools let you record a bill-to recipient, purchase order and project details. Choose the fields the billing owner needs for the transaction, and use the appropriate professional process for any applicable requirements. ## Resolve a mismatch before the draft leaves the office If the recipient differs between the client record and the approved proposal, preserve both source references and ask the responsible account owner which one should guide the draft. If a billing milestone is unclear, leave the trigger unresolved and route it to the person who approved the work. A clean note about the conflict is more useful than silently choosing the value that looks most recent. After the billing owner has prepared a draft, your own review process can compare it with the recorded inputs. Do not mark an invoice sent based on a draft status or mark it paid because a payment was expected. Keep those events distinct in whatever system your business already uses. ## Interpret the sample without treating it as a rulebook In the CSV, the fictional design milestone has a known project reference but an unresolved purchase order number. The row remains open because the source note only mentions that a PO may exist. The billing owner should ask for the number or record that no reference was supplied, then preserve that response with the project record. Use the template to reduce back-and-forth between the client-facing owner and billing. Adapt fields to your own approved process and the information your client actually provides. If you need a legal or tax determination, get it from the appropriately qualified person; this operational checklist cannot supply it. ## Keep the handoff narrow A useful billing handoff answers who should receive the draft, which approved work it relates to, what source supports its amount and trigger, and which questions remain. It does not decide legal requirements, taxes, payment entitlement, or the treatment of a transaction. Those decisions sit outside the purpose of this register. ## Using Areinum Ask Areinum Assistant to organise the administrative details you provide against the approved project record and prepare a list of gaps. The billing owner checks the sources and handles the invoice through the normal process. ## Questions you may have ### What if a purchase order is mentioned but no number is recorded? Leave the reference unresolved and ask the client contact whether one was issued. Record the reply or that no reference was supplied. ### Which amount should go into the draft? Use the amount and currency from the approved commercial record and ask the person responsible to resolve any mismatch. ### Does this checklist determine tax or legal invoice requirements? No. It helps organise administrative inputs; use the appropriate professional process for requirements and financial decisions. ### Will the assistant send the invoice? This guide organises the inputs. The billing owner checks the draft and decides how to handle and send it. ## Sources and further reading - [Add, customize, and share invoices in HoneyBook](https://help.honeybook.com/en/articles/5189729-add-customize-and-share-invoices-in-honeybook): The vendor help article describes configurable invoice fields including bill-to recipient, purchase order, and project details. Vendor product documentation, not an independent checklist of legal or tax requirements and not evidence of invoice rejection or payment outcomes. (2026-10-18) Download the original worksheet: https://areinum.com/guides/collect-invoice-details-before-sending/invoice-preparation-handoff.csv ## Invoice preparation handoff All client names, billing contacts, references, purchase order values, and invoice states in the example are fictional. | Client or project | Invoice item | Owner | Recipient as confirmed | PO or routing reference | Approved source | Amount and currency source reference | Billing trigger from source | Administrative state | Next action | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | Cedar Lane Studio | Two service page drafts | Avery, billing coordinator | Billing contact confirmed by account owner | Not supplied | Accepted proposal PROP-CL-08 v2 | PROP-CL-08 v2, billing line | Milestone listed in approved project record | PO reference needs clarification | Ask client contact whether a PO number was issued | | Juniper Bicycle Co | Approved product photography set | Riley, billing coordinator | Client billing desk | PO-JBC-204 per client note | Project record JOB-JBC-41 | JOB-JBC-41, billing terms section | Billing milestone recorded as complete by project owner | Ready for billing owner review | Compare draft details with project record | | Fern Market | Seasonal campaign design | Morgan, account owner | Recipient name differs between client record and proposal | Not supplied | Proposal PROP-FM-12 and client record REF-FM-7 | PROP-FM-12 and REF-FM-7, source conflict unresolved | Source does not clearly identify the billing trigger | Hold for clarification | Ask account owner to resolve the source mismatch | 1. The client names, project references, PO values, and billing states are fictional. Replace them with references from your approved records. 2. Copy each detail from its source and keep the source reference. Use not supplied or needs clarification when evidence is missing. Assign an owner to each open action. 3. Record the source reference for the approved amount and currency. Do not invent, calculate, or copy an amount or currency that is absent from the approved record. 4. Do not calculate amounts or infer a due date. The billing owner should use the approved commercial record and your established review process. 5. An administrative handoff is not proof that an invoice was reviewed, sent, paid, or legally sufficient. ### Keep confirmed details separate from questions A fictional studio checks invoice inputs against the source for each detail. | Detail | Example source | Administrative state | Next action | | --- | --- | --- | --- | | Recipient | Client record updated by account owner | Confirmed for draft | Use the confirmed recipient in the draft | | Project reference | Accepted proposal PROP-CL-08 v2 | Confirmed | Carry the reference into the draft | | Purchase order reference | Client note mentions a PO but gives no number | Needs clarification | Ask the client contact whether a reference was issued | | Billing trigger | Approved milestone note | Internal confirmation pending | Billing owner to compare the draft with the approved record | ### Limits of this method - The list is an administrative prompt for preparing an invoice draft. It does not identify legal invoice requirements or tax treatment. - Use the accepted commercial record and qualified advice for decisions about amounts, entitlement, tax, or required invoice content. ## Related reading - [What to Clarify in a Proposal Before the Client Agrees](https://areinum.com/guides/clarify-proposal-before-client-agrees/) - [Turn an accepted service package into separate scheduled jobs](https://areinum.com/guides/accepted-service-package-to-scheduled-jobs/) - [One conversation for the work behind your business](https://areinum.com/product/assistant/) Explore the demo: https://platform.areinum.com/ The demo uses sample company data. Access may need to be arranged.