A Voyage Charter In (VC In) looks similar to a Cargo, except that it has an Owner field instead of a Charterer field and other fields related to a purchase rather than a sale. You can use it to view and manage VC In contracts; for details, see information on the Cargo form. VC In contracts also appear on the Trading P&L Summary.
VC In List
The VC In List contains all VC In contracts that you have the right to view.
On the Trading menu, under Trades, next to VC In, click List.
On the Chartering menu, under Cargo, next to VC In, click List.
As with any other list, you can search, select, adjust, pin, filter, group, and sort columns, reset to the default view, save user views, and export.
By default, the following filters are applied, but you can change them:
Enter the Number of Copies, Total Period, and Start date and then click Create.
Edit line items for the copies as needed and then click OK.
Copying a VC In to a Cargo
To copy a VC In to a Cargo, click the copy icon, and then click Copy to Cargo.
Copying a VC In to a Cargo and Linking Back
To copy relevant details from a VC In to a Cargo and Link them in a Relet connection (similar to clicking Releton a Cargo), click the copy icon, and then click Copy to Cargo and Link Back. Pricing, demurrage, broker, and Extra Freight Terms details are not copied onto the Cargo.
Adding a VC In to an Estimate
To create an Estimate from a VC In, click Estimate and then click Add Cargo to New Estimate. An Estimate is created with the Cargo. If a vessel has been nominated, the new Estimate uses this vessel.
To add the Cargo to an existing Estimate, click Estimate and then click Add Cargo to Existing Estimate. Enter Estimate Search Criteria and select the Estimate.
Creating or Opening a Voyage Fixture from a VC In
To create a Voyage Fixture from the VC In, click Create Fixture. If the VC In is linked to a Sale Cargo, the Voyage Operation Type is set to RELT; otherwise, it is set to SPOT.
After the Voyage Fixture is created, the button changes to Open Fixture.
Scheduling or Opening a Voyage from a VC In
To create a voyage from the VC In, click Schedule Voyage. All the information from the Cargo moves to the voyage.
After the voyage is created, the button changes to Open Voyage.
If you have the Bulk Update Cargo ContractsModule Right selected, under Actions in Chartering, a column of check boxes appears in the VC In List. To bulk update VC Ins, select the contracts you want to update and then click the Bulk Update action link at the top of the list. To select multiple consecutive rows, select the first row and then press and hold Shift. Select the last row and then release Shift.
Acknowledging Revisions
This feature cannot be disabled.
For Cargo and VC In forms, if an update is imported via the Messaging Service, it must be acknowledged. When a Cargo or VC In has at least one unacknowledged revision:
In the Cargo List and VC In List, the row of the Cargo or VC In is highlighted, and its Un-ackRev column contains Y.
In the Voyage Manager Cargo List (enabled with configuration flagCFGEnableVoyManagerCargoList), the row of the Cargo or VC In is highlighted.
To acknowledge all highlighted revisions, on the Cargo or VC In Revisions panel, click ... and then click Acknowledge Revisions.
When the Enable Cargo Emissions Allocation flag (CFGEnableCargoEmissionsAllocation) is enabled in an IMOS environment, a new Emissions tab will become visible on the Cargo and VC In contracts. This tab is to be used to capture the contractual details that were agreed to with the counterparty on the contract for how emissions expenses will be settled over the life of the contract. Clicking on this Emissions tab on a Cargo Contract will show the following three fields:
Settlement Type - Defines how the contract is structured to settle emissions expenses.
Options are N/A (default), CASH, ALLOWANCES and HYBRID
Billing Period - Defines the period frequency that the emissions expense will be invoiced
Payment Terms - Defines the terms for how the invoices are to be paid/settled following receipt or delivery
Uses the Payment Terms as they are defined in the Data Center
Related Configuration Flags
Name/Flag
Description
Use Company Lob Trade Area Hierarchy CFGUseCompanyLobTradeAreaHierarchy
Sets up a hierarchy between Company, LOB, and Trade Area on several forms.
Enables the following types of intercompany contracts to be mirrored: Cargo COA, VC In COA, Cargo, VC In, Time Charter In, Time Charter Out, and FFA/Option/Bunker Swap Trade. When a contract of one of these types is created with internal counterparties, a mirrored contract is automatically created from the opposite perspective, so that users from both legal entities can manage the contract and include it in both their operational planning and their trading exposure and P&L.
When both CFGEnableContractMirroring and CFGEnableTCInvoiceMirroring are Y, and when a TC contract is mirrored, TCO invoices are mirrored from TCI invoices. Incremental invoice type is unavailable for such mirrored TC invoices.
If an **OV voyage has cargoes with multiple internal charterers, it can be mirrored with multiple RELT voyages, one for each internal charterer's company.
Show Remittance in Cargo CFGShowRemittanceInCargo
Adds Remittance Bank, Invoice %, Payment Terms, and Balance % fields to the CP Terms Details, Cargo COA, Cargo, VC In COA, and VC In forms. Also adds a Remittance Bank field to Time Charter Other Information. Remittance information flows between these places; for example, fixing an Estimate will transfer the remittance information.
On a Cargo COA, VC In, or Time Charter Out, changing the Company clears the remittance bank information, as this may change with a change to the Company.
On a VC In COA or Time Charter In, changing the Owner clears the remittance bank information, as this may change with a change to the Owner.
A default value for the Remittance Bank for each currency can be selected in the AddressBank Links tab for Cargo COA, Cargo, and Time Charter Out (Other Information) contracts, but it can be changed later.
When enabled, the Commissionable setting of an Operations Ledger Code alone determines whether claim and freight adjustment line items are commissionable. When enabled, the commissionable setting cannot be overridden in invoices or per broker.
This flag controls the default setting for broker commissions on Claims by setting the default value of M on TC In, TC Out, Cargo, Cargo COA, VC In, and VC In COA broker grids. Possible values:
0 (default): Claims are not commissionable.
1: Claim commissions will be invoiced separately.
2: Commissions will be deducted from the Claim Invoice.
Also adds Add Default Brokers to the TCO Estimate toolbar to default internal brokers by applicable rules.
Apply IC Adjustment to Xfrt CFGApplyICAdjustmentToXfrt
If enabled, for a model B mirrored freight contract (Cargo / VC In and Cargo / VC In COAs), an Extra Freight Term is adjusted by IC Adj % in the same way as the base freight, if the Extra Freight Term type is Rate or Lumpsum (not Percent).
Enable Operations LOB CFGEnableOpsLOB
If enabled, displays an LOB (Line of Business) field on the Address (Type W), Estimate, Voyage Fixture, Voyage, and contract forms.
Enable Standards CFGEnableStandards
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 ChargeExtra 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 back-created Estimate.
Enables the Shuttle Tanker Workflow and master data forms necessary for freight invoicing of time and bunkers for both the actual voyage and theoretical return legs, most commonly used by shuttle tankers.
Adds an option to Keep Booking No. when copying a Cargo or VC In.
Enable Voyage Manager Cargo List CFGEnableVoyManagerCargoList
Adds Cargo and Cargo Handling tabs to the Voyage Manager. The Cargo tab is similar to the Cargo List, but only includes cargoes associated with the voyage. The Cargo Handling tab is similar to the Cargo Handling form; it includes a list of all cargoes associated with the voyage, with a line for each load and discharge. Lines highlighted in yellow indicate transshipment cargoes, while lines highlighted in blue indicate interservice cargoes.
If a Cargo or VC In has at least one unacknowledged revision, its row is highlighted in the Cargo List.
Store Firming ETA on Cargo Trigger CFGStoreFirmingETAOnCargoTrigger
When a voyage’s status is set to the configuration flag value (forecast, scheduled, or commenced), a static Firming ETA field populates on the linked Cargo or VC In Itinerary/Options tab. You can compare this value with the actual ETA in a custom Report Designer report.
To disable this flag, leave the value blank.
Note:
Firming ETA will be cleared out if the voyage status is set to a status prior to the status of the configuration flag setting and will only be repopulated when the voyage status is set back to the one associated with the trigger type.
When the cargo is unscheduled from a voyage, the Firming ETA field will be cleared out as well so that it no longer shows a value
Enable Cargo Delivered CFGEnableCargoDelivered
Enables you to save Cargoes, VC Ins, or bookings with only a load or discharge port.
JavaScript errors detected
Please note, these errors can depend on your browser setup.
If this problem persists, please contact our support.
