Laporan kustom

Odoo comes with a powerful and easy-to-use reporting framework. The engine allows you to create new reports, such as tax reports, or balance sheets and income statements with specific groupings and layouts.

Penting

Activate the developer mode to access the accounting report creation interface.

To create a new report, open the Accounting app and navigate to Configuration ‣ Accounting Reports. From here, you can either create a root report or a variant.

Root reports

Root report dapat dianggap sebagai laporan akuntansi yang netral dan umum. Mereka bertindak sebagai model pada mana versi akuntansi lokal akan dibangun. Bila laporan tidak memiliki root report, maka akan dianggap sebagai root report itu sendiri.

Example

Laporan pajak untuk Belgia dan AS akan masing-masing menggunakan versi umum yang sama sebagai dasar dan mengadaptasikannya untuk regulasi domestik.

When creating a new root report, you need to create a menu item for it. To do so, open the report and, on that same report, click the (Actions) icon, then select Create Menu Item. Refresh the page; the report is now available under Accounting ‣ Reporting.

Catatan

Kasus yang memerlukan pembuatan root report baru itu langka, seperti pada kasus di mana otoritas pajak negara memerlukan tipe laporan yang baru dan khusus.

Varian

Variant adalah versi khusus negara dari root report dan, oleh karena itu, selalu merujuk ke root report. Untuk membuat variant, pilih root report umum di field Root Report saat membuat laporan baru.

When a root report is opened from one of the accounting app's main menus, all its variants are displayed in the variant selector in the top right corner of the view.

Example

In the following image, VAT Report (BE) is the variant of the root Generic Tax report.

Report lines

After having created a report (either root or variant), you need to fill it with report lines. You can either create a new one by clicking on Add a line, or modify an existing report line by clicking on it. All report lines require a Name, and can have an optional additional Code (of your choice) if you wish to use their value in formulas.

Expression

Each report line can contain one or multiple expressions. Expressions can be seen as sub-variables needed by a report line. To create an expression, click on Add a line within a report line.

When creating an expression, you must attribute a Label used to refer to that expression. Therefore, it has to be unique among the expressions of each line. Both a Computation Engine and a Formula must also be indicated. The engine defines how your formula(s) and subformula(s) are interpreted. It is possible to mix expressions using different computation engines under the same line if you need to.

Catatan

Tergantung pada enginenya, subformula juga mungkin diperlukan.

'Odoo Domain' engine

With this engine, a formula is interpreted as an Odoo domain targeting account.move.line objects.

Subformula ini memungkinkan Anda untuk mendefinisikan bagaimana baris pergerakkan yang cocok dengan domain digunakan untuk menghitung nilai dari expression:

sum

Hasilnya adalah jumlah dari semua saldo dari baris pergerakkan yang cocok.

sum_if_pos

Hasilnya adalah jumlah dari semua saldo dari baris pergerakkan yang cocok bila jumlahnya positif. Bila tidak, adalah 0.

sum_if_neg

Hasilnya adalah jumlah dari semua saldo dari baris pergerakkan yang cocok bila jumlahnya negatif. Bila tidak, adalah 0.

count_rows

The result is the number of sub-lines of this expression. If the report line has a group-by value, this will correspond to the number of distinct grouping keys in the matched move lines. Otherwise, it will be the number of matched move lines.

You can also put a - sign at the beginning of the subformula to reverse the sign of the result.

'Tax Tags' engine

A formula made for this engine consists of a name used to match tax tags. If such tags do not exist when creating the expression, they will be created.

Saat mengevaluasi expression, perhitungan expression dapat secara kasar diekspresikan sebagai: (jumlah baris pergerakkan dengan tag + ) - (jumlah baris pergerakkan dengan tag - ).

Example

If the formula is tag_name, the engine matches tax tags +tag_name and -tag_name, creating them if necessary. To exemplify further: two tags are matched by the formula. If the formula is A, it will require (and create, if needed) tags +A and -A.

'Aggregate Other Formulas' engine

Use this engine when you need to perform arithmetic operations on the amounts obtained for other expressions. Formulas here are composed of references to expressions separated by one of the four basic arithmetic operators (addition +, subtraction -, division /, and multiplication *). To refer to an expression, type in its report line's code followed by a period . and the expression's label (ex. code.label).

Subformula dapat merupakan salah satu dari yang berikut:

if_above(CUR(amount))

Nilai dari ekspresi aritmetika akan dikembalikkan hanya bila lebih besar dari nilai yang disediakan sebelumnya. Bila tidak, hasilnya akan menjadi 0.

if_below(CUR(amount))

Nilai dari ekspresi aritmetika akan dikembalikkan hanya bila lebih kecil dari nilai yang disediakan sebelumnya. Bila tidak, hasilnya akan menjadi 0.

if_between(CUR1(amount1), CUR2(amount2))

Nilai dari ekspresi aritmetika akan dikembalikkan hanya bila di antara nilai yang disediakan sebelumnya. Bila tidak, hasilnya akan menjadi 0.

if_other_expr_above(LINE_CODE.EXPRESSION_LABEL, CUR(amount))

Nilai dari ekspresi aritmetika akan dikembalikkan hanya bila nilai ekspresi yang ditunjukkan oleh baris kode dan label expression lebih besar dari nilai yang disediakan sebelumnya. Bila tidak, hasilnya akan menjadi 0.

if_other_expr_below(LINE_CODE.EXPRESSION_LABEL, CUR(amount))

Nilai dari ekspresi aritmetika akan dikembalikkan hanya bila nilai ekspresi yang ditunjukkan oleh baris kode dan label expression lebih kecil dari nilai yang disediakan sebelumnya. Bila tidak, hasilnya akan menjadi 0.

CUR adalah kode mata uang yang huruf besar, dan jumlah adalah jumlah nilai yang diekspresikan dalam mata uang tersebut.

Anda juga dapat menggunakan subformula cross_report untuk mencocokkan expression yang ditemukan di laporan lain.

'Prefix of Account Codes' engine

This engine is used to match amounts made on accounts using the prefixes of these accounts' codes as variables in an arithmetic expression.

Example

21

Ekspresi aritmetika juga dapat merupakan satu awalan, seperti di sini.

Example

21 + 10 - 5

Formula ini menambahkan saldo dari baris-baris pergerakkan yang dibuat pada akun yang kodenya dimulai dengan 21 dan 10, dan mengurangi saldo dari mereka yang akunnya dimulai dengan 5.

Anda juga dapat mengabaikan pilihan sub-awalan.

Example

21 + 10\(101, 102) - 5\(57)

Formula ini juga bekerja dengan cara yang sama seperti contoh sebelumnya tapi mengabaikan awalan 101, 102, dan 57.

Anda dapat menerapkan 'sub-filter` pada kredit dan debit menggunakan akhiran C dan D. Pada kasus ini, akun hanya akan dianggap bila awalannya cocok, dan bila total saldo baris pergerakkan yang dibuat pada akun adalah kredit/debit.

Example

Akun 210001 memiliki saldo -42 dan akun 210002 memiliki saldo 25. Formula 21D hanya cocok dengan akun 210002, sehingga mengembalikkan 25. 210001 tidak cocok, karena saldonya adalah credit.

Pengecualian awalan dapat digabungkan dengan akhiran C dan D.

Example

21D + 10\(101, 102)C - 5\(57)

Formula ini menambahkan saldo dari baris-baris pergerakkan yang dibuat pada akun yang kodenya dimulai dengan 21 bila debit (D) dan menambahkan 10 bila kredit (C), tapi mengabaikan awalan 101, 102, dan mengurangi saldo dari akun dengan awalan 5, tapi mengabaikan awalan 57.

Untuk mencocokkan huruf C atau D di awalan dan tidak menggunakannya sebagai akhiran, gunakan pengecualian kosong ()`.

Example

21D\()

Formula ini mencocokkan akun yang kodenya dimulai dengan 21D, terlepas dari tanda saldo.

Di atas menggunakan awalan kode untuk mengikutsertakan akun, Anda juga dapat mencocokkan mereka dengan tag akun. Ini berguna terutama, sebagai contoh, bila negara Anda tidak memiliki standarisasi bagan akun, di mana awalan yang sama mungkin digunakan untuk tujuan yang berbeda di perusahaan.

Example

tag(25)

This formula matches accounts whose associated tags contain the one with id 25.

If the tag you reference is defined in a data file, an xmlid can be used instead of the id.

Example

tag(my_module.my_tag)

This formula matches accounts whose associated tags include the tag denoted by my_module.my_tag.

You can also use arithmetic expressions with tags, possibly combining them with prefix selections.

Example

tag(my_module.my_tag) + tag(42) + 10

The balances of accounts tagged as my_module.my_tag will be summed with those of accounts linked to the tag with ID 42 and accounts with the code prefix 10

C and D suffixes can be used in the same way with tags.

Example

tag(my_module.my_tag)C

This formula matches accounts with the tag my_module.my_tag and a credit balance.

Prefix exclusion also works with tags.

Example

tag(my_module.my_tag)\(10)

This formula matches accounts with the tag my_module.my_tag and a code not starting with 10.

'External Value' engine

The 'external value' engine is used to refer to manual and carryover values. Those values are not stored using account.move.line, but with account.report.external.value. Each of these objects directly points to the expression it impacts, so very little needs to be done about their selection here.

Formulas can be one of the following:

sum

If the result must be the sum of all the external values in the period.

most_recent

If the result must be the value of the latest external value in the period.

In addition, subformulas can be used in two ways:

rounding=X

Replacing X with a number instructs to round the amount to X decimals.

editable

Indicates this expression can be edited manually, triggering the display of an icon in the report, allowing the user to perform this action.

Catatan

Manual values are created at the date_to currently selected in the report.

Both subformulas can be mixed by separating them with a ;.

Example

editable;rounding=2

is a correct subformula mixing both behaviors.

'Custom Python Function' engine

This engine is a means for developers to introduce custom computation of expressions on a case-by-case basis. The formula is the name of a python function to call, and the subformula is a key to fetch in the dictionary returned by this function. Use it only if you are making a custom module of your own.

Kolom

Reports can have an indefinite number of columns to display. Each column gets its values from the expressions declared on the lines. The field expression_label of the column gives the label of the expressions whose value is displayed. If a line has no expression in that field, then nothing is displayed for it in this column. If multiple columns are required, you must use different expression labels.

When using the period comparison feature found under the Options tab of an accounting report, all columns are repeated in and for each period.

Line grouping

Non-standard grouping is possible by adding or using existing fields on the Journal Item model, provided that the fields are related and non-stored.

Catatan

Grouping lines requires the report to have explicit report lines that can be edited. The deferred reports, for example, do not support grouping lines as they use dynamic lines that are generated.

Create a new field on journal item

To create a non-stored, related field in the Journal Item model, first go to Accounting ‣ Journal Items, and click the (bug) icon, then click Fields. Click New to create a new field, and complete the following fields:

• Field Name: a technical name for the field

• Field Label: the label to be displayed for the field

• Field Type: the type of field that this related field should point to

• Stored: Leave this field unchecked as only non-stored fields can be used to group lines.

• Related Model: If the field type is one2many, many2many, or many2one, select the model of the original field to group by.

• Related Field Definition: the technical path to the field you want to group by

  Example

  To group by the sales team of the commercial partner, set the related field definition to move_id.team_id.

Group lines

To group lines, go to the Lines tab of the desired report, click on the line you want to group, and edit the Group by field. Enter the technical name (Field Name) of the field to use as the grouping key.

Tip

To find a list of all the model's fields and their technical names, go to Accounting ‣ Journal Items, and click the (bug) icon, then click Fields. The technical name of each field is listed in the Field Name column.

Lihat juga

Consolidation via grouping by account code

Custom tax report setup

Report configuration

Tip

All technical terms and functions of Odoo's reports engine are explained in the previous sections of this page. We strongly recommend reading these sections before setting up a custom tax report.

To create a custom tax report, open the Accounting app, navigate to Configuration ‣ Accounting Reports, then click New:

• Enter a name for your report.

• Select a Root Report.

• Under the Availability field, select Country Matches, then select the Country matching your company.

Next, create a report line by clicking the Add a line. Once created, click that report line to configure it:

• Click Add a line again to create an Expression and name it.

• In the Definition tab, select a Computation Engine for that expression depending on the following scenarios:

Scenario A (Tax grids)Scenario B (No tax grids)Scenario C (Advanced Engines)

In this scenario, your company uses tax grids:

• Select Tax Tags as the computation engine. Odoo uses this field to link the report line to your taxes.

• In the Formula field, type your short grid identifier (e.g., vat_sales_base). Odoo automatically generates the + and - variants of this tag for you to map inside Configuration ‣ Taxes.

• In the Subformula field, enter either base to report the untaxed amount, or tax to report the actual tax amount collected/paid.

Repeat this process as necessary. Then, Save & Close.

Alternatively, you can:

• Select Aggregate Other Formulas as the computation engine. Odoo uses this field to perform math on lines already present in the report rather than scanning raw transactions.

• In the Formula field, use basic algebra referencing your line codes (e.g., LINE_10 - LINE_20).

Repeat this process as necessary. Then, Save & Close.

In the Options tab of an Expression, populate the Carry Over To field with a formula to always carry over balances or only carry them over when the amount is negative. Leave this field blank if you do not want to use this feature.

Example

if_below(EUR(0))

This formula will only carry over amounts below 0.00 EUR.

Tax configuration

Next, go to Configuration ‣ Taxes and click New to create and configure new taxes for your custom tax report. Create your Sales and Purchases taxes, and populate the Tax Grids for all taxes using the matching tax grids you created earlier. Finally, make sure to specify both a tax payable and tax receivable account for each tax.

Example

Closing entry

To close taxes, a tax group must be specified on each tax used in your custom tax report. To do this, open the Accounting app, navigate to Configuration ‣ Taxes, open a tax that requires a tax group, click the Advanced Options tab, and select a group in the Tax Group field. Once assigned, click the (right arrow) icon and set both a Tax Payable Account and a Tax Receivable Account.

Tip

• When everything has been set up, make sure to test your report by creating invoices, bills, and credit notes using the taxes specific to that report. Finally, test the closing entry itself.

• If you want to hide a specific account from displaying in the tax closing entry, go to Configuration ‣ Taxes, select the tax, and click the (settings adjust) icon. From there, check the Tax Closing Entry box to adjust its visibility.

Lihat juga

Tax closing