What to Collect Before Sending an Invoice

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.

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

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.

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.

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.

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.

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.