pub struct AccountingPeriodCreate {
pub client_id: i64,
pub end_date: NaiveDate,
pub increment_document_number: bool,
pub is_closed: bool,
pub start_date: NaiveDate,
pub balances: Option<AccountingPeriodBalanceTransfer>,
pub copy_master_data: Option<bool>,
pub extra: Map<String, Value>,
}Expand description
An accounting period is the date range for one finance client’s books, usually a financial year. Accounts and cost centers belong to a period. Closing a period prevents ordinary account and transaction changes; it is separate from making individual transactions immutable.
Fields§
§client_id: i64Finance client owning this period.
end_date: NaiveDateLast date of the period.
increment_document_number: boolWhether document numbers are incremented automatically. Required in both creation and update.
is_closed: boolWhether the period is closed for ordinary accounting changes. This flag alone does not make transactions immutable.
start_date: NaiveDateFirst date of the period. Used to match the previous period by subtracting exactly one year.
balances: Option<AccountingPeriodBalanceTransfer>Optional opening-balance transfer. Both an openingBalanceAccount and a nonempty from list are needed to start a transfer. The previous period must have the same client and a start date exactly one year earlier.
copy_master_data: Option<bool>Copy the previous period’s accounts, cost centers and related finance master data. The previous period is matched by client and a start date exactly one year earlier. Without a match, an empty period is created. Ordinary transactions are not copied. The current copy implementation retains the previous incrementDocumentNumber setting.
extra: Map<String, Value>Fields not described by the spec, e.g. instance-specific DB fields.