ApplyToOpenInvoices | Apply To Open Invoices | Boolean | Yes | When on, a settlement credit note is applied against the supplier account's open invoices, oldest first, right after it is saved. It has no effect on invoice settlement. |
AutoGLPosting | Auto GL Posting | Boolean | Yes | Copied onto the created credit note or invoice as its posting request. A settlement credit note is still created as Draft and is posted with Post General Ledger. |
ClaimType | Claim Type | PickList | Yes | The claim type this setup settles. It must equal the claim's Claim Type exactly, and only one setup per type should be active. Choose the same value your claims carry; a claim type that is not in this setup's own list needs the same value added to it before claims of that type can be settled. Values: Trade Schemes(CLT-04), CLT-04R, QPS Scheme (CLT-04), Cashback(CLT-04), Provision (CLT-04), Structural Rate Difference Contract Pricing, PSR Incentive (CLT6,7), PSR Salary (CG 1,2), Training Claim, Damage, Shortage, Rate Difference, Reimbursment, Sale, Service, Purchase, Excess, Transport, Part To Part. |
CreatedById | Created By | Lookup → UserAccount | Yes | |
CreatedDateTime | Created Date | DateAndTime | Yes | |
HeaderMapping | Header Mapping | MultiLineText | | Optional JSON object that overrides fields on the created document's header. Each key is a document field; each value is a claim field path, @approvedAmount (the claim's Total Approved Amount), @approvedQuantity (its Total Approved Quantity) or @const:<value>. It is applied after xMatix fills the document, and it is not checked on save; an error fails the settlement run. For a batch it reads the first claim. |
IsActive | Active | Boolean | Yes | Only active setups are used by settlement and batching. A new setup starts inactive. |
LineMapping | Line Mapping | MultiLineText | | Optional JSON object that overrides fields on each created document line. Values are claim line field paths, @approvedAmount (Unit Price times Approve Quantity of that line), @approvedQuantity (its Approve Quantity) or @const:<value>. Only lines with an Approve Quantity above zero produce a document line. It is not checked on save. |
ModifiedById | Modified By | Lookup → UserAccount | Yes | |
Name | Document Number | Text | Yes | The setup's name, typed when the setup is created. Nothing numbers setups and the name does not have to be unique. |
OwnerId | Owner | Lookup → UserAccount | Yes | |
RaiseEventName | Raise Event Name | Text | | Optional business-rule event raised on the claim after settlement. It is also raised when the document is None or when no setup matches the claim's type, so a setup can be used for events only. If the event cannot be raised, the settlement still succeeds. |
SettlementDocument | Settlement Document | PickList | Yes | What an approved claim produces. A credit note (the default) or an invoice is created as a Draft document on the claim's supplier account; None creates nothing and only raises the event. The settlement job recognises only the stored values CreditNote, Invoice, None and Adjustment, so any other stored value, including Adjustment (Part to Part), fails the run as not supported. Batch settlement accepts only a credit note or an invoice. Values: Credit Note, None. |
SimulateMode | Simulate Mode | Boolean | Yes | When on, the settlement and batching jobs only report what they would create and write nothing, so the claim stays Approved. The reported amount is the claim's Total Approved Amount, not the line total. Claims approved while it was on are not settled automatically when it is switched off; start a settlement run for them. |
UpdatedDateTime | Modified Date | DateAndTime | Yes | |
