P2 · Trying to get paid
Invoicing That Gets Paid Faster
Create invoices that clear AP quickly with the right legal customer, due date, PO reference, itemized scope, payment methods, reminders, and clean reconciliation.
An invoice should identify your business, the client legal entity, invoice number, issue date, due date, services or milestone, amount, taxes if applicable, payment instructions, and any purchase-order reference the client requires. Net-7, net-15, and net-30 describe time after invoice issuance; 'due on receipt' removes ambiguity but does not force a large company to bypass its AP process. Ask about vendor onboarding before the first invoice is urgent.
Keep invoice numbers sequential and auditable
A sequential invoice-number system helps both bookkeeping and client reconciliation. Avoid reusing numbers after a canceled invoice; issue a credit or corrected document so the audit trail remains intelligible.
Invoice acceptance checklist
- Customer record
- Use the client’s correct legal/billing name, billing contact, email or portal, PO/vendor number, tax information, and remittance instructions. Confirm these requirements before the first invoice rather than after a rejection.
- Invoice identity
- Use a unique invoice number, issue date, due date, itemized service or milestone description, amount due, currency, and the contract/project reference. Match wording to what procurement approved so AP can recognize the charge.
- Payment terms
- Carry the agreed net terms, deposit credit, late-fee language, and payment methods from the contract into the invoice. Do not invent a fee or change the payment window unilaterally on the bill.
- Payment rail
- Offer the approved card, ACH, bank-transfer, check, or processor link and make the payee details unambiguous. For larger B2B invoices, verify whether the client requires a vendor portal or ACH enrollment before due date.
- Reconciliation
- Record gross invoice revenue separately from processor fees, refunds, chargebacks, and net bank deposits. A $2,000 invoice that settles as less than $2,000 is still a reconciliation problem, not evidence that revenue equaled the payout.
Choose payment rails for the client and ticket size
Offer payment methods that fit the ticket size and client. Card is convenient but can add fees and dispute exposure; ACH is often cheaper but still requires correct account controls and settlement expectations.
AP fields and PO references can matter more than reminder copy
Put the PO, project code, billing contact, or department exactly where the client's AP team expects it. Many 'late clients' are actually invoices sitting in an exception queue because a required field is missing.
Automate reminders without pretending a not-yet-due invoice is late
Automate reminders but write them like a human. A day-zero confirmation, due-date reminder, and escalating overdue notices can be scheduled without pretending the client is delinquent before the due date.
Turn a completed milestone into an AP-ready invoice
AP-ready invoice check: before sending a $7,500 milestone invoice, confirm the client's legal entity, billing email, PO number, milestone description, net terms, ACH instructions, and remittance contact. One missing PO can delay payment longer than any clever reminder subject line can fix.
What makes an invoice easy for AP to approve
An invoice can be perfectly designed and still sit unpaid if it fails the client's accounts-payable rules. Before the first bill, confirm the customer's legal entity, billing address, AP email, purchase-order number, project code, tax information, payment method, and whether the vendor must be onboarded in a portal. Use a unique invoice number and one unambiguous due date. Net-7, net-15, and net-30 are counting conventions; they do not override a large customer's procurement process if the required PO or vendor record is missing.
Reconciliation matters as much as sending. If a $2,000 card invoice produces a $1,941.70 bank deposit after a 2.9% + $0.30 processor fee, the books should still show $2,000 of gross revenue and the processor fee separately, subject to your accounting method and tax treatment. The same applies to refunds and chargebacks. Keep invoice terms consistent with the signed contract: a surprise late fee typed onto an invoice may not create a valid obligation if the agreement never contained it. Automate reminders if useful, but make the first overdue message sound like an administrative check, not an accusation.
Build the invoice from the customer’s accounts-payable requirements, not just your own template. Before the first invoice, confirm the legal bill-to name, AP email or portal, purchase-order requirement, vendor ID, tax documentation, currency, and whether the client rejects invoices missing a project code. Then include your legal business name, contact information, unique invoice number, invoice date, due date, description tied to the contract or milestone, amount, tax if legitimately applicable, payment instructions, and the PO or reference the buyer requires. A beautiful PDF sent to the project manager can still sit unpaid if procurement expects it in a portal. For recurring clients, save the approved billing profile so the next invoice does not repeat onboarding mistakes.
Reconcile payment rails all the way to the bank. If an invoice is $2,000 and the processor deposits $1,938 after fees, record the $2,000 customer payment and the $62 processing cost separately when appropriate rather than reducing revenue to the net deposit. Match each deposit to an invoice or group of invoices so a later 1099-K can be reconciled to gross processed payments without double counting. Automate reminders around the actual due date, but make the sequence human: confirmation when the invoice is sent, a short reminder near or just after due date, then a firmer request for a specific payment date. If the client says ‘it’s with AP,’ ask for the AP contact, submission date, and scheduled pay run. The goal is to remove process ambiguity before escalating the relationship.
Use invoice aging as a management report, not just a collections list. Group open balances by current, 1–30 days late, 31–60, and older, then review the pattern by client. A single late invoice can be administrative; repeated lateness is a credit-policy signal. For new clients, compare promised terms with actual payment days and decide whether the next project needs a larger deposit, shorter terms, card/ACH authorization, or no additional work until the old balance clears. If a customer disputes a line item, separate the undisputed amount and ask whether it can be paid on schedule while the specific issue is resolved. That keeps a small question from freezing an entire invoice unnecessarily.
Before sending every invoice
- Use unique invoice numbers.
- Confirm legal entity and billing contact.
- Include required PO/project codes.
- Show one unambiguous due date.
- Reconcile gross payment, fees, refunds, and bank deposit.
Invoice questions that affect payment speed
Who should the invoice be addressed to?
Use the legal customer or entity responsible for payment and send it through the billing contact or AP channel the client requires. A project manager can approve the work while a different entity or department actually pays, so confirm both before the first invoice.
Is net 7 always better than net 30?
Not automatically. Shorter terms can improve cash flow, but enterprise clients may have procurement cycles that make them unrealistic. Agree on the term before work starts, show a calendar due date on the invoice, and price the relationship with the real payment cycle in mind.
What details prevent invoice rejection?
Include a unique invoice number, issue date, due date, legal names, service or milestone description, amount, applicable tax, payment instructions, and any PO or vendor reference. The goal is to make approval possible without an email asking what the invoice is for.
Should I offer multiple payment methods?
If the economics and risk are acceptable, yes. ACH can be cheaper while cards can increase convenience; settlement timing and dispute exposure differ. Reconcile gross collections, processor fees, refunds, and net bank deposits separately so payment convenience does not create messy books.