2.1

P1 

Import format Field has option: MPESA

2.2

P1

If there is no import plugin set, then the Import Format options will be blank and if the User tries to import a file and Continue, the following error message will be displayed at the top.  Also if the User does not select a plugin even if there are options then the following error message will be displayed.

Please select the import type.

2.3

P1

If there is no Mode of Payment configured in Mifos to be "MPESA/ZAP", then an error message will be thrown on the Import screen:

No payment type found named <bank>
where <bank> is the first cell of that file.

3.1

P1

M-PESA is an Excel format (97)

3.2

P1

M-PESA import file first few lines contain description of file.  These are to be ignored.  Only data after row of column headings will be imported in the Transactions section.

3.3

P1

Import file will have columns in below table 

3.4

P1

There will be bare basic error checking - to successfully import the data.

3.5

P1

If a row contains a cell that's missing a required field, Mifos displays an error message for each row this occurs.
Row <#> is missing data.
where the row # is the original row # of the import file.

3.6

P1

Dates are in the format YYYY-MM-DD HH:MM:ss.  If any value under Date column does not start in format of YYYY-MM-DD, then Mifos displays an error message for each row this occurs.
  Date in Row <#> does not begin with expected format (YYYY-MM-DD).
where the row # is the original row # of the import file.

3.8

P1

If first value under the Transaction Party Details column does not contain an client Government ID that matches any client in Mifos and/or the next values do not correspond to a Loan Product or Savings Product in Mifos or does not match any open loan account or savings account where a payment/deposit can be applied to the client, or if the default order set in configuration cannot be applied in any way, Mifos throws an error message

Client ID could not be found from Transaction Party Details or accounts could be applied to transaction in Row <#>


where the row # is the original row # of the import file.

See new attachment for example of import file and below for more details

3.81

P1

Check that Status column says "Completed".  If it has any other status, Mifos throws the following error message:
Status in Row <#> is <status> instead of Completed.
where <#> is the row # of import file, and <status> is the status found in the Status column.

3.9

P1

Check if the same file name has been imported.  If so, then throw an error message and reject the whole import.

Same file name has been imported.  Please import a different file.

3.10

P1

After clicking on Continue, Mifos will display the Review & Submit screen with the following:
Review the information below.  Click Submit if you want to continue with import or click Edit to make changes. Click Cancel to return to Admin page without submitting information.

Import information

Import file name: <name of file>
Import Status: <#> rows contained no errors and will be imported.

where <#> is the number of valid rows being imported. 
See mockup.

3.11

P1

User can then either

1. Click on Edit import information to go back to previous screen and upload new file.
2. Continue with import and Submit.
3. Cancel out of the workflow (returning to Admin screen).

3.12

P1

If User clicks on Submit, Mifos imports the file and displays confirmation screen

3.13

P1

There is no option to revert a file upload once it has been submitted.

3.14

P1

There is no checking of duplicate rows (see 3.9)

3.15

P1

Currency of values imported is directly inherited from the loan product that the loan account is mapped to.

3.16

P1

If there are no rows found with import data, the following error message should be thrown:

No rows found with import data.

Receipt

No

Receipt ID

Receipt ID is exclusive to MPESA, we can ignore

None

Date

Yes

Payment date

Validate date is in range (see above)

YYYY-MM-DD time

2009-08-26 12:39:42

Transaction Date

Details

No

Contains information payment received from phone number, telephone number, MFI account number

Ignore

Status

Yes

Completed

Check that Status says Completed. 

Must be Completed to accept row.  Other statuses throw an error

Completed, Attempted, Cancelled, Declined

Completed

Withdrawn

No

Amount paid from MFI

Only use for Disbursals, Phase 2

00

Paid In

Yes

Transaction amount paid to MFI

Validate it's an amount and check same validations in Mifos against digits after decimal

Should be digits after decimal = 0

200

Transaction amount

Balance

No

Balance of MFI

Ignore

520,499

Balance Confirmed

No

automatic check in system

Ignore

true

Transaction Type

No

Ignore

Pay Utility

Other Party Info

No

Phone number, telephone number

Ignore

0722926212 - CYNTHIA OMONDI 

Transaction Party Details

Yes

"Client account number assigned by MFI"

We will use this to have Client National ID and include short names) of product(s) applied to the client's accounts if it is different than the default order set in ImportTransactionOrder

Validate that ID matches a client's in Mifos, and validate 3-4 letter codes corresponds to a loan or savings product in Mifos

Just client ID, to client ID plus product(s)

1. 3029149635
2. 30556 AL1

1. Client's National ID
2. Client's National ID, and Advance Loan 1

4.1

P1

Assumption: All transaction detail is for loan repayments (loan fees, interest, principal) and/or savings deposits. There is no data in file for loan disbursals, savings withdrawals, client, group or center fees, or client attendance.

4.2

P1

Date is actual repayment date recorded

4.3

P1

For Loan Accounts: Amount that is being paid - pre-payments, partial payments, and over-payments if there are future installments are allowed.  Amount in file is applied in the following order - Penalties, Fees, Interest, Principal.

4.4

P1

Date cannot be before today in Mifos

If they have backdated transactions on, then date can be before today up til last meeting date

4.5

P1

Mode of Payment must be configured in Mifos to have MPESA/ZAP, which will be the mode of payment used for all transactions in that import.

4.6

P1

If there is an overpayment of the entire loan, Mifos should throw an error.

4.7

P1

Default order of transactions is set in new setting in a properties file called ImportTransactionOrder.
Accounts to which repayments and deposits are made should be applied to in the order specified here when importing a row.
Example: ImportTransactionOrder = AL1, NL1, SP1
In this case, all rows that do not specify a product name after the client ID should have its transaction amount applied to in this order.  Only the next payment due will be applied.  In this example, if the client owes $10 on AL1 next installment and $20 on NL1, and the client pays $100 then those respective amounts would be applied, and then $70 deposited in SP1.
There should always be only 1 savings account and at the end

Will the properties file reside with the plugin as a separate file or in the global properties file

4.8

P1

If there is any product short name specified after the client ID, then the whole transaction amount should just be applied to that account. The product can be a loan or savings product.
There's existing logic in there to take also a few loan or savings accounts if it's specified.  We'll leave that in there for now but we can choose to remove it later.

4.9

P1

Related to 4.7, it is not always necessary for the client to have accounts with all products set in the ImportTransactionOrder  field.  If the first account is not found, the plugin should continue to parse and skip to the next account.  If NO accounts are found bearing any of the products listed in the ImportTransactionOrder , THEN an error should be thrown indicating accounts were not found.

Does this feature affect Bulk Loan Creation?  How?

No

Does this feature affect Collection Sheet Entry?  How?

No

Does this feature affect Redo Loans?

No

Does this feature affect Undo Loans?

No

Will the feature be a high use-case scenario?

No

Will the feature have potential for high concurrency?

No

Does the feature include complex UI or data gathering logic that will be used by a significant portion of the user base?

No

Does the feature contain risks of database connection timeout or ASP page timeout?

Will the feature contain any bulk insert/update/delete transactions?

Will the feature contain any caching mechanisms or cache refreshing mechanisms?

Unclear

Could the feature result in a large amount of data being sent to the client or between the database and web server?

Yes

Would users on a low bandwidth connection likely face issues with a part of this feature?

Depends on size of file

Does the feature affect existing batch jobs or require adding any new batch jobs?

Unclear