Page Comparison

3.1

P1

M-PESA is an Excel format (97) Remember

there was something wrong with format Is there a way to open the default XML?

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 Changes for 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

Yes

Receipt ID is proof of payment and a unique MPESA identifier that can be cross-reference with clients phone receipt. Need to be imported into Mifos since needed in the KEEF Collection Sheet.

Receipt ID is exclusive to MPESA

Check that there is not an existing RECEIPT ID

Alphanumeric

Y29DW127

Transaction Details - Receipt ID

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

Yes

Safaricom generated phone number and name associated with phone number

Compare first 10 digits to phone number. If none exists, error
Is it always 10 digits in Kenya?

First 10 digits must correspond to a Phone # or Mobile # in Mifos

Numeric

0722926212 - CYNTHIA OMONDI 

Phone Number or new field Mobile Number

Transaction Party Details

Optional

Ask about if client number will be here, in what order will that information be listed in this field

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

CHANGE from previous: no more client national ID's and this field is now optional - only use if transactions to be applied are different than default order

Validate 3-4 letter codes corresponds to a loan or savings product in Mifos

Everything before first space

Mifos product codes

SP1

Savings Product 1

6.1

P1 

Receipt ID must now be imported and stored in Transaction Details - Receipt ID field

6.2

P1

When importing, must check to see if Receipt ID already exists in any transaction in Mifos - if YES, then ignore the row and

Mifos throws an error message

Transaction Transactions associated with Receipt ID <receipt ID> in Row <#> has already been imported.

where the row # is the original row # of the import file and <receipt ID> is the receipt ID that was found.

6.3

P1

Other Party Info must be imported.  Take first 10 digits as phone number, and compare with Client's Phone Number fields in Mifos.  If there is not a match, then ignore the row and

Mifos throws an error message

Client with phone number <phone number> in Row <#> was not found.

where the row # is the original row # of the import file and <phone number> is the phone number.

If there is a match, store in Client's Phone Number field, and use this as identifier for transaction.

6.4

P1

Changes to Transaction Party Details - no more taking of National ID - remove this functionality and