Organisations | Automated Direct Entry Batch (ADEB)

Automated Direct
Entry Batch (ADEB)


What's Automated Direct Entry Batch (ADEB) and who it's for?


ADEB allows CDF transaction account holders to send multiple debits or credits in one file, called a batch. You can create a batch file in your ERP, accounting or payroll platform and send it securely to CDF via secure file transfer protocol (SFTP). 

 

Batches are also known as Cemtex or Australian Banking Association (ABA) files.

Photography: CDF

Requirements


Am I eligible for ADEB?

To utilise ADEB, account holders must meet all minimum viable requirements:

Active CDF transaction account
Ability to generate batch files in ABA format using an ERP, accounting or payroll package
Ability to encrypt and send batch files using SFTP and PGP keys
Access to technical support to establish file transfer and encryption protocols
Access to technical support to configure the ERP, accounting or payroll package to meet file formatting requirements

Step-By-Step Process


If your organisation meets the minimum requirements, our team will work with you to ensure a seamless transition:

Step 1: Application

Contact your CDF Relationship Manager or our Client Services Group to initiate an application.

Step 2: Scope

Your CDF Relationship Manager will arrange a meeting with you to discuss your application – we recommend you bring along your technical support team to meet our Data & Integration team and gather all required information upfront.


CDF will ask for the following information:

  • The name of the ERP, accounting or payroll package(s) used to generate batch files 
  • The CDF account number(s) you want to debit or credit using ADEB (you may request DE files for different accounts depending on your requirements) 
  • If you want to process direct debit files that you have appropriate agreements in place with your payers and an active Direct Debit User ID (if a new ID is required your RM will assist you with an application) 
  • Confirmation your system can generate ABA files 
  • Confirmation your technical support team can configure batch files in the required format 
  • Confirmation your technical support team can encrypt and transfer files using SFTP and PGP keys 
  • Contact details for your technical support team 
  • Contact details for your accounts or administration team

Step 3: Agreement

If all parties agree ADEB is a viable option, your Relationship Manager will provide a written agreement confirming your application and outlining the terms and conditions of acceptance 

Step 4: Build, Test, Implement

Once your signed agreement is received, our Data & Integration team will commence building, testing and implementation of your ADEB solution.

The CDF Corporate Card solution can seamlessly integrate with many accounting platforms, including, but not limited to:

FAQs


  • Can I process direct debits as a batch?

    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. 

  • Can I debit credit cards?

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

  • Can I have more than one account linked to ADEB?

    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. 

  • Can I change or cancel ADEB?

    • 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.  
  • Do batch files need to be authorised?

    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.  

  • How and where can I authorise files?

    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. 

  • What is the cut-off time for files to be authorised?

    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. 

  • How are batch files sent to CDF?

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

  • Naming batch files

    The file name must include the following 6 data points:  


    CDF account number: for example, 2345678S1.1 

    Date: use YYMMDD format. 

    Time stamp: use HHMMSS format. 

    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. 

    Approval code: use A if your batch will be approved in CDF Online or D if approved in your ERP. 

    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 

  • Formatting batch files

    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 
  • Can I change my batch narrative?

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


    The formatting options are: 


    Static – each batch file will have the same narrative (for example you require each batch to reflect PAYROLL) 

    Dynamic – each batch file will have a different narrative generated by your ERP or accounting package

    Reformatted – CDF will rename each batch file to match a narrative you nominate when setting up your ADEB product 

  • Can I make changes to a batch file?

    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.

Pictured: CDF Staff

Troubleshooting


How are batch errors managed?

We will notify you as soon as possible if a batch error occurs. CDF requires account holders to nominate a contact email address to which all error notifications are sent (a group inbox is recommended). 


Important: Files with errors cannot be amended by CDF. All error files will require amendment and reprocessing by the Account Holder.

Error messages

Error messages will be emailed to your nominated contact email in the following format:

 

Subject: Payment file failed 

Message: Please review and resubmit payment file “file name”. The message will refer to the specific lines within the file which are causing the file error, for example: Line 1 no header record in file

View ADEB Troubleshoot Matrix

Help and more information


General Enquiries

For general enquiries relating to CDF ADEB speak to a member of team.

ADEB Terms & Conditions

Read the ADEB Terms & Conditions

The Fund is required by law to make the following disclosure. Investment in the Fund is only intended to attract investors whose primary purpose for making their investment is to support the charitable purposes of the Fund. Investors’ funds will be used to generate a return to the Fund that will be applied to further the charitable works of the Archdiocese of Melbourne and the Dioceses of Sale, Bunbury and Ballarat. The Fund is not prudentially supervised by the Australian Prudential Regulation Authority nor has it been examined or approved by the Australian Securities and Investments Commission (ASIC). An investor in the Fund will not receive the benefit of the financial claims scheme or the depositor protection provisions in the Banking Act 1959 (Cth). The investments that the Fund offers are not subject to the usual protections for investors under the Corporations Act (Cth) or regulation by ASIC. Investors may be unable to get some or all of their money back when the investor expects or at all and investments in the Fund are not comparable to investments with banks, finance companies or fund managers. The Fund’s identification statement may be viewed here or by contacting the Fund. The Fund does not hold an Australian Financial Services Licence.