Software summer offer: free consulting sessions.
An ACMR product

The books, kept where the work already happens.

Irish invoicing, VAT, payroll and statutory accounts, running inside the dashboard your team is already in.

A recording of LogOS in use: asking what VAT is owed for the period, settling an overdue invoice and watching the journal post, then clearing an unmatched line on the bank feed. A demo company, on sample figures
92

gaps an accountant found, all closed

74

automated checks on every build

6 years

of documents kept against a return

Nothing posts unless it balances.

Double entry is enforced in the ledger itself, not in the forms on top of it. Money is held as whole cents. A posting that does not balance is rejected, so the trial balance and the balance sheet agree every time you open them.

Your chart of accounts

Starts on a seeded Irish chart. Edit it to match how you already code things. An account in use cannot be switched off underneath you.

Bring the old books in

Opening balances load from CSV or keyed entry. An unbalanced trial balance is refused rather than plugged.

Periods close and stay closed

Post into a closed period and it comes back refused. Year end rolls retained earnings, and the balance sheet foots to net assets.

Every entry has a name on it

An audit log tied to the signed-in user, maker-checker approval where it matters, and reversals that leave the original in place.

Sales · the journal that invoice posted, both sides in balance

The old system’s books come with you.

Most businesses arrive with years in QuickBooks, Sage or Xero, a payroll bureau, and a spreadsheet nobody wants to open. Those become one ledger, and it has to balance before anything posts.

QuickBooksSales and purchase ledgers
SageNominal ledger and year end
XeroBank feed and reconciliation
ExcelThe workbook holding it together
A payroll bureauPayslips by email, once a month
Trial balance in balance7 modules · one ledger · from 1 Jan

Opening balances

Loaded from CSV or keyed in, then proved. An unbalanced trial balance is refused rather than plugged, so you start on a set of books that foots.

Customers, suppliers and staff

The debtor and creditor ledgers, the chart of accounts and the employee master arrive as records you can work with, not as a PDF export.

The paperwork

Invoices, bills and payslips attach to the transactions they belong to and are kept for six years, so an audit is not a search of somebody’s inbox.

We do the move with you rather than handing you an importer and wishing you luck.

Sales, purchases and the bank, on one ledger.

An invoice, a supplier bill and a bank line are three views of one entry.

Getting paid

Sales and debtors

Invoices carry sequential numbering, both VAT numbers and the rate breakdown. Quotes convert, recurring invoices run, part payments allocate. Aged debtors, statements, and statutory late payment interest at the ECB rate plus eight points. Invoices go out as a branded PDF, or export as Peppol BIS Billing UBL XML. Sending over the Peppol network needs an access point, and none is connected yet.

Paying out

Purchases and creditors

Bills arrive by upload, or by mailbox once a mailbox is connected, and land as a draft for you to check. Approving posts a balanced purchase journal, and that is when the VAT input is recognised. Payment runs produce a SEPA pain.001 file and remittance advice. Purchase orders, goods receipts and three-way match are there for the trades.

Squaring the bank

Banking and reconciliation

Current, savings, credit card and cash, each with its own GL code. Statements import from CSV or CAMT and tie out to the closing balance. When a line does not match, it tells you why. One click posts the adjusting journal, and the rule is remembered next time.

Purchases · a scanned bill, still a draft until you approve it
Bank · every account on its own GL code, one exception left to clear

The Irish year, in the order it arrives.

Payroll every run, the VAT3 every two months, the RTD and the annual set at year end. Each one is built from posted transactions, and the workings are on screen. The rates and bands loaded today are 2026 sample figures, which the section below sets out in full.

Every pay run

PAYE, PRSI and USC

Worked out cumulatively, and every payslip reconciles gross to net. Classes A, S and J, including director Class S. Payslips and the Employment Detail Summary, BIK, pension, AVC and auto-enrolment contributions. The payroll journal posts with the run.

Every two months

The VAT3, and the RTD once a year

T1 minus T2 carries to T3 when you owe it and to T4 when you are due it, on effective dated rates of 23, 13.5, 9 and zero percent. Reverse charge and postponed accounting post both sides, so the net effect is nil. The RTD fills every box, split by category, geography and rate. The cash-receipts basis sits alongside the invoice basis.

EU and subcontractors

VIES, EC sales and RCT

EU VAT numbers validated, the EC sales list built from the same postings, RCT withholding at 0, 20 and 35 percent.

Year end

CT1, iXBRL and the B1

Add-backs, loss relief, the 12.5 and 25 percent split, close-company surcharge and R&D credit, all posting a balanced journal. Capital allowances run straight line at 12.5 percent over eight years, with the motor CO2 limits applied. Accounts are tagged for FRS 102 (IE) or IFRS and checked by a structural validator. They are not yet validated against the official taxonomy.

Sole traders

Form 11

The same books produce a Form 11 at 20 and 40 percent with credits, Class S PRSI, USC and preliminary tax.

Every pay run · gross to net, and the journal it posts
Every two months · the VAT3, agreed back to VAT control
Year end · the corporation tax computation, line by line
Status

What is finished, and what is not.

Four things in LogOS reach outside the app, and each runs against a test adapter until it is connected to a live provider. The rates it calculates on are the fifth. Here is where all five stand today. LogOS produces the returns. It is not tax advice, and it does not replace your accountant signing them off.

Statutory filing

Test adapter

The VAT3, RTD, payroll submission, CT1, DWT, B1 and iXBRL are built, validated and return a receipt from a test ROS or CRO adapter. Nothing has been submitted to Revenue. Live submission and the official taxonomy package are the next piece of work.

Card payments

Test adapter

The pay link, settlement and the ledger side of a payment are built end to end. It runs on a test provider until a payment account is keyed in.

Bank feeds

No provider yet

Consent handling and server-side tokens are in place, but no open-banking provider is chosen. Today statements come in by CSV or CAMT import and tie out to the closing balance.

Reading bills

Test adapter

Upload, extract, edit and approve is built. The extractor runs on a test adapter until it is keyed, and the draft is always yours to check before anything posts.

Tax and payroll bands

2026 sample figures

The calculation engines are built and tested against worked examples. The bands loaded today are 2026 sample figures. They are replaced with the official tables before anyone runs a live year.

Start at the number, end at the invoice.

Every figure traces back to the transaction that made it. Click a figure on the dashboard and keep clicking until you reach the invoice. No export needed.

The figure on the dashboard

Debtor days, creditor days, margin, cash, budget variance and cost-centre splits, next to a deadline calendar.

The statement behind it

Trial balance, P&L, balance sheet footing to net assets and cash flow, with the notes and abridged accounts. Prior year sits in the next column.

The month it happened in

Date-range P&L with drill-down, so any figure comes apart by period on screen.

The document itself

The invoice, bill, payslip or journal that caused it, with six years of attachments. Save the view as a report definition, or export the lot to CSV or Excel.

Reports · the sales figure, opened onto the invoices behind it

The parts an accountant asks about first.

LogOS gets handed to a bookkeeper, an accountant and an owner at the same time. Access, the close routine and client separation are built around those three people.

Sign in and access

Hashed passwords, httpOnly sessions, roles and permissions, expiring invite and reset tokens. Two-factor by TOTP with single-use backup codes, and no credential is ever rendered to the browser.

One switcher, every client

A practice portfolio with a multi-client switcher. One database schema per client. Cross-client access is tested, not assumed.

The month-end list

A close checklist that ends in the period lock, accountant queries on the entries in question, batch approve and batch pay.

GDPR export and erase

Erase redacts the personal fields and leaves the trial balance intact, so the books still foot after a request.

Sterling and dollar postings

EUR, GBP and USD postings settle to a euro base with the realised FX gain or loss recognised. Picking a currency on the invoice form is not built yet, so foreign currency comes in by API or journal.

A read-only assistant

Scoped to one client, read-only, with an audit trail of everything it was asked. It answers from the books. It cannot post to them. Enabled per client.

Audit mode · read-only, financial records only

It answers from the books. It cannot change them.

Hand an accountant an audit session and it is scoped to one client, restricted to the financial records, and cannot reach settings or connections. Every question it was asked is on the audit trail.

The audit

A practising accountant listed 92 gaps in LogOS. We closed all 92.

They went through the app and wrote the list. We closed it in twelve waves. The closures are ours, and they have not been re-audited by them.

74 automated checks

A harness reruns a full set of books end to end and checks every figure comes out the same, to the cent. They check the figures, from a posted invoice through to the VAT3 and the balance sheet.

What we have not tested

Nobody has clicked through every screen in a browser since the banking work went in. The numbers are tested. The screens are not.

Come and see it running.

A live instance with a demo company on it. Raise an invoice, run payroll, build the VAT3, then click a figure back to the document it came from. If it does not fit how you work, we will say so.

A walkthrough on a live instance

Invoices, a payroll run, a VAT3 and the drill-down, on a demo company rather than slides.

The written guide

A 31-page guide covering how every area works, and a 12-page overview if you want the short version.

A straight answer on your setup

Tell us what you run on now: a bureau, Sage, spreadsheets, or nothing. We will say what moving would actually involve.