- Figures come from your recordsThe assistant never generates numbers. It reads the journal, the registers and the documents.
- Versioned rule cardsTax rules are explicit cards with a legal reference and a version. Cards awaiting accountant review are labelled and lower the confidence.
- Read-only by designThe assistant has no access to posting, approval, period locking or filing. Every question and answer is written to the audit trail.
Accounting that prepares the work. You approve it.
Acco reads your invoices, proposes the accounting treatment and VAT, and posts to an immutable ledger only when a person approves.
Immutable ledgerHash-chained audit trailBuilt for Bulgarian VAT
The whole loop, from document to filing-ready records.
Built for sole traders, small companies and the accountants who serve them. Only what works in the product today is listed here.
Document capture
PDF, images and XML invoices. Validated, stored immutably, queued for extraction.
/uploadExtraction and checks
Field-by-field values with confidence. UIC, VAT number and IBAN are verified by rules.
/extractReview queue
Low-confidence fields stand out. Correct, approve or reject, with a full history.
/reviewLedger and periods
Balanced double-entry postings, reversing corrections, locked accounting periods.
/ledgerInvoicing
Sequential numbering, proformas, credit and debit notes, product catalogue with VAT codes.
/invoicesBanking and reconciliation
CSV/XLSX statement import, ranked match suggestions, payments, receivables and payables.
/bankingVAT and SAF-T
Purchase and sales registers, period summary, VIES dataset; SAF-T dataset and validation in beta.
/vatReports
Trial balance, P&L, balance sheet, general ledger, monthly revenue and expenses, cash flow.
/reportsAI Accountant
Answers fixed questions from your records, cites sources, and never changes anything.
/assistantSeven steps. Two of them are yours, and nothing moves past them without you.
Document
Upload a PDF, photo or XML. It is checked and stored immutably.
AutomationExtraction
Fields are read with a confidence score. UIC, VAT number and IBAN are verified by rules.
AutomationReview
You see the document and the fields side by side. Weak fields are flagged.
Your decisionSuggestion
Accounts, expense category and VAT treatment are proposed from rules and memory.
AutomationApproval
Approve, correct or reject. Nothing proceeds without this step.
Your decisionLedger
A balanced entry is posted. It cannot be edited; corrections reverse it.
AutomationExplain
Reports, VAT and the AI Accountant read from the ledger and cite it.
AI explanationCheck what was read. Fix what needs fixing.
The source document sits next to the extracted fields. Deterministic checks run first; the AI suggestion comes with its reasoning; the approval buttons belong to you.
- Rules before probabilityUIC checksum, VAT-number format and IBAN mod-97 are decided by validators, not by a model.
- Confidence you can act onEach field shows a score and its origin. Low-confidence fields and failed checks are highlighted.
- Correct, then approveEdit fields, regenerate the suggestion, approve or reject. Every step lands in the audit trail.
Nothing is posted without a person. Automation prepares, you decide, the assistant explains.
Acco prepares
Reads documents, verifies identifiers, proposes accounts and VAT treatment, builds registers and reports.
In the product: extraction, suggestions, registers
A person approves
Only a user with the right role can approve a document, lock a period or issue an invoice. The AI cannot.
In the product: approve, post, lock, issue
The assistant explains
Answers a fixed set of questions from your records, cites the entries it used, and abstains when the data is not there. It reads only.
In the product: AI Accountant
Know who owes you, what you owe, and what the bank says.
Issued invoices become receivables, approved purchase invoices become payables, and imported bank statements are matched against both. Everything by due date, in EUR.
Sequential numbering, proformas, credit and debit notes; open items and ageing by due date.
Posted purchase invoices appear as open payables, grouped by due-date bucket.
CSV/XLSX import with duplicate detection; ranked match suggestions you confirm.
Registers and reports computed from the ledger, not typed into a form.
Acco follows Bulgarian accounting and VAT rules out of the box: UIC and VAT-number checks, VAT treatments from 20% standard to intra-EU acquisitions, purchase and sales registers per period, Cyrillic invoice PDFs and SAF-T preparation for the NRA. Every figure traces to a journal line and the document behind it.
- VAT registers and period summaryPurchase and sales registers, output and input VAT, the amount payable or refundable for the month. VIES dataset for intra-EU supplies.
- Management reportsTrial balance, P&L, balance sheet, general ledger, revenue and expenses by month, cash flow. CSV export for the monthly reports.
- SAF-T preparation betaDataset and validation today. XML export and binding to the official NRA schema are planned.
Ask why. Get an answer with sources. Nothing changes.
A fixed set of questions about your VAT, receivables, payables and results. Each answer is built from the ledger and the registers, cites the entries it used, and shows a confidence level. When the data is not there, it says so.
Built so you can trust the numbers and show how you got them.
Each company is separated at the database level. A request outside its context is refused, not just hidden.
Approve, lock and issue are tied to roles. The server re-checks the action; the interface only reflects it.
A posted entry is never edited. A mistake is corrected with a new, reversing entry, so the history stays visible.
Lock a period to close it. Posting into a locked period is refused.
Source files are stored with an immutable version history, so every posting can be traced back to the original document.
What is available today, and what is coming.
Only capabilities that exist in the product are listed as available. Anything still being validated is marked beta.
Available
- Document capture and extractionPDF with a text layer and XML invoices, parsed nativelyLive
- OCR for photos and scanned PDFsEU document-AI provider (Azure Document Intelligence, EU region enforced); enabled per deploymentBeta
- Review queue with corrections and approvalLive
- Immutable ledger, journal, accounting periodsLive
- Invoicing: numbering, proformas, credit and debit notesPDF generated on issueLive
- Bank import (CSV/XLSX), matching, paymentsLive
- VAT registers, period summary, VIES datasetVAT-number format check; live VIES lookup configurable per deploymentLive
- Reports: trial balance, P&L, balance sheet, GL, monthly, cash flowCSV export for the monthly reportsLive
- AI Accountant with citationsLive
- SAF-T dataset and validationXML export is enabled per deployment; binding to the official NRA schema is plannedBeta
Planned
- Extraction accuracy validation on real scanned invoicesRunbook and scoring tool exist; the labelled sample set is being collectedPlanned
- Invoice PDF download and email sending from the appThe PDF is generated and stored; sending from the interface is not wired yetPlanned
- VAT return export in NRA formatDEKLAR / POKUPKI / PRODAGBI files for manual filingPlanned
- Official SAF-T XSD bindingExport today validates against the internal dataset schemaPlanned
- Two-factor authentication (TOTP)Enrolment from profile settingsPlanned
Frequently asked
Posting, VAT and AI
Does Acco post anything automatically?
No. Document postings are approved by a person in the review screen. Issuing an invoice or confirming a bank match posts the related entry when you take that action. Nothing reaches the ledger on its own.
How is VAT handled?
The VAT treatment is proposed per document from rules: standard 20%, reduced 9%, zero, intra-EU acquisitions and import. Purchase and sales registers and the period summary are computed from posted entries.
Does Acco submit anything to the NRA?
No. Registers, the period summary and the SAF-T dataset are prepared for you; filing remains your action. An export in the NRA return file format is planned.
What does the AI do, and what can it not do?
It reads documents, proposes accounts, categories and VAT treatment, and explains figures with citations. It cannot post, approve, lock periods or file. Those actions belong to people and are recorded in the audit trail.
What is currently in beta?
OCR for photos and scans (an EU document-AI provider, enabled per deployment, accuracy validation on real invoices in progress) and SAF-T (dataset and validation; XML export enabled per deployment, official schema binding planned).
Records and data
Can a posted entry be edited?
No. The ledger is append-only. A mistake is corrected with a reversing entry, so what happened stays visible.
How are my data protected?
Each company is isolated at the database level, the ledger is append-only, and every state-changing action is written to a hash-chained audit trail. When OCR for scans is enabled, the document-AI provider is restricted to EU regions by configuration.
What happens to my data at launch?
It stays in your company. Early-access companies keep their ledger, documents and history when public plans are introduced.
Start with one invoice.
Create an account, upload a document and see the suggested posting. The decision, as always, is yours.
Controlled access while we validate extraction and VAT on real documents.
EUR functional currency. Human approval on document postings. Hash-chained audit trail.