Recurring journals in Business Central

Recurring journals in Business Central automate the periodic postings that finance teams would otherwise re-key every month: rent, lease payments, scheduled accruals, depreciation outside the FA module, payroll provisions, intercompany cost transfers, and any other regular non-document journal.

The recurring journal. It looks like a regular general journal but with extra columns that control repetition. Each line carries:

• Recurring Method — how the amount is calculated:

  • Fixed — same amount each period.
  • Variable — amount manually entered each period; otherwise zero.
  • Balance — reverses to zero the GL account's balance each period (used for clearing accounts).
  • Reversing Fixed / Variable / Balance — same as above plus an automatic reversing entry the following day (for accruals that reverse next period).

• Recurring Frequency — a date formula expressing how often the line should re-post: 1M (monthly), 1Q (quarterly), 1Y (annually), 7D (weekly), or compound formulas.

• Posting Date Formula — the formula that computes the next posting date when the journal is run.

• Expiration Date — when the line stops re-posting (blank for indefinite).

How it works. When the user posts a recurring journal, Business Central:

1. Posts the lines using the dates and amounts.
2. Advances the Posting Date of each line by the Recurring Frequency.
3. Resets the Amount to zero on Variable lines (forcing manual entry next period) or keeps the Fixed amount.
4. Skips lines whose expiration date has passed.

The same journal is then ready for next period's run — no manual rebuild.

Allocations. Recurring journal lines support allocations — splitting a single posting across multiple destinations by percentage. Common use: an IT cost recorded centrally, allocated 40% to Sales, 30% to Operations, 20% to Finance, 10% to Other. The allocation rule is configured once, executed on every run.

Dimension defaults. Each recurring line carries default dimensions, so postings tag the right cost centre, project, or other dimension without manual entry every period.

Reversing entries. The reversing recurring methods are the classic accrual pattern: post an accrual on month-end, automatically reverse on the first of the next month, accrue again with new amounts. Standard finance hygiene without manual reversal effort.

Multiple batches. Recurring journals live in batches like regular journals, so you can organise by frequency, owner, or purpose: a "Month-End" batch with all monthly accruals, a "Quarterly" batch, a "Weekly Payroll Provision" batch.

Approval workflow. Like other journals, recurring journals can be routed through approval workflow before posting.

Operating discipline.

• Document the purpose of each recurring line in the Description and the External Document No. fields — controllers six months in should understand why each line exists.
• Review quarterly — recurring entries become invisible noise if nobody reviews them. Expired contracts, changed allocations, stale amounts all degrade the GL.
• Use expiration dates for time-bounded postings (a 24-month lease, for example).
• Standardise the batches — month-end accruals in one batch, fixed monthly costs in another, allocations in a third.

Limits. Very complex calculation logic (e.g. allocations based on a formula across actuals) belongs in custom code or a Power Automate flow that builds the journal from a calculation — recurring journals handle fixed-rule patterns well, not data-driven complex logic.