Grouped by the solution they serve. Each one names exactly what is Community, what is an add-on, and what the agent does.

Nine hundred statement lines, and the only place the match exists is in one person's head
Read →
The asset register lives in a spreadsheet, and the depreciation entry is typed in every month
Read →
The department is in the account number, because there was nowhere else to put it
Read →
Nothing is wrong with the books. The close still runs beside the system, not inside it.
Read →
The bill is dated December. The books closed in December.
Read →
It is the same invoice. It has a different reference.
Read →
The expense report is a spreadsheet emailed around, and it reaches the ledger a month after the money left
Read →
The payment is made in the bank's website. The ledger finds out on Thursday.
Read →
The bill matches the PO. The price doesn't.
Read →
This vendor is late every time, and the person who knew that has left.
Read →
Everybody knows which customers are late. Nobody can say it from the system.
Read →
The budget lives in a spreadsheet, and the variance is a copy-paste on the fifth working day
Read →
The cash position is accurate. It is also a day behind the bank, and the gap is a file somebody has to fetch.
Read →
The board pack is assembled in a spreadsheet, and the ledger is where the numbers were before somebody moved them
Read →
Entity A raises the invoice. Somebody keys the matching bill into Entity B. At month end, somebody finds them both again.
Read →
The tax was right on the invoice. Proving it three quarters later is the part nobody scoped.
Read →
The system says forty-three. The shelf has forty. Both numbers were true at some point today.
Read →
"Has it shipped?" is a question somebody answers by walking to the warehouse
Read →
Where the pallet goes when it lands is decided by whoever is on shift
Read →
The parts list is not in dispute. Which of those parts is a thing you build is.
Read →
The freight invoice turns up three weeks after the goods, and half of them have already shipped back out
Read →
You negotiated the price in March. In June somebody paid list.
Read →
The approval happened. It happened in an email thread.
Read →
The change is two lines. Every route to it runs through somebody's licence desk.
Read →
The reorder point is a number somebody typed once, and nothing since has argued with it
Read →
The cost of the run is assembled after the fact, in a spreadsheet, from three exports
Read →
Two orders both need that machine on Tuesday, and the system has no opinion about which one gets it
Read →
The run came up short, and now there are two versions of what is outstanding
Read →
Everybody on the floor knows the standard time is wrong. The system has no way to hear it.
Read →