Version 2.5.6.180

The following pricing versions are now available:

• Pricing 2.0 is intended for compatibility with version 2.4 or earlier. Prices are linked to product items. For a product item that has item variants, prices must be specified for each variant separately.
• Pricing 2.5 is intended for compatibility with version 2.4. This expanded feature set includes:
• Price accounting by product items, variants (as well as variant attributes), series (as well as series attributes), packages. Prices are linked to product items. For a product item that has item variants, a single price can be assigned for all variants.
• Both common and individual price types can be set for a specific warehouse, store format, partner, or agreement.
  

  A wizard is available to assist in migration to pricing 2.5. Migration is performed starting from a date specified in the wizard. During migration, it is not recommended to set prices, modify price types or item kinds.

  To run the Migrate to pricing version 2.5 wizard, go to Master data and settings – Master data and sections – CRM and marketing – Marketing – Start migration.

  Pricing 2.5 is the default choice for new infobases; however, you can roll back to pricing 2.0.

 

Currencies can now be specified for price groups.

Price usage options are changed. Option “Use while selling to customers” is replaced by options:

• On wholesale.
• On retail sale.

Predefined product item filters can now be set for price types. Filters can be set by item attributes, variant attributes, or product segment attributes (to set the filter, follow Assign prices to – all items hyperlink in the price type card).

New price setting methods are added. Additional price calculation parameters are implemented, depending on the selected price setting method.

The following data composition schemes are no longer available:

• Cost + profit share (intercompany).
• Cost + share (intercompany).
  

  To specify markups by price groups, follow the corresponding hyperlink in the main form of price type card. No context will be lost.

  Rounding rules for all prices are now set in the main form of price type card. To set price rounding by ranges, follow Specify rounding by price groups hyperlink in the auxiliary form of price type card.

  Separate trigger thresholds are now available for price increase and price decrease. Trigger thresholds are set in the main form of price type card. Trigger thresholds can be clarified for each goods price group as well as by price groups in the Clarification of trigger thresholds by price groups window.

  Maximum discount or markup percentage can be set for each price type separately. Discounts (markups) are set in the main form of price type card. Maximum discount or markup percentage can be clarified by price groups in the Clarification of maximum discount (markup) percentage by price groups window.

 

What’s new in the list of price types form:

• We added panel of price type usage locations (store formats, agreements, partners, warehouses).
• We added filters by price usage and purpose (only for pricing 2.5).
  

  We added a scheduled job for automated price calculation in accordance with schedule. To run the job, use the Configure price auto-update schedule command in the list of price types form.

What’s new in the price list UI:

• Price list column hierarchy.
• Price list column viewing and editing mode.
• Price list column sorting.
• Additional data grouping when setting prices.
• Additional item filters.

Unified price change form is implemented with the following options:

• Change by percentage.
• Change by value.
• Set price.
• Calculate using formula.

New options in quick price change panel:

• Making changes to selected lines in the main price setting form.
• Canceling changes made to selected lines.

Information bar is moved to control panel.

Control panel now displays price change history.

Price lists now support temporary (special) prices. Temporary prices can be set to a specific date (as before) or for a period. For example, prices can be reduced for the duration of a promotional event and automatically restored after the event ends.

 

The form now contains information on price types in documents and promotional events.

The report now can include additional item properties and images from product profiles.

“Additional properties” mechanism is added to the “Price groups” catalog.

 

New filters are added to Step 2:

• Show mapped products only.
• Show lines with changed prices.

Price registration setup form is added. To open the form, follow Price registration setup hyperlink at Step 2. The form contains the following options:

• Register all prices, or Register changed prices only.
• Register all items (and create items that were not recognized), or Register recognized products only (and ignore products that were not recognized).

Price registration settings are removed from Step 3. Information bar is added, which displays the prices to be registered.

 

You can now choose to provide discount for Products not from segment (in Provided for field).

Repeated sales report is implemented. The report helps to send proposals to customers at convenient time and through convenient channels, improving customer communications.

The main purpose of the Repeated sales report is to assist making customer calls in an efficient manner, ensuring stable sales to regular clients.

The report generates structured lists of customers who are most likely to make a specific purchase. The predictions are based on the sales history data.

 

Support of document names used by vendors is implemented for incoming documents. The Incoming document name attribute is added to all incoming documents for this purpose.

Incoming document names are used in AR/AP accounts reconciliations and displayed in AR/AP object selection lists.

Support of source document names allows to:

• Match infobase documents with documents received from vendors.
• Generate AR/AP accounts reconciliations and select AR/AP objects using source names.

 

Settlement details generation method By invoices is now By AR/AP documents.

The following mixed settlement details generation methods are implemented:

• Order for prepayment, Invoice for invoice. This method involves automated allocation of order prepayment by invoices in accordance with prepayment % for shipment:
  • Both order and invoice are used as AR/AP objects.
  • Multiple prepayments are allowed for a single order.
  • Payments exceeding the planned prepayment amount are allowed for an order.
  • When transferring prepayment from order to invoice, AR/AP documents are selected according to FIFO and transferred to invoice.
  • When registering an invoice for an order, any remaining prepayment amount is automatically transferred from the order to invoice in accordance with prepayment % specified in order payment schedule.
  • Prepayment control is performed during invoice posting.
  • Invoice payment schedule contains a prepayment stage.
  • If order payment schedule contains several prepayment/credit stages, invoice payment schedule for this order shall contain all of these credit stages and a single-line prepayment stage with due date equal to the date of invoice.

• Contract for prepayment, Invoice for invoice. This method involves automated allocation of contract prepayments by invoices in accordance with prepayment % for shipment:
  • Both contract and invoice are used as AR/AP objects.
  • Prepayments are allowed for contracts.
  • Payment schedule can be specified either in the contract (contract schedule), or in the order/invoice.
  • When registering an invoice for a contract, any remaining prepayment amount is automatically transferred from the contract to invoice in accordance with prepayment % specified in order payment schedule.
  • When transferring prepayment from contract to invoice, AR/AP documents are selected according to FIFO and transferred to invoice.
  • Prepayment control is performed during invoice posting, provided that fulfillment schedule is determined by orders/invoices.
  • Overdue AR control and maximum AR amount control is available for contracts.
  • If fulfillment schedule is determined by orders/invoices and order payment schedule contains several prepayment/credit stages, invoice payment schedule for this order shall contain all of these credit stages and a single-line prepayment stage with due date equal to the date of invoice.

 

Settlement details generation methods Contract for prepayment, Invoice for invoice and Order for prepayment, Invoice for invoice now have the following features:

• Order invoice payment schedule includes prepayment option used for prepayment control prior to shipment.
• Orders are not filled in the invoice payment schedule. Instead, filled stage lines are grouped by shift, date, and payment method.
• If order payment schedule contains several prepayment/credit stages, invoice payment schedule for this order shall contain all of these credit stages and a single-line prepayment stage with due date equal to the date of invoice. Payment dates for credit stages are recalculated from the invoice date, including any grace periods. Prepayment data cannot be changed. Generally, preplayment amount is equal to the sum of registered advance payments.

Settlement details generation methods By orders, and By contracts are updated. If order payment schedule contains several prepayment/credit stages, invoice payment schedule for this order shall contain all of these credit stages specified from the invoice date, including any grace periods. Prepayment stage is classified as “Credit (planned)” with payment date equal to the invoice date. Invoice payment rules do not include a prepayment stage because prepayment control is performed during ordering stage.

 

Debt offsetting transaction setup wizard now has new functionality.

Customer advance transfer and Vendor advance transfer offsetting transactions are added for advance transfer purposes.

Transfer of debt owed by customer and Transfer of debt owed to vendor transactions are added for debt transfer purposes.

Debt offsetting now supports:

• Transferring advances between orders without loss of AR/AP document or advance rate.
• Transferring advances from payment documents to invoices without loss of AR/AP document or advance rate.
• Transferring settlements on debenture contracts.

 

Regardless of the number of documents registered for an AR/AP object, last documents in the chain must be processed without any delay (less than 1 second).

Now, allocation of planned payments, shipments, and deliveries can be performed in background mode.

If Perform allocation of planned settlements in background option is enabled (Master data and settings – Master data and sections – Treasury and settlements – Settlements), allocation of planned payments, shipments, and deliveries is performed in background mode immediately after the documents are posted.

This allows for faster posting but it takes several seconds to several minutes (depending on the number of posted documents) to update the planned calculations data in reports.

 

The following scenarios are supported:

• Lessor accounting:
  • Operational lease:
    • Commencement of lease.
    • Lease payments.
    • Return from lease.
    • Commencement of lease under loan agreement.

• Leaseholder accounting:
  • Receipt of the lease.
  • Lease payments.
  • Lease terms modifications.
  • Redemption of leased items.
  • Return from lease.
  • Security payment return.
  • Calculation of discount rate, present value, interest.

 

Business activities often require making changes—reversals or corrections—to documents reflecting business transactions.

The following documents now support reversals and corrections:

• Receipt of goods to warehouse.
• Transfer of goods
• Internal inventory consumption (Write off as expenses).
• Other recording of goods as received.
• Write off goods shortages.
• Inventory surplus recognition.
• Goods damage.
• Goods misgrading.
• Goods assembly.
• Movement of products and materials.

To make a change, generate a new document from the current document.

You can generate the following types of adjustment documents:

• Storno.
• Correction.

Generated document includes a reference to the source document stored in the Document correction attribute.

After making changes, the original document is locked for further editing.

If several correction were made to the original document, all correction documents are available at hyperlink all corrections.

Storno document contains the minimum required information and a reference to the original document.

Once a document is cancelled, correction documents can no longer be created on its basis.

Documents with corrections or reversals are marked with a special symbol in the document list form, and column Corrected (reversed) document contains references to their base documents.

Printed forms of these documents include numbers and dates of their original documents that were corrected or reversed.

 

For cost accounting by lines of business, invoices and documents for internal consumption without order can now be created for non-pegged goods shipment.
On pegging basis check box is added to invoices. This check box enables inventory consumption with pegging for lines of business. If this check box is not selected, empty inventory assignments are used for consumption in specified Line of business.

 

«Turnovers by VAT» report is implemented (Financial result and controlling – Financial result reports). The report displays information on incoming and outgoing VAT for period, broken down by company. The report is intended for acquiring and analyzing data for preparing VAT reports as required by state authorities.

 

“International financial accounting” subsystem now supports linking transactions to multiple charts of accounts with different structure, dimensions, accounting currencies, and report formats.

Now, companies with multinational branch offices can easily set up multiple national charts of accounts using national currencies and keep accounting on the basis of operational procedure data.

Multiple charts of accounts can be used with:

• IFA financial report builder.
• Budgeting data sources.

 

Filling of document attributes using statistical data can now be disabled in user’s personal settings (Master data and settings – Service – Personal settings).

Queries for statistical data filling are optimized.

 

Author attribute is added to the majority of documents. The attribute is displayed in Read-Only document forms and all document lists. Author attribute is displayed in document forms, document list forms, and document journal. Author attribute is added to the common document journal.

Manager attribute is filled from contract, agreement, or partner data. Any available source is used for this purpose. If manager cannot be determined from these sources, statistical data is used. If manager cannot be determined from statistical data, the current user is registered as manager.

In Cash account receipt note and Cash account issue note, the Cashier attribute is now renamed to Author. The current user is registered as Author . Cashier attribute is added. It is filled from the list of responsible persons. When printing, Cashier is used first. If blank, Author is used instead. Author and Cashier are displayed in the document form.

Providing base document for authorized signatories is no longer mandatory.

Customer invoice document form now displays Dispatched by attribute. This attribute is filled with the name of financially liable person for the warehouse. If blank, it is determined from statistical data.