About Nexus Ledger
Built by an Amazon seller. Books that prove themselves.
Connect your Amazon account once through the official Selling Partner API — read-only, no buyer personal data. Settlements, fees, refunds and reserves become balanced double-entry journal entries; cost of goods is units sold × the unit cost you set per SKU; and the trial balance ties to the cent. The entry on the right assembles itself as you scroll — and lands balanced.
A real Amazon settlement assembles into a balanced double-entry journal entry — revenue, referral and FBA fees, refunds, and cost of goods sold at the unit cost set per SKU — with debits equal to credits at 34,160.00.
FIG 1 — Settlement → Journal entry
Amazon settlement · Mar 1–14
- Double-entry · DR = CR
- Bank reconciliation
- Cost of goods from your SKU unit cost
- One-click settlement approval
- Multi-currency
- 11-year audit retention
- Read-only · no buyer PII
- Profit by SKU
- Bilingual EN + AR
What we believe
Three convictions, encoded — not advertised.
These are not slogans. Each one lives in a database constraint, an RLS policy, or an agent prompt — so the product cannot drift from them on a future pull request.
Integrity
Debits equal credits, or it does not post.
Every journal entry must satisfy SUM(debits) = SUM(credits) within ±0.0001. The check runs as a database constraint trigger, not in application code — so even an AI bug or a stray service-role write is rejected at commit time.
- Immutable once posted — corrections are reversal pairs
- Period close requires the trial balance to tie
Traceability
Every field drills to its pixel.
A trial-balance row drills into its journal entries; each entry into its source settlement or supplier invoice; each extracted document into the OCR/LLM job that produced it — model, prompt version, confidence. If the chain breaks, the field is wrong.
- Source document behind every posted figure
- Append-only audit log, 11-year retention
Boundaries
Default-deny, and the AI is bound too.
The model never holds a service-role key — it reads what a bookkeeper would read, cites entry numbers, and never invents figures. If a workflow would need one seller’s data to leak into another’s view, we do not ship it; we build the safe boundary instead.
- Customer Data is never used to train any model
- Row-level isolation per seller, even within one workspace
How it works
Connect Amazon. The books assemble themselves.
One pipeline runs end to end. A settlement lands and walks itself from a read-only API pull to a closed period — each step a real part of the engine, each output traceable back to the transaction that produced it.
- STEP 01Connectread-only
Link Amazon through the official Selling Partner API
A one-time read-only connection — no buyer personal data, no write access. Finances, settlements, fees, refunds and reserves flow in as structured events, not a screenshot of a report. Your SKUs and their unit costs are yours to enter once, at onboarding.
- STEP 02Decompose
Each settlement splits into its real lines
A payout never lands as one opaque deposit. It is decomposed into revenue, referral and selling fees, FBA fulfilment fees, refunds, and reserve movements — each line mapped to an account in your chart of accounts, ready to post.
- STEP 03ComposeDR = CR
A balanced double-entry journal entry is proposed
The decomposed lines compose into one journal entry where SUM(debits) = SUM(credits) is enforced by a database constraint trigger, not application code. If it cannot balance, it does not propose — there is no half-posted state.
- STEP 04Costunit cost
Cost of goods follows every sale
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 the moment its settlement sale is posted — on by default for a new book, and you can switch it off, and it never touches the bank.
- STEP 05Approve
One click per settlement — cost of goods follows
You approve every settlement and bank match with one click; its cost of goods follows automatically when you post the sale. Manual entries post when you approve them. With two or more users, dual control binds; a solo owner posts as sole approver, with a permanent attestation in the audit log. Posted entries are immutable and corrected only by reversal pairs.
- STEP 06Tie± 0.01 base
The trial balance ties, then the period closes
The trial balance is computed live from the posted entries — never a cached snapshot that can drift — and every row drills back to its journal entry, its source settlement or invoice, and the extraction job that produced it. Period close requires the trial balance to tie within ±0.01 in the client's base currency — a closed period refuses new entries without an explicit adjustment flag and admin role.
Inside the engine
The accounting depth a connector never had.
A settlements connector hands a spreadsheet a number. Nexus runs the books underneath: cost of goods from your SKU unit cost, multi-currency, period close, reversal control, and an append-only audit trail — the parts that make books an auditor will sign.
Cost of goods from your unit cost
You set a unit cost for each SKU at onboarding and can edit it any time. Each settlement sale books cost of goods at units sold × that cost, and the entry posts automatically when you post the sale.
Multi-currency at the right rate
Settlements in CAD or MXN convert to your reporting currency at the journal entry’s posting-date FX rate from a daily feed. Realised gain or loss books to a separate account at settlement; unrealised at period-end.
Period close that must balance
Closing a period requires the trial balance to tie within ±0.01 in your base currency. Once closed, the period refuses new entries unless they carry an explicit adjustment flag and an admin role.
Posted is immutable
A posted journal entry can never be silently mutated. Corrections create a new reversal entry linked to the original; the reversal pair is visibly distinct in the trial balance and explorer.
Append-only audit log
Every state change writes actor, from-state, to-state, a payload diff, timestamp and IP. The log has no UPDATE or DELETE policy — it is evidence, retained 11 years to clear the ISA 230 bar.
Every figure drills to its source
A trial-balance row drills to its journal entries, each entry to its source settlement or supplier invoice, each document to a signed-URL page render and the OCR / LLM job — model, prompt version, confidence.
Who we serve
Two kinds of seller. One workflow engine.
The same balance-or-it-doesn’t-post engine runs underneath both — what differs is the access model.
Owner-operators running their own books.
Owner-operators who keep their own books — Amazon sellers in the US, Canada and Mexico first. Connect Amazon once and settlements, fees, refunds and reserves become balanced entries; you enter each SKU’s unit cost once at onboarding, and cost of goods follows every sale from it. The founder runs their own FBA business on Nexus.
- One workspace, one chart of accounts, one book of record
- Cost of goods from the unit cost you set per SKU
- Profit by SKU you can actually defend
The proof is the product
Not a claim — the actual artifacts.
A trial balance whose debits tie to credits and an approval queue where you approve each settlement with one click — its cost of goods follows automatically when you post the sale. Real fixture numbers, balanced to the cent.
| Account | Debit | Credit |
|---|---|---|
| 1100Amazon clearing | 19,100.00 | — |
| 1330Inventory — FBA | — | 9,360.00 |
| 4000Amazon sales — US | — | 24,800.00 |
| 5000Cost of goods sold | 9,360.00 | — |
| 5210Referral & selling fees | 3,200.00 | — |
| 5220FBA fulfilment fees | 1,800.00 | — |
| 4001Sales returns & refunds | 700.00 | — |
| Totals | 34,160.00 | 34,160.00 |
- 34,160.00JE-018839Awaiting approval
Amazon settlement · Mar 1–14
- 9,360.00JE-018838Posts with the sale
Cost of goods · Mar 1–14
- 5,000.00JE-018837Posted
Referral & FBA fees
One platform vs three tools
Replace the connector, the ledger, and the spreadsheet.
The usual Amazon-seller setup stitches a settlements connector to a separate cloud ledger to an inventory spreadsheet — and the seam between them is where reconciliation breaks and the bilingual and COGS work falls through. Nexus is the one platform underneath all three.
The stitched stack
connector + ledger + spreadsheet
- A settlements connector posts a summary into a ledger it does not own — you reconcile across two systems.
- Cost of goods lives in a spreadsheet beside the books and lags the sale.
- Bilingual Arabic books are bolted on later, if at all — RTL print rarely survives the chain.
- A trial-balance row points at a connector summary, not the underlying settlement line.
- Three subscriptions, three data models, three places a number can drift.
Nexus Ledger, one platform
connect → auditable books
- Each settlement is decomposed and posted as one balanced entry inside the book of record itself.
- Cost of goods posts from the unit cost you set per SKU — automatically, when you post each settlement sale.
- Bilingual EN ↔ AR books from the first entry, not a translation pass.
- Every trial-balance row drills to its journal entry, its source document, and the extraction job.
- One workspace, one chart of accounts, one audit trail — nothing to reconcile against itself.
Bilingual by design
Your books speak Arabic and English.
The same journal entry — accounts, narratives, trial balance and PDF exports — stored and rendered in both languages. Toggle it.
| 1100 | Amazon clearing | 19,100.00 | — |
| 5210 | Referral & selling fees | 3,200.00 | — |
| 5220 | FBA fulfilment fees | 1,800.00 | — |
| 4001 | Sales returns & refunds | 700.00 | — |
| 4000 | Amazon sales — US | — | 24,800.00 |
Same entry, both books. Flip the toggle — the ledger mirrors, right to left.
The market we build for
A North-American Amazon seller has a specific shape.
Sellers on Amazon in the US, Canada and Mexico are paid in settlements that net sales, fees, refunds and reserves into one deposit, often in more than one currency. A settlements connector posts a summary into a ledger it does not own, and cost of goods lives in a spreadsheet beside the books — so the month never quite closes.
We start from the reality that exists: settlements with fees, refunds and reserves; cost of goods from the unit cost each seller sets per SKU; the payout reconciled to the bank; other costs entered with their receipt; period close with adjustment entries; reversal-paired corrections; audit-log-as-evidence. Then we layer AI on top — settlement-to-entry composition and an assistant grounded in the live ledger — to compress the busy work of retyping.
The win condition is not “replace the bookkeeper.” It is: let the seller, or their bookkeeper, spend their time on the business — not retyping settlements. That is the wedge.
Who built it
A seller with accounting depth, tired of three tools.
Nexus Ledger is built by an Amazon seller who runs their own FBA business on it — and who has closed bilingual books, worked through audit-grade reporting, and reconciled settlements, fees and inventory by hand across a settlement connector, a cloud ledger and a spreadsheet. Nexus replaces those three tools with one traceable book of record. We are building the tool we wished we had, and we use it every day.
Nexus Ledger AI is operated by Hayatiq AI Solutions F.Z.E, of Ajman Free Zone, Ajman, United Arab Emirates. Incorporated on 2026-07-30 under trade licence no. 56374, it has ratified and assumed every agreement entered into during formation, with no interruption of service and no change to governing law without your express consent. The full terms are in the Terms of Service.
What we do not do
Lines we hold on purpose.
Crossing any of these would dilute the wedge — so we don’t.
One-click approval
AI proposes. You approve with one click.
Every settlement and bank match waits for your one click; its cost of goods follows automatically when you post the sale — on by default for a new book, and you can switch it off, and it never touches the bank. Manual entries post when you approve them.
No filing
We prepare; you file.
The Service prepares trial balances, reports and audit packs. Filing any return with a tax authority is the customer’s responsibility.
No bundled ERP
Bookkeeping is the core, not a bundle.
HR, Procurement and CRM are real workflows but they are not part of the core accounting tier — they are opt-in, separately scoped add-ons. Sellers who only want bookkeeping pay only for bookkeeping.
Questions sellers ask
The honest answers.
A one-time, read-only connection through Amazon’s official Selling Partner API — financial events, settlements, fees, refunds and reserves. No write access and no buyer personal data. We read what a bookkeeper would read to post your books.
Want to see settlements become a real ledger?
Start a free 30-day pilot on your own settlements — or try the interactive demo first, which runs on a fully anonymised reference dataset.