From c79c66a74088c1f1323fc29ab855784ff1c725ab Mon Sep 17 00:00:00 2001 From: Simon Michael Date: Sat, 6 Sep 2025 07:03:05 +0100 Subject: [PATCH] ;doc:posting dates: link to legacy syntax --- hledger/hledger.m4.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/hledger/hledger.m4.md b/hledger/hledger.m4.md index 388361173..4deb928b4 100644 --- a/hledger/hledger.m4.md +++ b/hledger/hledger.m4.md @@ -1269,7 +1269,10 @@ dates](#smart-dates) documented in the hledger manual.) You can give individual postings a different date from their parent transaction, by adding a [posting comment](#posting-comment) containing a [tag](#tags) (see -below) like `date:DATE`. This is probably the best +below) like `; date:DATE`. +(There's also a [Ledger-compatible syntax](#bracketed-posting-dates), `; [DATE]`, which can be convenient.) + +This is probably the best way to control posting dates precisely. Eg in this example the expense should appear in May reports, and the deduction from checking should be reported on 6/1 for easy bank reconciliation: