Header: 

  1. Batch reference 
  2. Bank account - IBAN - Swift 
  3. Bank file format (would be set by default, but can be edited) 
  4. Aggregation method
    1. aggregate by supplier
    2. aggregate by supplier IBAN 
    3. Don't aggregate

Buttons:

newly creating the batch: 

  1. Save draft
  2. Submit for approval 

Approving the batch: 

  1. Approve
  2. Reject

Fully approved:

  1. Download bank file 
  2. Proces the batch 
  3. Reject (with permission)


Filter: 

  1. Transaction from date - Transaction to date
  2. From supplier - to supplier
  3. Due date 
  4. Due date action calculation 
    1. As per document
    2. Calculate per terms
    3. None
  5. Include supplier on hold
  6. Include Remittance EFTS

Grid: 

Account Invoice number OutstandingDoc total Due dateExternal order number IBANSwiftPercentageAmount to paySupplier edit (Button)












Assumptions: 

  1. If the aggregation method is not selected default is None 
  2. Creating a UDF for the suppliers which indicates if the supplier should be excluded from the payment batch by default. 

Validations: 

in backend and frontend

  1. Selected bank account has IBAN and swift 
  2. Supplier has correct IBAN and swift on selected invoices
  3. The total of the batch should be above zero
  4. Checking if the invoice has been used in another payment batch
  5. Bank file should be selected
  6. Validate if there is a workflow created for the batch 

hard validation on the database:

  1. Should not be allowed if the transaction has been already allocated. 
  2. Should not be created when the outstanding is 0