Sundry Creditors

This code records amounts relating to sundry creditors, expected to be settled within the next 12 months. As a liability account, it normally carries a credit balance: credit entries increase the balance (recording new amounts owed) and debit entries decrease it (recording payments made).

Real-world examples

Hospitality

A restaurant takes a £200 deposit for a private function that's later cancelled, with £150 agreed to be refunded and £50 retained as a cancellation fee. The £150 owed back doesn't relate to a trade supplier, so it isn't run through the main purchase ledger — it's posted directly as a credit of £150 to 2101 (Sundry Creditors), clearing to a debit against 1200 (Bank) once the refund goes out.

Professional services

A consultancy occasionally owes a one-off referral fee to another firm that introduced a client, agreed as a single arrangement rather than a standing supplier account. A £600 referral fee owed is a credit of £600 to 2101 (Sundry Creditors), with the debit side usually an introducer-fee or marketing code, clearing to 1200 once paid. Because it's ad hoc and won't recur monthly, it's kept out of the main creditors ledger (2100) so it doesn't distort the pattern of regular trade purchases reviewed there.

Commonly confused with

Code 2101 (Sundry Creditors) is easy to confuse with code 2100 (Creditors Control Account), the control account it feeds into. Day-to-day postings from individual invoices go to a named account like this one; the control account is the running total Sage reconciles against the sales or purchase ledger, so you shouldn't normally post the same transaction to both.

What a mis-posting here costs you

An error posting to Sundry Creditors misstates what the business owes, and for a Current Liabilities code specifically it can distort the working capital and current ratio that lenders and suppliers look at when assessing short-term financial health.

Other codes in Current Liabilities