Straight answers.

No — and you never will. GOaccounting works from the PDF statements your bank already emails you. No screen-scraping, no shared credentials, no live access to your account. Statements are parsed read-only and balanced against their own totals.

FNB, Standard Bank and Capitec statements are parsed today, with more added as founding customers need them. If your bank isn't on the list, one redacted sample statement is usually enough for us to build the reader.

No. Bank statements are parsed by exact, bank-specific readers — a hard rule enforced inside the engine. AI is used only where it's the right tool (reading supplier invoices), and everything it extracts is validated and reviewable.

It asks you — once. Uncertain items land in a short review queue you can clear from your phone. Every answer becomes a permanent rule, so the same question is never asked twice.

Yes — backlogs are what the engine eats for breakfast. Forward your old statements and invoices and the same pipeline processes them, months at a time. Catch-up is part of founding-customer onboarding.

Yes. VAT is captured per line on every invoice and computed through proper VAT control accounts, so your VAT201 numbers come from the ledger, not a spreadsheet.

Your data lives in an isolated tenant, encrypted in transit and at rest, and is never sold or shared. Suppliers' and customers' personal information is minimised and protected — see the Security page for the full posture.

Absolutely — and they'll like what they find: a clean trial balance, journals with an audit trail to source documents, and a month that's actually closed. Many of our design conversations are with accountants who want their clients on GOaccounting.

You're one of the first ten businesses on the platform. You get hands-on onboarding from the founder, a permanent price lock, a direct line for support, and real influence on the roadmap. In exchange we get your honest feedback.