DDA - Dbito Direto Autorizado (Authorized Direct Debt)

How it works
The customer (debtor) must register himself as Electronic payer in one or more banks
with which he has relationship.

The customer will request his register in each chosen Bank;

If the customer leaves to be electronic payer he must ask to cancel him in all
banks in which he has asked for registering.

Clearance
The boletos interbank clearance system will use the current clearance systems to billets
settlement (SILOC and SIPROC).

Old Model (Manual)

Boletos delivery with paper billets

Bank bond issues the paper boletos

Payers choose the bank for payment
Send to payers

DDA Model
Electronic boletos presentation

1. Banks bond verify if customer is an electronic payer, generate the

electronic boleto and send it to DDA;
2. DDA storages all electronic boletos;

3. The bank of the customer checks in DDA the boletos which belongs to their
customers electronic payers and present them through several available
channels;
4. The payers do the payment of their electronic boletos through those
channels (internet etc.) put available by their banks.

How it works in Knauf today

DDA is only used by Knauf Drywall
The job is completely manual.
1.
2.
3.
4.

Mr. Luiz Marinho access the bank through internet;

Selects all electronic boletos to be paid;
Process payment in internet banking;
Do settlement manually in Totvs.

How it works in SAP

1. The DDA process requires the (outgoing) payment (F110) because the
acceptance of the payer is needed (authorized debt);
2. In accounts payable, the electronic payment slip received from the bank contains
the barcode information;
3. This barcode information (44 digits) is distributed over various fields in the
incoming file, and needs to be converted into a 47 digit numerical barcode, and
then updated in the corresponding accounting document (vendor invoice);
4. No payment can be done without the barcode in the accounting document;
5. These documents with the updated numerical barcode, are included in the next
payment run (F110);
6. Before the 47 digit numerical barcode is updated in the open vendor invoice, the
CNPJ/CPF number, due date and the amount present in the incoming file is
compared with that of the open invoice in the system. If these 3 values match,
only then the numerical barcode is updated in the open vendor invoice;
7. The documents where these 3 values do not match with that of the open vendor
invoice in the system, are displayed in an error log.These error records need to
be later handled manually;
8. For FEBRABAN and ITAU, the incoming bank file contains a new SEGMENT 'G'.
This segment is specific to this new DDA requirement, and contains the complete
information about the barcode.
The program RFEBKA00 is modified accordingly to handle the incoming bank file

with the new Segment 'G', and updates the barcode automatically in the open
invoice if the document is successful (CNPJ, due date and Amounts match);
9. For BRADESCO, the bank file does not contain an explicit segment for DDA.
The Bradesco file format contains just a Header, Detail Register and Trailer. The
Detail register contains all informatiom about the barcode. The program
RFEBKA00 is modified accordingly to handle the incoming barcode information
present in the incoming file and updates the 47 digit numerical barcode
automatically in the corresponding vendor invoice, if the document is
successful(CNPJ, due date and Amounts match);
10. In accounts receivables, there are certain changes in the existing file layouts,and
some field contents for remittance and return file formats. There is no new
requirement in the accounts receivable process.
The modifications suggested above (reported in SAP Note 0001514922 from
29.06.2011) will be provided in the next SAP support package.
For immediate results, its necessary to perform the following manual steps in
sequence:
1. Do the manual steps as explained in the document
"Documents_Note_1514922_DDIC_1.zip" to create the database objects.
2. Do the manual steps as explained in the document
"Documents_Note_1514922_DDIC_2.zip" to create the database objects.
3. Do the manual steps as explained in the document
"Documents_Note_1514922_FM1.rar" to create the Function modules.
4. Once these manual steps have been done, apply the correction instructions
attached to the note .

WARNING!!!:
NO ONE HAS USED THIS PROCEDURE IN BRAZIL SO FAR
ALL RESEARCHES DONE BY US WITH OTHER COMPANIES HAS SHOWN THAT
THOSE COMPANIES ARE USING "Z's" PROGRAMS TO SOLVE TO DEAL WITH
DDA PAYMENTS.
THIS IS HAPPENING DUE TO OSS Notes ARE VERY RECENT AND THE SAP
SOLUTION CAN STILL CONTAIN SOME BUGS WHICH CAN DRIVE US TO OPEN
OSS NOTES