Hledger.Data.Posting

Make a posting to an account.

Make a virtual (unbalanced) posting to an account.

Make a posting to an account, maybe with a balance assertion.

Make a virtual (unbalanced) posting to an account, maybe with a balance assertion.

Make a partial, exclusive balance assertion.

Make a total, exclusive balance assertion.

Make a partial, inclusive balance assertion.

Make a total, inclusive balance assertion.

Get a posting's status. This is cleared or pending if those are explicitly set on the posting, otherwise the status of its parent transaction, or unmarked if there is no parent transaction. (Note the ambiguity, unmarked can mean "posting and transaction are both unmarked" or "posting is unmarked and don't know about the transaction".

Tags for this posting including any inherited from its parent transaction.

Tags for this transaction including any from its postings (which includes any from the postings' accounts).

Strip all prices from a Posting.

Apply some account aliases to the posting's account name, as described by accountNameApplyAliases. This can fail due to a bad replacement pattern in a regular expression alias.

Find and apply the appropriate display style to the posting amounts in each commodity (see journalCommodityStyles). Main amount precisions may be set or not according to the styles, but cost precisions are not set.

Like postingApplyCommodityStyles, but neither main amount precisions or cost precisions are set.

Add tags to a posting, discarding any for which the posting already has a value. Note this does not add tags to the posting's comment.

Add the given hidden tag to a posting; and with a true argument, also add the equivalent visible tag to the posting's tags and comment fields. If the posting already has these tags (with any value), do nothing.

Get a posting's (primary) date - it's own primary date if specified, otherwise the parent transaction's primary date, or the null date if there is no parent transaction.

Get a posting's secondary (secondary) date, which is the first of: posting's secondary date, transaction's secondary date, posting's primary date, transaction's primary date, or the null date if there is no parent transaction.

Get a posting's primary or secondary date, as specified.

Sorted unique account names referenced by these postings.

Join two parts of a comment, eg a tag and another tag, or a tag and a non-tag, on a single line. Interpolates a comma and space unless one of the parts is empty.

Add a tag to a comment, comma-separated from any prior content. A space is inserted following the colon, before the value.

Like commentAddTag, but omits the space after the colon.

Add a tag on its own line to a comment, preserving any prior content. A space is inserted following the colon, before the value.

Special tags hledger sometimes adds to mark various things. These should be hidden tag names, beginning with _. With --verbose-tags, the equivalent visible tags will also be added. These tag names are mentioned in docs and can be matched by user queries, so consider the impact before changing them.

Special tags hledger sometimes adds to mark various things. These should be hidden tag names, beginning with _. With --verbose-tags, the equivalent visible tags will also be added. These tag names are mentioned in docs and can be matched by user queries, so consider the impact before changing them.

Special tags hledger sometimes adds to mark various things. These should be hidden tag names, beginning with _. With --verbose-tags, the equivalent visible tags will also be added. These tag names are mentioned in docs and can be matched by user queries, so consider the impact before changing them.

Special tags hledger sometimes adds to mark various things. These should be hidden tag names, beginning with _. With --verbose-tags, the equivalent visible tags will also be added. These tag names are mentioned in docs and can be matched by user queries, so consider the impact before changing them.

Special tags hledger sometimes adds to mark various things. These should be hidden tag names, beginning with _. With --verbose-tags, the equivalent visible tags will also be added. These tag names are mentioned in docs and can be matched by user queries, so consider the impact before changing them.

Sum all amounts from a list of postings.

Negate the posting's main amount and balance assertion amount if any.

Negate the posting's main amount but not the balance assertion amount.

Render a posting, at the appropriate width for aligning with its siblings if any. Used by the rewrite command.

Render one posting, on one or more lines, suitable for print output. Also returns the widths calculated for the account and amount fields.

There will be an indented account name, plus one or more of status flag, posting amount, balance assertion, same-line comment, next-line comments.

If the posting's amount is implicit or if elideamount is true, no amount is shown. If the posting's amount is explicit and multi-commodity, multiple similar postings are shown, one for each commodity, to help produce parseable journal syntax. Or if onelineamounts is true, such amounts are shown on one line, comma-separated (and the output will not be valid journal syntax).

If an amount is zero, any commodity symbol attached to it is shown (and the corresponding commodity display style is used).

By default, 4 spaces (2 if there's a status flag) are shown between account name and start of amount area, which is typically 12 chars wide and contains a right-aligned amount (so 10-12 visible spaces between account name and amount is typical). When given a list of postings to be aligned with, the whitespace will be increased if needed to match the posting with the longest account name. This is used to align the amounts of a transaction's postings.

Render a transaction's postings as indented lines, suitable for print output.

Normally these will be in valid journal syntax which hledger can reparse (though they may include no-longer-valid balance assertions). Explicit amounts are shown, implicit amounts are not.

Postings with multicommodity explicit amounts are handled as follows: if onelineamounts is true, these amounts are shown on one line, comma-separated, and the output will not be valid journal syntax. Otherwise, they are shown as several similar postings, one per commodity. When the posting has a balance assertion, it is attached to the last of these postings.

Posting amounts will be aligned with each other, starting about 4 columns beyond the widest account name (see postingAsLines for details). The postings will appear balanced (amounts summing to zero). Amounts' display precisions, which may have been limited by commodity directives, will be increased if necessary to ensure this.

Prepend a suitable indent for a posting (or transaction/posting comment) line.

Show an account name, clipped to the given width if any, and appropriately bracketed/parenthesised for the given posting type.

Render a transaction or posting's comment as indented, semicolon-prefixed comment lines. The first line (unless empty) will have leading space, subsequent lines will have a larger indent.

Render a balance assertion, as the =[=][*] symbol and expected amount.

Apply a transform function to this posting's main amount (but not its balance assertion amount).

Apply a specified valuation to this posting's amount, using the provided price oracle, commodity styles, and reference dates. See amountApplyValuation.

Maybe convert this Postings amount to cost.

Generate equity conversion postings corresponding to a Posting's cost(s) (one pair of conversion postings per cost), wherever they don't already exist.

Make a market price equivalent to this posting's amount's unit price, if any.

Get the commodity symbols used in a posting's amounts (not including costs).