User Story 1: Find Invoice
The user should be able to search invoices (Sales, Purchase etc..) in the system and be able to filter records based on invoice Id, status, invoice date, invoice description etc.. A link to the invoice should be provided w.r.t. each invoice coming in the result set, to navigate the user to a quick view of respective invoice.
Use Case Name | Find Invoice |
Actor | Account Manager |
Description | User should be able to search invoices (Sales, Purchase etc..) in the system. |
Trigger | The Account Manager accesses the accounting. |
Precondition | None. |
Basic Path |
|
Post-condition | User is able to Find Invoices. |
User Story 2: View Invoice
The user can navigate to an invoice detail view from search result set. The user should be able to review invoice for its Order, Customer / Vendor, Date, Due Date, Payment Applied, Items. The user should be able to generate PDF from invoice detail view for the corresponding invoice.
Use Case Name | View Invoice |
Actor | Account Manager |
Description | User should be able to search invoices (Sales, Purchase etc..) in the system. |
Trigger | The Account Manager accesses the accounting. |
Precondition | None. |
Basic Path |
|
Post-condition | User is able to view invoice details |
User Story 3: Update Invoice Status
Use Case Name | Update Invoice Status |
Actor | Account Manager |
Description | User should be able to update the invoice status of the system. |
Trigger | The Account Manager accesses the accounting. |
Precondition | None |
Basic Path |
|
Post-condition | User is able to update invoice status |
User Story 4: Create Payment
Use Case Name | Create Payment |
Actor | Account Manager |
Description | User should be able to create a new payment |
Trigger | The Account Manager accesses the accounting. |
Precondition | None |
Basic Path |
|
Post-condition | User is able to create a new payment. |
User Story 5: Find Payment
Use Case Name | FInd Payment |
Actor | Account Manager |
Description | User should be able to Find Payment in the system. |
Trigger | |
Precondition | NONE |
Basic Path |
|
Post-condition | User is able to Find Payments. |
User Story 6: View Payment
Use Case Name | View Payment |
Actor | Account Manager |
Description |
|
Trigger | The Account Manager accesses the accounting. |
Precondition | None |
Basic Path |
|
Post-condition | User is able to view payment status. |
User Story 7: Edit Payment
Use Case Name | Edit Payment |
Actor | Account Manager |
Description |
|
Trigger | The Account Manager accesses the accounting. |
Precondition | None |
Basic Path |
|
Post-condition | User is able to update payment details. |
User Story 8: Update Payment Status
The system should allow the user to update the status manually to 'Received' or 'Cancel'.
Use Case Name | Update Payment Status |
Actor | Account Manager |
Description |
|
Trigger | The Account Manager accesses the accounting. |
Precondition | None |
Basic Path |
|
Post-condition | User is able to update payment status. |