document-posting

Write the controlled register last with БлокироватьДляИзменения = Истина, then run the negative-balance query after that write at the end of the transaction. Uncontrolled registers go earlier with БлокироватьДляИзменения = Ложь in a stable order, following the std661 shape.

Name each accounting subject the document affects first; each subject becomes its own register, not a column on an existing one. Inspect candidate registers for dimensions, resources, and periodicity, and ensure dimensions are meaningful for both receipt and expense movements.

The platform picks the branch by comparing the document date with the session date, exposed as РежимПроведенияДокумента.Оперативный. The real-time branch is the usual place for availability checks; the regular branch must stay correct on its own for backdated entry and initial data load.

The platform writes record sets implicitly when the handler returns, so an explicit Записать() is diagnostic АПК:105 under standard 450. The sanctioned exception is the balance-control shape, where the controlled register must be written before its control query runs.

Skip control where it cannot fail: a receipt document only increases balances, and re-posting cannot write off more than the first posting already did. Control only the balances that can actually go negative to avoid unnecessary locks.

No. Standard 603 prohibits disabling posting to model drafts or lifecycle stages. An unposted document is already a draft, and lifecycle stages should be implemented as statuses on a posted document.