Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.leedab.com/llms.txt

Use this file to discover all available pages before exploring further.

When a deduction batch arrives, Deductions reads every line, assigns it to the right category, generates a numbered credit note per item, and produces a summary spreadsheet by driver and category — automatically.

​
Sources

SourceWhat it monitors
Client deduction sheetsIncoming monthly batches
Monthly invoicesRecords to match deduction lines against
Driver recordsDriver identifiers and assignment history

​
Triggers

  • New deduction batch — A new monthly file is received
  • Dispute window — A deadline is approaching for an unresolved line
  • Refund pending — A credit note was issued but the refund hasn’t been confirmed

​
Outputs

OutputDescription
Numbered PDFsSequentially numbered credit note per deductible line
Summary spreadsheetTotals by driver and category with line-level detail
Refund queueIssued credit notes awaiting confirmation, sorted by aging

​
Categories

CategoryCovers
Lost shipmentsDispatched but not confirmed received
Traffic finesFines against vehicles during delivery
Vehicle damageDamage claims on a specific run
SIMsSIM card or device charges in the batch
Additional categories are configured during onboarding and stored in Deductions’ memory.

​
Memory

Deductions keeps a history of prior batches, credit note numbers, and categorization decisions. It catches duplicate lines across batches, tracks unresolved refunds, and flags unusual spikes in a category.

​
Usage

Mention @deductions in Slack, Teams, WhatsApp, or Telegram. 
@deductions  Has the April batch been processed?
@deductions  Show me the summary for driver D-1188 across the last three months.
@deductions  Which credit notes from March are still showing as refund pending?
@deductions  Flag line 47 in the May batch as disputed — the loss occurred before the contracted period.