Configuration & Settings in Jules

Product documentation — How Jules is set up per organization to reflect your trading rules, currencies, trade terms, integration endpoints, and dashboard preferences.

---

Table of Contents

1. Overview
2. Organization Configuration
3. Currencies & Exchange Rates
4. Business Rules
5. Trade Terms Reference Data
6. VAT Configuration
7. ERP Integration
8. Flags & Alerts
9. Stockpiles (Warehouse Configuration)
10. Dashboards
11. Views & Saved Filters
12. Accounts Payable / Receivable (APAR)
13. Default Form Parameters
14. User Configuration
15. Relationships with Other Modules
16. Key Business Rules
17. Glossary

---

Overview

Configuration in Jules operates at two levels: organization-wide settings that apply to all users in a tenant, and user-level preferences that each person customizes individually. Everything described in this article lives in the Settings area of the application and is managed by administrators.

Jules is a multi-tenant platform — each organization has its own isolated configuration. No settings bleed across tenants.

---

Organization Configuration

The organization config is the top-level settings object for an entire Jules tenant. It controls platform-wide behaviors for operations, invoicing, logistics, and display.

Core Settings

Operations Settings

Operation End Date Offsets

Jules can automatically pre-populate the end date on new operations based on configurable offsets (in days) per operation direction and market type:

Invoicing Settings

Invoice types covered by openInvoiceSettingsOn and defaultInvoiceDateOfCreation:

Display Settings

Jules allows each organization to choose which currency and volume unit is displayed in each major list view. This does not affect the stored currency — it only controls how amounts are presented.

Page-Level Configuration

The pageConfig object allows hiding or showing specific UI elements per page:

Commercial Targets

Posting Period

The postingPeriod defines the open accounting window during which operations and invoices can be posted. It is a date range (minDate / maxDate) configured by the administrator.

---

Currencies & Exchange Rates

Jules is a multi-currency platform. Currency configuration spans three related modules: Currency, BaseCurrency, and ExchangeRate.

Currencies

The currencies list shows the full list of currencies available to an organization. Each currency has:

Base Currencies

The base currency concept in Jules allows defining separate reference currencies for different cost types. This enables organizations trading across multiple currency zones to normalize calculations correctly.

An organization can have multiple base currencies — one per type — allowing separate purchase and sales reporting currencies.

Exchange Rates

Jules maintains two layers of exchange rates:

ExchangeRate fields

Overriding rates

Administrators can manually override any rate. Once an organization rate is set, it takes precedence over the public rate. Rates are stored with a timestamp so historical conversion accuracy is preserved.

---

Business Rules

Business rules control how Jules validates and enforces commercial thresholds. They are configured per organization and applied automatically during operation management.

Closing Rules

Closing rules define conditions that must be satisfied before an operation can be marked as closed. They act as a checklist that Jules verifies when a trader attempts to move an operation to the CLOSED status.

Closing rules are configured by administrators and evaluated against operations at the time of closure. If a rule is not met, Jules will block or warn the user depending on the configuration.

Deviation Rules

Deviation rules trigger alerts when a purchase operation is approaching its end date without sufficient execution progress. The system evaluates each confirmed buy operation against the deviation rules for its quality and market type.

Deviation Rule fields

The deviation check computes how far through the operation's lifespan you are (based on dateOfCreation to endDate) and flags it if the validityThresholdRate is breached while the operation is still CONFIRMED and not sufficiently executed.

Cut-Off Day

The cut-off day setting defines the calendar day within a period (month or week) after which new operations or invoices cannot be posted into that period. This is a key accounting control used to enforce period-end discipline.

---

Trade Terms Reference Data

These modules define the reference lists that populate dropdowns throughout Jules. They are maintained by administrators and shared across the organization.

Incoterms

Incoterms (International Commercial Terms) define the division of transport, cost, and risk responsibilities between buyer and seller. Jules maintains a curated list of incoterms scoped by market type and operation direction.

Jules filters available incoterms dynamically based on the operation type and market type, ensuring traders only see relevant options.

Payment Terms

Payment terms define when and how payment is due on an operation. They are one of the most customizable reference entities in Jules — each payment term can include multiple slices representing partial payments.

PaymentTerm fields

PaymentTermsSlice fields

Each payment term can have multiple slices representing installments:

Modalities

Modalities define the transport or loading modalities available for containers and freight bookings (e.g., "20' standard container", "40' High Cube", "Flat rack"). They are a simple reference list maintained by administrators.

Release Conditions

Release conditions define the contractual conditions under which goods or payment are released (e.g., "Original BL received", "Inspection certificate approved"). They appear as selectable options on operations and invoices.

Sectors

Sectors categorize companies and operations by industry segment (e.g., "Scrap Metal", "Plastics", "Paper & Cardboard"). They are a simple reference list used for filtering and reporting.

---

VAT Configuration

The VAT configuration module allows Jules to automatically determine the correct VAT rate and clause to apply on an invoice, based on the transaction's characteristics. This eliminates manual VAT selection errors and ensures compliance.

How VAT Config works

Jules evaluates multiple boolean flags about the trade transaction and matches them to a VAT config record that returns the correct rate and clause. The matching logic uses the following conditions:

VAT Config output

VAT configuration is filtered based on the billing entity and invoice type, returning only the VAT configs applicable to that billing entity context.

---

ERP Integration

Jules supports bi-directional synchronization with external ERP systems (such as SAP, Navision, or Sage). When containers are loaded or deliveries are confirmed, Jules can automatically push those events to your ERP, keeping your financial records in sync.

Integration endpoint configuration is handled by your technical team during onboarding.

---

Flags & Alerts

Flags are annotation markers that users can attach to operations, containers, allocations, and shipments to signal that something requires attention. They are not automated — they are created manually by traders.

Flag types

Flag structure

Pre-defined reason codes

Jules provides a set of standard flag reasons:

For "Others" flags, administrators can maintain a library of custom reason codes available to their organization.

---

Stockpiles (Warehouse Configuration)

Stockpiles represent physical storage locations within a site — they are the warehouse-level configuration that tracks material inventory. Each stockpile belongs to a site and is associated with one or more qualities.

Stockpile fields

Stockpiles are used to track incoming and outgoing material flows at the warehouse level, and they feed directly into the KPI dashboard for stock position reporting.

---

Dashboards

Jules supports embedded analytical dashboards that provide visual KPIs and data visualizations beyond the standard operational tables. Dashboards are configured by administrators and surfaced to users within the application.

Dashboard configuration

Dashboards are accessible directly from the Jules navigation menu. Authentication is handled automatically — users do not need to log in separately to the BI tool.

Built-in Dashboard Queries

Jules also exposes native analytical views used within the built-in dashboard pages:

Product Balance

The Product Balance view provides a real-time view of material positions across operations, broken down by quality, market, and port:

Each product balance record shows the operation's contracted quantity against allocated, booked, loaded, and delivered quantities.

Average Purchase Cost

The Average Purchase Cost view calculates the weighted average purchase cost per quality, filterable by region and subregion. This is used to benchmark sourcing costs across geographies.

---

Views & Saved Filters

Jules allows users to save their filter combinations as views so they can return to a specific data perspective quickly. Views are personal by default but can be shared across the organization.

View fields

Administrators can reorder views across the organization to promote the most useful ones to the top of the list.

---

Accounts Payable / Receivable (APAR)

The APAR module provides a consolidated view of outstanding payables and receivables across all operations. It aggregates invoice data and payment term slices to give traders and finance teams a single source of truth for cash flow visibility.

APAR record fields

APAR records are read-only — they are derived from invoice and payment term data and cannot be edited directly.

---

Default Form Parameters

Jules can pre-fill certain form fields based on the user's recent activity or administrator-defined defaults. This reduces data entry time and improves consistency.

Default form parameters are resolved at the time a new form is opened and applied as initial values. Users can override any pre-filled value before saving.

Supported defaults

---

User Configuration

Each Jules user has a personal configuration profile that controls their individual experience within the platform. This is separate from the organization-wide settings and can be updated by each user from their profile settings.

User config fields

---

Relationships with Other Modules

Configuration settings in Jules underpin nearly every other module in the platform. The table below shows key dependencies:

---

Key Business Rules

1. Organization config is tenant-scoped — changes to organization settings affect all users in that tenant immediately.
2. User config is personal — changes to user preferences only affect that individual user.
3. Exchange rates resolve in order — organization rates always take precedence over public rates. If no organization rate exists, the public rate is used.
4. VAT config is deterministic — given the same set of transaction flags, the same VAT rate and clause will always be returned. There is no manual VAT override at the invoice level.
5. Deviation rules are evaluated at the operation level — they apply to confirmed buy operations only and are recalculated on each check.
6. Closing rules are blocking — if a closing rule is not satisfied, the operation cannot transition to CLOSED status.
7. Posting period is enforced globally — no invoice or operation can be posted outside the configured minDate / maxDate window.
8. Stockpile quantities are derived — Jules calculates stock positions from load and delivery events; quantities are never entered manually.

---

Glossary