v1.1.0 - UX Improvement for Handle Import Validation
Problem
User feels pain when trying to import excel data, as every failure to import has to be checked back to spreadsheet.
importing process also takes time and not user friendly
The following problems need to be addressed:
- Scenarios 3.1.S1 and 4.1.S1 only require screenshot and UI updates.
- The new flow for handling import failures is covered in scenarios 3.1.S2 and 4.1.S2.
- All failed scenarios need their error messages updated to align with scenarios 3.1.S2 and 4.1.S2.
Solution
- The system will support importing transaction data from CSV files.
- If the import process fails due to invalid or incomplete data, the system will save the uploaded data as a draft and display the import errors inside the application.
- Users can review and update the data directly in the app, then submit the corrected data again without having to modify and re-upload the original CSV file.
Features
| Feature | Description |
|---|---|
| 3. Chart of Accounts | Structured list of all accounts used by a company to record financial transactions. |
| 3.1. Import Chart of Account | Upload chart of account data in bulk (CSV/Excel). |
| 4. Journals | Transaction management features for recording and reviewing financial journals. |
| 4.1. Import Journal | Upload transaction data in bulk (CSV/Excel) to create journal entries automatically. |
Scenarios
3.1. Import Chart of Account
| 3.1.S Success Scenarios |
|---|
| 3.1.S1. User can import chart of accounts (COA) successfully. |
| 3.1.S2. User can fix failed import chart of accounts (COA) successfully. |
4.1. Import Journal
| 4.1.S Success Scenarios |
|---|
| 4.1.S1. User can import journals successfully. |
| 4.1.S2. User can fix failed import journals successfully. |