Back office and reports

Sending the books to Xero or Sage

Aura has always produced proper journals — every sale, refund and cash-up double-entered, with VAT201 and a trial balance. What it could not do was put them in your accounting system, so someone downloaded a file once a month and imported it by hand. That step is where the mistakes were.

Settings → Accounting connects it. Choose Xero or Sage, paste the business reference your accountant gives you, and set push from — the earliest date to send. Journals before that date are never pushed, so switching this on in August does not drop February into a closed period.

Then it pushes: every journal, oldest first, with the accounting system's own reference recorded against each one so a disagreement can be traced from a line in Aura to a line in your ledger.

It cannot post the same thing twice. That matters more than it sounds — a duplicated journal duplicates revenue, and the person who finds it is usually your auditor, months later. Aura claims each entry before it sends it, and every attempt carries the same reference, so a timeout, a retry or an impatient second tap is recognised by Xero or Sage as the document it already has.

If something is refused — a closed period, an account that does not exist — it says so against that entry, with the reason, and stops trying. Retrying would send the same thing for the same answer.

Pausing. Set it to "not connected" or switch it off during an audit; the settings are remembered and nothing is sent until you turn it back on.

One thing to tell your accountant: the tokens live on the server's configuration, not in Aura's database. Nobody can read them back out through the app, which is deliberate — they are the keys to your books.

More in Back office and reports

All collections →
Still stuck? Mail support@aurapos.co.za or use the support page — include your venue name and what you were doing.