Reference · v1
The operator's manual for audit-grade books.
Connect once, let every settlement reconcile to a balanced double-entry, and approve before anything posts. These are the guides, references, and trust pages for running Nexus Ledger end to end.
Can't find what you need? Send us a question and we'll respond within one to two business days.
- Sections
- 3
- Guides
- 10
- Reply (business days)
- 1–2
- Database-enforced double-entry
- Posted entries are immutable
- Every entry human-approved
- Bilingual books · EN ↔ AR
- Append-only audit trail
- Every figure traces to a document
How the manual is organised
Three pillars, one chain of custody.
Every guide ladders up to the same promise: a figure you can trust because you can trace it from a trial-balance row back to the source document.
Connect
Get set up
Create an account, complete the two-step wizard, import your chart of accounts, and open your first set of books.
- Magic-link sign-in with mandatory MFA for admins
- Chart-of-accounts import with type and nature mapping
Compute
Run the daily flow
Upload, review, approve, post. Each settlement becomes a balanced journal entry routed through your approval chain.
- Prepare, check, approve — nothing auto-posts
- Drill from any trial-balance row to its source document
Control
Stay compliant
Bilingual books, long-horizon retention, and an append-only audit trail behind every state transition — wired in, not bolted on.
- Row-level isolation on every table
- Append-only audit log with multi-year retention
How the platform runs
Connect Amazon once. The books keep themselves — one platform, end to end.
A seller authorises Amazon (read-only) and supplier invoices flow in. From there a single pipeline carries every settlement all the way to a closed period — no separate connector, no separate ledger, no spreadsheet in the middle. Each stage below is a real movement the product performs.
Connect & ingest
Authorise the Selling Partner API once. Settlements, fees, refunds, reserves and FBA inventory stream in; supplier invoices and vouchers are OCR-read (Mistral OCR 3) and classified per page.
Read-only · no buyer PII
Compose the entry
Each settlement is assembled into one balanced double-entry against an IFRS chart of accounts — sales, referral & fulfilment fees, refunds, reserves — every line traceable back to its source row.
Dr 1100 Cr 4000 / 5210 …
Relieve COGS at WAC
Units shipped are relieved from a perpetual inventory subledger at weighted-average cost, so cost of goods sold and profit-by-SKU are exact — not a period-end estimate.
Dr 5000 COGS Cr 1330 Inventory
Apply VAT per line
Output and input VAT are computed per line at the marketplace rate — KSA 15% / UAE 5% — and captured ZATCA-aware (UUID, QR payload, hash) ready for the VAT register.
KSA 15% · UAE 5% · ZATCA-aware
Prepare → check → approve
Nothing auto-posts. Every draft runs the firm approval chain — Senior Accountant prepares, Finance Manager checks, CEO/Admin approves — and a DB trigger refuses any entry where debits ≠ credits.
SUM(debits) = SUM(credits)
Trial balance ties
Posted entries refresh a materialised trial balance. Every row drills from a balance back to its journal entry, to its source document, to the pixel on the PDF — the chain never breaks.
Balanced · Difference 0.00
Close the period
Period close requires the TB to balance within SAR 0.01. Once closed, the period refuses new entries unless flagged as an admin adjustment — books are frozen and dated.
Period close · ±0.01 tolerance
Immutable & retained
Posted entries are immutable — corrections are reversal entries, never edits. The audit log is append-only with 11-year retention, so the books stay defensible for years.
Append-only · 11-year retention
The proof is the product
A trial balance that ties. VAT that nets. Nothing posts itself.
These are the artifacts the platform hands you — rendered from illustrative figures, balanced exactly the way a real period is. Debits equal credits to the cent, the GCC VAT summary nets, and every entry waits for a human to approve it.
| Account | Debit | Credit |
|---|---|---|
| 1000Cash & cash equivalents | 486,210.00 | — |
| 1100Marketplace clearing | 149,430.00 | — |
| 1330Inventory — FBA (WAC) | 312,480.00 | — |
| 4000Marketplace sales | — | 742,900.00 |
| 5000Cost of goods sold (WAC) | 281,640.00 | — |
| 5210Referral & selling fees | 63,720.00 | — |
| 2200VAT payable | — | 34,180.00 |
| 3000Equity & retained earnings | — | 516,400.00 |
| Totals | 1,293,480.00 | 1,293,480.00 |
| Line | Base | Rate | VAT |
|---|---|---|---|
| Output VAT — KSA sales | 227,866.67 | 15% | 34,180.00 |
| Output VAT — UAE sales | 96,400.00 | 5% | 4,820.00 |
| Input VAT — supplier invoices | 40,266.67 | 15% | 6,040.00 |
| Net VAT payable | 32,960.00 | ||
- 42,318.66JE-2026-000231Awaiting your approval
Amazon US settlement — Mar 1–14
- 58,900.00JE-2026-000227Checked
Supplier PO & stock receipt — Shenzhen
- 7,815.30JE-2026-000226Posted
Amazon CA settlement — net deposit
Why one platform
One platform vs. the stitched stack.
The usual setup is a settlements connector, a separate general ledger, and spreadsheets to bridge the gaps — three tools, three reconciliations, and a manual seam where COGS, VAT and inventory fall through. Nexus Ledger is the connector and the accounting in one.
Under the hood
One connector, one ledger, one source of truth.
The integration is read-only and idempotent by construction: the same file or settlement ingested twice produces exactly one entry. Here is what actually moves the data from Amazon and your invoices into balanced books.
Selling Partner API (read-only)
The official Amazon SP-API streams settlements, fees, refunds, reserves and FBA inventory across US / CA / MX and the .sa / .ae marketplaces. No CSV exports, no buyer personal data requested.
Settlement → journal entry
Every settlement event is mapped to a line on a balanced entry. Multi-currency deposits convert to the base currency at the posting-date FX rate, with realised FX gain/loss to its own account.
Invoice & voucher extraction
Supplier invoices and bilingual voucher batches are OCR-read, classified per page, then field-extracted under forced tool-use against a strict schema — every field returns a confidence score.
Confidence-gated extraction
Fields below 0.85 are held for human review; anything below 0.6 is re-tried on a stronger model before it can queue. The system never acts on a low-confidence field as if it were verified.
Perpetual WAC inventory
Inbound stock receipts (with freight and duty capitalised) feed a weighted-average-cost subledger that ties to the inventory control account; issues relieve COGS at that running average.
Idempotent & retry-safe
Every file carries a content-hash idempotency key and every external call uses exponential backoff with jitter, so a re-run, a retry or a duplicate upload never double-books a single transaction.
Saudi compliance, by design
GCC compliance is in the schema, not a bolt-on.
Bilingual books, ZATCA-aware invoice capture, GOSI-aware salary templating and a SOCPA-endorsed IFRS chart of accounts are encoded into the data model and the extraction prompts from day one. These describe how the product is designed and aligned — customers remain responsible for their own filings.
Books in Arabic + English
Every account carries name_en + name_ar; JE narratives, the trial balance and PDF exports render bilingually. The one thing no settlement connector in the seller space ships.
ZATCA Phase 2 inputs
Invoice capture records the UUID, QR payload and hash, and flags missing-QR invoices. Phase 1 consumes e-invoice inputs — it does not issue clearance.
VAT 15% (KSA) / 5% (UAE)
A tax-codes table drives per-line VAT at the marketplace rate; output, input and net feed a VAT register. Foreign-currency lines convert to the base currency at the posting-date FX rate.
GOSI salary split
Salary JE templates auto-split contributions per nationality — the 21.5% Saudi rate on the capped base vs the 2% expat employer-only line — so payroll posts correctly without manual maths.
SOCPA-endorsed IFRS COA
A default IFRS-aligned chart of accounts, customisable per client via the import wizard, so the books map to the standard Saudi statutory framework out of the box.
PDPL data residency
Personal data is stored in an EU region with GDPR adequacy under a DPA with SCC-equivalent terms; an in-KSA self-hosted path is available for tenants that require data to stay in-Kingdom.
≥ 10-year retention
Documents and the append-only audit log are kept 11 years by default (ISA 230 + SOCPA), with hard-delete only via an admin RPC that itself writes an audit entry.
Full traceability
A trial-balance row drills to its journal entry, to its source document, to a signed-URL page render and the extraction job that produced it — model name, prompt version, token counts, confidence scores.
Browse the guides
Pick a collection.
Each tab swaps in place — no wall of identical cards. Open any guide to read the full walkthrough.
- 01Create an account and start your pilotSign up via magic link, complete the two-step onboarding wizard, import your chart of accounts, and create your first client workspace.
- 02What Nexus Ledger is and who it servesThe product thesis, the guiding beliefs, and what we deliberately do not do.
- 03How we protect your dataDatabase-enforced double-entry, posted-entry immutability, row-level isolation on every table, and an append-only audit log.
Questions, answered
What sellers ask before they connect.
Short, specific answers grounded in how the product actually works — connection, control, compliance and your data.
Read-only access to your Selling Partner financial data — settlements, fees, refunds, reserves and FBA inventory. We never request buyer personal data, and we never have authority to change anything in your Amazon account.
Ready when you are
Open your first set of books.
Start a 30-day pilot, import your chart of accounts, and post your first approved entry — the guides above walk you through every step.