Operation and payment

The payable form separates two different things, into two blocks:

Block	Answers
OPERATION & DOCUMENT	What this obligation is and which document represents it
PAYMENT INFORMATION	The coordinates to execute it (barcode, Pix, bank details, tax form)

note

There is no longer a generic "Payment method" field on a payable. The second field is labelled by the operation you pick — and the list of options changes along with it.

OPERATION & DOCUMENT

Operation type

The primary axis. Two options:

Option	What it means
Document payment	Settle a document that already exists: a bank slip, a utility bill, a tax form or a Pix charge
Transfer	Send money to a beneficiary

Until the operation type is chosen, the second field doesn't even appear.

The second field changes its name with the operation

Operation type	Field label	Options
Document payment	Document	Bank slip · Utility bill · Tax / tribute · PIX
Transfer	Transfer type	Bank transfer (TED) · PIX

• Switching the operation type resets the second field when the chosen option doesn't belong to the new operation.
• A tax is a document, not a "payment method" — that's why it shows up under Document, and never in a list of methods.
• PIX appears on both axes, with different meanings: under Document payment it's the copy-and-paste code of a charge; under Transfer it's a key or bank details for a beneficiary.

Document

Also in this block: Document number and Document date — the invoice/bank slip identification.

PAYMENT INFORMATION

This panel only appears when the operation × document combination has coordinates to enter. Its title is "PAYMENT INFORMATION" — or "TAX FORM DATA" when the document is a tax.

Operation → Document	What the panel asks for
Payment → Bank slip	Barcode
Payment → Utility bill	Barcode
Payment → Tax / tribute	Tax type + How to enter: Barcode or Guide fields
Payment → PIX	Pix code (copy-and-paste)
Transfer → PIX	Pix key or Bank details tabs — you pick one path
Transfer → TED	Bank details: bank, branch + digit, account + digit

Beneficiary (transfers only)

Both transfers — TED and PIX — also ask who receives, in fields of their own:

Field	Required to send to the bank
Beneficiary name	Yes
Beneficiary tax ID	Yes
Transfer purpose	No

warning

Without those two fields, sending to the bank won't go out. The institution requires the name and tax ID of whoever receives on any transfer, and the dispatch inbox blocks the row until they're filled in.

Picking a supplier fills the beneficiary in for you — name and tax ID come from the person, along with the Pix key and the bank details of their primary account. This happens the moment you select the person in the Supplier field, and it overwrites whatever is already there. The fields stay editable: the beneficiary can legitimately be someone else (an employee of the supplier, an authorized third party).

note

This panel doesn't pay anything. It only stores the coordinates on the record. Payment happens in one of two ways — outside (and you settle it) or through sending to the bank. See Lifecycle.

PIX — copy-and-paste

When you paste the code, the system draws the QR code right away — you can scan it in your bank app and pay outside.

"Look up QR data" goes further: it fetches the charge and shows the Payee, the QR amount, the Due date and whether it can be paid. It's read-only — it's there so you can check before sending.

With the data on screen, "Fill form with this data" brings it into the form:

From the QR	Goes to
Amount	Amount (R$)
Due date	Due date
Description	Description — only if it's empty; whatever you wrote is not overwritten
Payee	Supplier

The QR's payee becomes the Supplier. There is no "Beneficiary" field here — that only exists on a transfer. The system looks for an existing supplier by the payee's tax ID (CPF or CNPJ); if it finds one, it selects it. If not, it leaves the name filled in as a new supplier, which gets registered on save.

PIX — key

The Key type (CPF, CNPJ, email, phone, random) is detected automatically from the key you type — it's a read-only field; you don't select it.

Tax — barcode or data

There are nine types: DARF, GRU, GPS, FGTS, DARE, ICMS, ISS, IPTU and ITBI.

note

Only four accept the structured tax form. DARF, GRU, GPS and FGTS get the "How to enter" field, to choose between Barcode (the default) and Guide fields — and from there the fields vary by type. The other five accept the barcode only; for them, "How to enter" doesn't even appear.

This does not limit sending to the bank: all nine are sendable. See Tax / tribute.

Post-confirmation lock

Once the bank confirms the payment, the whole panel goes read-only: the coordinates now describe a bank transaction that has already executed and can no longer change.

What about cash, card, cheque?

Cash, credit card, debit card, direct debit, check and "other" exist in the system and can arrive through CSV import or through the API — but no form offers them. There is no such field on payables, on receivables, or on transactions.

Where they do show up is on the reading side: the payables list has the Settlement column and the transactions list has Payment method, both hidden by default and switchable from the column selector. A bill imported with "cash" shows "cash" there — you just can't type it in.

If the obligation is neither a document nor a transfer, leave the operation type blank: how the money actually left is recorded at settlement (financial account + date), not here. The select opens empty on a new bill — but it only has the two options, with no "None": once an operation is chosen, there's no going back to blank from the screen.