IT Consulting Invoice Submission Checklist: Six Details to Verify

An IT consulting invoice can describe the right work and still be incomplete for the customer’s accounts payable process. Before submitting, compare the invoice with the current purchase order, statement of work, milestone approval, and billing instructions that apply to the engagement.

Treat this as a document review, not a universal rulebook. Customer requirements vary. If a document is missing, silent, or inconsistent, record that uncertainty and ask the relevant contact rather than assuming a requirement or an exception.

Six checks before submission

1. Customer’s legal entity

Read the contracting or ordering document for the precise entity that engaged your firm. Compare it with the bill-to name and address on the invoice. A familiar group brand or project team name may not be the legal entity named in the order.

If the source documents use different entity names, pause and confirm which entity should be billed. Do not select an entity based only on an email signature or a previous invoice for another engagement.

2. PO and project reference

Check whether a PO is required by the applicable customer instructions or engagement documents. If there is an issued PO, compare its reference with the invoice and verify that it relates to the billed project and scope.

Also include any separate project, cost-centre, or engagement reference the customer explicitly requests. Do not substitute one identifier for another. If no PO can be found, distinguish “not present in our records” from “not issued” and ask for confirmation.

3. Billing period

State the period the services cover using clear start and end dates. Compare that period with the contract, PO, approved time record, or other source that governs the work. Check that the invoice does not describe a period outside the engagement or duplicate a period already billed.

If the source uses a milestone rather than dates, do not manufacture a service period. Use the format required by the customer or confirm the right description.

4. Agreed milestone or fee basis

Check the amount and description against the agreed basis: for example, a named delivery milestone, a fixed-fee stage, or approved time and materials. Confirm that any milestone billed is the one authorized for invoicing, not simply one that appears complete to the delivery team.

Where a milestone approval or timesheet is part of the customer’s documented requirements, verify it is available and covers the claim. If the documents do not say whether approval is needed, ask rather than presenting an assumption as a rule.

5. Supporting documents

Review the stated list of required attachments. Depending on the engagement, it may name a signed milestone approval, timesheet, expense record, or another specific item. Attach only the relevant documents and check that they correspond to the invoice period, project, and amount.

A file not found in your folder is not necessarily a file that was never created or sent. Describe what you checked, and request a copy or clarification if the requirement appears unmet.

6. Submission route

Use the current submission instructions for this customer and entity. Confirm whether the invoice should be sent to a named address, uploaded through a customer portal, or delivered by another specified route. Check for stated file, naming, or reference requirements before sending.

Do not assume that a route used by another customer or subsidiary applies here. ReadySetBill does not submit an invoice to a customer portal or send it on your behalf.

Fictional example: Cedarline Systems

Cedarline Systems is a fictional IT consultancy preparing invoice CS-118 for fictional customer Morrow Works Ltd. The invoice covers a cloud migration discovery milestone for 1–30 April and cites PO MW-6024. The signed order identifies Morrow Works Ltd., the same project, and PO MW-6024; its schedule names a discovery milestone, while the billing instructions request an approved milestone record and submission through the customer’s supplier portal.

Before sending, Cedarline checks that the invoice’s bill-to entity matches the order, that the April dates match its service record, and that the billed description and amount correspond to the agreed discovery milestone. It confirms the milestone record is attached and follows the named portal route. If the record is not in Cedarline’s files, it should not claim that approval never happened; it should locate or request the document before treating the attachment requirement as resolved.

This example illustrates a checking method only. It does not represent a real customer, approval, or universal IT consulting requirement.

A short pre-send review

Are the invoice entity and address supported by the applicable contract or order?
Does each required PO and project reference match its source?
Are the billed dates or period explicit and consistent with the work record?
Does the amount map to the agreed milestone or fee basis?
Are the specified supporting documents available and relevant?
Does the chosen submission method match the current customer instructions?
Are unanswered conflicts or missing records clearly identified for follow-up?

Keep a copy of the instructions and supporting evidence used for the review. If two authoritative documents disagree, do not quietly choose one; ask the customer contact which instruction applies and record the response.

ReadySetBill checks an invoice against customer documents provided to it and may identify potential blockers. It cannot supply missing project approvals or determine an unstated customer preference. See the frontend-only demo for a sample report, or create an account to check your own invoices. Real account checks require an account.