Walk through Codesloci — UAE E-Invoicing
14 of 20 screens are live in the demo. Everything else is visible but marked, with a reason — nothing is a dead link.
How to sign in
The demo has its own login because that is part of the product. These accounts are fictional, the passwords are deliberately fake, and each one sees a different slice of the platform — so it is worth signing in as more than one.
| Role | Password | What they can see | |
|---|---|---|---|
| owner | [email protected] | Codesloci@Demo | Everything, including the plan, users and lock periods |
| admin | [email protected] | Codesloci@Demo | Everything operational, plus users — not the plan or billing |
| accountant | [email protected] | Codesloci@Demo | Sales, purchases, accounting and the VAT return — no users or plan |
| bookkeeper | [email protected] | Codesloci@Demo | Day-to-day entry: invoices, bills and payments. Cannot post journals |
| viewer | [email protected] | Codesloci@Demo | Read-only across the platform. Nothing can be created or edited |
What to try first
- Open the invoice editor and change a line’s tax category — watch the VAT recompute and round
- Find the invoice flagged as a rounding edge case: part-paid, foreign currency, off by a fils
- Open E-invoicing → Outbox and filter to Rejected, then read why the provider refused one
- Run E-invoicing → VAT return and drill from a box into the documents that sum to it
- Switch the language to العربية in the header — the whole shell flips to right-to-left
- Click a greyed menu item, such as Purchases → Bills, to see what it does in the real platform
Every screen, and whether it is in the demo
Grouped the way the real platform groups them. A screen marked not in the demo is still visible in the demo's navigation — clicking it explains why and offers a walkthrough, rather than doing nothing.
Get started
The onboarding checklist the platform opens on. Two of its six steps need a provider contract or a ledger, and say so.
Inbox
Where uploaded and emailed documents land before becoming bills. Shows the real empty state and explains the upload pipeline.
Profit and loss
KPIs and an eighteen-month series, every figure computed from the seeded documents rather than stored.
Cashflow
The second dashboard tab, framed as money in and out.
Reports
The reports index. Three render with data; the rest are listed honestly with what each one needs.
Customers
Fourteen buyers with format-valid TRNs, and whether each is reachable on the Peppol network.
Invoices
46 documents with search, status and place-of-supply filters, sorting and pagination.
Invoice editor
The signature screen. Full-bleed and outside the shell, as the platform routes it. Coded tax categories, and rounding shown as a visible step.
Quotes, credit notes, cash invoices, delivery notes
The rest of the sales document types the platform issues.
Each reads the customer ledger, which the static demo does not model — it shows documents, not journal entries.Suppliers, bills and supplier payments
The purchase side: suppliers, bills, payments, debit notes and purchase orders.
The purchase ledger is not modelled in the demo. The screens exist in the real platform.Bank accounts, journals and chart of accounts
The general ledger: bank feeds, manual journals, the chart of accounts and fixed assets.
Bank reconciliation needs a bank feed, and the rest need the ledger — neither of which a browser-only mock can honestly provide.Outbox
What has been transmitted, what the provider rejected, and the penalty exposure of leaving it. A nav item the reference product does not have.
VAT return
Return boxes computed from delivered documents, with per-emirate apportionment. Every box drills down to the documents that sum to it.
Three-way reconciliation
The sales ledger, the traffic the provider accepted, and the computed return — with every variance itemised and given a reason.
Provider settings
Credentials and endpoint for your Accredited Service Provider.
Accreditation is a contract with a provider, not a feature. The demo transmits through a sandbox adapter, exactly as the real platform does in development.Payroll, pay runs and employees
Payroll runs, employee records, claims and beneficiaries.
Payroll needs statutory tables and a pay-run engine. Simulating a payslip would misrepresent it rather than demonstrate it.Items
Coded UN/ECE unit codes and UNCL5305 tax categories, derived from the invoice lines that actually use them.
Warehouses, movements and adjustments
Multi-warehouse stock positions, movement history and adjustments.
Adjustments post to the ledger, and the demo seeds no warehouse data. The screens exist in the real platform.Help
How much of the navigation is live, and where to go for the rest — counted from the menu itself.
Settings
Tax categories that genuinely change what the editor offers, plus a switch that makes every screen fail so the error states are demonstrable.
Good to know before you open it
- It runs entirely in your browser. There is no server, and nothing you type leaves the page.
- Your edits persist across a refresh, and Reset data in the demo bar puts the sample data back.
- A guided tour starts on your first visit and can be replayed from the demo bar.
- English and Arabic, with a right-to-left layout — switch language in the demo bar.
- Dark by default, matching the real platform. There is a light/dark switch in the demo bar.
- It works on a phone as well as a desktop.