Settlement Pattern Library
Reserve and timing-gap review for NetSuite payouts
Use this pattern when payout timing, reserves, or holdbacks make the close look wrong before the source detail is understood.
The method
How do you review reserves and timing gaps in NetSuite reconciliation?
Reserve and timing-gap review explains why source transactions and cash deposits land in different periods. The operator method separates expected timing from true exceptions, documents the reason, and keeps unresolved reserves or delayed payouts from being force-fit into the current close.
Key takeaways
- Not every mismatch is an error; some differences are expected timing.
- Reserves and holdbacks need their own review path before posting.
- Period cutoff logic should be documented in the reconciliation workflow.
- Unresolved timing should stay visible until cash and source detail resolve.
01 · The pattern
How do you tell timing from a true exception?
A timing gap has source evidence that explains why the activity and cash fall in different periods. A true exception lacks a match, violates the configured rule, or needs judgment. The review should prove the difference before finance decides how to carry it.
| Difference type | Evidence to look for | Treatment |
|---|---|---|
| Expected payout delay | Source activity ties out but cash settles later. | Track as timing with the expected resolution path. |
| Reserve or holdback | Channel shows funds withheld or released on a later event. | Separate from fees and review until release or reversal. |
| Missing source match | Cash or source line has no NetSuite counterpart. | Hold as an exception with owner and root-cause review. |
| Period cutoff conflict | Source date and NetSuite posting date follow different rules. | Apply the documented cutoff policy consistently. |
02 · The pattern
Why should reserves stay visible?
Reserves affect cash confidence and close explanation. If they are buried inside fees, adjustments, or generic clearing, finance loses the ability to distinguish expected channel behavior from missing activity. Keeping reserves visible preserves the audit trail and review path.
- Track reserve source, amount, period, and expected resolution.
- Separate reserve release from new sales activity.
- Do not use reserves to hide unrelated settlement differences.
- Escalate unresolved or unexplained holdbacks through a human review gate.
03 · The pattern
How does this pattern connect to reconciliation automation?
Automation can route timing gaps and reserve lines faster, but it should not decide ambiguous close treatment without policy and approval. A governed workflow can identify likely timing, attach evidence, and hold unresolved items until finance signs off.
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.
Timing gap
A timing gap is a mismatch caused by source activity and cash settlement landing in different dates or periods.
Reserve
A reserve is a held-back amount that may release later and should be tracked separately from fees and true exceptions.
Cutoff policy
A cutoff policy defines how finance treats activity that crosses the boundary between accounting periods.
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.