Skip to main content
Skip table of contents

IMOS - Standards for Expenses

Configuration flag CFGEnableStandards enables the use of standards for expenses and related features:

  • Either of two options for capturing and using standards for expenses:
    • Expense Standards: On this form, standard expenses can be defined for ports, passing ports, and canals. Standards are applied based on the exact Port and Berth (when specified), and then on matching criteria and Effective Dates.
    • Standard Expenses: On this form, standard expenses can be defined and applied individually, for the voyage or for the Port, Berth, and Cargo. The form has a table with one Standard Expense per row, where you can create, view, and modify all definitions, and filters to help you find existing definitions and determine which ones will be applied in specific voyage scenarios. This form is enabled by the addition of configuration flag CFGEnableAllStdExpMatches.
  • The Port Expenses Details form, to view and edit standard port expenses and miscellaneous voyage expenses
  • The use of standard expenses on Voyage Estimate Other Expenses

This config flag also adds a Rebillable column to the Business Rules table.

Related Configuration Flags

Hides the Port Expense field on some forms, enables standards for expenses, and adds a Port Expenses Details form and a Port Expenses Details button on the Port Expenses Summary to open it. When detail-level port expenses are being used, the PortExp column in the Voyage Itinerary behaves the same as the PortExp column in the Estimate itinerary:

  • For a port with no detail-level port expenses, you can edit its PortExp amount in the Voyage Itinerary Cargo Tab. The voyage P&L shows this amount as estimated expenses for that port.
  • For a port with a single detail-level expense, that amount appears and can be edited in the voyage itinerary PortExp field. An estimated expense entered before creating the detail-level expense is no longer displayed in the voyage P&L.
  • For a port with multiple detail-level expenses, the itinerary PortExp field shows the sum of the detail-level expenses for that port and cannot be edited.
  • When CFGVoyageExpenseAllocation is set to Y, a Voyage Expense Allocation section will be added to the Voyage Estimate Profit & Loss Report, and optionally to the Voyage Profit & Loss Report.

An ECA Factor field also appears on COA, Cargo/VC In, and CP Terms Details forms. When ECAFactor is used in an IMOS ECA Recovery Charge Results/Fee expression and an ECA Factor value is entered on a contract, an ECA Recovery Charge Extra Freight Term is generated on that contract.

  • When a COA is created from an Estimate, ECA Factor is copied from CP Terms to the COA.
  • When a COA Lifting is created, ECA Factor is copied from the COA to the Cargo.
  • When a cargo is scheduled, ECA Factor is copied from the cargo to the backcreated Estimate.

When enabled along with CFGEnableStandards, the Standard Expenses form is available instead of the Expense Standards form. All standard expense definitions created using this form are individually evaluated and applied to voyages and Estimates.

Also, a Rebill Type column is available in the Business Rules table, and is part of a unique index of the table. It allows the following values: Non-Rebillable, Rebillable, Advance Rebillable, <blank>. For the same Source and Code, an applicable rule whose Rebill Type column is not blank takes precedence over a rule whose Rebill Type column is blank.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.