Textbooks present these as mirror images: one records what you owe, the other what you are owed. That is true and it is not very useful, because the two behave nothing alike day to day.
The difference that matters is who controls the document.
The definitions, briefly
The purchase ledger — also called accounts payable, or the bought ledger — records invoices from your suppliers and what you have paid against them. It sits behind the trade creditors figure in your balance sheet.
The sales ledger — accounts receivable — records invoices you have issued to customers and what they have paid. It sits behind trade debtors.
Both are subsidiary ledgers: detailed accounts per supplier or customer, summarised into a single control account in the nominal ledger.
The asymmetry nobody mentions
On the sales ledger, you create the document. You decide the format, the reference, the terms, when it goes out. It arrives in your system already structured, because your system made it.
On the purchase ledger, someone else creates the document. Hundreds of someones, each with their own layout, their own reference format, their own idea of what a line item is, sending it whenever they feel like it, by whichever channel they prefer. That variety is the whole reason entry resists being sped up.
That single asymmetry explains almost every practical difference between the two.
| Purchase ledger | Sales ledger | |
|---|---|---|
| Who authors the document | Your suppliers | You |
| Arrives as | Whatever they send | Structured data you generated |
| Main operational cost | Getting data in | Getting money in |
| Fails by | Documents lost, entered late, entered twice | Customers paying late |
| The lever | Automation of capture | Credit control and follow-up |
| Fraud exposure | Fake or altered supplier invoices | Bad debt |
| Who you chase | Nobody — you are the payer | Customers, repeatedly |
Why they fail differently
The sales ledger fails at collection. The data is fine. Your system produced it, it is already coded, it is already correct. What goes wrong is that customers do not pay on time. The work is chasing, and the skill is knowing who to chase, how hard, and when to stop supplying.
Automating a sales ledger mostly means automating reminders.
The purchase ledger fails at capture. By the time an invoice is in the ledger, the hard part is over — paying it is a scheduled, mechanical act. What goes wrong is upstream: the invoice is in someone's inbox, or in a pile, or entered with a transposed figure, or entered twice, or entered three weeks after it arrived.
Automating a purchase ledger means removing the typing, because the typing is where the delay, the errors and the duplicates all come from.
This is why "we automated our invoicing" means completely different things depending on which ledger someone is talking about, and why software that is excellent at one is often irrelevant to the other.
The one place they meet
Both feed the same reconciliation, and both distort the same reports when they are behind.
An unentered purchase invoice understates creditors and overstates profit. An unrecorded sales receipt overstates debtors and makes your credit control chase someone who has already paid. In both cases the ledger is not wrong so much as incomplete, and incomplete is harder to spot than wrong.
The asymmetry shows up here too. You will notice a missing sales receipt, because a customer will tell you they have paid. Nobody tells you about a missing purchase invoice until the supplier's statement arrives, or until they stop delivering.
Which to fix first
If both are behind, the purchase ledger is usually the better first target, for an unglamorous reason: it is entirely within your control.
Improving the sales ledger requires other people to change their behaviour — customers have to pay sooner. Improving the purchase ledger requires nobody's cooperation at all. The documents already arrive; the question is only what happens to them next.
That said, if cash is the binding constraint rather than time, collection is where the money is. Faster purchase ledger processing improves accuracy, close speed and control. It does not by itself improve cash — arguably the reverse, since entering invoices promptly makes liabilities visible sooner.
Worth being honest about which problem you actually have.
Terms you will see used interchangeably
- Purchase ledger / accounts payable / AP / bought ledger / creditors ledger
- Sales ledger / accounts receivable / AR / debtors ledger
British practice tends to say purchase and sales ledger; American practice says payable and receivable. Cloud accounting software mostly uses "bills" and "invoices", which is clearer in the interface and less clear in conversation — "invoice" then means both the thing you send and the thing you receive.
Cribble works on the purchase ledger side — the one where the documents arrive in whatever form the sender chose. Invoices are forwarded by email, read whatever their layout, and posted to Xero as coded bills once someone has approved them.