local:shop:structure:classes:bill

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
local:shop:structure:classes:bill [2018/02/16 12:07]
florence
local:shop:structure:classes:bill [2024/05/14 15:39] (current)
Line 1: Line 1:
-===== The Bill class : concept ​of order and bill statuses=====+<​html><​!-- nomoodle --></​html>​{{ :​logo-apl.png?​nolink |}}<​html><​!-- /nomoodle --></​html>​ 
 +===== The Bill class : Concept ​of order and bill statuses=====
 ===== Moodle Integrated Shop : Structural elements ===== ===== Moodle Integrated Shop : Structural elements =====
  
Line 5: Line 6:
 ====Introduction==== ====Introduction====
  
-**La facture est un objet regroupant l'​ensemble des éléments constituant ​: **+**The bill is an object that groups all the constituent parts of : **
  
-   Une commande, tant que le paiement n'est pas effectif+  ​A purchase orderas long as payment has not taken place. 
-   ​Une facture Proformatant que le lettrage avec la séquence comptable n'est pas effectif+  A pro forma billas long as no cross-reference coding has taken place
-   ​Une factureune fois lettrée avec la séquence comptable.+  A billonce cross-reference coding has taken place.
  
  
Line 16: Line 17:
 ==== Orders and bills in life cycle==== ==== Orders and bills in life cycle====
  
-Orders and bills have a life cycle determined by a status and transition engine.+Orders and bills have a life cycle that is determined by a status and transition engine.
  
 **Possible statuses include:** **Possible statuses include:**
Line 22: Line 23:
  
 ===IN PROGRESS:​=== ===IN PROGRESS:​===
-When a back office operator manually creates an order, it takes the In progress status.+When a back-office operator manually creates an order, it takes the In progress status.
  
 ===PLACED:​=== ===PLACED:​===
Line 28: Line 29:
  
 ===PENDIND :=== ===PENDIND :===
-Orders have been confirmed by the customer but payment used is offline or is delayed for an asynchronous response. Offline payments must be handled manually by a back office operator.+Orders have been confirmed by the customer but payment used is offline or is delayed for an asynchronous response. Offline payments must be handled manually by a back-office operator.
  
 ===PAID :=== ===PAID :===
-Bill has been paid in full because an online immediate method of payment was used or because it was marked as such by a back office operator after physical payment was received.+Bill has been paid in full because an online immediate method of payment was used or because it was marked as such by a back-office operator after physical payment was received.
  
 ===COMPLETED :===  ===COMPLETED :=== 
Line 37: Line 38:
  
 ===CANCELLED :=== ===CANCELLED :===
-Back office operators can cancel orders that have not yet been officially entered into accounting.+Back-office operators can cancel orders that have not yet been officially entered into accounting.
  
 ===FAILED :== ===FAILED :==
-These bills mark a failed online payment process. ​Le retour négatif de l'​interface de paiement ​des causes diversescomme par exemple une erreur de saisie du code bancaire par le clientun serveur bancaire trop occupé momentanément pour répondre la banque qui refuse le paiement, etc.+These bills mark a failed online payment process. ​There are many different reasons for negative response from the payment interfacesuch as a customer typing in the wrong bank code, a bank server momentarily too busy to respondthe bank declines payment, etc. 
  
 ===PAYBACK :=== ===PAYBACK :===
Line 46: Line 48:
  
 ===ALL:=== ===ALL:===
-Listing de toutes les facturesquelque soit leur état.+List of all billsregardless of their status.
  
  
local/shop/structure/classes/bill.1518779231.txt.gz · Last modified: 2024/04/04 15:50 (external edit)