Not a suite of half-integrated modules with their own version of the truth. A single ledger every part of the product reads from and writes to.
Start free trialThis is the whole architecture, and it is the reason the numbers agree. Most finance stacks are several systems with a reconciliation process bolted between them — which is a process that exists purely to paper over the fact that there is more than one version of the truth.
Hover a source or an output to trace its path
Invoicing does not keep its own copy of what a customer owes. It reads the receivables control account, which is the same account the balance sheet reads. There is no sync job between them because there is nothing to sync.
Nothing is edited in place. A correction is a new entry that reverses and replaces, so the history of what you believed and when is still there afterwards — which is the only version of an audit trail that survives contact with an auditor.
A total resolves to its entries, an entry to its source document, and a document to the connector and the rule that produced it. Four steps from a number on a board pack to the bank line it came from.
Running a twelve-month profit and loss does not lock the ledger. Feeds keep landing while the report is drawn, and the report states the instant it was taken rather than pretending to be timeless.
Profit, cash, receivables, payables, ageing and runway — read from the ledger as it stands, not assembled from a report you had to run first.
Profit, cash, receivables, payables and runway read straight from the ledger. There is no report to run first, and no export to reconcile against.
Every figure is the ledger as it stands right now — not a snapshot from the last close, and not a number somebody refreshed on Tuesday.
Sales, purchases, banking, payroll and tax all post into the same ledger. That is the only reason the totals on this screen agree with each other.
Figures shown are from a demonstration workspace.
Not a suite of half-integrated modules. A single double-entry ledger that invoicing, banking, VAT and reporting all read from and write to — which is why the numbers agree.
Manage your organisation’s ledger architecture — assets, liabilities, equity, revenue and expenses.
Raise an invoice and receivables and revenue move in the same instant. There is no sync, because there is nothing to sync to.
Feeds land against the bank nominal directly. A matched transaction is a posted entry, not a note to post one later.
Every nominal carries its treatment, so the return is a read of the ledger rather than a rebuild of it.
Profit and loss, balance sheet and trial balance are three views of one set of entries — which is why they cannot disagree.
Figures shown are from a demonstration workspace.
Invoicing that posts rather than queues. Everything on these two screens is one system: the list is what the composer produces, and the balance sheet reads the same number back.
£7,410.39 is the balance on the receivables control account, not a sum of rows on a screen. It is the same figure the balance sheet reads back in folio 06.
Not a list of documents you once sent. A live balance per invoice, so a part-payment reads as a part-payment rather than as an unexplained difference somebody reconciles later.
The moment a due date passes, the invoice changes state and the chase begins. Nobody runs a report on Monday morning to discover who is late.
The nominal and the VAT rate sit on the line itself, so posting is decided as the invoice is written rather than afterwards by somebody else.
Due dates come from the customer's agreed terms. They drive the overdue state and the chase sequence, and nobody types them twice.
Each line carries its nominal and its VAT rate, so the double entry exists by the time you press send. There is no coding queue on the other side of it.
Receivables, revenue and the VAT control account all move in one posting — so your position is current the instant the customer has the invoice.
Figures shown are from a demonstration workspace. Customer names are invented.
Most software calls itself MTD compatible. What that usually means is it can file a number you worked out somewhere else. Here the boxes are queries over posted entries, and every one of them opens into the transactions behind it.
The product knows which quarter is open, when it is due, and which ones you have already filed. You cannot file against the wrong period, and you cannot miss one you did not know about.
Every one of the nine is a query over posted entries. There is no export, no workbook, and no fortnight at quarter end spent tying the return back to the books.
The return sits open until a human approves it. Automation is worth having right up to the point where legal responsibility starts, and not one step past it.
Every figure opens into the transactions behind it, down to the individual sale. If HMRC asks how you arrived at Box 1, the answer is one click, not one afternoon.
Each account carries its VAT code, so mixed-rate and zero-rated lines are ordinary rather than exceptional, and the return builds itself correctly.
Adjust a posted transaction in an open period and the boxes move with it. There is no second place to remember to update.
Figures shown are from a demonstration workspace. WAW Profi is not a tax adviser; the return is yours to review and approve before it is submitted.
Banks, cards, payment processors, payroll and your commerce stack. Open banking feeds land in seconds and backfill up to seven years of history.
Our AI reads your chart of accounts, your past corrections and your supplier patterns. By week two it codes the vast majority of transactions without being asked.
Payments are matched to invoices, part-payments are split, and anything genuinely ambiguous is queued for a human with the evidence already attached.
Statements, board packs and a rolling twenty-four month forecast that updates as the money moves. Export to your warehouse or hand your accountant a login.
Every other product screen on this site is a recreation, built by hand to demonstrate an idea. This one is the real component from the real codebase, running on seeded figures instead of your ledger — try the tabs, the general ledger, the print settings. It behaves like the product because it is the product.
Figures are from a seeded demonstration workspace — £9,200.00 net profit for the period, checkable against the trial balance above. Never a real customer’s books.
Chart account 1000 — Bank Current — is the same ledger account behind the report above. This is the real transactions screen, switching accounts and searching by memo against seeded data instead of a live bank feed.
Ledger transactions posted to each bank account.
Current account
Northbank • Sort: 20-00-00 • ****4417
Ledger Balance
£19.00
12 transactions
| Date | Description | Source | Spent | Received | |
|---|---|---|---|---|---|
| 14 Aug 2026 | Kestrel Group · INV-2214 | invoice | — | — | |
| 11 Aug 2026 | Rent — Q3 | bill | £1,600.00 | — | |
| 7 Aug 2026 | Aurora Cloud Ltd · BILL-3390 | bill | £3,200.00 | — | |
| 3 Aug 2026 | Northbank plc · INV-2201 | invoice | — | £4,820.00 | |
| 1 Aug 2026 | August payroll run | payroll_run | £24,000.00 | — | |
| 28 Jul 2026 | Meridian Partners · INV-2188 | invoice | — | £7,260.00 | |
| 24 Jul 2026 | Professional fees — audit | bill | £1,600.00 | — | |
| 19 Jul 2026 | VAT payment — Q2 | vat_return | £4,180.00 | — | |
| 15 Jul 2026 | Ashgrove Ltd · INV-2176 | invoice | — | £3,940.00 | |
| 9 Jul 2026 | Cost of sales — materials | bill | £5,600.00 | — | |
| 2 Jul 2026 | Kestrel Group · INV-2160 | invoice | — | £6,120.00 | |
| 27 Jun 2026 | June payroll run | payroll_run | £24,000.00 | — |
Two seeded accounts, a GBP current account and a USD operating account — switch between them with the selector. Figures are illustrative, from a demonstration workspace.
Connect your accounts, let WAW Profi backfill the history, and see your first automated close before the trial is out.