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/Cheque Transaction — entity reference
REFERENCE · Last reviewed

Cheque Transaction — entity reference

One cheque and its clearing lifecycle, either drawn by the company or received from a customer. Rows are normally created automatically when a cheque-mode Payment is saved — drawn from an active register when the number was left blank, otherwise recorded as typed — and they link back to that document by source entity name and source record id. Moving the status to Cleared posts the clearing journal that moves the money between the Cheques In Hand account and the bank; moving it to Bounced reverses the originating document's posted journal. Presented and Cancelled are recorded only and trigger no posting, and the rule that a cheque in a terminal state cannot change state lives in the cheque service rather than in save-time validation, so editing the record directly can still move it out of Cleared or Bounced.

Fields

FieldLabelTypeRequiredWhat it does
AmountAmountCurrencyThe cheque value, always positive — a save at zero or below is rejected — and the amount of the clearing journal posted when the cheque clears. Direction, not the sign of this figure, decides which way the money moves.
BankAccountIdBank AccountLookup → BankAccountThe company's bank account the cheque is drawn on. It is populated only when the number was drawn from a register — cheques recorded from a payment with a manually entered number are saved with it empty, which also means the duplicate-number check, scoped per bank account, does not apply to them.
ChequeDateCheque DateDateAndTimeThe date written on the cheque face. Save is rejected when it is in the future, and it is the date used when a cheque is generated automatically from a payment.
ChequeNumberCheque NumberTextThe printed cheque number, including the register prefix when one was allocated. It must be unique per bank account, so cheques saved without a bank account escape that check entirely.
ChequeRegisterIdCheque RegisterLookup → ChequeRegisterThe cheque book the number came from, set only when the number was allocated automatically. When present it activates the save-time check that the cheque number lies inside that register's start-to-end range.
ClearedDateCleared DateDateAndTimeStamped when the status moves to Cleared, defaulting to today when none is supplied, and it becomes the date of the clearing journal. It is stamped once and is not cleared again if the status is later changed.
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated OnDateAndTimeYes
DirectionDirectionTextIssued for a cheque the company writes, Received for one taken from a customer. It decides which way the clearing journal goes — a received cheque debits the bank and credits Cheques In Hand, an issued one does the reverse — and only issued cheques draw a number from a register. Note that a received cheque is still created with status Issued, so direction and status carry different meanings.
IdIdGuidYes
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextYes
OwnerIdOwnerLookup → UserAccountYes
PartnerAccountIdPartner AccountLookup → Account
PartyAccountIdParty AccountLookup → AccountThe customer or supplier on the other side of the cheque, taken from the originating payment's account when the cheque is generated. It is a different link from the partner account, which is the owning company.
RecordTypeIdRecord TypeGuid, hidden
SourceEntityNameSource Entity NameTextThe entity name of the money document the cheque came from — in practice Payment. Together with the source record id it is the idempotency key that stops a second cheque being created for the same document.
SourceRecordIdSource RecordGuidThe id of the originating money document.
StatusStatusPickListOnly Cleared and Bounced do anything — they post the clearing journal and reverse the source document respectively — and the terminal-state lock exists only in the cheque service, not in save-time validation, so editing the record directly can still move a cleared or bounced cheque back out of that state.
UIPropsUI PropsText
UpdatedDateTimeUpdated OnDateAndTimeYes

Actions

ActionLabelTypeWhat it does
CloneCloneServerAction (Clone)Create a copy of this record
DeleteDeleteDeleteDelete
EditEditEditEdit
EditInlineEdit InlineEditInlineEdit Inline
NewNewNewNew

Validations

ValidationApplies toError messageNotes
Amount ValidationAmount, ErrorAmount cannot be 0 or NegativeAmount Validation

Lookup filters

FilterLookup fieldNotes
Bank Account FilterBankAccountId