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/Period Close Check — entity reference
REFERENCE · Last reviewed

Period Close Check — entity reference

One evaluated line of a period-close run: a single integrity test with a stable machine code, whether it was blocking, whether it passed, and a detail string naming the offending counts. Four of the ten tests are mandatory and gate the close: every posted journal balances, no draft or pending journals are dated in the period, receivable and payable open items tie to their allocations, and no unresolved posting failures remain queued. The other six are advisory and record a warning without stopping the close. Rows are written by the close service at evaluation time, not entered by hand.

Fields

FieldLabelTypeRequiredWhat it does
CheckCodeCheck CodeTextThe stable machine identifier of the test, drawn from a fixed set of upper-case codes such as LEDGER_BALANCED, NO_DRAFT_JOURNALS, OPEN_ITEMS_TIE and NO_FAILED_POSTINGS. Match on this rather than on the display text, which is prose written at evaluation time and may change.
CheckNameCheck NameTextThe readable sentence describing what the test asserts, copied onto the row by the close service when the run was recorded. It is a snapshot for the audit trail, not a link to a configurable checklist definition.
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
DetailDetailTextPopulated only when the item failed, carrying the offending counts or amounts such as how many journals were unbalanced or how far a control account drifted from its subledger. It is left empty on a pass.
IdIdGuidYes
IsMandatoryIs MandatoryBooleanWhether this item blocks the close. Only four codes are blocking: journals balance, no draft or pending journals dated in the period, receivable and payable open items tie to allocations, and no unresolved posting failures. Everything else is advisory.
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextYes
OwnerIdOwnerLookup → UserAccountYes
PartnerAccountIdPartner AccountLookup → Account
PassedPassedBooleanThe outcome at the moment the run was recorded. Advisory items are often false on a successfully closed period, so a false value alone does not indicate a problem; read it together with whether the item was blocking.
PeriodCloseIdPeriod CloseLookup → PeriodClose
RecordTypeIdRecord TypeGuid, hidden
UIPropsUI PropsText
UpdatedDateTimeModified DateDateAndTimeYes

Actions

ActionLabelTypeWhat it does
CloneCloneServerAction (Clone)Create a copy of this record
EditEditEditEdit
NewNewNewInlineNew