Gasell has two active external debt collection integrations (Svea Inkasso, Invoice Inkasso (Qvickly)) plus an internal Self-Collection process. The external ones share the same fixed-width flat file format over SFTP. The formats is legacy Intrum/Svea formats.

For the Svea Inkasso process (standard), Gasell starts the debt collection process after the debcollection letter has been sent. So Both the reminder letter and the debt collection letter is handled by Gasell. 

For the Invoice Inkasso process the process starts after the reminder letter and the debt collection process is handled per individual invoice.

Cases OUT — Our system → Debt collector

Format: Fixed-width text file (batch), uploaded via SFTP Code: Models/DebtCollection/Intrum/NewCasesFile.php

Per case (contract):

• Our internal customer ID
• Debt collector's customer number

Customer identity:

• Social security number (stripped of -/+)
• Name (private or company)
• Address, zip, city
• Phone
• C/O name (optional)
• Country code ISO-3
• Customer type: private / company / unknown

Per invoice:

• OCR reference
• Invoice date, due date
• Invoice remaining amount (öre)
• Late payment fee
• Invoice type:
  • 01 Grid invoice part 1
  • 02 Standard/power invoice
  • 06 Collection fee
  • 14 Reminder fee
  • 89 Production facility
• Currency (ISO 4217)
• Invoice comment / delivery address

Energy/site context per invoice:

• Site object ID
• Site consumption (kWh)
• Net area code
• Contract termination date
• Site disconnection date

Status updates IN — Debt collector → Our system

Gasell sends files but receives nothing back automatically. There is no inbound cron job, no file parser, and no status sync.

Internal statuses are tracked outbound-only:

• DEMAND_PROCESS_REQUEST_1
• LATECOMER_REQUEST_2
• INJUNCTION_TO_PAY
• DEMAND_PROCESS_INVOICE
• Self-collection variants (termination notice, bailiff notice, etc.)

Payments from Gasell to debt collector 

When a payment is registered in Gasell on a debt-collected invoice, we notify the collector via a Messages file:

Code: Models/DebtCollection/Intrum/MessagesFile.php

Payment notification (outbound, post 620):

• Debt collector case reference
• OCR reference
• Payment date, payment amount
• Invoice remaining amount after payment
• Site object ID

Site event notifications (outbound, posts 660/661/662):

• Contract termination
• Site disconnection
• Site reconnection
• Includes: site ID, event date, new customer address, invoice type

Payments from debt collector → Our system

Payments are received as standard OCR/BGC bank file payments, not through a separate debt collection format. They are identified as debt collection payments in two ways:

Automatic identification (BGC file)

When a BGC Max bank file is imported, the payer name field (bgc_name) is checked:

• Contains "SVEA INKASSO AB" → payment_source_id = DEBT_COLLECTION_COMPANY
• Contains "INVOICE INKASSO AB" → payment_source_id = DEBT_COLLECTION_COMPANY

Code: Models/Payment/File/Row/DbObject.php

Manual registration

In the admin UI ("Unregistered payments"), there is a button "Register debt collection payment" that opens the payment registration form with payment_source_id pre-set to DEBT_COLLECTION_COMPANY.

Code: sites/adm/application/modules/payment/Controllers/PaymentRegistrationController.php

Data captured per payment

Payment sources: Models/Payment/Source.php

• 1 = Customer
• 2 = Debt collection company
• 3 = External company (Markedskraft)
• 4 = External company (Svea Ekonomi)