This is the heart of the project as most of the services implemented will interact with the accounting journal. There is one main service which takes care of the different rules accross the countries, this module defines the content of a company's accounting journal.

Besides modules adding entries to the journal, there are also a bunch of applications which read from it so let's view the content of the main module.

The journal is the place where all events are written up for a company and it must contain all necessary elements to retrieve all required details. We will first list the mandatory entries of a journal for the account manager, then we will cover the table(s) and fields involved to finish with the main functions to implement in our module.

Following is a table showing the entries in the order for the journal in its XML or TXT format.

Order	Reference
1	JournalCode
2	JournalLib
3	EcritureNum
4	EcritureDate
5	CompteNum
6	CompteLib
7	CompAuxNum
8	CompAuxLib
9	PieceRef
10	PieceDate
11	EcritureLib
12	Debit
13	Credit
14	EcritureLet
15	DateLet
16	ValidDate
17	Montantdevise
18	Idevise

Here is the diagram showing the actions involved within the service.

Secondary actors can interact with the service to retrieve and treat information directly with the journal (ie: ERP services...)

A few classes to deal with :

The chart account references will match the ones defined within the Chart of Accounts service. A user won't be able to enter something different.

In france we have these codes :

FEC extension

The FEC extension defines a standard to display the above entry codes in the right order. For instance, the french government requires the following rules :

Legifrance.gouv

The FEC file generation will be dedicated to another service covering different formats.