Sending payments to the bank
Smart Finance sends payables to the bank through the Banking Gateway. Sending is a manual action — done by a person, one bill at a time or in batch from the inbox — never by an automatic trigger. Only the status tracking runs in the background.
Prerequisites
- Banking Gateway connected and active, with the source account already synced.
- An official bill: it is only sendable once authorized, or if it is legacy/imported (see the authorization gate). A bill awaiting authorization or rejected is blocked.
- Operation type set and the payment coordinates filled in — barcode, PIX key, bank details. See Operation and payment.
- "Pay from" set — that's the account the money leaves from.
Dispatch flow
There is no "schedule" on the screen. Sending is always your click — nothing goes out on its own, on any date. What the system sends to the bank, along with the payment, is the date it should settle: the bill's due date. If the bill is already past due, it goes out today — the gateway doesn't pay with a backdated date.
Gateway status
The status mirrors the payment's real state on the gateway:
| Status | What it means |
|---|---|
| Pending | Created on the gateway, not processed yet |
| Awaiting approval | In the institution's approval queue |
| Approved | Approved — but not settled yet |
| Scheduled · Awaiting scheduled date | Set for a future date |
| Awaiting funds | Not enough money in the account to settle |
| Overdue | Past the date and never settled |
| Finishing | In final processing |
| Confirmed | Settled — the money left |
| Reproved · Rejected | Refused by the institution |
| Failed | Processing error |
| Canceled | Dispatch cancelled |
"Approved" is not the end. It's the state that misleads the most: the batch was approved, but the institution has not settled yet. What closes the cycle is Confirmed. The final states are Confirmed, Canceled, Rejected, Reproved and Failed.
Automatic settlement
Settlement happens when the gateway reaches Confirmed — not at Approved, which is still an intermediate step. Once there, the system marks the bill as paid and creates the outgoing transaction in the source account.
With no "Pay from" set, there is no automatic settlement. The system would have nowhere to post the outflow: the bill stays Confirmed and open. See Lifecycle.
The "Refresh status" button fetches the current state on demand, without waiting for the automatic tracking.
Cancel dispatch
"Cancel dispatch" undoes the dispatch while the payment hasn't reached a final state. The bill stays on the gateway track, now carrying the "Canceled" badge, and "Mark as paid" comes back — so you can close the bill outside, if the payment ends up happening some other way.
That's why a bill already sent does not offer "Cancel": voiding it here would leave the payment alive on the gateway. The route is to cancel the dispatch first.