Auto-Ledger posting guide: get your loans detected

5 min readUpdated 31 Oct 2026/knowledgebase/auto-ledger-posting-guide

Auto-Ledger can prepare a private suggestion from eligible public Reddit evidence. A recognized title is the beginning of that path, not a promise that a post will be collected, approved, delivered, funded, or resolved. Nothing is written to your private ledger until you accept a pending suggestion.

The current end-to-end posting path is intentionally narrow: r/BorrowNew posts with the Prearranged Loan flair and a title recognized by the prearranged parser. r/loanhelp_ titles, comments, and flair changes can contribute to the local loan graph, but the r/loanhelp_ → private Auto-Ledger inbox expansion is not shipped yet.

Community rules come first

Follow the subreddit's current rules, required flair, and moderator instructions first. LoanLedger's examples are supplemental machine-readable shapes; they do not replace a community template or give permission to use a title the community does not allow.

If the community's current required format conflicts with a verified example below, follow the community rule. That post may need operator correction until a separately reviewed parser change adds coverage.

Verified r/BorrowNew prearranged shape

For the usual borrower-authored prearranged post, use the Prearranged Loan flair and name the lender after with:

[PRE] with u/LenderName $100 repay $110 8/1/26

The parser reads LenderName as the lender; the post author supplies the borrower. The first amount is principal, the amount after repay is the agreed repayment total, and the final value is the due date.

The parser also recognizes this lender-authored shape, but use it only when the community permits the lender to author that kind of post:

[PRE] lending $100 to u/BorrowerName repay $110 8/1/26

Here the post author supplies the lender and the named handle is the borrower.

For either shape:

PieceParser contract
[PRE]Keep the tag at the front, with brackets.
u/NameUse the exact Reddit username and the u/ prefix. The parser checks syntax, not account ownership or spelling.
First amountPrincipal actually being sent.
repay amountThe total expected back, fee included.
DateInclude the year. 8/1/26, 8/1/2026, and a preceding on or by are recognized in these shapes.

Currencies

An amount beginning with $ is read as USD. The verified prefixes are C$ for CAD, A$ for AUD, £ for GBP, and € for EUR. Use the same prefix on principal and repayment:

[PRE] with u/LenderName £75 repay £85 15/8/26

The numeric date is read day-first only when its first field is greater than 12, as in 15/8/26. Use an explicit year and an unambiguous date whenever possible.

Known partial and unsupported shapes

The prearranged candidate collector reads the title, not body-only terms:

[PRE] details inside

That title produces no prearranged parse. A title with principal but no repay amount also produces no prearranged parse:

[PRE] with u/LenderName $100 due 8/1/26

A date such as 3/4 is ambiguous. The current parser recognizes the other terms but cannot normalize the date; the staging row may retain the raw date for operator correction:

[PRE] with u/LenderName $100 repay $110 3/4

Posts that split a loan into installments can use this shape. LoanLedger can turn this shape into a suggestion, but that is switched off, so these posts do not become suggestions yet.

[PRE] $120 repay $150, $75 8/1, $75 8/15 lender u/ExampleLender

Nothing here promises they will become suggestions later.

Borrowers normally write r/BorrowNew posts. Sometimes the lender writes the PRE post and names the borrower with the full terms. LoanLedger can turn this shape into a suggestion, but that is switched off, so these posts do not become suggestions yet.

(PRE) loaned $100 to u/ExampleBorrower, repay $120 by 8/20/26

It does not change how borrowers post, and nothing here promises these posts will become suggestions later.

r/loanhelp_ graph-readable structure

r/loanhelp_ is borrower-first and its native flair/command workflow remains authoritative. The examples in this section improve retained graph evidence; they do not promise a private Auto-Ledger suggestion today.

A request title with terms is readable when the post timestamp is available to frame a yearless due date:

$150 - Repay $180 on 6/14 - Cash App - MD - reason

When the community's current rules call for its loan command, an explicit lender comment carries more complete terms:

$loan $150 repay $180 on 6/14

Plain funding language can still establish a funding event, but this example does not carry a repayment total:

Sent $150 via Cash App

Clear repayment language is recognized:

Received $180, paid in full

The native repayment command is also recognized:

$paid

Comment evidence still needs the thread, author role, and flair history. A parser match alone does not establish the counterparty, actual payment rail, or complete lifecycle.

What happens after a recognized BorrowNew title

  1. We read the post. It needs the Prearranged Loan flair and a title in a shape we recognize.
  2. A person at LoanLedger checks it and may correct it.
  3. It goes to the account whose saved Reddit username matches the lender in the post.
  4. It waits for you in Tools. It enters your ledger only when you accept it.

There is no pickup-time guarantee, and no suggestion is promised. A suggestion can be late or missing when we have not read the post yet, Reddit could not be read, the title was not recognized, the post did not make clear who lent, it is still waiting to be checked, sending is paused, or the lender's Reddit username in the post does not match the one saved on the account.

Privacy and separate reporting systems

Do not publish private payment account identifiers, contact details, screenshots, or messages to improve parsing. Public titles and comments should contain only what the community already permits.

Auto-Ledger suggestions, moderated Signal submissions, and Warden reports are separate systems. A parseable loan post is not a public accusation or a Warden report, and private evidence belongs only in the purpose-built restricted workflow.