Yes - account holders with a valid Direct Debit User ID (DDI) can process batches of direct debits from Australian bank accounts. It is the responsibility of the account holder to hold a record of consent between the account holder and the payer. Your CDF Relationship Manager can help you confirm whether you have a DDI or support you to apply for one. 

No – ADEB can only be used for debiting Australian bank accounts. Please consult your Relationship Manager to explore options for managing credit card debits.

Yes – if you hold more than one transaction account you can create batches for each account, however you will need to provide CDF with details of each account. Each account will be configured based on the account and batch requirements – the CDF team is here to guide you through this. All accounts must be captured in your signed agreement. 

• Yes – all changes, including adding or removing accounts are treated as a new application, please engage with your Relationship Manager or our Client Services Group to request changes, and allow a minimum of 28 days for this process. 

• To cancel an ADEB agreement, please provide written confirmation to your Relationship Manager advising you wish to cancel the service and allow 28 days for this request to be finalised. Once cancelled, services cannot be reactivated, a new application will be required. 

Yes - Account Holders are responsible for checking and authorising each batch file before it is processed. The file must be authorised in line with your CDF transaction account authority. For example, if your account requires two people to authorise transactions, two current authorised signatories must authorise the file. 

Batch files can be authorised before they are sent through your ERP system, or after upload by logging into CDF Online. 

It is the account holder’s responsibility to ensure that files are authorised before cut-off times and by the required authorised signatories. 

CDF requires all files to be received and authorised by 4.00pm AEST on weekdays. Files received outside this time, including on weekends or public holidays, will be processed on the next business day. 

CDF will work with you to establish a secure connection to our server using CDF provided SFTP credentials and PGP key for file encryption.

• The file name must include the following 6 data points:  

1. CDF account number: for example, 2345678S1.1 
2. Date: use YYMMDD format. 
3. Time stamp: use HHMMSS format. 
4. Batch description / batch narrative: enter a short description of the batch, such as Salaries 25JAN. This is the same as the batch narrative and will appear on your bank statement. 
5. Approval code: use A if your batch will be approved in CDF Online or D if approved in your ERP. 
6. File destination code: .ABA file format 

• Each of the above data points must be separated by underscores, and
• Batches must be in .ABA file format.  

Example file name: 234567S1.1_251118_142012_Salaries 25JAN_D.ABA

Important:  

• The file name must be exactly 120 characters, including spaces 
• The batch description / batch narrative must not exceed 30 characters. If the batch description / batch narrative is longer than 30 characters, it will be shortened 
• Do not use special characters in the file name 
• If the file is not named in this format CDF will rename it to meet our naming conventions 
• Files must be saved as .ABA – CDF does not accept .ABA.TXT file format 

All files must be in the following standard format: 

• Type 0 (Header Record): Starts with 0, followed by blank spaces, bank/user details and the date in DDMMYYYY format 
• Type 1 (Detail Record): Starts with 1, containing destination BSB, account number, indicator flags, transaction codes (e.g., 50 for external credit), amount in cents (no decimal point), payee name, and source account details  
• Type 7 (File Total Record): Starts with 7, containing net/total debit and credit amounts in cents to balance the batch 

When applying for ADEB, you must advise how your batch narrative will be formatted.  

The formatting options are: 

1. Static – each batch file will have the same narrative (for example you require each batch to reflect PAYROLL) 
2. Dynamic – each batch file will have a different narrative generated by your ERP or accounting package
3. Reformatted – CDF will rename each batch file to match a narrative you nominate when setting up your ADEB product 

No – once your file has been authorised it cannot be changed by the account holder or by CDF.  

If your file has been received but not processed our Client Services Group may be able to cancel the file for you - please contact our Client Services Group on 1800 134 135.