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

Revenue Recognition Schedule — entity reference

A deferred-revenue release plan for one billed amount. The header names the company, the deferred-revenue liability account, the revenue income account and the total to release; its lines hold one dated amount per period. A background job posts each Pending line once its period date arrives (debit deferred revenue, credit revenue) and the schedule completes when the recognized amount reaches the total. Saving a header creates no lines: lines are created through the data API or an integration, and the initial deferral is posted by the invoice or a journal, not by the schedule.

Fields

FieldLabelTypeRequiredWhat it does
BusinessUnitIdBusiness UnitLookup → BusinessUnitThe finance business unit the schedule belongs to. Filled from the Deferred GL Account's default business unit when left blank on save. It is not copied onto the recognition journals, whose lines take business unit and branch from their GL accounts.
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
DeferredGLAccountIdDeferred GL AccountLookup → GLAccountThe liability account holding the not-yet-earned balance. Every release debits it. Required for posting, must be active, and must not be a control account because recognition journals carry no party.
DocumentNumberDocument NumberTextThe source document's number. When set it replaces the schedule name in the recognition journal's label and narration. Not on the standard layouts.
EndDateEnd DateDateAndTimeEnd of the recognition window. Informational only: each line posts on its own Period Date.
IdIdGuidYes
MethodMethodTextThe intended plan, for example StraightLine or Milestone. Free text, defaults to StraightLine, and has no effect on posting; nothing generates lines from it.
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextYes
NumberOfPeriodsNumber Of PeriodsNumberHow many periods the release is planned over. Informational only: nothing creates lines from it.
OwnerIdOwnerLookup → UserAccountYes
PartnerAccountIdPartner AccountLookup → AccountThe company whose books the recognition journals post to. It decides which fiscal calendar the journal date is checked against. Hidden on single-company tenants.
PartyAccountIdParty AccountLookup → AccountThe customer the deferred revenue relates to. Record-keeping only; it is not put on the recognition journal lines.
RecognizedAmountRecognized AmountCurrencyThe amount released so far. Each posted line adds its amount; treat it as read-only, because it decides when the schedule completes.
RecordTypeIdRecord TypeGuid, hidden
RevenueGLAccountIdRevenue GL AccountLookup → GLAccountThe income account each release credits. Required for posting: a schedule without it refuses every line with 'Schedule needs both a deferred-revenue and a revenue GL account.' Not on the standard create or record layout, so add it to the layout or set it through the data API.
SourceEntityNameSource Entity NameTextThe kind of document the schedule was raised from, for example Invoice. A record-keeping label only; it does not link to or check the document.
SourceRecordIdSource RecordGuidThe record id of the source document, settable through the data API. Nothing reads it.
StartDateStart DateDateAndTimeStart of the recognition window. Informational only: each line posts on its own Period Date.
StatusStatusTextActive, Completed or Cancelled; free text that defaults to Active. Only Active schedules (or schedules with no status) have their lines posted. Posting sets Completed when the recognized amount reaches the total; set Cancelled to stop further releases. Not on the standard layouts.
TotalAmountTotal AmountCurrencyThe full amount to release. When the recognized amount reaches it the schedule becomes Completed and no further lines post, so a schedule with no total completes after its first release. Shown on the record page, not on the create form.
UIPropsUI PropsText
UpdatedDateTimeModified DateDateAndTimeYes

Actions

ActionLabelTypeWhat it does
CloneCloneServerAction (Clone)Create a copy of this record
DeleteEntityDeleteDeleteDeleteEntity
DeleteHeaderDeleteDeleteDeleteHeader
DeleteRowDeleteDeleteDeleteRow
EditEntityEditEditEditEntity
EditInLineEditEditInlineEditInLine
EditRowEditRowEditEditRow
NewNewNewNew