Skip to main content

Create case as managing partner

POST 
/managed-cases

Creates a collection case on behalf of your client (or yourself) through the Debitura platform.

Understanding the Creditor Field: The creditor is the party that the debtor owes money to. This can be:

  • Your client's company - When you're submitting cases on behalf of clients you represent
  • Your own company - When you're submitting your own debt collection cases

How It Works:

  1. You provide the creditor's basic information (company name + country)
  2. Debitura creates a creditor record (if one doesn't exist)
  3. The collection case is created under that creditor
  4. You are set as the managing partner
  5. The case is automatically assigned to a collection partner based on jurisdiction

Managing Partner Benefits:

  • Submit cases on behalf of your clients via API
  • Maintain your client relationships
  • Leverage Debitura's global partner network
  • Monitor case progress through read-only access
  • Provide full-service debt recovery to your clients

Required Fields:

  • CreditorCompanyName - The company name of who the debtor owes money to
  • CreditorCountryAlpha2 OR CreditorCountry - Creditor's country (provide either code or name)
  • CurrencyCode - Case currency (e.g., 'USD', 'EUR', 'DKK')
  • Date - Invoice issue date
  • AmountToRecover - Claim amount
  • Debtor - Complete debtor information with jurisdiction

Debtor Rules:

  • debtor.type must be "Company" or "Private" (case-insensitive)
    • Company → debtor.name is mandatory (company name)
    • Private → debtor.name is mandatory (individual's full name)
  • For Company debtors, debtor.contactPerson is required
  • debtor.country (or debtor.countryAlpha2) is always required
  • debtor.stateAlpha2 is required for US cases - provide the two-letter state code (e.g., "CA", "NY"). For non-US cases, this field is optional.
  • debtor.state is a general-purpose region field (not used for US jurisdiction resolution)

Optional Fields:

  • DueDate - Invoice due date
  • AmountToRecoverOver6Months - Cumulative amount more than 6 months overdue (includes 12+ and 24+)
  • AmountToRecoverOver12Months - Cumulative amount more than 12 months overdue (includes 24+)
  • AmountToRecoverOver24Months - Cumulative amount more than 24 months overdue
  • ClaimLines - The unpaid invoices making up the claim (see below)
  • Comments - Additional notes
  • ClaimDescription - Description of the claim
  • CreditorReference - Your client's internal reference
  • CollectionPartnerId - Override automatic partner matching
  • IsTest - Mark as test case (excluded from production metrics)

Submitting Claim Lines (recommended for multi-invoice claims): Instead of totalling the claim yourself, send the unpaid invoices and let us do the arithmetic:

"claimLines": [
  { "dueDate": "2024-01-15", "amount": 423.42, "reference": "INV-1001" },
  { "dueDate": "2025-05-02", "amount": 700.87, "reference": "INV-1042" }
]
  • amount is the outstanding balance on that invoice — what the debtor still owes on it, already net of payments received and credit notes issued. It is not the invoice's original face value. Leave fully settled invoices out; every amount must be greater than zero, with at most 2 decimals.
  • We derive AmountToRecover and all three age buckets from the lines, so send claimLines instead of AmountToRecover and the AmountToRecoverOver6/12/24Months fields. Sending both is a 400.
  • Use claimLines whenever the debtor has already part-paid: it is the only way to express an honest age profile on a part-paid claim, because the buckets are then computed on the same outstanding balances the total is computed on.
  • claimLines prices on exact age data. Sending a single DueDate instead is an approximation and can produce a different quote for the same claim.
  • claimLines is a pricing input only. It is not stored and is not shown to the collecting partner — include a per-invoice breakdown in Comments if the partner needs to see one.
  • Maximum 1000 lines. Per-line errors are returned keyed by index, e.g. ClaimLines[2].DueDate.
  • If you omit the case-level DueDate, it is set to the oldest due date across your lines — so in that case Date must not be later than the earliest claimLines dueDate, or the request is rejected with a 400 on Date. Send an explicit DueDate if you need a different case due date.

Response: Returns the created case details including the case ID, reference number, and assignment information.

Important Notes:

  • The 12+ and 24+ fields must be supplied together. The 6+ field is optional, but when supplied it requires both other buckets.
  • Cumulative values must satisfy AmountToRecover ≥ 6+ ≥ 12+ ≥ 24+. DueDate may coexist with age buckets.
  • Creditor records are created fresh each time (no duplicate detection)
  • Contract requirements are automatically bypassed
  • Production cases enter Debitura's internal verification before proceeding to the assigned collection partner
  • Test cases bypass internal verification because delayed auto-validation is only scheduled for production cases
  • Cases appear in your 'Managed Cases' list
  • You have read-only access to monitor case progress

Request​

Responses​

Case created successfully