...
Column Name | Required | Description | Comments | Validations | Range | Example | Maps to Mifos | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Receipt | No 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, we can ignore | None |
|
|
| 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 | No Yes | Phone number, telephone number | Ignore |
| Safaricom generated phone number and name associated with phone number | Compare first 10 digits to phone number. If none exists, error | 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 | Yes | "Client account number assigned by MFI" | We will use this to have Client National ID and 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 | 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 | 1. Client's National ID | SP1 | Savings Product 1 |
Loan Repayment and Savings Deposit Details
...
Date | Name | Role | Status |
|
| PM |
|
|
| Dev |
|
|
| QA |
|
Changes
Add new client field for Mobile Number OR Use Existing Phone Number field in Address?
FR# | Pri | Description | Comments / Mockups |
|---|---|---|---|
5.1 | P1 | Add new field for Mobile Number for clients. |
|
5.2 | P1 | This field will appear under Address section under Phone Number |
|
5.3 | P1 | OR: Use existing Phone Number field? |
|
Import File Differences
FR# | Pri | Description | Comments / Mockups |
|---|---|---|---|
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 |
|
6.3 | P1 | Other Party Info must also 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 |
|
6.4 | P1 | Changes to Transaction Party Details - no more taking of National ID - remove this functionality and ... |
|