Niblin reconciles Shopify, Amazon, wholesale and retail settlements to your general ledger, tracks deductions to resolution, and locks the month with a full audit trail. FP&A reads locked actuals, so the forecast starts from numbers finance has signed off.
See how Niblin models it
Reconciliation
Each channel's expected payouts are compared with what the platform settled and what reached the bank, within tolerances you set.

Deductions
Retailer and marketplace deductions are tied to the invoice or order they came from, coded by reason, and tracked until they are recovered or written off. Our trade spend guide explains how they hit net revenue.
Close and lock
A configurable checklist confirms every source has landed and every tie is within tolerance. Then the controller locks the month.

Connect Shopify, Amazon Seller Central, SPS Commerce, ShipBob and QuickBooks, Xero or Zoho Books.
Confirm a ledger assignment from each source's cost codes to your chart of accounts.
Work the checklist: settlements, bank matches, deductions and GL ties.
Lock the month. Variance, the forecast and the board pack read the locked numbers.
Most brands close with the accounting system plus a set of reconciliation sheets. The hard part is settlements, bank deposits and deductions across many channels, and it repeats every month under deadline pressure from the board pack.
| Spreadsheet model | Niblin | |
|---|---|---|
| Settlements | Spreadsheet modelPayout reports ticked off by hand | NiblinMatched, short, over or pending per settlement |
| Bank deposits | Spreadsheet modelMatched line by line | NiblinMatched to payouts by reference, then amount and date |
| Deductions | Spreadsheet modelA running list per retailer | NiblinTracked to recovery or write-off with reason codes |
| GL tie-out | Spreadsheet modelSpot checks | NiblinTie-out per cost head with tolerances |
| Close status | Spreadsheet modelChecklist in a shared file | NiblinConfigurable checklist, then a lock |
| After the lock | Spreadsheet modelEdits change past numbers | NiblinPrior-period adjustments, earlier versions kept |
No. Your books stay in QuickBooks, Xero or Zoho Books. Niblin sits on top: it reconciles channel settlements and deductions to your general ledger, runs the close checklist and locks the month for FP&A. Your controller still posts journals in the accounting system as before.
Niblin matches each payout to a bank deposit, first by the payout reference in the bank narration, then by payer, amount and date within the channel's settlement window. Anything left is matched by hand, and unmatched items past the window appear on the close checklist.
Yes, with controller approval. Reopening or relocking creates a new lock record, and earlier locks and their adjustments are never deleted. Changes that arrive after a lock appear as prior-period adjustments in the next variance bridge, so the board sees what changed and why.
Variance analysis, the rolling forecast and the board pack all read the locked month. The forecast starts from actuals finance has signed off, and the board pack matches the books. Lines still landing at pack time ship as labelled estimates and true up the following month.
Each deduction is tied to the invoice or order it came from, coded by the channel's own reason codes and tracked as pending, disputed, recovered or written off. Recoveries are booked as their own entries rather than hidden reversals, so every deduction stays visible through the close until it is recovered or written off.
Learn the method
Related solutions
See how Niblin reconciles every channel to your books and locks the month for planning.
See how Niblin models it