12Hardware & Building Supplies · ERP software

Credit customers, limits and settlements for a building supplier

A supplier selling to contractors on account, needing credit control the counter can enforce.

  • Customer accounts and credit limits
  • Limit warning and approval at billing
  • Invoice-level settlement allocation
  • Receivable ageing

The problem

Contractor credit was tracked on a ledger card. Nobody at the counter knew when a customer was over their limit, and settlements were matched to invoices from memory at month end, which left disputes that took days to resolve.

What we built

We put credit limits and outstanding balance in front of the person billing, with approval required to exceed a limit. Settlements are allocated against specific invoices so the ageing is always explainable line by line.

Modules delivered

  • Customer accounts and credit limits
  • Limit warning and approval at billing
  • Invoice-level settlement allocation
  • Receivable ageing
  • Customer statements
  • Collection follow-up list

What changed

What the delivered system does differently from the process it replaced.

  • Over-limit sales require an approval rather than passing unnoticed
  • Every settlement is traceable to the invoices it paid
  • Statements are generated rather than compiled

Built with

The stack chosen for this build.

  • Go
  • PostgreSQL
  • REST API

Why this customer is not named

Most of our customers allow the work to be described but not their name published. Where a customer has given permission, their name and testimonial appear here.

Independent accounts of our work are published by customers themselves on our Facebook reviews page.

Does this look like your problem?

If any of this is familiar, the first step is the same one this project started with: a free requirement study that ends in a written scope and a fixed price.

SYODONTECH
Credit customers, limits and settlements for a building supplier | Case Study | Sydon Tech