Marathon Documentation - User contributions [en]

News:Changes to ISO payment file format

2026-05-20T11:28:39Z

VJ:

<translate>

{{News
|Changes to ISO payment file formats SEB SE and Deutsche Bank NL
|module=Accounting
|group=Payments
|version=546W2605
|revision=0
|case=CORE-8079
|published=2026-05-20
}}


Changes to ISO payment file formats SEB SE and Deutsche Bank NL


Due to new requirements for the pain.001.001.03 payment file format we have made adaptations to the existing payment file formats for SEB Sweden and Deutsche Bank NL.


The new requirements are to atleast include the Town of the the Supplier.


This means that all Suppliers, including Supplier you have to pay out expenses, needs to have atleast the town registered in the Town/City field.


This is a global requirement and more updates of the pain.001.001.03 payment formats for other banks will be done continuously by us during 2026.

</translate>

News:Changes to ISO payment file format

2026-05-20T11:18:58Z

VJ: Marked this version for translation

<translate>

{{News
|Changes to ISO payment file formats SEB SE and Deutsche Bank NL
|module=Accounting
|group=Payments
|version=546
|revision=43118
|case=1028301
|published=2018-05-31
}}


Changes to ISO payment file formats SEB SE and Deutsche Bank NL


Due to new requirements for the pain.001.001.03 payment file format we have made adaptations to the existing payment file formats for SEB Sweden and Deutsche Bank NL.


The new requirements are to atleast include the Town of the the Supplier.


This means that all Suppliers, including Supplier you have to pay out expenses, needs to have atleast the town registered in the Town/City field.


This is a global requirement and more updates of the pain.001.001.03 payment formats for other banks will be done continuously by us during 2026.

</translate>

News:Changes to ISO payment file format

2026-05-20T11:18:48Z

VJ: Created page with "<translate> {{News |Changes to ISO payment file formats SEB SE and Deutsche Bank NL |module=Accounting |group=Payments |version=546 |revision=43118 |case=1028301 |published=20..."

<translate>
{{News
|Changes to ISO payment file formats SEB SE and Deutsche Bank NL
|module=Accounting
|group=Payments
|version=546
|revision=43118
|case=1028301
|published=2018-05-31
}}

Changes to ISO payment file formats SEB SE and Deutsche Bank NL

Due to new requirements for the pain.001.001.03 payment file format we have made adaptations to the existing payment file formats for SEB Sweden and Deutsche Bank NL.

The new requirements are to atleast include the Town of the the Supplier.

This means that all Suppliers, including Supplier you have to pay out expenses, needs to have atleast the town registered in the Town/City field.

This is a global requirement and more updates of the pain.001.001.03 payment formats for other banks will be done continuously by us during 2026.

</translate>

News:New Voucher sequence

2026-05-20T10:24:34Z

VJ: Marked this version for translation

<translate>

{{News
|New Voucher sequence
|module=Accounting
|group=Vouchers
|version=546W2605
|revision=0
|case=CORE-7981
|published=2026-05-20
}}


New Voucher sequence


We have added a new Voucher sequence: Vx.


The voucher sequence is meant to be used for the autogenerated vouchers that by default is placed in the Bx sequence.


It is optional to use the new voucher sequence, and also optional to use the voucher with only some specific functions of the available ones mentioned below.


Since the voucher sequence differs from the Bx sequence, and is for autogenerated vouchers, no approval process is in place.


To set up the new Voucher sequence, go to ''Accounting|Backoffice|Base registers|Voucher sequences'' and create a new series.


The naming convention of the vouchers are from VA-VZ and V0-V9.


The new Voucher sequence is usable for the following functions and settings:


Book away discrepancies.


The voucher sequence needs to be added to the parameter Voucher type for book-away and pending discr in ''Media|Backoffice|Base registers|Parameters, tab Reconcilation''.


With it set, the generated vouchers for booked away discrepancies in the Reconcilation function will be placed in the Vx voucher.


{{ExpandImage|voucher_vseries_book_away_parameter.png}}


Revaluation of invoices.


In the selection before doing the printout. The generated voucher is in the set sequence.


{{ExpandImage|voucher_vseries_revaluation_function.png}}


Clearing of accounts.


The Voucher sequence is added in the parameters in ''Accounting|Backoffice|Base registers|General ledger|Parameters''.


With it set, the generated vouchers from the Clearing of accounts function is placed in the Vx sequence.


{{ExpandImage|voucher_vseries_clearing_parameter.png}}


Disposals and Depriciations.


A parameter has been added in ''Accounting|Backoffice|Base registers|Inventory ledger|Parameters''.


The parameter affects both Disposals and Depriciations. With the parameter set, the generated vouchers from the Disposals and Depriciations functions are placed in the Vx sequence.


{{ExpandImage|voucher_vseries_dispose_depric_parameter.png}}


Update periodical allocations.


A new parameter has been added in ''Accounting|Backoffice|Base registers|General ledger|Parameters, tab Registration''.


With the parameter set, the generated vouchers from the Update periodical allocations funtion will be placed in the Vx sequence.


{{ExpandImage|voucher_vseries_periodical_parameter.png}}

</translate>

News:New Voucher sequence

2026-05-20T10:24:21Z

VJ: Created page with "<translate> {{News |New Voucher sequence |module=Accounting |group=Vouchers |version=546W2605 |revision=0 |case=CORE-7981 |published=2026-05-20 }} New Voucher sequence..."

<translate>
{{News
|New Voucher sequence
|module=Accounting
|group=Vouchers
|version=546W2605
|revision=0
|case=CORE-7981
|published=2026-05-20
}}

New Voucher sequence

We have added a new Voucher sequence: Vx.

The voucher sequence is meant to be used for the autogenerated vouchers that by default is placed in the Bx sequence.

It is optional to use the new voucher sequence, and also optional to use the voucher with only some specific functions of the available ones mentioned below.

Since the voucher sequence differs from the Bx sequence, and is for autogenerated vouchers, no approval process is in place.

To set up the new Voucher sequence, go to ''Accounting|Backoffice|Base registers|Voucher sequences'' and create a new series.

The naming convention of the vouchers are from VA-VZ and V0-V9.

The new Voucher sequence is usable for the following functions and settings:

Book away discrepancies.

The voucher sequence needs to be added to the parameter Voucher type for book-away and pending discr in ''Media|Backoffice|Base registers|Parameters, tab Reconcilation''.

With it set, the generated vouchers for booked away discrepancies in the Reconcilation function will be placed in the Vx voucher.

{{ExpandImage|voucher_vseries_book_away_parameter.png}}

Revaluation of invoices.

In the selection before doing the printout. The generated voucher is in the set sequence.

{{ExpandImage|voucher_vseries_revaluation_function.png}}

Clearing of accounts.

The Voucher sequence is added in the parameters in ''Accounting|Backoffice|Base registers|General ledger|Parameters''.

With it set, the generated vouchers from the Clearing of accounts function is placed in the Vx sequence.

{{ExpandImage|voucher_vseries_clearing_parameter.png}}

Disposals and Depriciations.

A parameter has been added in ''Accounting|Backoffice|Base registers|Inventory ledger|Parameters''.

The parameter affects both Disposals and Depriciations. With the parameter set, the generated vouchers from the Disposals and Depriciations functions are placed in the Vx sequence.

{{ExpandImage|voucher_vseries_dispose_depric_parameter.png}}

Update periodical allocations.

A new parameter has been added in ''Accounting|Backoffice|Base registers|General ledger|Parameters, tab Registration''.

With the parameter set, the generated vouchers from the Update periodical allocations funtion will be placed in the Vx sequence.

{{ExpandImage|voucher_vseries_periodical_parameter.png}}

</translate>

File:Voucher vseries book away parameter.png

2026-05-20T10:18:45Z

VJ:

File:Voucher vseries revaluation function.png

2026-05-20T10:18:34Z

VJ:

File:Voucher vseries clearing parameter.png

2026-05-20T10:18:25Z

VJ:

File:Voucher vseries periodical parameter.png

2026-05-20T10:18:16Z

VJ:

File:Voucher vseries dispose depric parameter.png

2026-05-20T10:18:08Z

VJ:

News:Block collective group in Media

2026-04-21T12:01:59Z

VJ: Created page with "<translate>  {{News |Block Collective group in Media |module=Media |group=Base registers |version=546W2602 |revision=0 |case=CORE-7751 |published=2026-02-24 }} <!--..."

<translate>

{{News
|Block Collective group in Media
|module=Media
|group=Base registers
|version=546W2602
|revision=0
|case=CORE-7751
|published=2026-02-24
}}


Block Collective group in Media


We have added the possibility of blocking Collective groups in Media, as well as adding a Only active in the list of Collective groups.


{{ExpandImage|med_block_collective_group.png}}

</translate>

File:Med block collective group.png

2026-04-20T12:38:19Z

VJ:

News:New functionality in Table registration

2026-04-17T09:29:06Z

VJ: Marked this version for translation

<translate>

{{News
|New functionality in Table registration
|module=Media
|group=Media plans
|version=546W2604
|revision=0
|case=CORE-8017
|published=2026-04-17
}}


New functionality in Table registration


Some new functionality has been added to the Table registration function.


Surcharges (meaning pricerows without a Default surcharge code) are now deleted when the amount is changed to 0.


Another new functionality is related to discounts.


In the template there is now the possibility to Lock discount.


With that activated, if a sum in Gross or Net is changed, the Discount remains unchanged.


Note that the Lock discount is applied to the whole Table template meaning that all possible values in the Discount column are locked.


{{ExpandImage|med_tr_lock_discount.png}}

</translate>

News:New functionality in Table registration

2026-04-17T09:28:48Z

VJ: Created page with "<translate> {{News |New functionality in Table registration |module=Media |group=Media plans |version=546W2604 |revision=0 |case=CORE-8017 |published=2026-04-17 }} New fun..."

<translate>
{{News
|New functionality in Table registration
|module=Media
|group=Media plans
|version=546W2604
|revision=0
|case=CORE-8017
|published=2026-04-17
}}

New functionality in Table registration

Some new functionality has been added to the Table registration function.

Surcharges (meaning pricerows without a Default surcharge code) are now deleted when the amount is changed to 0.

Another new functionality is related to discounts.

In the template there is now the possibility to Lock discount.

With that activated, if a sum in Gross or Net is changed, the Discount remains unchanged.

Note that the Lock discount is applied to the whole Table template meaning that all possible values in the Discount column are locked.

{{ExpandImage|med_tr_lock_discount.png}}

</translate>

File:Med tr lock discount.png

2026-04-17T09:24:52Z

VJ:

News:Date format on exports from Marathon

2026-04-15T14:34:17Z

VJ: Marked this version for translation

<translate>

{{News
|Date formats on exports from Marathon
|module=System
|group=Base registers
|version=546W2604
|revision=0
|case=CORE-8021
|published=2026-04-15
}}


Date formats on exports from Marathon


A change has been made so that exports from lists in Marathon done via the Export button or right click + spreadsheet, disregards the date format
in Marathon and uses the local date format used on the users computer.

</translate>

News:Date format on exports from Marathon

2026-04-15T14:34:05Z

VJ: Created page with "<translate> {{News |Date formats on exports from Marathon |module=System |group=Base registers |version=546W2604 |revision=0 |case=CORE-8021 |published=2026-04-15 }} Date..."

<translate>
{{News
|Date formats on exports from Marathon
|module=System
|group=Base registers
|version=546W2604
|revision=0
|case=CORE-8021
|published=2026-04-15
}}

Date formats on exports from Marathon

A change has been made so that exports from lists in Marathon done via the Export button or right click + spreadsheet, disregards the date format
in Marathon and uses the local date format used on the users computer.

</translate>

News:Net net column in Client invoices and Book discrepancies

2026-04-15T14:20:11Z

VJ: Marked this version for translation

<translate>

{{News
|Net-net column in Client invoices and Book discrepancies, Reconiliation tab
|module=Media
|group=Media plans
|version=546W2604
|revision=0
|case=CORE-7918
|published=2026-04-15
}}


Net-net column in Client invoices and Book discrepancies, Reconciliation tab


We have added a column for Net-net in the Client invoices and Book discrepancies sections in Reconciliation on an Order or Insertion in Media|Media plans.


{{ExpandImage|Med_net_net_column_reconciliation_order.png}}

</translate>

News:Net net column in Client invoices and Book discrepancies

2026-04-15T14:20:00Z

VJ: Created page with "<translate> {{News |Net-net column in Client invoices and Book discrepancies, Reconiliation tab |module=Media |group=Media plans |version=546W2604 |revision=0 |case=CORE-7918..."

<translate>
{{News
|Net-net column in Client invoices and Book discrepancies, Reconiliation tab
|module=Media
|group=Media plans
|version=546W2604
|revision=0
|case=CORE-7918
|published=2026-04-15
}}

Net-net column in Client invoices and Book discrepancies, Reconciliation tab

We have added a column for Net-net in the Client invoices and Book discrepancies sections in Reconciliation on an Order or Insertion in Media|Media plans.

{{ExpandImage|Med_net_net_column_reconciliation_order.png}}

</translate>

File:Med net net column reconciliation order.png

2026-04-15T14:19:12Z

VJ:

News:Batch change Cost centre and Cost objects as Inactive

2026-04-15T14:13:34Z

VJ: Marked this version for translation

<translate>

{{News
|Batch change Cost centre and Cost objects as Inactive
|module=Accounting
|group=Base registers
|version=546W2604
|revision=0
|case=CORE-7953
|published=2026-04-15
}}


Batch change Cost centre and Cost objects as Inactive


It is now possible to mark several Cost centres and Cost objects as inactive via Batch change.

</translate>

News:Batch change Cost centre and Cost objects as Inactive

2026-04-15T14:13:23Z

VJ: Created page with "<translate> {{News |Batch change Cost centre and Cost objects as Inactive |module=Accounting |group=Base registers |version=546W2604 |revision=0 |case=CORE-7953 |published=202..."

<translate>
{{News
|Batch change Cost centre and Cost objects as Inactive
|module=Accounting
|group=Base registers
|version=546W2604
|revision=0
|case=CORE-7953
|published=2026-04-15
}}

Batch change Cost centre and Cost objects as Inactive

It is now possible to mark several Cost centres and Cost objects as inactive via Batch change.

</translate>

News:Mark Staff categories as inactive

2026-03-13T13:19:40Z

VJ: Marked this version for translation

<translate>

{{News
|Mark Staff categories as inactive
|module=Project
|group=Base registers
|version=546W2603
|revision=0
|case=CORE-7875
|published=2026-03-13
}}


Mark Staff categories as inactive


Staff categories are now possible to be marked as inactive.


We have also added an Only active filter to the list Staff categories in Project|Backoffice|Base registers|Staff categories


{{ExpandImage|Pro_staff_categories_active.png}}


{{ExpandImage|Pro_staff_categories_active_list.png}}

</translate>

News:Mark Staff categories as inactive

2026-03-13T13:18:59Z

VJ: Created page with "<translate> {{News |Mark Staff categories as inactive |module=Project |group=Base registers |version=546W2603 |revision=0 |case=CORE-7875 |published=2026-03-13 }} Mark Sta..."

<translate>
{{News
|Mark Staff categories as inactive
|module=Project
|group=Base registers
|version=546W2603
|revision=0
|case=CORE-7875
|published=2026-03-13
}}

Mark Staff categories as inactive

Staff categories are now possible to be marked as inactive.

We have also added an Only active filter to the list Staff categories in Project|Backoffice|Base registers|Staff categories

{{ExpandImage|Pro_staff_categories_active.png}}

{{ExpandImage|Pro_staff_categories_active_list.png}}

</translate>

File:Pro staff categories active list.png

2026-03-13T13:16:53Z

VJ:

File:Pro staff categories active.png

2026-03-13T13:16:44Z

VJ:

News:Block code change functions

2026-03-13T12:54:47Z

VJ: Marked this version for translation

<translate>

{{News
|Block code change functions
|module=System
|group=Base registers
|version=546W2603
|revision=0
|case=CORE-7792
|published=2026-03-13
}}


Block code change functions


We have implemented an improvement in Marathon related to how codes are used in the system.


Codes are used in databases to create references between different tables.


For example, a project manager on a project is indicated by registering the employee code in the project manager field.


In many systems, internal codes that are not visible to the user are used. In Marathon, we have chosen to work with visible codes—partly to enable quick registration of references for those who know the code by heart, and partly to be able to display information in a more compact and clear format in tables with many columns.


Since codes are also used for references from our BI system, our new function Engage, and other external systems, it is important that they are stable and consistent.


To ensure that no references risk pointing incorrectly in the future, we will therefore remove the possibility to change existing codes in Marathon.


This change strengthens data quality and contributes to a more robust and reliable overall solution in a world with increasing interaction between different systems.


When the ability to control the codes decreases, a minor adjustment in the way of working may be needed.


At the same time, it opens up for a more user-friendly, modern, and consistent way of working in the system.


Instead of entering a code directly into a field, we recommend that you use the quick search function, which searches by names.


This makes the registration both smoother and more intuitive, especially when a code is not remembered.


Similarly, we recommend that you choose to display names instead of codes in tables wherever possible.


This provides a clearer and more readable overview.


Change code is blocked in the following registers:


Project|Backoffice|Base registers: Employees, Clients & Projects, Fee codes, Purchase codes and Other codes.


Media|Backoffice|Base registers: Clients, Agreements and Media.


Accounting|Backoffice|Base registers: Suppliers and Asset types.

</translate>

News:Block code change functions

2026-03-13T12:54:37Z

VJ: Created page with "<translate> {{News |Block code change functions |module=System |group=Base registers |version=546W2603 |revision=0 |case=CORE-7792 |published=2026-03-13 }} Block code chan..."

<translate>
{{News
|Block code change functions
|module=System
|group=Base registers
|version=546W2603
|revision=0
|case=CORE-7792
|published=2026-03-13
}}

Block code change functions

We have implemented an improvement in Marathon related to how codes are used in the system.

Codes are used in databases to create references between different tables.

For example, a project manager on a project is indicated by registering the employee code in the project manager field.

In many systems, internal codes that are not visible to the user are used. In Marathon, we have chosen to work with visible codes—partly to enable quick registration of references for those who know the code by heart, and partly to be able to display information in a more compact and clear format in tables with many columns.

Since codes are also used for references from our BI system, our new function Engage, and other external systems, it is important that they are stable and consistent.

To ensure that no references risk pointing incorrectly in the future, we will therefore remove the possibility to change existing codes in Marathon.

This change strengthens data quality and contributes to a more robust and reliable overall solution in a world with increasing interaction between different systems.

When the ability to control the codes decreases, a minor adjustment in the way of working may be needed.

At the same time, it opens up for a more user-friendly, modern, and consistent way of working in the system.

Instead of entering a code directly into a field, we recommend that you use the quick search function, which searches by names.

This makes the registration both smoother and more intuitive, especially when a code is not remembered.

Similarly, we recommend that you choose to display names instead of codes in tables wherever possible.

This provides a clearer and more readable overview.

Change code is blocked in the following registers:

Project|Backoffice|Base registers: Employees, Clients & Projects, Fee codes, Purchase codes and Other codes.

Media|Backoffice|Base registers: Clients, Agreements and Media.

Accounting|Backoffice|Base registers: Suppliers and Asset types.

</translate>

News:Cost centre group as multi select and column selection in Accounting reports

2026-03-13T10:15:13Z

VJ: Marked this version for translation

<translate>

{{News
|Cost centre group as multi select and column in Accounting reports
|module=Accounting
|group=Reports
|version=546W2603
|revision=0
|case=CORE-7948
|published=2026-03-13
}}


Cost centre group as multi select and column selection in Accounting reports


We have made the field Cost centre group a multi select option in Accounting reports, where it previously was a single choice field.


We have also added the possibility for column selection on Cost centre groups via Column templates.


For the selection to work, there can not exist a Cost centre with the same code as the Cost centre group.


Column selection on CC/CCG XXX is done like 61/XXX in Op1 in the column template.

</translate>

News:Cost centre group as multi select and column selection in Accounting reports

2026-03-13T10:15:09Z

VJ: Created page with "<translate> {{News |Cost centre group as multi select and column in Accounting reports |module=Accounting |group=Reports |version=546W2603 |revision=0 |case=CORE-7948 |publish..."

<translate>
{{News
|Cost centre group as multi select and column in Accounting reports
|module=Accounting
|group=Reports
|version=546W2603
|revision=0
|case=CORE-7948
|published=2026-03-13
}}

Cost centre group as multi select and column selection in Accounting reports

We have made the field Cost centre group a multi select option in Accounting reports, where it previously was a single choice field.

We have also added the possibility for column selection on Cost centre groups via Column templates.

For the selection to work, there can not exist a Cost centre with the same code as the Cost centre group.

Column selection on CC/CCG XXX is done like 61/XXX in Op1 in the column template.

</translate>

News:New column in Groups

2026-02-25T09:13:32Z

VJ: Marked this version for translation

<translate>

{{News
|New column in Groups
|module=Project
|group=Base registers
|version=546W2602
|revision=0
|case=CORE-7702
|published=2026-02-25
}}


New column in Groups


A new column has been added in Project|Backoffice|Base registers, Groups.


The new column displays the company code added in the field Company in G/L,P/L and S/L.


{{ExpandImage|Pro_column_kam_ftg.png}}

</translate>

News:New column in Groups

2026-02-25T09:13:23Z

VJ: Created page with "<translate> {{News |New column in Groups |module=Project |group=Base registers |version=546W2602 |revision=0 |case=CORE-7702 |published=2026-02-25 }} New column in Groups<..."

<translate>
{{News
|New column in Groups
|module=Project
|group=Base registers
|version=546W2602
|revision=0
|case=CORE-7702
|published=2026-02-25
}}

New column in Groups

A new column has been added in Project|Backoffice|Base registers, Groups.

The new column displays the company code added in the field Company in G/L,P/L and S/L.

{{ExpandImage|Pro_column_kam_ftg.png}}

</translate>

File:Pro column kam ftg.png

2026-02-25T09:12:52Z

VJ:

News:Kiwibank file format

2026-02-24T16:02:56Z

VJ: Marked this version for translation

<translate>

{{News
|Kiwibank file format
|module=Accounting
|group=Payments
|version=546W2602
|revision=0
|case=CORE-7846
|published=2026-02-24
}}


Kiwibank file format


We have developed the possibility to create payment files compatible with the New Zealand bank Kiwibank's format.


The file format is a standard setting for New Zealand Marathon clients.

</translate>

News:Kiwibank file format

2026-02-24T16:02:49Z

VJ: Created page with "<translate> {{News |Kiwibank file format |module=Accounting |group=Payments |version=546W2602 |revision=0 |case=CORE-7846 |published=2026-02-24 }} Kiwibank file format..."

<translate>
{{News
|Kiwibank file format
|module=Accounting
|group=Payments
|version=546W2602
|revision=0
|case=CORE-7846
|published=2026-02-24
}}

Kiwibank file format

We have developed the possibility to create payment files compatible with the New Zealand bank Kiwibank's format.

The file format is a standard setting for New Zealand Marathon clients.

</translate>

News:Naming of credit classes in Project

2026-02-24T14:41:52Z

VJ: Marked this version for translation

<translate>

{{News
|Naming of Credit classes in Project
|module=Project
|group=Base registers
|version=546W2602
|revision=0
|case=CORE-7712
|published=2026-02-24
}}


Naming of Credit classes in Project


We have added the existing functionality for naming Credit classes in Media, to Credit classes in Project.


The fields for naming the Credit classes is in Project|Backoffice|Base registers|Parameters, tab General


{{ExpandImage|Pro_name_credit_classes.png}}

</translate>

News:Naming of credit classes in Project

2026-02-24T14:41:41Z

VJ: Created page with "<translate> {{News |Naming of Credit classes in Project |module=Project |group=Base registers |version=546W2602 |revision=0 |case=CORE-7712 |published=2026-02-24 }} Naming..."

<translate>
{{News
|Naming of Credit classes in Project
|module=Project
|group=Base registers
|version=546W2602
|revision=0
|case=CORE-7712
|published=2026-02-24
}}

Naming of Credit classes in Project

We have added the existing functionality for naming Credit classes in Media, to Credit classes in Project.

The fields for naming the Credit classes is in Project|Backoffice|Base registers|Parameters, tab General

{{ExpandImage|Pro_name_credit_classes.png}}

</translate>

File:Pro name credit classes.png

2026-02-24T14:40:52Z

VJ:

News:Code list in Export All projects

2026-02-24T14:11:57Z

VJ: Marked this version for translation

<translate>

{{News
|Code list in Export all projects
|module=Project
|group=Base registers
|version=546W2602
|revision=0
|case=CORE-7750
|published=2026-02-24
}}


Code list in Export all projects


We have added the selection Code list in the export function Export all projects.


The code list's ID present on the project will be included in the exported spreadsheet.


{{ExpandImage|Pro_export_all_projects_code_list_input_selection_view.png}}

</translate>

News:Code list in Export All projects

2026-02-24T14:11:46Z

VJ: Created page with "<translate> {{News |Code list in Export all projects |module=Project |group=Base registers |version=546W2602 |revision=0 |case=CORE-7750 |published=2026-02-24 }} Code list..."

<translate>
{{News
|Code list in Export all projects
|module=Project
|group=Base registers
|version=546W2602
|revision=0
|case=CORE-7750
|published=2026-02-24
}}

Code list in Export all projects

We have added the selection Code list in the export function Export all projects.

The code list's ID present on the project will be included in the exported spreadsheet.

{{ExpandImage|Pro_export_all_projects_code_list_input_selection_view.png}}

</translate>

File:Pro export all projects code list input selection view.png

2026-02-24T14:10:53Z

VJ:

File:Med collective clients blocked.png

2026-02-24T14:03:46Z

VJ:

News:New selection in Export of Accounts

2026-02-24T13:49:54Z

VJ: Marked this version for translation

<translate>

{{News
|New selection in Export of Accounts
|module=Accounting
|group=Base registers
|version=546W2602
|revision=0
|case=CORE-7839
|published=2026-02-24
}}


New selection in Export of Accounts


We have added Approval to the selection in Export of Accounts.


If the checkbox Approval is checked on the Account, the column Approval in the exported spreadsheet will have an X in it.


{{ExpandImage|Acc_baseregisters_export_approval_selection.png}}

</translate>

News:New selection in Export of Accounts

2026-02-24T13:49:40Z

VJ: Created page with "<translate> {{News |New selection in Export of Accounts |module=Accounting |group=Base registers |version=546W2602 |revision=0 |case=CORE-7839 |published=2026-02-24 }} New..."

<translate>
{{News
|New selection in Export of Accounts
|module=Accounting
|group=Base registers
|version=546W2602
|revision=0
|case=CORE-7839
|published=2026-02-24
}}

New selection in Export of Accounts

We have added Approval to the selection in Export of Accounts.

If the checkbox Approval is checked on the Account, the column Approval in the exported spreadsheet will have an X in it.

{{ExpandImage|Acc_baseregisters_export_approval_selection.png}}

</translate>

File:Acc baseregisters export approval selection.png

2026-02-24T13:49:23Z

VJ:

News:Inactivation of VAT classes

2026-01-16T10:03:01Z

VJ: Marked this version for translation

<translate>

{{News
|Inactivation of VAT classes
|module=Accounting
|group=Base registers
|version=546W2601
|revision=0
|case=CORE-7523
|published=2026-01-16
}}


Inactivation of VAT classes


The possibility to mark VAT classes as inactive has been added.


In addition an Only active filter has been added to the list of VAT classes.


{{ExpandImage|acc_vat_classes_active_checkbox.png}}


{{ExpandImage|acc_vat_classes_only_active.png}}

</translate>

News:Inactivation of VAT classes

2026-01-16T10:02:49Z

VJ: Created page with "<translate> {{News |Inactivation of VAT classes |module=Accounting |group=Base registers |version=546W2601 |revision=0 |case=CORE-7523 |published=2026-01-16 }} Inactivatio..."

<translate>
{{News
|Inactivation of VAT classes
|module=Accounting
|group=Base registers
|version=546W2601
|revision=0
|case=CORE-7523
|published=2026-01-16
}}

Inactivation of VAT classes

The possibility to mark VAT classes as inactive has been added.

In addition an Only active filter has been added to the list of VAT classes.

{{ExpandImage|acc_vat_classes_active_checkbox.png}}

{{ExpandImage|acc_vat_classes_only_active.png}}

</translate>

File:Acc vat classes only active.png

2026-01-16T10:00:32Z

VJ:

File:Acc vat classes active checkbox.png

2026-01-16T10:00:10Z

VJ:

News:Changes to app Utilization rate

2025-12-17T12:32:46Z

VJ: Marked this version for translation

<translate>

{{News
|Changes to app Utilization rate
|module=Project
|group=Applications
|version=546W2511
|revision=0
|case=CORE-7624
|published=2025-12-17
}}


Changes to app Utilization rate


The app Utilization rate has changed names to Occupancy rate and has gotten new selections.


The new selections are:


Accumalated year as of today's date, Per year, Show percentage, Show hours and Compare with previous year.


{{ExpandImage|App_occupancy_rate.png}}
</translate>