Accounting workflow as a standalone system - the ledger, statement and reconciliation work that the operational products currently each do for themselves.
In development. PBS Accounts is not available yet. Nothing is deployed, there is nothing to sign up to and nothing to buy, and we are not going to give you a date we have not committed to. It is here because a portfolio that shows only the finished things is not a portfolio. 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.
The whole operator job — a statement opened, reviewed and approved, and the approved result exported — is driven over a real network socket in the test suite rather than by calling functions, and the phone layout is measured rather than assumed. It stands up in one command on a developer's machine.
It is not deployed and there is no address to send you to. It is not a general ledger and it is not a bookkeeping package. Ten of its sixteen requirement rows are still blocked. When 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.
There is nothing to sign up to, 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.