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

Period Close — entity reference

The audit record of one run of the period-close checklist against a fiscal period. It stores how many checks ran, how many passed and how many blocking ones failed, plus the close status the period was moved to as a result. Its check children preserve every individual outcome, so a forced close stays visible long after the period moved.

Fields

FieldLabelTypeRequiredWhat it does
AllMandatoryPassedAll Mandatory PassedBooleanSet only when no blocking item failed. A forced close is deliberately recorded with this false, which is how an override remains auditable after the period has already moved on.
CloseDateClose DateDateAndTimeThe effective date stamped on the run, stored without a time component and defaulting to the day the close was executed rather than to the period's own end date.
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
FiscalPeriodIdFiscal PeriodLookup → FiscalPeriod
IdIdGuidYes
MandatoryFailuresMandatory FailuresNumberHow many blocking items failed. Any value above zero refuses the close unless the caller explicitly overrides, so a stored run carrying a positive count is by definition a forced close.
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextYes
NotesNotesTextFree text supplied by whoever ran the close. It is the usual place a justification for a forced close is captured, since the override path carries no separate reason field of its own.
OwnerIdOwnerLookup → UserAccountYes
PartnerAccountIdPartner AccountLookup → Account
PassedChecksPassed ChecksNumberHow many evaluated items passed, counting advisory items alongside blocking ones. It can legitimately fall short of the total on a perfectly valid close, because advisory failures never stop one.
RecordTypeIdRecord TypeGuid, hidden
StatusStatusTextThe close state applied to the period by this run, one of SoftClosed, Closed or Locked, rather than the state of the run record itself. SoftClosed marks a soft month-end, Closed and Locked are final, and a locked period can never be reopened.
TotalChecksTotal ChecksNumberHow many checklist items this run actually evaluated, blocking and advisory together. It is a count of what ran, not the size of a configurable checklist definition.
UIPropsUI PropsText
UpdatedDateTimeModified DateDateAndTimeYes

Actions

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

Lookup filters

FilterLookup fieldNotes
Partner Account FilterPartnerAccountId