Bank slip and Pix charges
From a receivable, Smart Finance creates a charge through the Banking Gateway — a bank slip (boleto) or a Pix — for the customer to pay. It is the mirror of sending payments, on the money that comes in.
The action is "Create charge", on the bill's detail screen.
Prerequisites
| Requirement | Bank slip | Pix |
|---|---|---|
| Banking Gateway connected | ✅ | ✅ |
| A customer linked to the bill | ✅ | ✅ |
| The customer's tax ID (CPF/CNPJ) | ✅ | ✅ |
| A due date on the bill | ✅ | ✅ |
| The customer's full address (postal code, street, district, city and state) | ✅ | — |
| A bank slip agreement registered on the gateway account | ✅ | — |
| A Pix charging account registered on the gateway account | — | ✅ |
The two rails are not the same charge with a different button. They change what the customer receives and what has to be registered beforehand — which is why the choice is made through two cards, each stating its own prerequisite.
If something is missing, the system says exactly what, instead of a generic error: "The customer needs a tax ID", "Bank slips require the customer full address", "No Pix charging account is registered", and so on.
Flow
A freshly created charge cannot be handed to the customer yet. Registration at the financial institution is asynchronous: while the state reads Registering, the bank slip does not exist at the bank yet and the Pix has no QR code. Wait until it reaches Registered.
Charge states
They show on the charge card and in the Status at the bank column of the receivables listing.
| State | What it means |
|---|---|
| Registering | created; the institution has not confirmed the registration yet |
| Registered | registered — it can go to the customer |
| Overdue | past the due date with no payment |
| Paid | the customer paid |
| Registration rejected · Registration failed · Generation failed | the institution did not accept it; the charge is not valid |
| Cancelled | undone |
The "Refresh" button fetches the current state on demand, without waiting for the background tracking.
Automatic receipt of payment
When the charge reaches Paid, the bill is marked as received on its own: it becomes Received, dated today, and the incoming transaction is created.
With no "Receive into" set, there is no automatic receipt. That field is what says which account the money landed in — without it the system does not guess, and marking the bill as received is left for you to do by hand. The charge stays marked as Paid.
While the charge stands, the bill does not change
With a charge that is Registering, Registered, Overdue or Paid, somebody out there can pay it — or already has. That is why the bill is locked on everything that describes the charge: amount, due date, customer and the like cannot be edited, and the bill cannot be deleted.
Editing here would not re-issue anything. The bank slip the customer is holding would stay the same — it is the system that would start lying about what was charged. To correct it, cancel the charge first.
Rejected or cancelled charges lock nothing: they exist for nobody.
Canceling the charge
"Cancel charge" undoes the charge on the gateway. The two rails behave differently, and the difference matters to your customer:
- Bank slip — stops being valid as soon as the gateway confirms, and the customer can no longer pay it.
- Pix — the cancellation is confirmed by the financial institution. Until that confirmation arrives, the customer can still pay.
That is why the answer distinguishes "Charge cancelled" from "Cancellation requested — waiting for the institution to confirm". In the second case, follow it until the state reads Cancelled.
A charge that is paid, already cancelled or that failed has nothing to cancel.
Related
- Receivables — lifecycle — the states of the bill itself
- Banking Gateway integration — connecting, syncing and tracking
- People — where the document and address the charge requires are kept