Business process elaboration – Order to payment : Différence entre versions
De Guide utilisateur des messages comptables UN/XML
| (23 révisions intermédiaires par le même utilisateur non affichées) | |||
| Ligne 16 : | Ligne 16 : | ||
[[Image:Use case e-Business and accounting (en).jpg|center|800px|]] | [[Image:Use case e-Business and accounting (en).jpg|center|800px|]] | ||
<br> | <br> | ||
| − | The use case shows when accounting and which accounts may be concerned at both trading partners | + | The use case shows when accounting and which accounts may be concerned at both trading partners. |
| + | |||
<br> | <br> | ||
| − | [[ | + | * [[Use case description – Accounting Token into the Order]] |
| − | + | * [[Use case description – Accounting Token into the Order confirmation]] | |
| − | + | * [[Use case description – Accounting Token into the Despatch Advice]] | |
| + | * [[Use case description – Accounting Token into the Normal invoice]] | ||
| + | * [[Use case description – Accounting Token into the Self Billing invoice]] | ||
| + | * [[Use case description – Accounting Token into the Remittance Advice]] | ||
| + | |||
| + | '''Element Identification''' | ||
| + | The elements below make up the Business Information Entity representing the Accounting Token based upon the existing ACC “Accounting Account. Details” as logged into Core Components Library 06B. | ||
| + | |||
| + | The BIE is repeated as many times as requested by the accounting procedure applied in the entity e.g. general account, sub account, cost accounting account, budget account, or account directly related to a specific amount on a document (e.g. insurance cost amount, additional invoice amount, transport amount, etc.) | ||
| + | |||
| − | + | {{gotoc|Jeton comptable}} | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Version actuelle en date du 28 juillet 2011 à 12:11
Scope
The process describes how customer and supplier can provide Accounting Token elements to enable automated generation of accounting entry from the e-document is used at each step in the supply chain.
Principles
From the earliest step, which is the Order from the customer, and the Order Confirmation of the supplier, the Accounting Token is encapsulated in each business documents.
The Order Confirmation is the required starting point of the Order process for the generation of the accounting entry, coherent with generally admitted accounting principles (GAAP).
Thus, an Order Change must always be followed by an Order Confirmation to allow the correct generation of the accounting entry reflecting the confirmed Order Change.
Use case: From Accounting Token into Order to Accounting Token into Payment
.jpg)
The use case shows when accounting and which accounts may be concerned at both trading partners.
- Use case description – Accounting Token into the Order
- Use case description – Accounting Token into the Order confirmation
- Use case description – Accounting Token into the Despatch Advice
- Use case description – Accounting Token into the Normal invoice
- Use case description – Accounting Token into the Self Billing invoice
- Use case description – Accounting Token into the Remittance Advice
Element Identification The elements below make up the Business Information Entity representing the Accounting Token based upon the existing ACC “Accounting Account. Details” as logged into Core Components Library 06B.
The BIE is repeated as many times as requested by the accounting procedure applied in the entity e.g. general account, sub account, cost accounting account, budget account, or account directly related to a specific amount on a document (e.g. insurance cost amount, additional invoice amount, transport amount, etc.)
