Writing off credits via CSV

Important
023360: Writing Off Credits via CSV is not enabled by default.
Please contact the Development team for further information if you would like to use this feature.
Additional charges may apply.

Overview

Writing Off Credits via CSV allows multiple customer credit balances to be written off in a single process using a CSV file.
The feature reads customer details and write-off values from a CSV file, matches them against unallocated customer credits, and automatically applies the write-off according to the configured matching rules.
By default, Khaos Control writes off credits from the oldest transaction to the newest transaction until the requested write-off value has been reached.

How the Write-Off Process Works

When a write-off value is specified in the import file, Khaos Control:
  1. Finds the customer's unallocated credits.
  2. Orders the transactions by date, oldest first.
  3. Applies the write-off value against those transactions.
  4. Continues until the specified write-off amount has been fully allocated.
If the remaining write-off value is less than the value of the next transaction, Khaos Control will partially write off that transaction instead of writing off the full amount.

Example

If a customer has:

TransactionValue
Credit 1£3,000
Credit 2£2,000
Credit 3£4,000

And the CSV file requests a write-off of £7,875, Khaos Control will:
  • Write off £3,000 from Credit 1.
  • Write off £2,000 from Credit 2.
  • Write off £2,875 from Credit 3.
The remaining balance of Credit 3 will remain unallocated.

Configuration

An updated application and changelog will be supplied with this functionality.
Two hidden System Value (SVN) options control the write-off behaviour:

OptionDescription
CSV_WRITEOFF_OLDEST_MATCHWrites off transactions from oldest to newest.
CSV_WRITEOFF_EXACT_MATCHAttempts to find an exact matching credit value before applying oldest-first matching.

No additional configuration is normally required.

How Customer Matching Works

The CSV file is matched against customer records using:
  • Company URN
  • Company Name
  • Company Class
  • Write-off value
Khaos Control uses information from the Unallocated Transactions report and processes matching credits according to the configured SVN options.

Using the Feature

Step 1: Open Unallocated Transactions

Go to:

[Accounts | Nominal Accounts | Unallocated Transactions]

This grid displays customer credits that are available for write-off.

Step 2: Create the CSV File

Create a CSV file containing:
  • Customer URN
  • Customer Name
  • Company Class
  • Write-off value in the Adj. Pot column

Requirements

  • Each customer must appear on a separate row.
  • Values must match the customer record exactly.
  • Only customers with available unallocated credits can be processed.

Step 3: Refresh the Grid

Save and close the CSV file.
Return to:

[Accounts | Nominal Accounts | Unallocated Transactions]

Refresh the screen to ensure all available credits are displayed before processing the write-off.

Step 4: Start the Write-Off Process

  1. Open the Other Actions menu.
  2. Select Write Off Credits.

Step 5: Select the CSV File

Browse to and select the write-off file.
Khaos Control will:
  • Validate each row.
  • Identify eligible write-offs.
  • Skip invalid entries.
  • Generate a log detailing any skipped records and the reason they could not be processed.

Step 6: Confirm the Write-Off

If valid write-offs are found, a confirmation window will appear.
This uses the same write-off process and confirmation dialog as the standard manual bad debt write-off procedure.
Enter the required details and confirm the write-off.

Step 7: Complete the Process

The credits will be written off according to the configured matching method.
Completed write-offs can be viewed from the customer's:

[Customer | Statement] tab.

Invalid Write-Offs

Rows will be skipped if:
  • The customer URN is incorrect.
  • The customer name does not match.
  • The company class does not match.
  • No unallocated credits exist for the customer.
  • The CSV data is invalid.
A validation log is produced when processing completes.

Matching Methods

Default Behaviour

By default, Khaos Control:
  • Sorts unallocated transactions by date.
  • Processes credits from oldest to newest.
  • Supports partial transaction write-offs where necessary.
This behaviour is controlled by:

CSV_WRITEOFF_OLDEST_MATCH

which is enabled by default.

Exact Match Behaviour

If the following option is enabled:

CSV_WRITEOFF_EXACT_MATCH

Khaos Control will:
  1. Search the customer's transactions for a credit value that exactly matches the requested write-off amount.
  2. Write off the matching transaction if found.
  3. If no exact match exists, revert to the standard oldest-to-newest processing method.

System Value Behaviour

ConfigurationResult
CSV_WRITEOFF_OLDEST_MATCH enabledWrites off credits from oldest to newest.
CSV_WRITEOFF_EXACT_MATCH enabledSearches for an exact value match before applying oldest-first processing.
Both options enabledExact match is attempted first. If no match is found, oldest-first processing is used.
Neither option enabledNo credits will be written off.

Additional Information

  • Processing is performed against unallocated credit transactions only.
  • Partial write-offs are supported when the remaining write-off amount is less than the next available credit.
  • A customer's credit history and write-offs can be reviewed from the Statement tab.
  • Validation logs are automatically generated for skipped records to help identify data issues before reprocessing.
  • Manual credit and bad debt write-off procedures
  • Unallocated Transactions
  • Customer Statement Tab
  • Nominal Accounts Overview
  • Accounts Module Overview

Did you find this article helpful?