Many invoice delays begin before the invoice exists. A client may need a specific legal name, department, purchase order, portal upload, billing email, or approval contact. Collecting those details during onboarding or before work begins is easier than discovering them after delivery.
Use this checklist as a conversation guide. Only collect information you need, store it securely, and check jurisdiction-specific fields with official guidance or a professional adviser.
Identify who does what
The person who commissions the work may not be the person who approves or pays the invoice. Ask for the project contact, billing contact, approver, and a backup route for questions. Confirm whether the client prefers invoices to a shared mailbox, procurement team, accounting platform, or named individual.
Record the client’s preferred communication channel and any restrictions on file format or size. If invoices go through a portal, ask for the exact vendor registration steps and who can help if the submission is rejected. Verify the address from a reliable source when payment instructions or contact details change.
Confirm how the client must be named
Ask whether the invoice should show a legal entity, trading name, branch, or specific subsidiary. A group may use several entities, and sending the bill to the wrong one can interrupt approval even when the project contact recognizes the work. Keep the name and billing address supplied by the client with the engagement record.
If the client provides tax, company, or registration identifiers, confirm which ones they expect you to show and whether they apply to your transaction. Do not assume that an identifier from an old invoice is still current. Avoid requesting sensitive data that is not needed for the transaction.
Ask about purchase orders and required references
Some organizations require a purchase order, project code, cost center, contract number, or goods receipt reference before an invoice can be approved. Ask which references must appear on the document and where they should go. Confirm whether the PO covers the amount and scope being billed, and whether it must be renewed for a new period or milestone.
Clarify whether the customer needs separate invoices by location, entity, department, project, or service line. Splitting an invoice may help their process, but agree that structure in advance so your records and their approvals remain aligned.
- Billing entity and address
- Invoice delivery channel and accepted file type
- Purchase order and project references
- Required approval or receipt step
- Whether one invoice or separate invoices are expected
Agree the commercial details
Before work starts, make the price, currency, scope, billing trigger, and payment terms easy to find in the written agreement. Clarify whether the amount is fixed, hourly, recurring, milestone-based, or subject to approved expenses. Confirm how deposits, partial billing, changes, and cancellations will be handled.
If the client has standard terms, read them before accepting the engagement and identify conflicts with your proposal. A purchase order can contain terms that differ from a quote or contract. Resolve differences in writing instead of assuming that the document with the latest date automatically governs.
Handle tax and location questions deliberately
Where the parties are established, what is being supplied, and whether the transaction is domestic or cross-border can affect tax treatment and required information. Collect the location and business details your process needs, but do not guess at registration status, tax rates, exemptions, or reverse-charge treatment.
Use the applicable government or tax authority guidance and qualified advice for those decisions. Keep the client-provided details and your own conclusion distinct in the record. If a client requests a tax statement, verify that you are entitled to make it before placing it on the invoice.
Keep the setup useful and current
Store the billing profile with access limited to people who need it. Note when the details were confirmed and who provided them. A client can change entity, address, portal, or approver, so confirm key details again when an invoice is rejected, a new contract begins, or a long period has passed.
A compact client setup form can collect the basics once and let you reuse them. Keep client data separate from invoice-specific details such as period, purchase order, and amount. Make it easy to update a profile without silently changing already-issued documents.
Use a final client-specific check
Before sending, compare the draft with the client’s setup record: entity name, address, contact, portal, references, currency, and agreed terms. Confirm the work or period, amount, attachments, and any approval evidence. This quick check catches mismatches that a generic proofread will miss.
If a client’s process changed, record the new instruction and confirm it through a known contact. When the invoice is rejected, ask for the reason and update the setup record so the same issue does not recur.