Overview
There is no dedicated “Installment” object in fusionCore. An installment is a Financial Event — the ledger record fusionCore writes for every money motion — that has been flagged as an installment. Specifically, each installment is a FCORE_PAY__Financial_Event__c record with:
Type__c = 'Installment'Status__c = 'Pending'Is_Installment__c = true
Each installment Financial Event has one or more FCORE_PAY__Financial_Event_Line__c child records — one per product included in that installment’s split.
When an installment is collected — manually or by the auto-charge batch — fusionCore produces a separate Financial Event with Type__c = 'Payment', and the original installment event is updated to Succeeded (or Failed if the charge did not go through).
Fields on an Installment Financial Event
Order Roll-Up Fields
fusionCore keeps a running summary of an Order’s installment plan on the Order record. These fields are maintained automatically as installments are generated, paid, or fail.
Next_Installment_Date__c and Next_Installment_Balance_Due__c are formula fields. They recalculate automatically and cannot be edited directly.
Limitations and Common Pitfalls
- There is no Installment object. Installments live entirely as
Financial_Event__c records. If you are building a report or list view, filter Financial Events on Is_Installment__c = true (and Type__c = 'Installment' for the scheduled, not-yet-paid charges).
- A Payment event is separate from the installment. Collecting an installment creates a new
Type__c = 'Payment' event; it does not convert the installment record in place. The original installment event moves to Succeeded or Failed.
- The roll-up formula fields are not writable.
Next_Installment_Date__c and Next_Installment_Balance_Due__c cannot be set by hand — adjust the plan to change them.
- Number Of Attempts is set by the batch.
Number_Of_Attempts__c reflects auto-charge retries and is not a field you edit manually.
