Page tree
Skip to end of metadata
Go to start of metadata

a.Accepting Invoice

Seller and receiver compromise in point of using application response in transferring phase of invoice. After receiver attains the invoice, he organizes "ACCEPT" application response and delivers to seller. Acceptance process is completed. Seller keeps application response along with the invoice throughout legal safekeeping duration. 


Activity Diagram of Accepting Invoice 

Party

Activity

Definition

Seller

Drawing up invoice and sending

Seller sends the invoice to receiver

Receiver

Receiving invoice

Purchaser, receives the invoice

Receiver

Sending application response

Sends application response to seller regarding that he accepts the invoice

Seller

Receiving application response

Application response is received and recorded after it is matched with invoice


b.Refusing Invoice

In the event of refusing the e-invoice for various reasons, "REFUSAL" application response is drawn up and sent to seller. In case of refusal, the reason of it has to be written in General Descriptions field of application response. Seller must keep the application response along with the refused invoice throughout legal safekeeping duration. 

Figure 3. Activity Diagram of Refusing the Invoice 


Party

Activity

Definition

Seller

Drawing up and sending invoice

Seller sends invoice to receiver

Receiver

Receiving invoice

Receiver accepts the invoice

Receiver

Sending application response

Sends application response to seller regarding that he refused the invoice

Seller

Receiving application response

Application response is received and recorded after it is matched with invoice

Seller

Refusing application response

Application response is received after matched with refused invoice it is recorded. Can be protested through external manners.

Seller

Accepting application response

Necessary regulations are done and a new invoice can be drawn up



c.Drawing Up Return Invoice

"RETURN" type invoice can be drawn up by receiver in case Trading Scenario is applied.

Because of the reasons came up after recording the invoice to legal books by seller or receiver, in case of returning all of the material or some of them, receiver sends return invoice and "RETURN" application response, which contains returning reasons, to seller. Seller keeps application response along with the invoice throughout legal safekeeping duration. Return invoice is drawn up using return invoice option from invoice type field in "UBL-TR Invoice" type invoice. The date, number, universal singular defining number and returning reason of sales invoice (belonging to returned material) is written to "General Descriptions" of return invoice. 

Figure 4. Activity Diagram of Returning Invoice 
 

Party

Activity

Definition

Seller

Drawing up and sending invoice

Seller sends invoice to receiver

Receiver

Receiving invoice

Receiver accepts the invoice

Receiver

Sending application response

Application response is sent to seller in which returning reasons are written

Receiver

Sending return invoice

Materials are returned and return invoice is drawn up

Seller

Receiving return invoice with application response

Application response and return invoive is received and recorded.


Trading Invoice Scenario Work Flow



Figure 5. Trading Invoice Scenario Workflow (Envelope Flow Template) 

In trading invoice scenario, mail box has the right to "ACCEPT", "REFUSE" and "RETURN" the received invoice. 



  • No labels