Economy Operations

Use Overview, Banking, Statement, Audit, Declarations, and Custom Delivery with clear action gates and validation checklists.

Overview

Economy is the operational finance and route-control workspace for daily simulation decisions.

Use this page as a full wiki for all Economy tabs, then apply the correct checklist for your current task.

Estimated time: 15 minutes Result: correct tab usage with validated outcomes Scope: Overview, Banking, Statement, Audit, Declarations, Custom Delivery
Required

Choose the correct Economy tab before executing actions.

Required

Validate action gates (approval, contest eligibility, telemetry status, base-save context).

Required

Use validation checkpoints after each section action to prevent finance/context drift.

Required

Use an offline profile (Steam Cloud disabled) before Custom Jobs operations.

Required

Select a valid Base Save before route actions.

Required

Choose Dispatch Active only when active delivery context exists in Base Save.

Required

Run Rescan whenever Custom Delivery status indicates scan_required.

Required

Custom Delivery execution creates clone in new slot; Base Save is never overwritten.

Overview workflow

Use OVERVIEW for quick financial health and rules posture before running cost-sensitive actions.

  1. Open Economy > OVERVIEW and read Economy Summary values first.
  2. Review Economy rules toggles (admin fee, interest, bonuses, penalties).
  3. Confirm rule toggles match your current operation policy before continuing to Banking or Statement.
  • Validate: summary values are coherent with recent trip events and no accidental rule toggle is active.
  • Common failure: changing rule toggles without intent and misreading later statement deltas.
  • Gameplay impact: active rule toggles change how future economy events affect your balance.

Banking workflow

Use BANKING to simulate rental costs, start rental only when eligible, and complete return safely.

  1. Open Economy > BANKING and run SIMULATE to preview expected outcome.
  2. Check simulation/rental status values before taking any commitment action.
  3. Use START RENTAL only when approval status is available.
  4. After operation window, open Return section and use CONFIRM RETURN only when settlement is available.
  • Validate: action buttons are enabled by state, not forced by retries.
  • Common failure: attempting return before settlement conditions are met.
  • Gameplay impact: rental start/return decisions directly change medium-term cash flow and payable totals.

Statement workflow

Use STATEMENT to inspect ledger events by window, group, and contest status.

  1. Open Economy > STATEMENT and choose window preset (4H, 24H, 7D).
  2. Apply filters (Contestable, Pending) to isolate actionable entries.
  3. Inspect grouped history (Fines, Tolls & Fees, Operations, Fuel) and open event detail context.
  4. Use Contest only on entries where contest action is available, then track status chips (Pending/Approved/Denied).
  5. Use CLEAR when you intentionally want to reset temporary filter focus.
  • Validate: contest count and status chips align with your latest actions.
  • Common failure: contesting non-eligible entries or reading grouped totals without filter awareness.
  • Gameplay impact: approved contests reduce effective losses, while denied contests preserve original charges.

Audit workflow

Use AUDIT for controlled cash correction when statement context requires manual adjustment.

  1. Open Economy > AUDIT and review current correction context carefully.
  2. Confirm value and reason before any write action.
  3. Execute APPLY CORRECTION once, then re-check statement impact and audit trace.
  • Validate: correction appears once with expected amount and rationale.
  • Common failure: repeated correction attempts without re-validating current balance context.
  • Gameplay impact: audit correction writes immediate balance adjustment and must match evidence.

Declarations workflow

Use DECLARATIONS to combine telemetry-backed trip data with RP expenses before submission.

  1. Open Economy > DECLARATIONS and review telemetry route summary first.
  2. Confirm telemetry details (fuel, infractions, fines, tolls, revenue, net) are coherent.
  3. Fill RP expenses (reference, lodging, meal, notes) with clear operational reason.
  4. Review preview block for final net impact.
  5. Submit with DECLARE only after telemetry and RP fields are consistent.
  • Validate: telemetry section is available and submit result matches expected declaration intent.
  • Common failure: submitting with incomplete reference/notes and losing audit clarity later.
  • Gameplay impact: declaration outcome can credit or debit driver balance based on telemetry and RP entries.

Custom Jobs prerequisite

Custom Jobs depends on stable local profile context. Keep your ATS/ETS2 operational profile in offline mode before cloning flows.

Complete first: Offline Save Setup (ATS/ETS2).

Operational quick path

  1. Open Economy > OVERVIEW and verify current financial/rules posture.
  2. Pick the correct operational tab: BANKING, STATEMENT, AUDIT, DECLARATIONS, or CUSTOM DELIVERY.
  3. Validate action gate conditions for the selected tab before executing any command.
  4. If using Custom Delivery, confirm offline profile + valid Base Save + flow selection (Offer vs Active).
  5. Execute action and verify result in the same tab (status chips/result messages/audit traces).
  6. Before leaving Economy, confirm no unresolved pending/blocked state remains.
Operator rule: pick tab by objective first, then run only actions that are currently unlocked for that tab context.

How to choose Base Save

Custom Jobs requires selecting the correct save slot folder from your ATS/ETS2 profile path.

  1. Open your profile path in Windows Explorer (example: %USERPROFILE%\Documents\American Truck Simulator\profiles\<profile-id>\save\ or %USERPROFILE%\Documents\Euro Truck Simulator 2\profiles\<profile-id>\save\).
  2. Inside save, pick a slot folder named with numbers only (for example 1, 12, 74).
  3. Open that slot folder and confirm game.sii exists inside it.
  4. In SimDuty, select this slot as Base Save and run Rescan.
Validation rule: if the selected folder does not contain game.sii, it is not a valid Base Save slot.

Decision checklist

  1. Confirm Offline Save Setup is complete and Base Save is selected.
  2. If the loaded Base Save already has an active Cargo delivery (cargo + trailer), choose Dispatch Active.
  3. If there is no active delivery in Base Save, choose Dispatch Offer to retarget observed Freight Market offers.
  4. If Dispatch thread gives CTA Open Dispatch Offer or Open Dispatch Active, follow that CTA unless context check proves mismatch.
  5. If Flow Status reports scan_required, run Rescan before apply/clone in either flow.

SimDuty Loads usage rule:

  • Use SimDuty Loads to learn/share/import route knowledge and then continue in Offer or Active clone flow.

Dispatch Offer flow

Dispatch Offer edits the observed Freight Market offer flow. Use it when you want to retarget a freight offer template, not a delivery already in progress.

Step 1 - Base Save

  1. Select Base Save in Economy > Custom Delivery.
  2. Confirm save context is valid (game/profile/slot recognized).
  3. If status asks for scan, run Rescan before continuing.
  • Validate: Base Save stage is unlocked and route stages are available.
  • Common failure: missing or stale save context; reselect save and scan again.

Step 2 - Context

  1. Open Dispatch Offer flow.
  2. Select an observed Freight offer template from the loaded save.
  3. Confirm source and current destination match the offer you intend to retarget.
  • Validate: you are working on an observed offer, not active-delivery context.
  • Common failure: no observed offers listed; run Rescan or load the correct Base Save.

Step 3 - Freight Combos

  1. Review Freight combo options for cargo + trailer compatibility.
  2. Keep current combo when it already matches your target operation.
  3. Apply a Freight combo preset only when you need a controlled override.
  • Validate: selected combo is coherent with offer template and route target.
  • Common failure: applying incompatible combo preset; return to observed-compatible combo.

Step 4 - Route Action

  1. Choose destination city and destination company for retarget.
  2. Apply route values.
  3. If scan_required appears after changes/import, run Rescan and reapply.
  • Validate: proposed destination reflects the intended freight market change.
  • Common failure: route mismatch after import; reopen Offer flow and apply route again.

Step 5 - Clone Preview

  1. Open Clone Preview.
  2. Compare current-in-save summary vs selected-for-clone summary.
  3. Confirm route before/after text matches your offer retarget decision.
  • Validate: preview shows Freight offer retarget, not active-delivery redirect.
  • Common failure: divergence warning ignored; stop and correct route/context before cloning.

Step 6 - Result

  1. Create clone.
  2. Read result message and confirm successful clone creation in new slot.
  3. Open the cloned slot in-game for final operation validation.
  4. Go to Freight Market and verify the expected offer route/origin/destination appears according to your retarget settings.
  • Validate: new slot exists and Base Save remains unchanged.
  • Validate: market content reflects the offer retarget in the cloned slot.
  • Common failure: expecting Base Save overwrite; this flow always writes to a clone slot.
Expected outcome: new cloned slot with offer retarget applied; original Base Save remains untouched.

Dispatch Active flow

Dispatch Active redirects a delivery already in progress. It only works when Base Save already contains active-delivery context with current cargo and trailer.

Step 1 - Base Save

  1. Select Base Save in Economy > Custom Delivery.
  2. Confirm this save has an active delivery in progress at save time.
  3. Run Rescan when requested by flow status.
  • Validate: Base Save stage is unlocked and Active context is available.
  • Common failure: save has no active job; load a save with active cargo + trailer or switch to Offer flow.

Step 2 - Context

  1. Open Dispatch Active flow.
  2. Read active context summary (current route/cargo/trailer context).
  3. Confirm context belongs to the delivery you intend to redirect.
  • Validate: active context is loaded and coherent before any route change.
  • Common failure: stale or wrong active context; change Base Save and rescan.

Step 3 - Cargo Combos

  1. Review Cargo combo compatibility summary for active delivery payload + trailer.
  2. Keep current active combo when no override is required.
  3. Apply compatible Cargo combo preset only when operation requires it.
  • Validate: combo remains valid for active delivery redirect.
  • Common failure: forcing invalid combo override; revert to compatible/current combo.

Step 4 - Route Action

  1. Select destination city and destination company for the in-progress delivery redirect.
  2. Apply active route values.
  3. If scan_required appears, run Rescan and apply again.
  • Validate: route action reflects active-delivery redirect behavior.
  • Common failure: trying to use this step as offer-market edit; use Dispatch Offer for that case.

Step 5 - Clone Preview

  1. Open Clone Preview.
  2. Compare current-in-save vs selected-for-clone summaries.
  3. Validate active route before/after summary lines.
  • Validate: preview shows active-delivery redirect, not Freight offer retarget.
  • Common failure: proceeding with unresolved warning text; fix context/route first.

Step 6 - Result

  1. Create clone.
  2. Confirm Result indicates successful clone creation.
  3. Open cloned slot in-game to validate redirected active delivery behavior.
  • Validate: new slot exists and Base Save remains unchanged.
  • Common failure: interpreting expected block as bug when no active delivery exists in Base Save.
Blocking rule: if no active delivery exists, execution is expected to block; switch to Dispatch Offer or load a valid active-delivery Base Save.

Dispatch Active cargo presets guide

Use this guide when you cannot find the expected cargo preset, cannot apply it, or the applied cargo is not visible in-game.

Why a cargo preset may not be visible

  1. Confirm Dispatch Active context is loaded from a Base Save with active cargo + trailer in progress.
  2. Check Flow Status and run Rescan if scan_required is present.
  3. Review compatibility summary counts (compatible templates/presets may be lower than total saved presets).
  4. If Keep current active cargo and continue is enabled, disable it to reveal cargo selection list and apply actions.

Cargo color legend and priority

  • Green: same trailer family (highest confidence).
  • Blue: cross-family overlap observed in save data (medium confidence).
  • Yellow: heuristic compatible (fallback confidence).

Operator order: prefer Green first, then Blue, then Yellow only when required.

Cargo Visual Policy (invisible cargo prevention)

  1. Safe (Recommended): applies only visual-ready presets; blocks missing visual metadata.
  2. Flexible (May break visuals): allows derived fallback when metadata is incomplete.
  3. Balanced: tries Flexible first, then retries with Safe if write fails.

Operational rule: use Safe for regular operations. Use Flexible only for controlled testing.

Quick recovery checklist

  1. Run Rescan and re-open Dispatch Active.
  2. Verify active delivery context still matches the intended job.
  3. Switch policy to Safe and apply a Green candidate first.
  4. If still blocked, test one Blue candidate and validate in clone slot result.
  5. If visuals fail after apply, revert to previous stable preset and retry with Safe-only candidates.

Operator anti-patterns

  • Starting Dispatch Active without an active delivery in progress (cargo + trailer) in Base Save.
  • Using Dispatch Active to change Freight Market offers instead of using Dispatch Offer.
  • Ignoring scan_required and trying to clone without Rescan.
  • Running Custom Jobs with cloud-synced profile context instead of offline profile context.
  • Expecting Base Save to change directly after clone execution.

SimDuty Loads workflow

SimDuty Loads is the collaboration layer for learning, sharing, importing, and auditing Offer/Active route context.

Operator quick-start (5 steps)

  1. Open Learning Preview, select source saves, run preview, then click Apply Learning.
  2. Open Learned Data and confirm entries match your current profile context.
  3. Open Share with Team and use Cargo + Trailer (Recommended) as default handoff intent.
  4. Open Import from Discord, validate preview context, then route to the matching Offer/Active flow.
  5. Open Share and Import Audit to verify traceability; if scan_required appears, run Rescan before Clone Preview expectations.

Step 1 - Learning Preview and Apply Learning

  1. Open Learning Preview in SimDuty Loads.
  2. Select source saves for learning.
  3. Run preview and review coverage of learned Offer/Active data.
  4. Click Apply Learning to persist reusable knowledge.
  • Validate: preview and apply results show learned data counts without errors.
  • Common failure: weak or empty learned output; recheck save selection and rerun preview.

Step 2 - Review Learned Data quality

  1. Open Learned Data in SimDuty Loads.
  2. Open learned sections for Offer and Active.
  3. Verify combos/placements match expected cargo and trailer context.
  4. Prefer stable candidates before publishing to team workflow.
  • Validate: learned entries are coherent for the active ATS/ETS2 profile context.
  • Common failure: mixing incompatible profile context; regenerate learning from the correct profile/save set.

Step 3 - Share intent selection

  1. Open Share with Team.
  2. Use Cargo + Trailer (Recommended) as default team handoff intent.
  3. Use Active Data only when destination guidance is needed without full combo payload.
  4. Use Full bundle (Advanced) for audit-heavy team sync when broader context packaging is required.
  • Validate: selected intent matches operational goal before publish.
  • Common failure: wrong intent for scenario; republish with the correct intent and verify audit status.

Step 4 - Import flow

  1. Open Import from Discord.
  2. Import using deep-link, Discord message/link, or JSON payload.
  3. Review import preview (type/scope/context) before confirming.
  4. Confirm import only when save context is valid for the payload type (SimDuty selected save slot or loaded Base Save, depending on type).
  5. After import, continue in the correct flow (Dispatch Offer or Dispatch Active).
  6. If flow indicates scan_required, run Rescan before expecting clone-ready state.
  • Validate: import context maps to the intended Offer/Active flow and clone stages.
  • Validate: import confirmation button is enabled before proceeding.
  • Common failure: importing Active context without active-delivery Base Save; switch save or use Offer as appropriate.

Step 5 - Audit and traceability

  1. Open Share and Import Audit after each publish/import operation.
  2. Use audit filters (All / Publish / Import / Fail) to isolate the event type you need.
  3. Check direction, status, source, and retry/latency details.
  4. Use latest audit event as first evidence for troubleshooting.
  • Validate: every critical share/import action has a traceable audit record.
  • Validate: each event card shows summary plus detail text.
  • Common failure: no clear traceability; rerun action with stable context and capture audit output.
Operational rule: SimDuty Loads prepares and distributes context, but final safety validation happens in Offer/Active Route Action and Clone Preview.

Path and reference

Main paths:

  • Economy > OVERVIEW
  • Economy > BANKING (SIMULATE, START RENTAL, CONFIRM RETURN)
  • Economy > STATEMENT (4H, 24H, 7D, Contestable, Pending, CLEAR)
  • Economy > AUDIT (APPLY CORRECTION)
  • Economy > DECLARATIONS (DECLARE)
  • Economy > Custom Delivery
  • Custom Delivery > Dispatch Offer
  • Custom Delivery > Dispatch Active
  • Custom Delivery > SimDuty Loads
  • SimDuty Loads > Share with Team
  • SimDuty Loads > Import from Discord
  • SimDuty Loads > Share and Import Audit
  • SimDuty Loads > Learning Preview
  • SimDuty Loads > Learned Data
  • Custom Delivery > Flow Status
  • Custom Delivery > Rescan
  • Custom Delivery > Clone Preview

Related Dispatch actions:

  • Open Dispatch Offer
  • Open Dispatch Active
  • Select Base Save

Validation checkpoint

  • Overview rules are reviewed before cost-impact actions in other Economy tabs.
  • Banking actions run only when corresponding gate state enables them.
  • Statement filters/presets are applied intentionally before contest decisions.
  • Audit correction is applied once with clear reason and revalidated in statement context.
  • Declaration telemetry and RP fields are consistent before submit.
  • Flow selection matches context (Offer without active delivery, Active with active delivery).
  • Base Save is selected and recognized before route actions.
  • scan_required is resolved with Rescan before apply/clone.
  • Clone preview reflects expected route/action context.
  • Execution produces a new slot and keeps Base Save intact.
  • SimDuty Loads share/import actions produce traceable audit records.
  • Selected share intent matches operational goal (Cargo + Trailer, Active Data only, or Full bundle (Advanced)).
  • Imported payload context matches the selected Offer/Active flow before clone execution.
  • Import confirmation is enabled only after valid save context is present for the payload type.
  • All SimDuty Loads sections are validated in sequence: Learning Preview, Learned Data, Share with Team, Import from Discord, and Share and Import Audit.

Quick support

Symptom: Banking action buttons stay disabled.

  • Check: whether approval/settlement state is actually available for the selected action.
  • Fix: rerun SIMULATE, refresh operation context, and retry only when gate is enabled.

Symptom: Statement numbers look inconsistent.

  • Check: active time preset and filter combination before reading grouped totals.
  • Fix: reset with CLEAR, apply one filter at a time, then re-check event groups.

Symptom: Contest action does not appear for an entry.

  • Check: whether that entry is contest-eligible in the current state.
  • Fix: move to eligible entries via Contestable filter and track status chips after submit.

Symptom: Audit correction applied but expected balance did not match.

  • Check: amount sign, reason context, and whether another correction was already applied.
  • Fix: validate latest statement entries first, then apply one controlled correction with explicit rationale.

Symptom: Declaration submit is blocked or result is unclear.

  • Check: telemetry availability and required RP fields (reference/notes/expense values).
  • Fix: complete missing fields, revalidate preview net impact, then submit once.

Symptom: Dispatch Active flow is blocked.

  • Check: whether Base Save has an in-progress active delivery with cargo + trailer context.
  • Fix: load a valid active-delivery save or switch to Dispatch Offer path.

Symptom: Dispatch Offer opens but expected market offer is missing.

  • Check: whether observed Freight offers were loaded/scanned from the selected Base Save.
  • Fix: run Rescan, then re-open Dispatch Offer and select an observed offer template.

Symptom: Offer clone succeeds but expected offer is not visible in Freight Market.

  • Check: whether the exact cloned slot is loaded and whether an owned trailer is filtering/hiding Freight offers.
  • Fix: load the cloned slot, detach owned trailer when testing Freight Market visibility, reopen market, and filter by expected origin/destination.
  • Fix: if still missing, confirm Base Save slot was valid (numeric folder with game.sii) and rerun Offer flow from scan stage.

Symptom: expected cargo preset is not visible in Dispatch Active.

  • Check: compatibility summary counts, active trailer context, and whether Keep current active cargo and continue is enabled.
  • Fix: disable keep-current mode, run Rescan, and choose a compatible candidate by color priority (Green -> Blue -> Yellow).

Symptom: cargo preset applies but cargo visuals look broken or invisible.

  • Check: active Cargo Visual Policy and candidate compatibility tier.
  • Fix: switch to Safe (Recommended), reapply a Green visual-ready preset, and validate result in clone slot.

Symptom: team received share but cannot reuse it correctly.

  • Check: share intent type and whether payload context matches Offer/Active target flow.
  • Fix: republish from Share with Team using the correct intent (Cargo + Trailer (Recommended) by default), then confirm success in Share and Import Audit.

Symptom: import succeeds but clone stages do not become ready.

  • Check: Flow Status for scan_required and Base Save context alignment.
  • Fix: run Rescan, reopen target flow, and revalidate route/context before Clone Preview.

Symptom: import preview is shown, but Import now stays disabled.

  • Check: whether payload type requires save context and whether a SimDuty selected save slot or Base Save is currently loaded.
  • Fix: select a valid save context, then reopen Import from Discord confirmation and proceed.

Symptom: audit shows failed publish/import.

  • Check: latest Share and Import Audit detail (direction, source, retry status, reason text).
  • Fix: correct failing context/input, rerun once, and confirm a successful event in audit.

Symptom: clone action is disabled after selecting values.

  • Check: Flow Status for scan_required or incomplete context.
  • Fix: run Rescan, reapply values, then reopen clone preview.

Symptom: import appears successful but values are not applicable.

  • Check: imported intent/type versus selected Offer/Active flow.
  • Fix: re-open with matching flow mode and confirm import context before apply.

Symptom: team cannot reuse shared data.

  • Check: share intent (combo/route/bundle) and payload quality.
  • Fix: preview learned data first, then share the appropriate artifact and verify audit status.

FAQ

  • When should I use each Economy tab? Use Overview for posture, Banking for rental lifecycle, Statement for ledger/contest, Audit for correction, Declarations for trip declaration, and Custom Delivery for route cloning workflows.
  • Can I skip Overview and go straight to action tabs? You can, but operationally you should check Overview first to avoid rule-state surprises in Banking or Statement outcomes.
  • Why is a Banking action unavailable? Banking buttons are state-gated; action only unlocks when approval/settlement conditions are met.
  • How should I read Statement safely? Select time preset first, then apply filters deliberately, then interpret grouped events and contest status chips.
  • When should I use Audit correction? Only when statement context confirms manual correction is required; apply once and verify resulting entries.
  • What is the safe Declarations order? Telemetry validation first, RP expenses second, preview third, submit last.
  • Can Custom Delivery overwrite my Base Save? No. Execution creates a clone in a new slot; Base Save is preserved.
  • Why does Dispatch Active block sometimes? It needs active delivery context in the loaded Base Save. Without it, the flow is intentionally blocked.
  • What is the core difference between Offer and Active? Dispatch Offer edits observed Freight Market offers; Dispatch Active redirects a delivery already in progress.
  • What do cargo preset colors mean? Green means same trailer family, Blue means observed cross-family overlap, Yellow means heuristic compatibility fallback.
  • How do I avoid invisible cargo after preset apply? Keep Cargo Visual Policy on Safe (Recommended) for normal operations and prioritize Green candidates.
  • Which share intent should I use first? Use Cargo + Trailer (Recommended) as default. Use Active Data only for route guidance and Full bundle (Advanced) for broader sync.
  • Is Full bundle (Advanced) behind an advanced mode? No. In the current UI, it is directly available when learned-data share conditions are met.
  • Why can import look successful but still require action? Import may still require Rescan and context validation before clone stages become ready.
  • Why is Import now disabled in confirmation? Some payload types require valid save context first (selected SimDuty save slot or loaded Base Save).
  • How do I verify share/import actually completed? Use Share and Import Audit and confirm a successful event with the expected direction and source.
  • When should I run Rescan? Run it whenever Flow Status indicates scan_required or after context/import changes.
  • Is SimDuty Loads required for every clone? No. Use it when you need learning/share/import collaboration or audit traceability.