Volume 20, Chapter 2
Core Business Systems: Accounting Software, POS
Definition
A POS system got chosen for its clean interface and low price. It turned out to have no real way to track a customer buying on credit, only cash-at-the-till sales fit its model cleanly. Rather than replace it, staff started keeping a separate paper note for credit sales alongside it, quietly recreating the exact fragmented record-keeping the software was bought to fix.
Accounting software automates the Finance Module, cash book, ledger, reports. A POS (Point of Sale) system automates the Order and Payment Modules, recording sales as they happen. Neither replaces the process this manual has already designed. They should automate it.
Why did a clean, cheap tool end up creating more work instead of less? Because it was chosen before anyone checked whether it actually matched how the business already sold things, on credit as well as cash. Software that doesn't fit the real process doesn't remove the paperwork, it just adds itself on top of it.
The single most important rule from Chapter 1: answer the one question, what data, who needs it, who sees it, before buying software, not after. Software chosen without that answer forces the business to bend its process to fit the tool, instead of the other way around.
What to Check Before Choosing
Covers your actual list of accounts
Must match Volume 07's financial structure, not a generic template.
Tracks credit sales and money still owed
See Volume 16, Chapter 2, many basic POS systems only handle cash sales well.
Connects to inventory
So a sale actually reduces recorded stock, see Volume 13.
Supports your approval ladder
Refunds and discounts should respect Volume 11's approval authority, not bypass it.
Exports your data
You should always be able to leave a tool and take your records with you.
Software should fit the process you've already designed, not become the reason you redesign your process around its limits.
Example Story: The POS That Couldn't Do Credit
Here's the full version of the clean-interface-cheap-price story from the start of this chapter.
A POS system adopted for its clean interface and low price turned out to have no real way to track a customer buying on credit. Only cash-at-the-till sales fit its model cleanly. Rather than replace it immediately, staff began keeping a separate paper note for credit sales alongside it, quietly recreating exactly the fragmented, dual-record problem the software was bought to solve.
The software wasn't broken. It simply didn't match how the business actually sold things. Switching to a system that handled Volume 16, Chapter 2's credit sale and receivables tracking natively ended the shadow paper system for good.
Across Industries
What "must have" software feature matters most changes depending on how each business actually takes orders and payment.
| Business | A System Requirement Specific to Them |
|---|---|
| Golden Crust Bakery | POS handling both walk-in cash sales and standing wholesale credit accounts |
| Rapid Auto Works | Tracking the cost of each specific repair order, not just generic entries |
| Precision Print & Press | Quotation-to-invoice conversion for custom, non-standard jobs |
Common Mistakes
Ignores whether it actually covers the required modules from Chapter 1.
A clear sign the software doesn't actually fit the process, see the example story.
Locks the business into a tool it can never leave without losing its own history.
Quiz Yourself
Practice Exercise
List your five most-used data fields from Chapter 1's Order and Payment Modules. Check whether your current (or prospective) accounting/POS software actually captures every one of them.
Quick Summary
Quick Summary
- Accounting software and POS should automate an already-designed process, not force a new one.
- Check coverage of your list of accounts, credit sales, inventory connection, and approval ladder before choosing.
- A shadow paper system running alongside your software is a sign it doesn't actually fit.