xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField Sales & SFACRMRewardsClaimsInventoryProcurementWarehouse 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
Auto DMSConsumer Goods DMSSales Force Automation (SFA) 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 test in a period-close checklist run, with its stable code, whether it was mandatory, whether it passed and a detail of what failed. The checklist has ten tests. Four are mandatory: every posted journal balances, no draft or pending-approval journals are dated in the period, receivable and payable open items tie to their allocations, and no posting failures are pending. The other six are advisory. They cover balance caches, open bank reconciliations, employee payable and advance control accounts, inventory write-downs and secondary-book valuation. No app, button or job runs the checklist out of the box. Close Period on a fiscal period only changes its status and writes no check rows, and this record is in no app or menu. Rows entered by hand are not produced by any test.

Fields

FieldLabelTypeRequiredWhat it does
CheckCodeCheck CodeTextThe stable code of the test, for example LEDGER_BALANCED, NO_DRAFT_JOURNALS, OPEN_ITEMS_TIE or NO_FAILED_POSTINGS. Match on the code rather than the readable name.
CheckNameCheck NameTextThe readable sentence describing what the test checks, copied onto the row when the run was recorded.
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
DetailDetailTextFilled only when the test failed, with the counts or amounts behind the failure, such as the number of unbalanced journals or the drift on a control account. Empty when the test passed.
IdIdGuidYes
IsMandatoryIs MandatoryBooleanWhether a failure of this test stops the close. Only the four ledger-integrity tests are mandatory: journals balance, no draft or pending-approval journals in the period, open items tie, and no pending posting failures.
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextYes
OwnerIdOwnerLookup → UserAccountYes
PartnerAccountIdPartner AccountLookup → AccountThe company whose fiscal period was checked, copied from the period.
PassedPassedBooleanWhether the test passed when the run was recorded. An advisory test can fail on a period that still closed, so read it together with Is Mandatory.
PeriodCloseIdPeriod CloseLookup → PeriodCloseThe checklist run this test belongs to. Every test of one run points at the same Period Close record.
RecordTypeIdRecord TypeGuid, hidden
UIPropsUI PropsText
UpdatedDateTimeModified DateDateAndTimeYes

Actions

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