Accounting workflow as a standalone system - the ledger, statement and reconciliation work that the operational products currently each do for themselves.
Price: £12 / month · see full pricing
Private pilot, by invitation. PBS Accounts is live at accounts.pascoesystems.co.uk. Public sign-up is closed: accounts are issued by an administrator, and each one gets a private workspace of its own that starts empty. Where each of our products stands is stated plainly.
Not bookkeeping. The part of accounts work that is nobody's favourite afternoon: a supplier sends a statement, and somebody has to decide whether it agrees with what you think you owe.
The statement is read line by line — invoice numbers, ticket references, dates and amounts. What could not be read is reported as unread rather than dropped, because a line that quietly disappears is the one that costs you.
Matching is supplier-first, and it will not attach a statement automatically when the account reference and the printed name point at different suppliers. It says exact, closest, conflict or no match, and a person decides. Guessing here is how one supplier's money ends up against another's account.
A running balance that does not follow from the line before it is a finding. So is a closing balance the supplier printed that their own rows do not reach. Both are surfaced rather than reconciled away.
Lines are confirmed, corrected or queried, and who did each and when is kept with the line. The approval is somebody's, and the record says whose.
Stated as measurement rather than as a claim, because the honest answer is more useful to you than an optimistic one.
Sign in and you land on your companies, each with its statement counts and a button through to its screens. Paste a supplier's statement in and it is laid out line by line, the running balance and the supplier's printed closing balance are checked against the rows, and the statement is matched to a supplier on your register by account reference and name — or the match is refused and said so. Correct a figure, add a line the supplier left off, or take one off, with the supplier's original kept beside your change. Approve it, and who did so and when is recorded with a fingerprint of exactly what was approved; withdraw an approval and the history stays. The approved statements are listed and exported as CSV. A supplier register belongs to the company. Every screen is documented in the app's own handbook, and it works on a phone.
A statement is pasted in as text; there is no PDF upload yet. It matches a statement to a supplier, but it does not yet reconcile a statement against your own purchase invoices — that is the next piece of the job. It is not a general ledger and it is not a bookkeeping package. Sign-up is by invitation while it is finished. When any of that changes, this page will say so — and the change will be a deployment, not a rewrite of this paragraph.
It is being extracted from work already running inside SiteLedger rather than restarted from a blank page, and the products it comes from keep their own financial workflows when it lands. Extraction is addition, not subtraction.
Sign-up is by invitation, so this is genuinely just a conversation. Tell us how your supplier statements arrive and where they currently go wrong, and we will tell you honestly whether this will help and when.