Search
Intermediate Certificate on pass

Customer & Vendor Management

Keep clean records for who you sell to and buy from — terms, statements, and history the whole system can trust.

4 lessons 35 min 5-question assessment 70% to pass

What you’ll learn

  • Explain why customer and vendor master data underpins operations
  • Maintain accurate records with terms, limits, and contacts
  • Read statements and history to manage balances early
  • Avoid duplicates and keep relationships auditable

Course content

4 lessons · 35 min of reading
01
Lesson 1 of 4 Reading 8 min

Master data: who you deal with

Customers and vendors are master records — the people and businesses you sell to and buy from. In AWRA every sale, invoice, payment, purchase order, and return links back to one of these records. Get the master data right and the rest of the system has someone to attach activity to; get it wrong and history scatters across duplicates.

A master record is created once and reused everywhere. That single source is why a customer’s full history — orders, invoices, payments, returns — can be seen in one place rather than reconstructed.

Decide a naming convention before you start loading records, because it is the cheapest fix now and the most painful later. Pick one form — say, registered business name first (“Jambo Hardware Ltd”), not the contact person — so “Jambo Hardware”, “J. Hardware”, and “Mary at Jambo” don’t become three records for one customer. The convention is what lets the next person find the existing record instead of creating a fourth.

Key takeaways

  • Customers and vendors are reusable master records.
  • Every transaction links back to a customer or vendor record.
  • One clean record per party keeps history together, not scattered.
  • Agree a naming convention up front (business name, not contact person) so the same party is always found, never re-created.
02
Lesson 2 of 4 Reading 9 min

Terms, limits, and contact details

A record holds more than a name. Payment terms such as net 30, credit limits, tax details, and contacts shape how you transact. Setting a customer’s terms means invoices and statements behave consistently; setting a vendor’s terms means you know when bills are due.

Credit limits are a quiet control: a customer near their limit can be flagged before another order ships, protecting you from over-extending. Because the terms live on the record, they apply automatically rather than relying on someone remembering.

Worked example: a customer on net-30 with a KES 200,000 limit already owes KES 185,000 and places a KES 40,000 order. AWRA flags it at order entry — before goods leave — so a manager can take a deposit, ship part now, or hold it, instead of discovering the over-extension only when the debt has already gone bad. The control is only as good as the limit, so review limits as customers grow rather than leaving the day-one figure forever.

Key takeaways

  • Records hold terms, credit limits, tax details, and contacts.
  • Terms drive consistent invoicing, statements, and due dates.
  • Credit limits flag over-extension before it becomes bad debt.
  • Limits only protect you if kept current — review them as customers grow rather than leaving the day-one figure.
03
Lesson 3 of 4 Practice 9 min

Statements and history

A statement summarises what a customer owes, or what you owe a vendor, over a period — invoices, payments, credit notes, and the running balance. It is the document you send to chase payment or to reconcile with a supplier.

Because every transaction posted live, the statement is a true picture, not an estimate. Reading it well — what is outstanding, what is overdue, what is disputed — is how balances get managed before they become problems.

A simple routine beats heroics here: run an aged statement monthly and work it by bucket — current, 30, 60, 90+ days. Chase the 60-day balances hardest, because that is where money is still collectible but slipping; the 90+ column is usually a sign you stopped following up two months too late. The statement tells you which customer to call today, not just the total they owe.

Key takeaways

  • A statement shows invoices, payments, credits, and the balance.
  • Live posting makes statements accurate, not estimated.
  • Reading statements is how overdue balances get managed early.
  • Work statements by ageing bucket and chase the 60-day balances hardest — that is where money is still collectible but slipping.
04
Lesson 4 of 4 Reading 9 min

Clean data and no duplicates

The biggest enemy of useful master data is duplication — the same customer entered twice, so their history and balance split in two. AWRA encourages one record per party; before creating a new one, you check whether it already exists.

Clean, de-duplicated master data is what makes reporting, credit control, and statements trustworthy. A duplicate vendor can hide a double payment; a duplicate customer can hide that they are over their limit. Keeping records tidy is real financial control, not just admin.

When you do find a duplicate, merge rather than just stop using one — an abandoned record still carries half the balance and half the history. Search by phone number or tax PIN as well as name before creating anyone new, since that is where the typo-proof match lives; “Acme Ltd” and “ACME Limited” share a PIN even when the names differ.

Key takeaways

  • Duplicates split history and balances across two records.
  • Check for an existing record before creating a new one.
  • Clean master data underpins credit control and trustworthy reports.
  • Search by phone or tax PIN, not just name, and merge duplicates rather than abandoning one half the balance.

Finished the material?

Take the 5-question assessment and earn your certificate — 70% to pass.

Take the assessment

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center