Receivables registration
About Banco Central Resolution No. 4,734
The Split de Pagamento product operates as a sub-acquirer model and complies with the regulations of Banco Central do Brasil Resolution No. 4,734.
Under this resolution, acquirers and sub-acquirers are required to insert and update receivables schedules in a registration entity. This change impacts credit operations secured by these receivables.
With these regulations, it is possible to use credit and debit card receivables as collateral for credit operations or assign them in discount transactions.
Financial institutions must also register with a registration entity authorized by Banco Central. This allows companies to use the amount scheduled in the financial agenda as collateral for credit or discount operations with their institutions.
Resolution No. 4,734 aims to promote greater competition in the payment market and provide more legal certainty in receivables negotiation operations within payment arrangements.
How reconciliation works in Split de Pagamento according to Receivables Registration
Due to Resolution No. 4,734/2019 and Circular No. 3,952/2019 published by the Conselho Monetário Nacional (CMN) and Banco Central do Brasil, which took effect on 06/07/2021, our reconciliation systems were restructured to comply with these regulations.
Below, we explain the main changes that occurred in the reconciliation structure of Split de Pagamento following the mentioned resolution.
Reconciliation flow – before
Split de Pagamento had a financial schedule structure divided by merchants, where payment batches were generated on the scheduled date for settlement.
In the example below, Merchant A has two transactions scheduled for settlement on 06/09. A batch is generated containing the total amount the merchant is due to receive, which is sent to the bank for settlement on the scheduled date.
New reconciliation flow
In the new model, the financial schedule introduces a new concept called Receivables Unit. These units consist of the amount the client is due to receive, payment date, and arrangement. URs follow a structure similar to the previous batch, but with one key difference: they are grouped by the client’s document number (CPF/CNPJ) instead of by merchant.
Reconciliation with contract effects
With Receivables Registration, it will be possible to negotiate open URs as discount operations or secured credit operations. As a result, a full or partial UR can be directed to another institution. In the example below, the client negotiated an Assignment with Change of Ownership with Banco do Brasil, where R$50.00 from a UR was used as collateral. The UR is split according to the amount agreed with the institution:
Reports
Below are the descriptions of the columns included in the transactional and receivables reports. You can request these reports through our support.
Transaction Report
| Name | Description |
|---|---|
| CorporateName | Legal name of the naster that performed the transaction |
| FancyName | Trade name of the master that performed the transaction |
| DocumentNumber | Document number of the master that performed the transaction |
| DocumentType | Document type of the master that performed the transaction |
| MerchantId | Unique identifier of the master that performed the transaction |
| TransactionId | Unique identifier of the transaction |
| AuthorizationDate | Transaction authorization date |
| CaptureDate | Transaction capture date |
| Amount | Transaction amount in cents |
| Installments | Number of installments |
| AuthorizationCode | Transaction authorization code |
| Nsu | NSU of the transaction |
| AcquirerTransactionId | Unique transaction identifier at the acquirer (TID) |
| TerminalLogicNumber | Logical number of the terminal where the transaction occurred |
| AffiliationCode | Affiliation code (EC) where the transaction occurred |
| CardNumber | Card number used in the transaction |
| Brand | Card brand (Visa, Master, etc.) |
| Product | Product (Credit, Debit, etc.) |
| OrderId | Order number set by the merchant |
| Status | Transaction status |
| TransactionChannel | Channel where the transaction occurred (Physical or E-commerce) |
| MasterRateDiscountType | Type of rate discount applied to the transaction |
Participants Report
| Name | Description |
|---|---|
| CorporateName | Legal name of the participant |
| FancyName | Trade name of the participant |
| DocumentNumber | Document number of the participant |
| DocumentType | Document type of the participant |
| MerchantType | Merchant type of the participant – Master or Subordinate (Seller) |
| MasterRateDiscountType | Type of discount applied to the merchant |
| TransactionId | Unique identifier of the transaction |
| OrderId | Order number set by the merchant |
| TransactionTotalAmount | Total transaction amount in cents |
| MerchantGrossAmount | Gross sale amount related to the participant in cents |
| MerchantNetAmount | Net amount related to the participant in cents |
| Mdr | MDR fee in % applied to the participant |
| Fee | Fee amount in cents applied to the participant |
| BankSlipFee | Boleto fee in cents (for boleto transactions) |
| RRTotalRate | Percentage rate applied by Split de Pagamento on the amount to be advanced via Receba Rápido |
| RRFee | Fee amount in cents applied by Split de Pagamento on the amount to be advanced via Receba Rápido |
Void Report
| Name | Description |
|---|---|
| CorporateName | Legal name of the participant |
| FancyName | Trade name of the participant |
| DocumentNumber | Document number of the participant |
| DocumentType | Document type of the participant |
| MerchantType | Merchant type of the participant – Master or Subordinate (Seller) |
| TransactionId | Unique identifier of the transaction |
| OrderId | Order number set by the merchant |
| TransactionTotalAmount | Total transaction amount in cents |
| VoidId | Unique identifier of the void |
| EventDate | Date when the void was processed |
| VoidTotalAmount | Total void amount |
| VoidGrossAmount | Gross void amount applied to the merchant in cents |
| VoidNetAmount | Net void amount applied to the merchant in cents |
| Reverted | Indicates if the void was reverted (0 for No, 1 for Yes) |
Chargeback Report
| Name | Description |
|---|---|
| CorporateName | Legal name of the participant |
| FancyName | Trade name of the participant |
| DocumentNumber | Document number of the participant |
| DocumentType | Document type of the participant |
| MerchantType | Merchant type of the participant – Master or Subordinate (Seller) |
| TransactionId | Unique identifier of the transaction |
| OrderId | Order number set by the merchant |
| TransactionTotalAmount | Total transaction amount in cents |
| ChargebackId | Unique identifier of the chargeback |
| EventDate | Date when the chargeback was processed |
| ChargebackTotalAmount | Total chargeback amount |
| ChargebackGrossAmount | Gross chargeback amount applied to the merchant in cents |
| ChargebackNetAmount | Net chargeback amount applied to the merchant in cents |
| Reversed | Indicates if the chargeback was reversed (0 for No, 1 for Yes) |
Schedule Report
| Name | Description |
|---|---|
| CorporateName | Legal name of the participant |
| FancyName | Trade name of the participant |
| DocumentNumber | Document number of the participant |
| DocumentType | Document type of the participant |
| MerchantType | Merchant type of the participant – Master or Subordinate (Seller) |
| MerchantId | Unique identifier of the Master that performed the transaction |
| AuthorizationDate | Transaction authorization date |
| CaptureDate | Transaction capture date |
| TransactionId | Unique identifier of the transaction |
| InstallmentNumber | Scheduled installment number |
| ForecastedPaymentDate | Expected settlement date for the schedule |
| Event | Event related to the schedule |
| InstallmentNetAmount | Event amount in cents |
| Brand | Card brand (Visa, Master, etc.) |
| Product | Product (Credit, Debit, etc.) |
| OrderId | Order number set by the merchant |
| AuthorizationCode | Transaction authorization code |
| Nsu | NSU of the transaction |
| AffiliationCode | Affiliation code (EC) where the transaction occurred |
Receivables Report
| Name | Description |
|---|---|
| CorporateName | Legal name of the entity maintaining the receivables unit |
| DocumentNumber | Document number of the entity maintaining the receivables unit |
| DocumentType | Document type of the entity maintaining the receivables unit |
| ReceivableId | Unique identifier of the receivables unit |
| URAmount | Total amount in cents of the receivables unit |
| HolderDocumentNumber | Document number of the entity maintaining the receivables unit |
| HolderDocumentType | Document type of the entity maintaining the receivables unit |
| ForecastedPaymentDate | Expected settlement date of the receivable |
| PaymentDate | Settlement date of the receivable |
| Brand | Card brand of the payment arrangement that composes the receivable |
| Product | Product of the payment arrangement that composes the receivable |
| PreContractedAmount | Amount in cents pre-contracted with the Receba Rápido system for the receivable |
| ReceivablePaymentGroupType | Receivable type (Livre → ExemptedSchedule / Negociado → DealedSchedule) |
| ForecastedAmount | Amount in cents expected to be settled |
| ReceivablePaymentGroupStatus | Settlement status of the receivable |
| PosContractedAnticipation | Indicates if the receivable is reserved due to anticipation (1 → Yes / 0 → No) |
| Bank | Name of the bank where the receivable will be settled |
| CompeCode | Bank code where the receivable will be settled |
| BankAccountNumber | Account number where the receivable will be settled |
| BankAccountDigit | Check digit of the account where the receivable will be settled |
| BankAccountType | Account type where the receivable will be settled |
| AgencyNumber | Branch number where the receivable will be settled |
| AgencyDigit | Check digit of the branch where the receivable will be settled |
| BankAccountDocumentNumber | Document number of the account where the receivable will be settled |
| BankAccountDocumentType | Document type of the account where the receivable will be settled |
| BankAccountHolderName | Name of the account holder where the receivable will be settled |
| ContractEffectProtocol | Unique identifier of the contract signed for receivables assignment |
Updated about 1 month ago