Reference · v1
The operator's manual for audit-grade books.
Connect once, let every settlement reconcile to a balanced double-entry, and approve each settlement with one click. 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
- One click per settlement
- Cost of goods from your SKU unit cost
- Bank reconciliation
- Multi-currency
- 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; TOTP MFA for admin roles (staged enforcement)
- 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 — only cost of goods follows its sale automatically
- 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). 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 and reserves stream in, read-only, with no buyer personal data.
Read-only · no buyer PII
Compose the entry
Each settlement is assembled into one balanced double-entry against your chart of accounts — sales, referral & fulfilment fees, refunds, reserves — every line traceable back to its source row.
Dr 1100 Cr 4000 / 5210 …
Cost of goods from your SKU unit cost
Cost of goods is units sold × the unit cost you set per SKU — entered at onboarding and editable later. It posts automatically when its settlement is approved and posted; that is on by default for a new book, it can be switched off, and it never touches the bank.
Dr 5000 COGS Cr 1330 Inventory
One click, or prepare → check → approve
You approve each settlement and each bank match with one click. Manual entries run the prepare → check → approve chain, and a DB trigger refuses any entry where debits ≠ credits. With two or more users dual control binds; a solo owner posts as sole approver, and each such post writes a permanent attestation to the audit log.
SUM(debits) = SUM(credits)
Trial balance ties
The trial balance is computed live from the posted entries — never a cached snapshot that can drift. Every row drills from a balance back to its journal entry and its source document — the chain never breaks.
Balanced · Difference 0.00
Close the period
Period close requires the trial balance to balance within 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 linked 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. One click per settlement. Cost of goods follows.
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, and every settlement waits for you to approve it in one click.
| Account | Debit | Credit |
|---|---|---|
| 1000Cash & cash equivalents | 486,210.00 | — |
| 1100Marketplace clearing | 149,430.00 | — |
| 1330Inventory — FBA | 312,480.00 | — |
| 4000Marketplace sales | — | 742,900.00 |
| 5000Cost of goods sold | 281,640.00 | — |
| 5210Referral & selling fees | 63,720.00 | — |
| 2000Accounts payable | — | 34,180.00 |
| 3000Equity & retained earnings | — | 516,400.00 |
| Totals | 1,293,480.00 | 1,293,480.00 |
- 42,318.66JE-2026-000231Awaiting your approval
Amazon US settlement — Mar 1–14
- 58,900.00JE-2026-000227Checked
Manual entry — supplier payment
- 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 cost of goods and the bank 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 settlement ingested twice produces exactly one entry. Here is what actually moves the data from Amazon into balanced books.
Selling Partner API (read-only)
The official Amazon SP-API streams settlements, fees, refunds and reserves for sellers in the US, Canada and Mexico. No CSV exports, no buyer personal data requested.
Settlement → journal entry
Every settlement event is mapped to a line on a balanced entry. Settlements in CAD or MXN convert to the reporting currency at the entry’s posting-date rate from a daily feed.
Fees, refunds and reserves
Referral and fulfilment fees, refunds and reserves each post to their own lines on the settlement entry, so every line traces back to its source row.
Bank reconciliation
Connect the live bank feed (one provider today) or upload a statement (CSV or OFX) from any other bank. Statement lines are matched or explained, and you approve each bank match with one click.
Cost of goods from your SKU unit cost
You set a unit cost for each SKU at onboarding and can edit it later. Cost of goods is units sold × that unit cost, and it posts automatically when its settlement is posted — on by default for a new book, switchable off, and it never touches the bank.
Idempotent & retry-safe
Every settlement carries an idempotency key and every external call uses exponential backoff with jitter, so a re-run, a retry or a duplicate never double-books a single transaction.
Controls, by design
Control is in the schema, not a bolt-on.
Double-entry integrity, an append-only audit log, bilingual books and multi-currency conversion are encoded into the data model from day one. These describe how the product is designed — customers remain responsible for their own filings.
Books in English + Arabic
Every account carries name_en + name_ar; JE narratives, the trial balance and PDF exports render bilingually, and the interface mirrors to right-to-left.
Multi-currency
Settlements in CAD or MXN convert to your reporting currency at the entry’s posting-date rate from a daily feed.
Double-entry, DR = CR
A database trigger refuses any entry where debits do not equal credits. Posted entries are immutable, and corrections are linked reversals.
Period close
Period close requires the trial balance to balance within 0.01, and a closed period refuses new entries unless flagged as an admin adjustment.
Data residency
Customer data is processed in an EU region (Stockholm) under a data-processing agreement, and is never used to train any model.
11-year retention
The append-only audit log is retained for 11 years by default.
Full traceability
A trial-balance row drills to its journal entry and on to its source document. Every state change is written to the append-only audit log.
Approval control
With two or more users dual control binds. A solo owner posts as sole approver, and each such post writes a permanent attestation to the audit log.
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, bank reconciliation and your data.
Read-only access to your Selling Partner financial data — settlements, fees, refunds and reserves. 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.