Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Merchants expect T+1 money on the calendar day after a sale and assume it is missing when weekends, holidays or cut-offs push the credit out.
T is the capture day after the cut-off is applied; the number counts bank working days, skipping Sundays, second and fourth Saturdays and bank holidays.
Note your settlement cycle and cut-off from the gateway agreement and keep the RBI holiday list for your state.
Each day's captured sales have an expected settlement date, and only credits that miss that date are chased.
In T+1, “T” is the day the payment was made (the transaction day) and the number counts working days after it. T+1 means the gateway should settle the money on the next working day. T+2 means two working days later. Weekends and bank holidays push those dates out, and your bank may post the credit that day or slightly later.
Do Saturdays, Sundays and bank holidays count in T+1?
Usually not. Most gateway agreements count bank working days. In India banks close on Sundays, on the second and fourth Saturdays of the month, and on public holidays, which vary by state. RBI publishes the holiday list for each state.
Two more details matter:
- Cut-off time. Payments captured after the gateway’s daily cut-off (often late evening) are treated as the next day’s transactions.
- Bank posting. Settlement credits typically go by NEFT, which runs every day, but the bank may post the entry to your statement a few hours later.
Your agreement is the final word on which days count.
When does money settle under T+0, T+1 and T+2?
Take October 2026: Saturday 10 October is the second Saturday (a bank holiday), and for this example assume Monday 12 October is a local bank holiday in your state. Assume all payments are before the cut-off.
| Payment made | T+0 | T+1 | T+2 |
|---|---|---|---|
| Friday 9 Oct, afternoon | Friday 9 Oct | Tuesday 13 Oct | Wednesday 14 Oct |
| Saturday 10 Oct | Tuesday 13 Oct (T moves to the next working day) | Wednesday 14 Oct | Thursday 15 Oct |
| Monday 12 Oct | Tuesday 13 Oct | Wednesday 14 Oct | Thursday 15 Oct |
The likely bank credit day is the same as the settlement day in most cases. Allow a few hours more for posting.
Worked example: ₹48,500 of Friday sales before a holiday stretch
A bakery captures ₹48,500 of online orders on Friday 9 October. It is on T+1, with an illustrative 2 percent fee.
- Fee: 2 percent of ₹48,500 = ₹970
- GST at 18 percent on ₹970 = ₹174.60
- Net settlement: ₹48,500 − ₹970 − ₹174.60 = ₹47,355.40
Saturday is a second Saturday, Sunday is closed and Monday is a bank holiday. The next working day is Tuesday 13 October. So ₹47,355.40 should arrive on Tuesday, four calendar days after the sale.
On Monday the owner looks at the bank and sees nothing. That is expected, not a problem. If Tuesday passes with no credit, then it is time to check the gateway’s settlement status.
Also note: if Saturday’s and Monday’s orders are on the same T+1 cycle, they settle on Wednesday, separately from Friday’s.
Which date goes in my books: the sale date, the settlement date or the bank credit date?
Each one has a job:
| Date | What you record |
|---|---|
| Sale date (9 Oct) | Sale and gateway receivable of ₹48,500 |
| Settlement date (13 Oct) | Matches the gateway’s settlement report |
| Bank credit date (13 Oct) | Bank receipt ₹47,355.40, fee ₹970, GST input ₹174.60, receivable cleared |
At a month-end that falls inside a holiday stretch, the gateway receivable will carry a balance. That balance is money in transit, not a mismatch, as long as it equals the captured sales not yet settled.
What to read next
- Next in this series: payment gateway settlement report columns explained
- Long weekends in practice: weekend and holiday settlement stretches
- The settlement step in detail: what is payment gateway settlement?
- When matching becomes daily work: payment gateway reconciliation
Payment-gateway settlement reconciliation is on the TransactIG roadmap.