Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.



Flows: 

...

Requirements: 

Phase1:

  1. Loading supplier transactions which are not allocated and not paid yet. 
  2. User can filter the transactions by 
    1. Supplier range 
    2. Due date
    3. on hold suppliers 
    4. Remittance cheque EFT
    5. transaction on hold
    6. Action date
  3. Can see the total 
  4. Can allocate the transactions individually or as a batch 
  5. Can view the supplier information of the transaction 
    1. the user with permission should be able to modify the supplier bank information.
  6. Can view attachments linked to that invoice
  7. Due dates are color-coded (red, yellow, green) to indicate urgency.
  8. Download the report of the transactions 
  9. Can download the bank file. 
  10. Can configure the bank file. (settings)
  11. Every action is permission based
  12. Email remittenace advise to the supplier, how much we are paying which invoice  
  13. Batch should be validated against the bank file structure. 
    1. supplier bank information should be validated.
    2. should be validated if the line has been already paid or not.

...

  1. Link the payments to the bank and directly pay them 
  2. Saving the batches as Draft and ability to load them later on
  3. Can create a batch from transactions and send it through approval


Different Flows: 

  1. a batch is created and going though the workflow (similar to the existing one in EPO)
  2. upon receiving an invoice we can select an option and and the payment which is already linked to a bank would be generated (and paid? )
  3. We set a flag on the invoice and the invoices with this flag would be already in a batch generated automatically (with option to add more)
  4. having the supplier lines aggrigated to one or we can pay suppliers line by line 

Restrictions 

  1. We can't add lines that are already in the batch 
  2. Making sure not to overpay a supplier
  3. We can't send a negative value (total)



Data structure 


Tables: 

Code Block
languagesql
titleHeader table
collapsetrue
CREATE TABLE [dbo].[PaymentBatchAccounts](
	[Id] [int] IDENTITY(1,1) NOT NULL,
	[AccountLink] [int] NOT NULL,
	[iAllowICPurchases] [bit] NOT NULL,
	[Master_Sub_Account] [nvarchar](max) NULL,
	[Account_Type] [nvarchar](max) NULL,
	[Description] [nvarchar](max) NULL,
	[iAccountType] [int] NOT NULL,
	[AcLookup] [nvarchar](max) NULL,
	[iForeignBankCurrencyID] [int] NOT NULL,
	[CurrencyCode] [nvarchar](max) NULL,
	[CurrencyId] [int] NOT NULL,
	[BranchId] [bigint] NULL,
 CONSTRAINT [PK_PaymentBatchAccounts] PRIMARY KEY CLUSTERED 

...