Where the Invoice Actually Goes
Sending it to the person who gave you the work is the most natural mistake in invoicing, and it costs a month.
Yourswho controls this stretch
The person who gave you the work is almost never the right place to send the invoice. In most organisations there is an invoicing address, a portal, or a shared mailbox, and anything sent elsewhere arrives nowhere useful.
The invoice problem in “Where the Invoice Actually Goes” is easier to resolve when the work behind it has an approved record. A service team assessing work days in a year for work days in a year can connect time and projects with the billing file, while the invoice and accounting system remains authoritative for amounts, tax and settlement.
It is the most natural mistake available and it routinely costs a full payment cycle.
Additional context for “Where the Invoice Actually Goes” is available through Upwork independent-work resources. A sound review separates the work record, invoice, approval and final settlement.
Why it happens
Because that is the relationship. Everything else about the job goes to that person, and the invoice feels like part of the same conversation.
- The invoice goes where it enters the system: the dedicated address, the portal, the shared inbox. This is the one that starts the clock.
- A copy goes to your contact as information, with a line saying it has been submitted and nothing is needed from them.
- Doing only the first leaves nobody internally aware you are waiting. Doing only the second may never enter the system at all.
What happens to it there
It sits in an individual's inbox. They may forward it, may file it to act on later, or may assume somebody else received it too.
None of those is a route into the system, and none produces a record.
The right route
Whatever their accounts payable says it is. A dedicated address, a portal, an EDI feed, or a specific person.
One question at the start of the relationship settles it for years.
The copy that is useful
Sending the invoice to the proper route and copying your contact is best of both: it enters the system and the person who can confirm receipt knows it exists.
The portal
Where one exists it is usually mandatory, and an emailed invoice is simply ignored.
Portals have their own note here; the point is that the route is not a preference.
Checking it arrived
A week after sending, ask accounts payable whether it has been received and matched.
This is the single most valuable administrative habit in this collection, and it is covered again in the wait.
"We never received it"
Answered by knowing exactly where and when you sent it, and by having sent it to the route they specified.
Answered by nothing at all if it went to one person's inbox.
When the route changes
Systems change, mailboxes are retired, companies are acquired. The announcement goes to an address you may not monitor.
A rejected or unacknowledged invoice is the first sign, and it is worth treating as information rather than as an error to repeat.
Several entities, several routes
Group customers often have different routes per company. The entity on the order decides which.
Sending the right invoice to the wrong group route is as fatal as sending it nowhere.
Keeping the record
Per customer: entity, route, reference required, format, cut-off, and a named contact in their finance function.
Six fields, checked once a year, and they prevent most of what this section describes.
Why the right route is not the obvious one
The natural instinct is to send the invoice to the person who gave you the work, because they are the person you have been dealing with. In a buyer of any size that is the one address almost guaranteed not to start the payment process.
Your contact's inbox is not an input to accounts payable. At best they forward it, adding a delay of however long it takes them to notice; at worst it is read, appreciated and left, because receiving an invoice does not feel like a task.
The invoice address exists precisely so that arrival is not dependent on anybody remembering. It is usually printed on the order, and asking for it takes one line.
Two routes for two purposes
The clean arrangement is to send the invoice to the process and a copy to the person, with the roles clearly different.
The invoice goes where it enters the system: the dedicated address, the portal, the shared inbox. That is the one that starts the clock and the one that matters if anybody later asks when you submitted it.
The copy goes to your contact as information, with a line saying it has been submitted and nothing is needed from them. It costs nothing, it means somebody internally knows the invoice exists, and it gives you a person to ask later without having to explain the job from the beginning.
What causes trouble is doing only one of the two. The invoice sent solely to the contact may never enter the system. The invoice sent solely into the system may sit unmatched for a month with nobody internally aware that a supplier is waiting, which is the state in which most of the delays described in this collection actually happen.
The route that changes without notice
Invoice addresses move. A buyer outsources its accounts payable function, introduces a portal, consolidates two entities, or simply changes a shared inbox, and the supplier learns about it from an unpaid invoice rather than from an announcement.
Confirming the route on each new order, rather than assuming last quarter's address still works, costs one glance at the paperwork and prevents the most frustrating version of this problem: a correct invoice, properly sent, to somewhere nobody reads.
The one-line rule
The invoice goes where their system reads, not where your relationship lives, and the person you deal with is copied rather than relied upon.