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/Revenue Recognition Schedule Line — entity reference
REFERENCE · Last reviewed

Revenue Recognition Schedule Line — entity reference

One period's slice of a revenue-recognition schedule: the amount planned for release, the amount actually recognized, and the journal that posted it. The background sweep picks up lines whose date has arrived while the parent schedule is still active, and posting is safe to retry because a line that already carries a journal or has left the pending state is skipped. The schedule's recognized-to-date total is summed from these lines, which is what keeps the deferred balance tied to the ledger.

Fields

FieldLabelTypeRequiredWhat it does
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated OnDateAndTimeYes
FiscalPeriodIdFiscal PeriodLookup → FiscalPeriod
IdIdGuidYes
JournalIdJournalLookup → JournalThe recognition journal that posted this line. It doubles as a re-delivery guard: a line already carrying a journal is skipped when the background job runs again, which is what makes the sweep safe to retry.
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextYes
OwnerIdOwnerLookup → UserAccountYes
PartnerAccountIdPartner AccountLookup → Account
PeriodDatePeriod DateDateAndTimeThe date the release falls due. The background sweep compares this against the current date, so it, rather than any linked fiscal period, is what actually triggers recognition.
PeriodNumberPeriod NumberNumberThe line's position in the release sequence, starting at one. It orders the schedule internally and is not a fiscal period number, so it should not be matched against the accounting calendar.
RecognizedAmountRecognized AmountCurrencyThe amount actually released once the line posted. Only lines that reached the recognized state contribute to the parent schedule's recognized total.
RecognizedDateRecognized DateDateAndTime
RecordTypeIdRecord TypeGuid, hidden
ScheduledAmountScheduled AmountCurrencyThe amount planned for release in this period. On a straight-line plan every line is equal except the final one, which carries the rounding remainder so the schedule totals exactly.
ScheduleIdScheduleLookup → RevenueRecognitionSchedule
StatusStatusTextEither Pending or Recognized. An unset value is treated as Pending by the background sweep, so a line with no status is still picked up rather than being stranded unposted.
UIPropsUI PropsText
UpdatedDateTimeUpdated OnDateAndTimeYes

Actions

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