Difference between revisions of "Alkimia/Usecases/payment"

Jump to: navigation, search
(Payment Detection Use Case)
 
Line 1: Line 1:
PAYMENT DETECTION
+
==PAYMENT DETECTION==
INTRODUCTION
+
====INTRODUCTION====
 
As soon KMyMoney or Skrooge becomes aware of an incoming payment, either through online banking or manual entry, it should
 
As soon KMyMoney or Skrooge becomes aware of an incoming payment, either through online banking or manual entry, it should
 
1. try to detect an unique identifier
 
1. try to detect an unique identifier
Line 9: Line 9:
 
Elena issues an invoice with Kraft over 364 Euro, due in 10 days. She marks the invoice to be sent in Kraft. In KMyMoney and Skrooge the amount of 364 Euro shows up as expected money together with the document id number, date and addressee of the invoice. Four days later, Elena checks the accounts via online banking. One transaction record contains the document id and the finance manager asks Elena if she can confirm that this is the money paying the invoice. She confirms that.\\Next time she starts Kraft she sees that the invoice is marked as payed.
 
Elena issues an invoice with Kraft over 364 Euro, due in 10 days. She marks the invoice to be sent in Kraft. In KMyMoney and Skrooge the amount of 364 Euro shows up as expected money together with the document id number, date and addressee of the invoice. Four days later, Elena checks the accounts via online banking. One transaction record contains the document id and the finance manager asks Elena if she can confirm that this is the money paying the invoice. She confirms that.\\Next time she starts Kraft she sees that the invoice is marked as payed.
  
ACTORS
+
====ACTORS====
 
1. USER
 
1. USER
 
2. Finance Manager
 
2. Finance Manager
PRECONDITIONS
+
====PRECONDITIONS====
 
1. must have an installed financial manager.
 
1. must have an installed financial manager.
 
2. law requirements must met for document identifier of the incoming voice.
 
2. law requirements must met for document identifier of the incoming voice.
 
3. The coming invoice must have a unique identifier attached to it.
 
3. The coming invoice must have a unique identifier attached to it.
BASIC FLOW
+
====BASIC FLOW====
 
1. open the list of unchecked invoices.
 
1. open the list of unchecked invoices.
 
2. check the unique identifier any of the invoice and see which document type it is.
 
2. check the unique identifier any of the invoice and see which document type it is.
Line 22: Line 22:
 
4. If the user validates it then mark the payment to be received.
 
4. If the user validates it then mark the payment to be received.
 
5. update the changes.
 
5. update the changes.
ALTERNATE FLOW
+
====ALTERNATE FLOW====
 
1. If the user says the unique identifier is invalid, then send the invoice to a “ invalid invoices" folder
 
1. If the user says the unique identifier is invalid, then send the invoice to a “ invalid invoices" folder
  
Line 29: Line 29:
  
  
USE CASE DIAGRAM
+
====USE CASE DIAGRAM====

Revision as of 13:49, 3 June 2011

PAYMENT DETECTION

INTRODUCTION

As soon KMyMoney or Skrooge becomes aware of an incoming payment, either through online banking or manual entry, it should 1. try to detect an unique identifier 2. validate if there is an expected payment filed with this unique identifier 3. if so, let the user validate if the detection is correct (optional) 4. mark the payment to be received Example: Elena issues an invoice with Kraft over 364 Euro, due in 10 days. She marks the invoice to be sent in Kraft. In KMyMoney and Skrooge the amount of 364 Euro shows up as expected money together with the document id number, date and addressee of the invoice. Four days later, Elena checks the accounts via online banking. One transaction record contains the document id and the finance manager asks Elena if she can confirm that this is the money paying the invoice. She confirms that.\\Next time she starts Kraft she sees that the invoice is marked as payed.

ACTORS

1. USER 2. Finance Manager

PRECONDITIONS

1. must have an installed financial manager. 2. law requirements must met for document identifier of the incoming voice. 3. The coming invoice must have a unique identifier attached to it.

BASIC FLOW

1. open the list of unchecked invoices. 2. check the unique identifier any of the invoice and see which document type it is. 3. Ask user if the expected payment is filed with the unique identifier. 4. If the user validates it then mark the payment to be received. 5. update the changes.

ALTERNATE FLOW

1. If the user says the unique identifier is invalid, then send the invoice to a “ invalid invoices" folder



USE CASE DIAGRAM


Content is available under Creative Commons License SA 4.0 unless otherwise noted.