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 (organizationConfig query) 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 query returns 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

Upserting rates

Administrators can manually override any rate using upsertOrganizationExchangeRates. Once an organization rate is set, it takes precedence over the public rate for that currency pair. 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 (closing_rules table) 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 using incotermsChoices(input: { marketType, 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 (id, value) 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 (VatConfig) 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

The filteredVatConfig query takes a billing entity and invoice type as required inputs, 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). The integration layer allows Jules to push and receive trade events.

ERP Loadings

When a container is loaded, Jules can push a loading record to the ERP:

ERP Deliveries

When a delivery is confirmed, Jules pushes a delivery record to the ERP:

Integration URLs

The IntegrationUrls module stores the endpoint URLs for each external system integration. These are configured per organization by the technical team and define where Jules sends its outbound webhooks and API calls.

ERP IDs on Reference Data

Many reference entities in Jules carry an erpId field (e.g., payment terms, sites, companies, qualities). This is the external ERP system's identifier for the same record, used to map Jules entities to their ERP counterparts during synchronization.

---

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, getOtherFlagReasonChoices returns the organization's custom reason library.

---

Stockpiles (Warehouse Configuration)

A stockpile is a named pile of material physically stored at a warehouse site. Stockpiles are the core of Jules' warehouse and stock management module — they track what is available, what is under quarantine, and what has been lost.

Stockpile fields

Stockpile statuses

Stockpile KPIs

The filteredStockpileKPIs query returns aggregate KPIs across filtered stockpiles:

Each KPI is expressed in both weight (tonnes or configured volume unit) and number of containers.

---

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 fetched via a token-based authentication mechanism:

• getDashboardToken — returns a session token valid for all dashboards

• getDashboardTokenById(id) — returns a token scoped to a specific dashboard

This ensures that the embedded BI tool can authenticate the user without requiring a separate login.

Built-in Dashboard Queries

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

Product Balance

The product balance query (getProductBalance) 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 getAveragePurchaseCost query 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

Views are named, saved configurations of a table page — including column visibility, sort order, active filters, search text, and row grouping. They allow teams to create shared workspaces tailored to specific workflows.

View fields

View visibility levels

Views can be reordered using upsertViewOrders, allowing administrators to control which views appear first for all users.

---

Accounts Payable / Receivable (APAR)

The APAR module (filteredApar) provides a consolidated view of accounts payable and receivable positions across the organization. It aggregates invoice and bill data for a company-level financial overview.

The query accepts optional companyId filtering to drill down to a specific counterparty's balance. Results are paginated and returned as structured JSON objects containing the consolidated payable/receivable balances.

This module is primarily used to give finance teams a summary of outstanding amounts before month-end closing.

---

Default Form Parameters

Default form parameters (defaultFormParameters) pre-fill certain form fields when users open specific creation dialogs. This reduces repetitive data entry for teams that predominantly work with one type of contract or logistics configuration.

These parameters are scoped to the organization and are managed by administrators in Settings.

---

User Configuration

User config (userConfig) is the per-user layer of configuration. Each user has their own preferences that do not affect other team members.

Saved Searches

Users can save and name frequently used filter combinations ("favorite searches") in:

Table Preferences

Default Market Type

Users can configure their default market type filter for the operations list:

---

Relationships with Other Modules

Configuration entities are consumed throughout the entire Jules application:

---

Key Business Rules

1. Organization-scoped isolation

Every configuration entity in Jules is scoped to a single organization (tenant). Exchange rates, payment terms, VAT configs, and views set by one organization are invisible to other organizations on the platform.

2. Exchange rate precedence

When Jules needs to convert a value between currencies, it first looks for an organization-specific rate for that currency pair. If none exists, it falls back to the latest public rate. This allows organizations to use their own negotiated or internally validated rates.

3. Incoterm filtering by direction and market

The list of available incoterms shown to a user is dynamically filtered. On a SELL/EXPORT operation, only incoterms configured for type: SELL and marketType: EXPORT are shown. This prevents traders from accidentally selecting terms incompatible with their deal structure.

4. Payment term slices must sum to 100%

When defining a payment term with multiple slices, the amountPercentage values across all slices must total 100%. Jules enforces this constraint to ensure no portion of an invoice payment is left unaccounted for.

5. VAT config is auto-matched — not manually selected

Users do not choose a VAT rate directly. Jules evaluates the trade characteristics at invoice creation time and automatically applies the matching VAT config. The matching is deterministic given the billing entity, invoice type, and trade geography conditions.

6. Deviation rules are proactive alerts

Deviation rules do not block operations — they surface warnings to help traders identify at-risk purchase operations before they miss their execution window. The alert fires when an operation has consumed more than validityThresholdRate of its available time but has not reached the expected execution progress.

7. Closing rules are enforced at closure

Unlike deviation rules, closing rules are evaluated as hard checks when a user attempts to mark an operation as CLOSED. If a closing rule condition is not met, the closure is blocked or the user is prompted to confirm they are overriding the rule.

8. Stockpile stock is tracked as received minus outbound

The "available" quantity in a stockpile is not a stored field — it is derived: available = received - outbound. The allocated field tracks committed stock that has not yet shipped. Stock that is quarantined or lost is excluded from the available pool.

9. Dashboard tokens are session-scoped

Embedded dashboard URLs are not directly accessible. Jules generates a short-lived authentication token for each session (via getDashboardToken) that is passed to the embedded BI tool. This ensures dashboards respect Jules' access control without exposing raw BI tool credentials to users.

10. Views with PUBLIC visibility are managed by admins

Any team member can save a PRIVATE view. Creating or modifying PUBLIC views (visible to all users) is a permission-controlled action, typically restricted to administrators or team leads to prevent noise in shared workspaces.

---

Glossary