xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField SalesCRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →
PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopers
SENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse cases
SOLUTIONS
FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →
RESOURCES
Knowledge CenterDeveloper & CLIBlogGuidesWhat is xMatix?Company facts
COMPANY
AboutCareersPartnersEventsContactAuthorsLegal
Sign in Request demo
Home/Docs/Entity Reference/Finance Case — entity reference
REFERENCE · Last reviewed

Finance Case — entity reference

A retail finance application raised against a sale: it records what the customer asked for and what the financier granted as parallel requested/approved/disbursed sets of amount, down payment, interest rate, tenure and EMI, and links the sale through OrderId and InvoiceId plus the financier through FinanceProviderId and FinancerSchemeId. It is live and wired into order-to-cash: creating one, changing its DisbursedAmount, or deleting it pushes the financed amount back onto the linked Order and Invoice, and when an invoice is raised for an order the platform re-tags the order's finance cases with the new InvoiceId. OrderId, InvoiceId, BranchId and PartnerAccountId are frozen after creation, and the partner/branch pairing is validated on insert.

Fields

FieldLabelTypeRequiredWhat it does
AccountIdAccountLookup → Account
ApprovalRemarksApproval RemarksText
ApprovedAmountApproved AmountCurrency
ApprovedByIdApproved ByLookup
ApprovedDownPaymentApproved Down PaymentCurrency
ApprovedInterestRateApproved Interest RateDecimal
ApprovedTenureMonthsApproved Tenure (In Months)Number
BranchIdBranchLookup → Branch
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
DeclinedByIdDeclined ByLookup
DeclinedRemarksDeclined RemarksText
DisbursedAmountDisbursed AmountCurrencyThe amount the financier actually paid out, and the only field on the case that drives anything downstream: changing it re-pushes the financed amount onto the linked Order and the linked Invoice. Creating or deleting the case does the same.
DisbursementDateDisbursement DateDate
DisbursementNumberDisbursement NumberText
EMIOnApprovedAmountEMI on Approved AmountCurrency
EMIOnDisbursedAmountEMI on Disbursed AmountCurrency
EMIOnRequestedAmountEMI on Requested AmountCurrency
ExternalIdExternalText
FinanceProviderIdFinance ProviderLookup → FinancerThe Financer funding this case. Where the customer has gone to a lender that is not on the master, OtherFinancer holds the name as free text instead - so a case can be financed with this left empty.
FinancerSchemeIdFinancer SchemeLookup → FinancerSchemeThe financier's product the case is written under. Nothing validates the case's amount or tenure against that scheme's minimum and maximum bounds - the scheme entity is never loaded by any code - so the bounds are advisory.
FinanceSchemeIdFinance SchemeLookupA second scheme reference distinct from FinancerSchemeId, with no code reading either; where both are populated nothing reconciles them. Prefer FinancerSchemeId, which is the one that maps to the FinancerScheme master.
IdIdGuidYes
InvoiceIdInvoiceLookup → InvoiceThe invoice the financed sale was billed on. It is usually not chosen by hand - when an invoice is raised for the case's order, the platform stamps the new invoice onto the order's finance cases that do not already have one. It is frozen against edits after creation.
ModifiedByIdModified ByLookup → UserAccountYes
NameNameText
OrderIdOrderLookup → OrderThe sales order being financed; it is the key the platform uses to find the case when an invoice is later raised. Frozen against edits after creation, along with the invoice, branch and partner-account links.
OtherFinancerOther FinancerTextFree-text name of a lender that is not on the Financer master, used instead of FinanceProviderId. Because it is unstructured it will not join to anything, so cases recorded this way are invisible to any analysis grouped by financier.
OwnerIdOwnerLookup → UserAccountYes
PartnerAccountIdPartner AccountLookup → AccountThe company that owns the case, validated against the chosen branch on insert and frozen thereafter. This is the company dimension, not the applicant - the customer applying for finance is AccountId.
RecordTypeIdRecord TypeGuid, hidden
RequestedAmountRequested AmountCurrency
RequestedDownPaymentRequested Down PaymentCurrency
RequestedInterestRateRequested Interest RateDecimal
RequestedTenureMonthsRequested Tenure (In Months)Number
StatusStatusPickListWhere the application stands - draft, documentation, approval in process, declined or approved.
TenureMonthsTenure MonthsPickListA picklist of standard tenures held separately from the numeric RequestedTenureMonths and ApprovedTenureMonths, which are what the requested and approved terms actually record. Nothing keeps this in step with them. Values: 12, 24, 36, 48, 60, 72, 84.
UIPropsUI PropsText
UpdatedDateTimeModified DateDateAndTimeYes

Actions

ActionLabelTypeWhat it does
BulkDeleteDeleteDeleteDelete the selected records
CloneCloneServerAction (Clone)Create a copy of this record
DeleteDeleteDeleteDelete
DeleteInListDeleteDeleteDelete in list page
EditEditEditEdit
EditInLineEditEditInlineEdit in page
EditInListEditEditInlineEdit
EditListRowEditEditEditListRow
NewNewNewNew

Validations

ValidationApplies toError messageNotes
Disbursed Amount ValidationDisbursedAmount, ErrorDisbursed Amount cannot be greater than the Requested AmountDisbursed Amount Validation
XM_DownPaymentAmountValidationRequestedDownPayment, ErrorRequested Down Payment cannot be NegativeRequested Down Payment cannot be Negative
EMI Amount Rule ValidationEMIOnRequestedAmount, ErrorEMI Amount should be less than or Equal to Disbursed AmountEMI Amount Validation
XM_RequestedAmountValidationRequestedAmount, ErrorRequested Amount cannot be Negative.Requested Amount cannot be Negative
Tenure Rule ValidationAccountId, ErrorTenure should not be less than 1Account Tenure must be greater than 1 month.

Lookup filters

FilterLookup fieldNotes
Branch For Partner AccountBranchIdBranch For Partner Account
Customer Account FilterAccountId
Partner AccountPartnerAccountId