For End Users and System Administrators
This document describes all configuration parameters for the StoreSettlement worker in POS Services. The StoreSettlement worker generates daily settlement files containing financial and operational data from the point-of-sale system. These files are used for accounting, reconciliation, and reporting purposes.
Settlement files contain various transaction codes (like IKU, IVA, B01, etc.) that represent different types of financial data. Each parameter below controls whether specific codes appear in the settlement file and how they are calculated.
Purpose: Determines the level of detail in settlement reporting - whether settlements are generated per store, per operator (cashier), or per workstation (cash register).
Valid Values: Comma-separated list containing one or more of:
Operator - Generates settlements grouped by cashier/operatorStore - Generates settlements grouped by store (consolidated)Workstation - Generates settlements grouped by cash register/terminalItemGroup - Generates settlements grouped by item group (rarely used)Default: Operator, Store, Workstation
Example: value="Operator, Store, Workstation"
How It Works:
Store is selected, you get one settlement file per store per day with all transactions combinedOperator is selected, you get separate settlement data for each cashier who worked that dayWorkstation is selected, you get separate settlement data for each cash registerImpacted Code(s): All settlement codes - this parameter determines the grouping level for all generated codes
Purpose: Specifies the folder location where settlement files will be saved after generation.
Valid Values: Any valid Windows file system path (must be accessible by the service account)
Default: c:\temp\
Example: value="c:\LPOS\Settlements\" or value="\\server\share\settlements\"
Important Notes:
Impacted Code(s): All settlement codes - determines where all settlement files are saved
Purpose: Controls how the settlement period is defined - whether it's a single business day, a date range, or a hybrid approach.
Valid Values:
Date - Settlement for a single business dayDateRange - Settlement spanning multiple daysHybrid - Combination approach (consult with support before using)Default: Date
When to Use Each:
Date for standard daily settlements (most common)DateRange when you need to generate settlements for multiple days at once (e.g., weekly settlements, re-running historical periods)Impacted Code(s): All settlement codes - determines the time period for all data queries
Purpose: Adjusts the settlement day boundary to align with business day instead of calendar day. Useful when stores close after midnight.
Valid Values: TimeSpan format HH:MM (hours:minutes)
Default: 0:00 (no offset, settlement day = calendar day)
Example:
value="0:00" - Settlement day runs from 00:00 to 23:59value="6:00" - Settlement day runs from 06:00 to 05:59 next dayvalue="-3:00" - Settlement day runs from 21:00 previous day to 20:59How It Works:
When you set an offset of 6:00, a settlement for "April 24" will include transactions from April 24 06:00 to April 25 05:59. This ensures late-night transactions (after midnight) are included in the correct business day.
Impacted Code(s): All settlement codes - shifts the time boundary for all transaction queries
Purpose: Controls whether non-sale items (items sold without affecting inventory) are included in settlement reports.
Valid Values: true, false
Default: false
How It Works: Non-sale items are special products that don't represent physical inventory but generate revenue (e.g., service fees, warranties, delivery charges, gift wrapping).
When to Enable:
Impacted Code(s): INO, N00-N99, O00-O99, P00-P99
Purpose: Enables tracking and reporting of cash balances in multiple currencies for stores that accept foreign currency.
Valid Values: true, false
Default: false
How It Works: When enabled, the settlement file includes separate balance sections for each currency (NOK, SEK, EUR, USD, etc.). Each tender transaction is reported with both the original currency amount and the converted amount in the store's base currency.
When to Enable:
Impacted Code(s): NO1-NO2, SE1-SE2, DA1-DA2, EU1-EU2, US1-US2, GB1-GB2, Z01-Z99
Purpose: Tracks cash movements into and out of the cash drawer during the business day (separate from sales).
Valid Values: true, false
Default: false
How It Works: Records two types of cash movements:
When to Enable:
Impacted Code(s): IVI (Inbound), IVU (Outbound)
Purpose: Reports payment card transactions with the original currency in which the card was charged (relevant for international card payments).
Valid Values: true, false
Default: false
How It Works: When a foreign customer pays with a card, this setting ensures the settlement shows both the local currency amount and the currency in which the card issuer was charged.
When to Enable:
Impacted Code(s): K01-K99 with currency codes (KNONOK, KSEUSEK, etc.)
Purpose: Reports cash transactions separated by currency type received.
Valid Values: true, false
Default: false
How It Works: Creates separate settlement lines for cash received in NOK, SEK, EUR, etc. This is different from EnableCurrencyBalance which tracks drawer balance - this tracks cash revenue by currency.
When to Enable:
Impacted Code(s): CNO, CSE, CEU, CUS, CGB, CDK, COT
Purpose: Reports the opening cash float by currency type.
Valid Values: true, false
Default: false
How It Works: When cashiers start their shift with an opening float (starting cash), this tracks how much of each currency was in that float.
When to Enable:
StoreSettlementEnableCurrencyBalance=true to function.Impacted Code(s): LNO, LSE, LEU, LUS, LGB, LDK, LOT
Purpose: Reports inbound/outbound cash movements separated by currency.
Valid Values: true, false
Default: false
How It Works: Extends EnableInboundOutboundChange to show which currency was added or removed. For example, if manager adds €50 in coins mid-day, this appears as EUR inbound change.
When to Enable:
StoreSettlementEnableInboundOutboundChange=true to function.Impacted Code(s): IVI, IVU with currency codes
Purpose: Enables fallback values when primary data sources are missing or incomplete.
Valid Values: true, false
Default: false
How It Works: If certain data isn't available (e.g., reason codes missing, item groups undefined), the system uses predefined fallback values instead of failing or skipping the transaction.
When to Enable:
Impacted Code(s): IRC, IRS and various codes when fallback logic applies
Purpose: Adds a grand total line at the end of settlement file summarizing all transactions.
Valid Values: true, false
Default: false
How It Works: Calculates and outputs a summary line (ING) showing total revenue across all transaction types, providing a single reconciliation point.
When to Enable:
Impacted Code(s): ING
Purpose: Enables lottery transaction processing and reporting in settlement files.
Valid Values: true, false
Default: false
How It Works: When enabled, lottery ticket sales, prize payouts, and related transactions are included in the settlement with appropriate categorization. Lottery sales are tracked separately from regular merchandise due to different commission structures and accounting treatment.
When to Enable:
Important Notes:
Impacted Code(s): IL1-IL9 (Lottery sales), IP1-IP9 (Prize payouts)
Purpose: Enables kickback/commission calculation and reporting in settlement files.
Valid Values: true, false
Default: false
How It Works: Kickbacks are financial returns or commissions that the retailer receives from suppliers based on sales volume, promotion participation, or contractual agreements. When enabled, the settlement calculates and reports these amounts based on configured rules.
When to Enable:
Common Kickback Scenarios:
Important Notes:
Impacted Code(s): IKB, KB1-KB9
Purpose: Indicates whether non-sale item transactions (breakage, internal use, etc.) require and use reason codes.
Valid Values: true, false
Default: false
How It Works: When enabled, the settlement process expects reason codes on item transactions like breakage or internal use, and includes those reason codes in reporting. This provides audit trail for why items were removed from inventory.
When to Enable:
Impacted Code(s): IV1-IV9 with reason code breakdown
Purpose: Indicates whether discount transactions require reason codes for audit and reporting purposes.
Valid Values: true, false
Default: false
How It Works: When enabled, the settlement process expects reason codes for discount transactions and includes them in validation and reporting. This is particularly important for manual discounts where managers must document why a discount was given.
When to Enable:
Common Discount Reasons:
Important Notes:
Impacted Code(s): IRM, IRK, IRP, IRG, IGR with reason code details
Purpose: Defines which VAT rates are used in settlement reporting and maps them to settlement file codes.
Valid Values: Semicolon-separated list in format CODE=RATE
Default: IM1=25;IM2=0;IM3=14;IM4=99
Example: value="IM1=25.00;IM2=15.00;IM3=12.00;IM4=0.00"
How It Works:
Country-Specific Examples:
IM1=25;IM2=15;IM3=0 (standard, reduced, zero)IM1=25;IM2=12;IM3=6;IM4=0IM1=25;IM2=0Impacted Code(s): IM1-IM9
Purpose: Specifies VAT rates for delayed payment transactions (credit sales, invoiced sales).
Valid Values: Semicolon-separated list in format CODE=RATE
Default: Empty
Example: value="IZ1=25.0;IZ2=15.0;IZ3=0.0"
How It Works: Credit sales or invoiced transactions often need separate VAT tracking since payment happens later. These are sales where customer takes goods now but pays later (account customers, invoice sales).
When to Configure:
Impacted Code(s): IZ1-IZ5
Purpose: Specifies VAT rates for bottle/can deposit refund transactions.
Valid Values: Semicolon-separated list in format CODE=RATE
Default: Empty
Example: value="IA1=25.0;IA2=0.0"
How It Works: Deposit refunds (bottle/can returns) have special VAT treatment. Original deposit usually includes VAT, refund should match. This configuration ensures correct VAT accounting for deposit returns.
Important Notes:
Impacted Code(s): IA1-IA5 (IN), IB1-IB5 (OUT)
Purpose: Specifies VAT rates for lottery prize payouts.
Valid Values: Semicolon-separated list in format CODE=RATE
Default: Empty
Example: value="IP1=0.0" (prize payouts typically have 0% VAT)
How It Works: When store pays out lottery prizes, these need separate VAT tracking. Prize payouts are typically VAT-exempt as they represent return of customers' money, not store revenue.
When to Configure:
Impacted Code(s): IP1-IP5
Purpose: Specifies VAT rates specific to online grocery order transactions.
Valid Values: Semicolon-separated list in format CODE=RATE
Default: Empty
Example: value="IC1=25.00;IC2=15.00;IC3=0.00"
How It Works: Online grocery orders picked up in-store need separate tracking from regular POS sales. This allows analyzing online channel performance and ensures correct accounting treatment.
When to Configure:
Related Configuration: Use with StoreSettlementGroceriesOnlinePriceChannel
Impacted Code(s): IC1-IC5
Purpose: Specifies VAT rates for web shop transactions processed through the POS system.
Valid Values: Semicolon-separated list in format CODE=RATE
Default: Empty
Example: value="IW1=25.0;IW2=15.0;IW3=0.0"
How It Works: Similar to groceries online, but for non-food web shop orders. Separates e-commerce transactions from physical store sales in settlement reporting.
When to Configure:
Impacted Code(s): IW1-IW5
Purpose: Defines VAT rates that apply to rebate transactions for own member organization.
Valid Values: Comma-separated list of VAT rates
Default: Empty
Example: value="25,15,0"
How It Works: Specifies which VAT rates apply when members of the retail chain's own loyalty program receive rebates or member discounts. This ensures correct VAT accounting for member benefit programs.
When to Configure:
Common Usage Scenarios:
Important Notes:
Impacted Code(s): IR1-IR5 (Own member rebates)
Purpose: Defines VAT rates that apply to rebate transactions for foreign member organizations.
Valid Values: Comma-separated list of VAT rates
Default: Empty
Example: value="25,15"
How It Works: Used when members from partner organizations (e.g., reciprocal member agreements with other retail chains) receive rebates. Separates foreign member benefits from own member benefits in settlement and accounting.
When to Configure:
Common Usage Scenarios:
Important Notes:
Impacted Code(s): IF1-IF5 (Foreign member rebates)
Purpose: Specifies which types of non-sale item transactions should be included in settlement reporting.
Valid Values: Comma-separated list of transaction types:
Breakage - Damaged items written offInternalUse - Items used internally by storeInventory - Physical inventory adjustmentsStockAdjustment - Manual stock correctionsReturn - Returns to supplierShrinkage - Loss/theftDefault: Empty (no item transactions included)
Example: value="Breakage,Inventory,Shrinkage"
How It Works: Only the transaction types listed will appear in settlement. Use this to focus on specific inventory movements that need daily reporting.
When to Configure:
Impacted Code(s): IV1-IV9
Purpose: Defines which reason/action code combinations identify breakage transactions.
Valid Values: Comma-separated list of code pairs in parentheses (reason,action)
Default: Empty
Example: value="(10,5),(11,5),(12,5)"
How It Works: POS system uses reason codes and action codes to classify transactions. This parameter tells settlement which combinations mean "breakage" so they can be reported correctly.
When to Configure:
Impacted Code(s): IV2, IBR
Purpose: Defines reason/action codes that identify delayed payment (credit) transactions.
Valid Values: Comma-separated list of code pairs (reason,action)
Default: Empty
Example: value="(16,11),(17,11)"
How It Works: Identifies sales where customer takes goods immediately but pays later (invoice sales, account customers). These need special handling in settlement.
When to Configure:
Impacted Code(s): IZ1-IZ5
Purpose: Defines reason codes for manual cash in/out transactions (not related to sales).
Valid Values: Comma-separated list of reason codes
Default: Empty
Example: value="101,102,103"
How It Works: When cashiers manually add or remove cash from drawer (not for change making), these codes identify the reason. Used for tracking non-sales cash movements.
Common Reasons:
Impacted Code(s): IIN, IUT
Purpose: Specifies which item groups represent deposit refund out (bottle/can return) transactions.
Valid Values: Comma-separated list of item group numbers
Default: Empty
Example: value="1,8,15"
How It Works: Bottle and can deposits are tracked by item group. This parameter tells settlement which groups contain deposit refund items so they can be properly categorized.
When to Configure:
Impacted Code(s): IUP, IIP
Purpose: Specifies which item groups represent lottery prize payout transactions.
Valid Values: Comma-separated list of item group numbers
Default: Empty
Example: value="50,51,52"
How It Works: When lottery prizes are paid out, the transaction is recorded against specific item groups. This identifies those groups so settlement can track prize payouts separately.
When to Configure:
Impacted Code(s): IP1-IP5
Purpose: List of EAN codes (barcodes) that trigger automatic deposit refund handling.
Valid Values: Comma-separated list of EAN barcodes
Default: Empty
Example: value="7035620001017,7035620001024,7035620001031"
How It Works: These EANs are typically printed on reverse vending machine (RVM) receipts or deposit return vouchers. When scanned at POS, they automatically process the deposit refund without requiring manual intervention or item lookup.
When to Configure:
Common Scenarios:
Important Notes:
Impacted Code(s): IUP, IIP, IA/IB codes
Purpose: Defines gift card type codes used in the system for settlement categorization.
Valid Values: Comma-separated list of gift card type identifiers
Default: Empty
Example: value="GIFT01,EGIFT01,FOREIGN01"
How It Works: Identifies and categorizes different types of gift cards: own store cards (full liability), electronic/mobile cards, and third-party/foreign cards accepted for payment. This ensures proper accounting treatment for each gift card type.
When to Configure:
Gift Card Categories:
Important Notes:
Impacted Code(s): IGK (Own gift cards sold), IG1 (Foreign gift cards), tender codes for redemptions
Purpose: Reason codes that identify dated item sales (items sold at discount due to approaching expiration date).
Valid Values: Comma-separated list of reason codes
Default: Empty
Example: value="BESTBEFORE,EXPIRY,DATED,CLEARANCE"
How It Works: Tracks sales of items with date-related markdowns, typically perishables approaching best-before date or seasonal items past season. Provides visibility into waste reduction efforts and markdown effectiveness.
When to Configure:
Common Use Cases:
Business Benefits:
Important Notes:
Impacted Code(s): IDT, DT1-DT9 (Dated item sales)
Purpose: Specifies the cashier/operator number to use when actual cashier cannot be identified.
Valid Values: Any string value (typically numeric)
Default: 9999
Example: value="999999"
How It Works: Sometimes transactions occur without proper cashier login (system errors, technical issues). This fallback cashier number ensures settlement can still be generated.
Important Notes:
Impacted Code(s): All operator-level codes when operator cannot be determined
Purpose: Specifies which payment card issuer IDs represent credit card transactions (vs. debit).
Valid Values: Comma-separated list of issuer ID codes
Default: Empty
Example: value="3,4,5,6" (Visa, Mastercard, Amex, Diners)
How It Works: Different cards may have different processing fees or settlement timing. This separates credit cards from debit cards in reporting.
When to Configure:
Impacted Code(s): K01-K99 with credit classification
Purpose: Identifies codes where negative counted values are valid (e.g., overage that must be removed).
Valid Values: Comma-separated list of code identifiers
Default: Empty
Example: value="IVI,IUT"
How It Works: Normally counted cash should be positive. However, some situations require recording negative amounts (removing excess cash, correcting overages). This prevents validation errors for legitimate negative values.
Impacted Code(s): Specified codes where negative values allowed
Purpose: General payment card type classification for settlement reporting.
Valid Values: Comma-separated list of card type codes
Default: Empty
Example: value="VISA,MC,AMEX"
How It Works: Groups payment cards by type for summary reporting. Provides high-level view of payment mix.
Impacted Code(s): R01-R99
Purpose: Maps specific payment cards to 'S' category in settlement (typically store-branded cards).
Valid Values: Comma-separated list of card identifiers
Default: Empty
Example: value="12,19" (might represent store loyalty card IDs)
How It Works: Some retailers have their own branded credit cards. These are tracked separately from external cards for commission and partnership accounting.
Impacted Code(s): S01-S99
Purpose: Maps specific payment cards to 'C' category in settlement (typically customer cards or specific card programs).
Valid Values: Comma-separated list of card identifiers
Default: Empty
Example: value="COOP,TRUMF"
How It Works: Similar to PaymentCardsS but different category. May represent partner cards, co-branded cards, or specific card programs requiring separate tracking.
Impacted Code(s): C01-C99
Purpose: Identifies coupon tender types for settlement categorization.
Valid Values: Comma-separated list of coupon type codes
Default: Empty
Example: value="MFG,STORE,DIGITAL"
How It Works: Different coupon types (manufacturer, store, digital/mobile) may have different reimbursement processes. Separating them in settlement aids reconciliation.
Coupon Categories:
Impacted Code(s): Q01-Q99
Purpose: Defines which tender control transactions affect cash drawer balance calculations.
Valid Values: Comma-separated list of control types:
Drop - Cash drops to safePayedIn - Cash added to drawerPayedOut - Cash paid out for non-salesFloat - Starting cash floatDefault: Empty
Example: value="Drop,PayedIn,PayedOut,Float"
How It Works: Cash drawer balance = opening float + sales + paid-in - paid-out - drops. This configuration determines which control transactions are included in that calculation.
Impacted Code(s): IDR, IKI, IIN, IUT
Purpose: Specifies the price channel identifier for online grocery transactions.
Valid Values: String matching a price channel key in the system
Default: Empty
Example: value="ShopAndGoCheckTerminal"
How It Works: Price channels allow different pricing for online vs. in-store. This identifies which channel represents online grocery orders so settlement can categorize them correctly.
When to Configure:
Impacted Code(s): IC1-IC5 (online grocery codes)
| Code Range | Description | Controlling Parameters |
|---|---|---|
| B01-B99 | Cash balance by tender type | None (always generated) |
| K01-K99 | Payment card transactions by card type | StoreSettlementPaymentCardTypes, EnablePaymentCardInCurrency |
| S01-S99 | Store-branded payment cards | StoreSettlementPaymentCardsS |
| C01-C99 | Customer/partner payment cards | StoreSettlementPaymentCardsC |
| Q01-Q99 | Coupon transactions by type | StoreSettlementCouponTypes |
| R01-R99 | General payment card reporting | StoreSettlementPaymentCardTypes |
| IKU | Customer count | None |
| IVA | Item quantity sold | None |
| IM1-IM9 | Sales by VAT rate | StoreSettlementVatCodes |
| IZ1-IZ5 | Delayed payment (credit) sales by VAT | StoreSettlementDelayedPaymentVatRates |
| IC1-IC5 | Online grocery by VAT | StoreSettlementGroceriesOnlineVatRates |
| IW1-IW5 | Web shop by VAT | StoreSettlementWebShopVatRates |
| IA1-IA5, IB1-IB5 | Deposit refund in/out by VAT | StoreSettlementDepositRefundVatRates |
| IP1-IP5 | Prize payouts by VAT | StoreSettlementPrizePayoutVatRates |
| IR1-IR5 | Own member rebates by VAT | StoreSettlementRebateOwnMemberVatRates |
| IF1-IF5 | Foreign member rebates by VAT | StoreSettlementRebateForeignMemberVatRates |
| INO | Non-sale items | StoreSettlementEnableNonsale |
| IVI, IVU | Inbound/outbound change | StoreSettlementEnableInboundOutboundChange |
| IV1-IV9 | Item transactions (breakage, inventory, etc.) | StoreSettlementEnabledItemTransactionTypes |
| IDR, IKI, IIN, IUT | Tender control transactions | StoreSettlementCashDrawerTenderControlTypes |
| IRM, IRK, IRP, IRG, IGR | Discount types | StoreSettlementHasDiscountReasonCodes |
| ING | Grand total | StoreSettlementEnableGrandTotal |
| IGK, IG1 | Gift card sales (own/foreign) | StoreSettlementGiftCardTypesCodes |
| IL1-IL9 | Lottery sales | StoreSettlementEnableLottery |
| IKB, KB1-KB9 | Kickback/commission | StoreSettlementEnableKickBack |
| IDT, DT1-DT9 | Dated item sales | StoreSettlementReasonDateItemSales |
| IUP, IIP | Deposit refund out/in | StoreSettlementDepositRefundOutItemGroups, StoreSettlementAutomaticDepositRefundEans |
| CNO, CSE, CEU, etc. | Cash by currency | StoreSettlementEnableCashInCurrency |
| NO1-NO2, SE1-SE2, etc. | Currency balance | StoreSettlementEnableCurrencyBalance |
| LNO, LSE, LEU, etc. | Delivered balance by currency | StoreSettlementEnableDeliveredBalanceInCurrency |
| IRC, IRS | Fallback values | StoreSettlementEnableFallbacks |
| Parameter | Default | Key Codes Affected |
|---|---|---|
| SettlementType | Operator, Store, Workstation | All codes |
| StoreSettlementOutputDirectory | c:\temp\ | File system |
| StoreSettlementPeriodType | Date | All codes |
| StoreSettlementTimeOffset | 0:00 | All codes |
| StoreSettlementEnableNonsale | false | INO, N00-N99, O00-O99, P00-P99 |
| StoreSettlementEnableCurrencyBalance | false | NO1-NO2, SE1-SE2, DA1-DA2, etc. |
| StoreSettlementEnableInboundOutboundChange | false | IVI, IVU |
| StoreSettlementEnablePaymentCardInCurrency | false | K codes with currency |
| StoreSettlementEnableCashInCurrency | false | CNO, CSE, CEU, COT |
| StoreSettlementEnableFallbacks | false | IRC, IRS |
| StoreSettlementEnableGrandTotal | false | ING |
| StoreSettlementEnableLottery | false | IL1-IL9, IP1-IP9 |
| StoreSettlementEnableKickBack | false | IKB, KB1-KB9 |
| StoreSettlementHasItemTransactionReasonCodes | false | IV1-IV9 with reasons |
| StoreSettlementHasDiscountReasonCodes | false | IRM, IRK, IRP, IRG, IGR with reasons |
| StoreSettlementEnabledItemTransactionTypes | Empty | IV1-IV9 |
| StoreSettlementVatCodes | IM1=25;IM2=0;IM3=14;IM4=99 | IM1-IM4 |
| StoreSettlementDelayedPaymentVatRates | Empty | IZ1-IZ5 |
| StoreSettlementDepositRefundVatRates | Empty | IA1-IA5, IB1-IB5 |
| StoreSettlementPrizePayoutVatRates | Empty | IP1-IP5 |
| StoreSettlementGroceriesOnlineVatRates | Empty | IC1-IC5 |
| StoreSettlementWebShopVatRates | Empty | IW1-IW5 |
| StoreSettlementRebateOwnMemberVatRates | Empty | IR1-IR5 |
| StoreSettlementRebateForeignMemberVatRates | Empty | IF1-IF5 |
| StoreSettlementCouponTypes | Empty | Q01-Q99 |
| StoreSettlementPaymentCardTypes | Empty | R01-R99 |
| StoreSettlementPaymentCardsS | Empty | S01-S99 |
| StoreSettlementPaymentCardsC | Empty | C01-C99 |
| StoreSettlementPrizePayoutItemGroups | Empty | IP codes |
| StoreSettlementDepositRefundOutItemGroups | Empty | IUP, IIP, IA/IB codes |
| StoreSettlementAutomaticDepositRefundEans | Empty | IUP, IIP, IA/IB codes |
| StoreSettlementGiftCardTypesCodes | Empty | IGK, IG1 |
| StoreSettlementReasonDateItemSales | Empty | IDT, DT1-DT9 |
| StoreSettlementCashDrawerTenderControlTypes | Empty | IDR, IKI, IIN, IUT, etc. |
| StoreSettlementGroceriesOnlinePriceChannel | Empty | IC codes |
| StoreSettlementUnknownCashierNumber | 9999 | Operator-level codes |
<add key="SettlementType" value="Store, Workstation" />
<add key="StoreSettlementOutputDirectory" value="c:\LPOS\Settlements\" />
<add key="StoreSettlementPeriodType" value="Date" />
<add key="StoreSettlementVatCodes" value="IM1=25;IM2=15;IM3=0" />
<add key="StoreSettlementEnabledItemTransactionTypes" value="Breakage,Inventory" /><add key="SettlementType" value="Store, Operator" />
<add key="StoreSettlementEnableCurrencyBalance" value="true" />
<add key="StoreSettlementEnablePaymentCardInCurrency" value="true" />
<add key="StoreSettlementEnableCashInCurrency" value="true" />
<add key="StoreSettlementEnableDeliveredBalanceInCurrency" value="true" /><add key="StoreSettlementGroceriesOnlinePriceChannel" value="ShopAndGoCheckTerminal" />
<add key="StoreSettlementGroceriesOnlineVatRates" value="IC1=25.00;IC2=15.00;IC3=0.00" />
<add key="StoreSettlementDepositRefundOutItemGroups" value="1,8" />
<add key="StoreSettlementDepositRefundVatRates" value="1=25.0;2=0.0" />
<add key="StoreSettlementAutomaticDepositRefundEans" value="7035620001017,7035620001024" />
<add key="StoreSettlementReasonDateItemSales" value="BESTBEFORE,EXPIRY" /><add key="StoreSettlementTimeOffset" value="6:00" />
<add key="StoreSettlementDelayedPaymentReasonAndActionCodes" value="(16,11)" />
<add key="StoreSettlementDelayedPaymentVatRates" value="IZ1=25.0;IZ2=15.0" />
<add key="StoreSettlementCashDrawerTenderControlTypes" value="Drop,PayedIn,PayedOut,Float" /><add key="StoreSettlementRebateOwnMemberVatRates" value="25,15,0" />
<add key="StoreSettlementRebateForeignMemberVatRates" value="25,15" />
<add key="StoreSettlementEnableLottery" value="true" />
<add key="StoreSettlementPrizePayoutVatRates" value="IP1=0.0" />
<add key="StoreSettlementPrizePayoutItemGroups" value="50,51,52" /><add key="StoreSettlementEnableKickBack" value="true" />
<add key="StoreSettlementGiftCardTypesCodes" value="GIFT01,EGIFT01,FOREIGN01" />
<add key="StoreSettlementHasDiscountReasonCodes" value="true" />Configuration File Syntax:
Parameter Values:
Directory and Permissions:
Testing:
Document Version: 2.0 (Updated with 8 New Parameters)
Last Updated: November 2025
Applicable to: POS Services StoreSettlement Worker
Configuration Files: App.config, POSServices.Workers.exe.config
Changes in Version 2.0:
End of Documentation