Settlement Pattern Library
Fee and adjustment isolation in settlement reconciliation
Use this pattern when fees and adjustments are being swallowed by net deposits or broad clearing entries.
The method
How do you isolate fees and adjustments before posting?
Fee and adjustment isolation separates the deductions inside a settlement before they hit the ledger. Instead of posting a net deposit and explaining it later, finance classifies processor fees, commissions, refunds, chargebacks, shipping adjustments, tax corrections, and marketplace credits against the source activity.
Key takeaways
- Fees and adjustments should be visible before a payout posts.
- Source categories need consistent NetSuite treatment and ownership.
- Repeated unknown adjustments usually point to a configuration or integration gap.
- Human review should remain in place for policy-sensitive or material differences.
01 · The pattern
Which fee and adjustment categories matter most?
The important categories are the ones that change revenue, fee expense, tax, cash, customer balances, or channel margin. The names vary by channel, but the operator question stays the same: what business event does this line represent, and where should NetSuite carry it?
| Category | Why it matters | Review gate |
|---|---|---|
| Processor and marketplace fees | They separate cost of selling from gross activity. | Confirm account mapping and channel treatment. |
| Refunds and chargebacks | They affect customer, cash, and revenue treatment. | Tie back to the original event before applying. |
| Shipping, tax, and discount adjustments | They can distort category-level reporting if netted away. | Review policy treatment and source classification. |
| Credits, corrections, and reimbursements | They can represent valid reversals or unexplained channel activity. | Hold unknown lines until the cause is documented. |
02 · The pattern
How should unknown adjustments be handled?
Unknown adjustments should not be buried in a generic account just to make the payout tie. They should be classified by source, held with the supporting line detail, routed to an owner, and resolved into a configured treatment once finance understands the cause.
- Keep the original channel label and source identifier.
- Classify the adjustment by likely cause.
- Use a review gate before ledger-impacting changes.
- Turn repeat unknowns into explicit mapping rules.
03 · The pattern
How does this pattern improve close quality?
When fees and adjustments are isolated, the close tells a clearer story. Finance can see why cash differs from gross activity, which categories changed the payout, and which exceptions still need judgment. That reduces explanation work without inventing claims about speed or savings.
Shared vocabulary
What terms matter on this page?
These definitions keep the method precise and extractable for answer engines, while giving finance a shared vocabulary for source files, NetSuite treatment, and review gates.
Adjustment
An adjustment is a source-system line that changes the payout but may not map cleanly to the original order without classification.
A chargeback is a disputed or withheld amount that reduces cash and needs a documented treatment path.
Mapping rule
A mapping rule defines how a source category should land in NetSuite when the supporting detail is complete.
Where it goes next
When the pattern becomes an operating decision
This pattern sits between the settlement library, productized reconciliation, and the service paths that explain why the mismatch keeps recurring.
If this reconciliation pattern is caused by connector behavior, the operating decision belongs with a Celigo NetSuite integration partner. If the issue comes from a stalled implementation or brittle partner handoff, compare it with NetSuite HealthCheck and recovery. If the same pattern recurs every close, evaluate Vista Recon against the full NetSuite payout reconciliation.
Authorship
Who wrote this guide?
Written by Dave Charland, Founder, Altura Innovation. Last updated 2026-06-16.
FAQ
Frequently asked questions
Need this pattern converted into a governed workflow?
Tell us where the source file, NetSuite record, and close process stop agreeing, and we will help scope the safest Vista Recon path.