The FileTrac SOAP API uses two parallel error signals: a numeric ResponseCode that classifies authentication-level outcomes, and a string ResponseMessage (or equivalent message field) that carries method-specific business-rule errors. SOAP faults are reserved for transport-level failures and are not raised for business errors.

Response Codes

ResponseCode	Message	Description
0	Success	No validation issues. The request was processed and the response is populated.
1	LoginOrPasswordInvalid	Either the `Login` or the `Password` failed validation.
2	AuthenticationParameterMissing	Either `Login`, `Password`, or `CompanyKey` was not supplied.
3	TruncatedTransmission	The request was interrupted before reaching the server in full.

When ResponseCode is non-zero, expect default empty payloads — empty strings, empty lists, empty objects, or 0 for an ID return.

Method-Specific Error Messages

When the request passes authentication but fails business validation, the API returns an error string in the response message field. The strings below are reproduced verbatim from the source documentation. Numeric prefixes (e.g. (1), (2)) are stable within each method's error set and are safe to branch on.

AddClaim

Error Message	Cause	Remediation
`ERROR extracting claim data`	The request was malformed or the claim payload could not be deserialized.	Validate the SOAP envelope structure against the WSDL.
`ERROR - The companyID supplied is not a valid ID for this adjusting company`	`ClientCompanyID` does not exist within the adjustment company.	Call `GetClientCompanies` first and supply an ID from that list.
`ERROR - The companyName supplied does not match any companyName for this adjusting company`	`ClientCompanyName` does not match any client-company name on record.	Match the name exactly as it appears in FileTrac, or use `ClientCompanyID`.
`ERROR - Both the companyID and the CompanyName supplied are invalid for this adjusting company`	Neither ID nor name matched a valid client company.	Re-fetch the list via `GetClientCompanies`.
`Branch for ACID not defined`	The adjustment company has no default branch defined and no branch was supplied on the request.	Supply `BranchID` or `BranchName`, or contact FileTrac Support to define a default branch.
`Error in inserting unassigned ClaimRep`	The system tried to assign the default UNASSIGNED Claim Rep and the operation failed.	Retry; if persistent, contact FileTrac Support.
`Error in inserting claim`	The claim insert failed at the database layer.	Retry; if persistent, contact FileTrac Support.
`Error in inserting into claimContacts`	A contact created alongside the claim failed to insert.	Validate the contact list payload; confirm required contact-type fields.
`Error in inserting into Message table`	A claim-creation note (from the `Note` parameter) failed to insert.	Retry; if persistent, contact FileTrac Support.
`Error in updating claim`	An update to an existing claim failed at the database layer.	Confirm the claim exists; retry.
`Error in UPDATING claimContacts`	A contact update failed.	Confirm the contact ID; retry.

AddClaimNote

Error Message	Cause	Remediation
`ERROR - Claim does not exist for that Adjusting Company`	`FileTracClaimID` does not identify a claim accessible to this login.	Confirm the claim ID via `GetClaimSummaries` or `GetClaimDetail`.
`ERROR inserting Note`	The note insert failed at the database layer.	Confirm note length is within the 4000-character limit; retry.

GetClientContacts

Error Message	Cause	Remediation
`ERROR - The companyID supplied is not a valid ID for this adjusting company`	`ClientCompanyID` is invalid.	Call `GetClientCompanies` and use an ID from that list.
`ERROR - The companyName supplied does not match any companyName for this adjusting company`	`ClientCompanyName` does not match exactly.	Match the name as it appears in FileTrac.
`ERROR - Both the companyID and the CompanyName supplied are invalid for this adjusting company`	Neither identifier matched.	Re-fetch the list via `GetClientCompanies`.
`ERROR retrieving Client Contacts`	An internal error occurred during retrieval.	Retry; if persistent, contact FileTrac Support.

GetClaimNotes

Error Message	Cause	Remediation
`ERROR – No Note found for that messageID`	The `NoteID` does not exist or is not accessible.	Confirm the `NoteID` via `GetClaimDetail`.
`ERROR – No Notes found for that claimID/File #`	The claim has no notes.	This is data state, not an integration error.
`ERROR retrieving Notes`	Internal error during retrieval.	Retry; if persistent, contact FileTrac Support.

GetClaimReports

Error Message	Cause	Remediation
`ERROR – No Report found for that reportID`	The `FileTracReportID` does not exist or is not accessible.	Confirm the report ID via `GetClaimDetail`.
`ERROR – No Claim Reports found for the claimID/File# provided`	The claim has no reports.	Data state, not an integration error.
`ERROR retrieving Reports`	Internal error during retrieval.	Retry; if the claim has large reports (30MB+) on Cloud, retry individually by `FileTracReportID`.

AddReserve

Error Message	Cause	Remediation
`ERROR inserting/updating Reserve`	The reserve insert/update failed.	Validate the payload; retry.
`(1) Claim not found - invalid claimID and/or File#`	The claim cannot be located.	Confirm `FileTracClaimID` via `GetClaimSummaries`.
`(2) Reserve Type not found - invalid reserveID and/or reserveName`	`ReserveTypeID` or `ReserveTypeName` is invalid for this adjustment company.	Confirm the reserve type exists in FileTrac Settings → Reserve Types.
`(3) Invalid contactID or contactName supplied: xxxxxx`	The contact does not exist within the claim.	Omit the contact (creates claim-level reserve), or confirm the contact via `GetClaimDetail`.
`(4) Cannot change reserve to amount lower than payments already against the reserve.`	The new reserve amount is less than the sum of payments already booked against the reserve.	Increase the proposed reserve amount, or void payments first.

AddReservePayment

Error Message	Cause	Remediation
`ERROR inserting Reserve Payment.`	The payment insert failed.	Validate the payload; retry.
`(1) Claim not found - invalid claimID or File Number`	The claim cannot be located.	Confirm `FileTracClaimID`.
`(2) Invalid contactID supplied: xxxxxx`	The `PayeeID` does not exist within the claim.	Confirm via `GetClaimDetail` or pass a name + contact type to create a new contact.
`(3) Invalid contact information supplied: 'contactFirstName contactLastName' for Type: contactType`	The first-name/last-name/type combination is invalid for creating a new contact.	Confirm the contact-type name or ID via `GetContactTypes`.
`(4) Payment amount exceeds balance of reserve.`	The payment amount exceeds the reserve less prior payments.	Reduce the payment amount, or increase the reserve via `AddReserve` first.

AddReserveRecovery

Error Message	Cause	Remediation
`ERROR inserting Reserve Recovery.`	The recovery insert failed.	Validate the payload; retry.
`(1) Claim not found - invalid claimID or File Number`	The claim cannot be located.	Confirm `FileTracClaimID`.
`(2) Invalid contactID supplied: contactID`	The `PayeeID` does not exist within the claim.	Confirm via `GetClaimDetail`.
`(3) Invalid contact information supplied: 'contactFirstName contactLastName' for Type: contactType`	New-contact creation failed validation.	Confirm contact-type name or ID via `GetContactTypes`.
`(4) Invalid recovery type information supplied. ID: 'recoveryTypeID' or Type: 'recoveryType'`	The recovery type does not exist.	Call `GetRecoveryTypes` and use an ID or name from that list.

AddDeductiblePayment

Error Message	Cause	Remediation
`ERROR inserting Deductible Payment.`	The payment insert failed.	Validate the payload; retry.
`(1) Claim not found - invalid claimID or File Number`	The claim cannot be located.	Confirm `FileTracClaimID`.
`(2) Invalid contactID supplied: 'contactID'`	The `PayeeID` does not exist within the claim.	Confirm via `GetClaimDetail`.
`(3) Invalid contact information supplied: 'contactFirstName contactLastName' for Type: 'contactType'`	New-contact creation failed validation.	Confirm contact-type name or ID via `GetContactTypes`.
`(4) Payment amount exceeds balance of deductible`	The payment amount exceeds the deductible less prior payments.	Reduce the payment amount.

AddInvoicePayment

Error Message	Cause	Remediation
`(1) Invoice not found - invalid InvoiceID or InvoiceNumber`	The invoice cannot be located.	Confirm via `GetInvoiceSummaries`.
`(2) Invoice has already been paid in full. Unable to apply additional payments`	The invoice has zero unpaid balance, and the one allowed excess payment has already been recorded.	No remediation — the invoice is fully resolved.

GetClaimData (legacy method name retained in error strings)

Error Message	Cause	Remediation
`ERROR inserting Note`	Legacy error string. Surfaces when an internal note write fails during data extract operations.	Retry; if persistent, contact FileTrac Support.

Voiding Payments and Recoveries

The API does not provide explicit void operations. Voids are recorded as inverse-amount transactions:

To void a deductible payment, call AddDeductiblePayment with the same data and a negative PaymentAmount.
To void a reserve payment, call AddReservePayment with the same data and a negative PaymentAmount.
To void a reserve recovery, call AddReserveRecovery with the same data and a negative RecoveryAmount.

Notes and reports cannot be voided through the API at all — AddClaimNote documentation explicitly states notes are not updateable.

Best Practices

Always check ResponseCode first. A non-zero ResponseCode invalidates the rest of the response.
Branch on numeric error prefixes when present. The (1), (2), (3), (4) prefixes are stable; the text after them may evolve.
Cache GetContactTypes, GetRecoveryTypes, and GetClientCompanies lookups. The most common error class is invalid lookup values; cache these to validate locally before submitting writes.
Log the verbatim error string. Several error messages embed the offending value (xxxxxx); logging the full string preserves diagnostic context.

Error Codes & Response Codes