Library · Payments · How to run this
SeamlessChex ACH return lag is not return-code skew
Return day minus settle day is the ACH return-code lag. Type both days plus ACH returns from one SeamlessChex cut.
Pair: ACH return-code lag on Payments. Skew twin: return-code skew. Hold twin: settlement-hold days.
What you type
Return day — Day index when the ACH return code posted in the cut.
Settle day — Day index when the original ACH settled in that same cut.
ACH returns — ACH returns that posted a return code in that cut.
Lag days = return day − settle day. Fat lag days mean cash looked settled too early — never invent a lag.
What not to do
Skip inventing lag days. Skip treating return-code skew as a clock. Skip dumping settlement-hold days into the return day field. Skip blending MIDs when one MID owns the late return.
Related: Payments, return-code skew, settlement-hold days, same-day ACH fail.
Procedure
- Type return day, settle day, and ACH returns.
- Read lag days.
- Tighten settle assumptions when lag days are material.
Failure modes
- Inventing lag days.
- Treating return-code skew as a clock.
- Dumping settlement-hold days into the return day field.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- ACH return-code lag days
- Return day − settle day.
Work with us — We run this job on your accounts. Services
FAQ
- Is this return-code skew?
- Skew is mix, not clock. [Return-code skew](/manuals/seamless-return-code-skew) is top code ÷ returns. This page is return day minus settle day.
- Is this settlement-hold days?
- Hold is reserve clock. [Settlement-hold days](/manuals/seamless-settlement-hold-days) is that door. This page is ACH return-code lag.
- What lag days should I invent?
- None. Pull return day, settle day, and ACH returns from the same SeamlessChex cut.