Receivables and payables

See what customers owe you, and what you owe suppliers

Receivables are amounts you expect to collect. Payables are amounts you expect to pay. A useful system keeps those two lists from blurring into one notebook total. Reminders, payment status, and ageing exist only to the degree you define them.

Why the two lists get mixed

In a small trading operation the same page sometimes shows a customer’s unpaid bills and a supplier’s advance, especially when one firm is both. Staff then answer “what do they owe?” from memory. A receivables view should answer only the collection question. A payables view should answer only the payment question. Netting them is a separate, explicit choice, not the default.

What can be organized

Each open amount needs a party, a source document, a date, and a remaining value. Receipts and payments reduce that value according to the allocation rule you use: against a specific bill, against the oldest bill, or as an on-account amount. If your office does not allocate against bills today, the software should not pretend that it does. The underlying history usually lives in party ledger management. This page is about the collection and payment view on top of that history.

Transaction history that explains a balance

A collections list that shows only a number will be disputed. From an outstanding row, a person should be able to see the bill and the receipts already adjusted, when those links are in scope. The same applies to a supplier bill and the payments made against it. If partial payments are common, say so. Partial allocation is a different screen from “paid in full”.

Reports you might specify

  • Open receivables by party, with or without bill detail.
  • Open payables by supplier.
  • Receipts and payments for a date range.
  • Ageing buckets, if you define the buckets and the due date each document carries.
  • A simple status such as unpaid, partly paid, or paid, if those words match how staff speak.

None of these printouts exist until they are specified. A reminder message, an SMS, or an automatic chase is a further feature with its own content and consent questions. Do not assume it. Reporting mechanics are discussed in business reports and records.

What depends on your requirements

Due dates differ. Some businesses give 30 days from the bill. Some give a term written on the order. Some never use a due date and simply chase the oldest balance. Credit limits, hold-on-dispatch rules, and early-payment discounts are the same: include them only if someone will maintain the data. An empty credit limit field does not manage credit.

Distribution and wholesale teams often feel this first, because the same party may have several pending bills on a route. See trading and distribution and wholesale and retail for that context. Manufacturing firms may care more about supplier payables against material receipts, described on manufacturing and production.

Do we automatically get ageing and payment reminders?

No. Ageing needs a due-date rule you define. Reminders are a separate feature. The default conversation is about listing what is receivable and what is payable, with the history that explains each figure.

Can a receipt sit on account until we know which bill it settles?

Yes, if that is how your clerks work and the scope includes an unallocated amount. The party balance should still be explainable.

Describe how you collect and how you pay

Tell us whether you chase bills, balances, or both. The list follows that habit.

Discuss Your Business
Back to topWhatsApp