Invoice

There was a time when asking for money happened entirely in conversation. One person would message another that this month came to $2,500, and the billing felt finished. The trouble started afterward.

To pay that out of company funds, the person on the other end had to file an internal approval, and there was no document to file. Screenshotting a chat thread got questions back from every approver: what is this for, which period does it cover, does it include tax? Each round of questions pushed payment out another week.

The seller had the same problem in reverse. When a customer asked three months later what that $2,400 had been for, the only record was a chat log. An invoice closes both gaps with one sheet of paper. It fixes what was charged, and that same sheet becomes the document the buyer files internally.

A single invoice states who is charging whom, for what, how much, and by when — with nothing left implied.

1. Issuer and recipient. Legal names, business registration numbers, addresses, and a contact on each side. Naming only the day-to-day contact as recipient means the document stalls whenever that person is out, so most sellers add the finance team's address alongside.
2. Invoice number. A unique number per document. It's the key you match payments against later — when $1,500 lands in the bank account, this number tells you which charge it settles.
3. Issue date and due date. When it went out and when payment is expected. Terms are usually set as a number of days, such as 30 days from issue, and nothing counts as late until that date passes.
4. Line items. Where each thing being charged for gets its own row, and where invoices go wrong most often. A row carries the plan name, the number of users, the period, the unit price, and the row total. Billing a twenty-person team as a single row reading "services, $2,400" invites questions from every approver; "Team plan / 20 seats / 3 months / $40 per seat" leaves nothing to ask. If the seat count changed mid-period, the prorated amount gets its own row.
5. Subtotal, tax, and total. Pre-tax amount, value-added tax, and the final figure, kept separate. Give only the total and the customer can't process the tax side, and their finance team will send the document back before paying it.
6. Payment details. Bank account information or a payment link. If you take cards, this is where the checkout page from your payment gateway — the service that routes card payments on your behalf — gets linked.
7. Reference numbers. The purchase order (PO) number, the document through which a customer formalizes intent to buy, or a contract number. At larger companies, approval often can't even begin without it.

Early on a salesperson writes them by hand; once the customer count grows, a billing system issues them automatically. Under a subscription model, where a fixed amount comes due each cycle, hundreds go out on the same day every month and hand-writing stops being possible. Even after the switch, enterprise customers on non-standard terms usually still get a human read.

The reader is never one person, and that shapes how the document gets written.

1. The day-to-day contact at the customer. They receive it and file the approval. They forward it as-is only when the line items match the contract they remember.
2. Their finance team. They look at the amount, the tax, and the due date. This is who actually sends the money.
3. Approvers up the chain. They see the amount without knowing the contract behind it. Lumped line items stop here, and the question comes back down the chain.
4. Accounting on both sides. They pull it back out when reconciling the books months later. That's why a sent invoice never gets edited — a wrong amount is voided and reissued under a new number.

"The invoice went out, but the PO number was missing, so their approval never got filed."

The document was sent and the buyer's process hasn't even started.

"This month's invoice has proration in it, so split it into two line items."

The price changed mid-month, so the period has to be shown in pieces rather than as one charge.

"We're 45 days past the invoice due date with no payment."

The account is late, and chasing it is now someone's job rather than something to keep waiting on.

At Pagedeck, enterprise invoices go out only after Sofia checks them. The system drafts them, but a person confirms the line items against the contract, because every month a few customers have added seats mid-period or carry a discount written into their agreement.

Last quarter one invoice skipped that check. It went out without the 15 percent discount the contract specified, the customer's contact wrote back, and voiding and reissuing took four days. The amount was corrected, but payment slipped by those four days, and the item was still on the list when Grace reviewed quarterly cash flow.

The most common mistake is treating a sent invoice as a completed charge. On the selling side, producing and sending the document is the laborious part, so everything after it feels like waiting. On the buying side, that's where the work starts: the contact files for approval, a manager signs off, and finance transfers on its next payment run. That sequence takes anywhere from two to six weeks depending on the company, and one missing reference number sends it back to the beginning. Plan cash against the send date and you'll be off by that gap every month.

Assuming invoices have a legally mandated format is nearly as common. Tax invoices do have a prescribed form and a filing deadline, so a document that looks similar seems like it would too. In practice the format is open and the seller decides what goes on it. Missing that leads two different directions. Some teams take the freedom as license to write vague line items and get stuck in the buyer's approval chain. Others assume the prescribed form is the real one and send a tax invoice in place of an invoice — at which point the customer's finance team is holding a document they can't file for approval, and payment stops.