Vista Recon · settlement reconciliation for NetSuite
Settlement file lands
Marketplace, processor, or wholesale detail arrives with the net deposit.
Controlled mappings
Exception hold
Unresolved differences stop for finance review.
Human approval
Finance reviews the proposed journal and remains the posting authority.
NetSuite posts
Only after approval.
Source detail, mappings, exceptions, and approval stay visible as one audit trail.
Vista ReconSettlement reconciliation for NetSuite
Vista Recon turns marketplace, processor, and wholesale settlement files into controlled NetSuite journal entries. Unresolved differences stop for review, a human approves the result, and only then does NetSuite post.
We agree on a secure transfer path before any settlement data changes hands. A generic example is always available.
The proof is the tie-out.
Source settlement lines, their controlled account mappings, the proposed journal entry, and the net deposit, visible together. The result must foot before it can move to human approval and posting.
Every line in the entry traces back to a line in the file: revenue net of fees, refunds, taxes, reserves, and adjustments, each in the account finance approved.
Vista Recon · Amazon settlement
Reconciled81,342 line items · 38 Amazon codes → 10 GL accounts
| GL account | Amount |
|---|---|
| 4000Marketplace revenue | 482,644.27 |
| 2250Sales tax collected | 25,012.14 |
| 2251Facilitator tax remitted | −25,010.37 |
| 5050Marketplace commission | −81,831.10 |
| 5060FBA fulfillment & storage | −86,481.08 |
| 5070Advertising & deal fees | −14,016.30 |
| 4500Promotions & coupons | −4,086.41 |
| 1450FBA reimbursements | 5,556.52 |
| 5080Returns & return shipping | −1,071.75 |
| 6900Adjustments | 168.58 |
| Net deposit → bankties to the penny | 300,884.50 |
AI maps your codes to your accounts once. You confirm it. Every settlement after is assigned deterministically, before it imports: the same answer every time.
Real Amazon settlement, anonymized · every channel ships its own format, mapped once
The deposit never tells the whole story.
Commerce systems record transactions and integration platforms move data, but neither proves the net cash belongs in the right accounts. Unexplained fees, reserves, and adjustments quietly become unrecovered margin: every channel, every settlement, every month.
01
The deposit hides the accounting detail
A single bank deposit can net together sales, fees, refunds, taxes, reserves, and adjustments. The cash amount alone does not explain how the settlement belongs in the ledger.
02
Every source speaks a different language
Marketplaces, processors, and wholesale partners use different files and labels. Their vocabulary still has to be mapped to your NetSuite accounts and transaction records.
03
Exceptions make shortcuts unsafe
Missing records, changed labels, and timing differences need a finance decision. A workflow that guesses or force-posts only moves the reconciliation problem into the general ledger.
From settlement file to approved journal entry.
Vista Recon reads the settlement file, applies controlled mappings, and prepares the journal entry finance expects. If the file does not tie out or contains an unresolved line, the workflow stops. A human reviews the evidence and approves before NetSuite posts.
01
Read the settlement file
Vista Recon ingests the source file and preserves the settlement detail finance needs to trace the deposit.
02
Apply controlled mappings
Known source labels follow finance-approved rules into the appropriate NetSuite accounts and reconciliation categories.
03
Build the journal entry
The reconciled lines become a proposed NetSuite journal entry with the source, mapping, and tie-out visible for review.
04
Stop, approve, then post
Unresolved differences are held back. A human reviews the result and remains the posting authority before NetSuite changes.
The first walkthrough, on your data.
The walkthrough follows one representative settlement from source file to proposed NetSuite posting path. We identify the mappings, exceptions, and approval owners the workflow would require, then decide whether Vista Recon is a responsible fit for the close process.
Bring
One representative settlement file
Bring the shape of the recurring problem to the session. If your own data will improve the walkthrough, we will agree on a secure transfer path before any file changes hands. Otherwise, we use a generic example.
Trace
The source-to-ledger path
We trace how the file becomes accounting today, where exceptions appear, and who owns the approval before anything posts.
Decide
Whether Vista Recon fits
We identify the required mappings, controls, and open questions, then decide whether there is a responsible next step to scope.
Bring one settlement file. Leave with a controlled path.
Trace the file, the NetSuite entry, the exceptions, and the human approval required before posting, on your own data if you send a file ahead.