BACS Indemnity Claims (DDICA) Importer (Web based, C# .NET)

We'd like to extend our current BACS XML file importer to support DDICA. See [login to view URL] Our application is web-based and written in C# .NET. We are already importing XML files from the BACS website which contain ADDACS and AUDDIS records. These are imported into our application database (MSSQL 2008) and a number of special actions performed. In programming this extension, we only need to record information about the Indemnity Claims in an existing table (currently users are entering indemnity claims manually) and to call an existing Cancel() function for each claim (each claim will correspond to an existing customer in our Customers database table for which the Cancel() function can be called. There is an existing UI for this web based app which has already been redesigned to support DDICA. I will provide a mockup of the existing UI and the new UI and full information on the database table that needs updating and the columns etc. and provide an empty test database.. ## Deliverables The objects to update will be any number of Transactions for said Customer, and the Cancel function will be called for the Services associated for Transactions of that customer. The db schema looks like this: - Transactions - Services - TransactionServices - Customers A Customer may have many Services and many Transactions (i.e. rows in Services have a CustomerId). Transactions will always have many Services (i.e. each row in Transactions has corresponding entries in TransactionServices which is a link-table back to Services). So the only columns in TransactionServices are TransactionServiceId, TransactionId and ServiceId. In human terms, Services are just 'payment schedules', which is why they ultimately result in transactions. When two Services are due to be debited on the same day, we collect them together in a single transaction, which is why a single transaction may link to multiple services in the database. When indemnity claims occur in the XML file, you'll be able to determine the transactions affected, update the the rows to mark them as 'claimed back' by the customer and then cancel the payment plans (i.e. cancel the Services attached to the Transactions). We already have a data layer. I will be able to supply more information on the pre-existing cancel function later.