Invoicing

Digital Invoices: Payment Terms, Tracking and Late Payment Follow-Up

SokoWise TeamSokoWise Team
•••7 min read
Digital Invoices: Payment Terms, Tracking and Late Payment Follow-Up

A digital invoice can reduce avoidable payment delays when the customer can quickly understand what was supplied, how much is due, when it is due, and how to pay. Sending an invoice electronically does not guarantee prompt payment; clear agreements, accurate records, and a consistent follow-up routine matter just as much.

Use an invoice as a record of an agreed sale or service, not as a substitute for confirming the scope and payment terms before work begins.

Make the invoice easy to approve

Before sending, verify:

  • Seller and customer names and the right contact.
  • A unique invoice number and issue date.
  • The goods or services supplied, with quantities and agreed prices.
  • Discounts, taxes, delivery, and the final total shown clearly.
  • Payment methods and any reference the customer should include.
  • Payment terms and a specific due date.
  • Contact details for questions or corrections.
  • Any required electronic tax invoice information for your jurisdiction.

An invoice with missing purchase-order details, an incorrect billing name, or a disputed quantity may be placed on hold even if the customer intends to pay. For repeat work, confirm the person who approves invoices and the format their accounts team accepts.

In Kenya, a business document called an invoice is not automatically an eTIMS tax invoice. Review current KRA eTIMS requirements and ask a qualified tax adviser which process applies to your transactions.

Agree on terms before the work

Discuss the deposit, milestones, delivery, cancellation, late-payment handling, and when the remaining amount is due before supplying goods or services. Write the agreement in plain language and put it on the quote, order confirmation, or contract as appropriate.

State a calendar date instead of an ambiguous phrase such as “pay within two weeks” when confusion is possible. If you use “net 14,” define whether that means 14 days from invoice issue, receipt, or approval. Terms vary by contract and applicable law, so do not assume a template is legally suitable for every sale.

For a large project, divide payment into clear milestones. For a recurring service, confirm the billing cycle, price changes, and cancellation process. A customer should know the total amount and what is included before approving the purchase.

Send and track consistently

Send the invoice to the agreed address or channel and keep a copy of the message, document, and delivery status. Record the invoice date, due date, amount, currency, customer, and current state. Mark an invoice paid only after you have matched the payment to the correct customer and invoice.

A simple aging schedule helps prioritize follow-up:

StatusAction
Not yet dueConfirm the customer received the invoice and can process it
Due soonSend a brief reminder with the invoice and payment details
Past dueContact the named approver, ask whether a detail is blocking payment, and agree a next step
DisputedPause repetitive reminders; identify the disputed item and document the resolution
Part-paidRecord the amount received and the balance, then confirm the remaining due date

Review open invoices at a regular interval. Start with high-value or long-overdue items, but do not ignore smaller balances that repeatedly create admin work.

A respectful follow-up sequence

A useful reminder is brief, specific, and easy to act on. Include the invoice number, original due date, unpaid balance, a copy or link to the invoice, and a contact for questions.

Example before a due date:

Hello Amina, invoice INV-104 for KES 24,000 is due on 18 November. I’ve attached it again for your records. Please let me know if your team needs a purchase-order reference or another document.

Example after a due date:

Hello Amina, our records show KES 24,000 remains outstanding on INV-104, due 18 November. Could you confirm the expected payment date, or tell me if there is an issue we should resolve?

If a customer raises a dispute, ask what line, quantity, date, or term they are questioning. Compare it with the signed quote, delivery confirmation, or work record. If the invoice needs a correction, issue a clearly linked replacement or credit note according to the relevant tax and record-keeping process instead of silently editing the old document.

Reduce avoidable delays

  • Confirm billing and approval contacts before delivery.
  • Send a quote first where scope or quantity may change.
  • Use item descriptions the customer recognizes.
  • Attach required delivery, purchase-order, or completion evidence.
  • Set a reminder when the invoice is sent.
  • Reconcile bank, mobile-money, card, and cash receipts regularly.
  • Record partial payments and agreed payment plans.
  • Escalate persistent non-payment through an appropriate business or legal adviser.

Do not add an unagreed penalty or change payment terms after the sale. If late fees or interest may apply, state the basis in advance and confirm it is lawful and contractually enforceable.

Use an accounts-receivable aging review

Aging means grouping unpaid invoices by how long they have been outstanding. Use your contract terms as the reference date; do not assume every customer has the same due period.

GroupReview question
Not yet dueHas the customer received the invoice and all required supporting documents?
Recently overdueIs an approval, purchase-order number, or correction holding it up?
Long overdueWho is the authorized decision-maker, and what next step was agreed?
DisputedWhich exact line, quantity, delivery, or term needs evidence?
Partly paidWhat balance remains, and is there a written payment schedule?

Keep a short contact log with the date, person contacted, response, and promised next action. This helps different staff members continue the conversation consistently and prevents multiple conflicting reminders.

If a customer cannot pay the full amount at once, consider whether a payment plan is commercially appropriate. Put the amount, dates, and treatment of a missed payment in writing. Check legal and contract requirements before charging interest or taking recovery action.

Use a sample reminder schedule

For example, a business might confirm receipt two working days after sending an invoice, send a reminder shortly before its agreed due date, then follow up after the due date if payment is not visible. The exact timing should fit the contract and customer relationship. For a large business customer, contact the accounts-payable team and ask whether a purchase order or supplier reference is missing.

Keep the tone factual and avoid implying that the customer has acted in bad faith. If a payment has been made but not matched, ask for a transaction reference and check the provider records before sending another demand. If the customer reports a genuine error, pause the reminder and resolve it.

Improve the process with a short monthly review

Compare how many invoices are paid by their due dates, how much remains overdue, the average time from issue to payment, and which disputes recur. Segment by customer type or invoice size only when it helps explain a decision. Averages can hide one large late invoice, so review individual balances as well.

Update templates when you find repeated errors. Keep copies of the original quote, approved changes, invoice, payment confirmation, and any credit note together so the transaction can be reconstructed later.

Use the aging list in a short cash-flow forecast, but distinguish expected collections from money already received. A customer promise to pay is useful planning information, not cleared cash. If a key payment is delayed, compare the revised expected date with payroll, supplier commitments, rent, and other due costs; adjust spending or discuss options early rather than relying on an unverified deposit.

For related document steps, see how to convert a quote into an invoice, how to design a readable branded invoice template, and receipt records and eTIMS requirements.