Prepare recurring expenses without copying last month

Create a recurring-expense register

For each material recurring cost, record public operational facts:

The range helps find changes; it is not an accounting threshold. A difference should trigger a document check, not automatic rejection.

Three recurring patterns that need different evidence

“Recurring” describes a pattern, not one workflow:

This distinction matters because a bank pattern cannot manufacture the current invoice, and a contract cannot prove that every debit is correct.

Monthly workflow

1. Collect the current invoice or contractual billing record.
2. Confirm service period, supplier entity, amount, currency, and tax detail.
3. Match the actual payment or keep it open if not yet paid.
4. Compare with the previous period and expected contract.
5. Investigate plan changes, added users, refunds, credits, or price increases.
6. Send treatment questions to professional review.
7. Update the recurring register only after the source explains the change.

This avoids copying stale invoice data into a new month.

Worked example: annual software renewal

A synthetic consultancy expects a monthly €99.00 software debit. In March, the card is charged €1,188.00. The amount is not a simple duplicate; it may be an annual renewal.

The reviewer needs the new invoice and service period. If it covers April through March, the cash leaves in March while the accounting effect may require a different period treatment. That decision belongs to the accountant. The operational control should label the event “annual renewal confirmed” and stop expecting a monthly invoice until the contract says otherwise.

Payment frequency and expense recognition are not the same decision. Do not allocate a real annual payment solely from the contract label or previous month.

Common changes to detect

• supplier legal entity or country changes;
• monthly plan becomes annual;
• added users or usage fees;
• invoice currency changes;
• price increase or discount expires;
• credit note or refund offsets a debit;
• subscription ends but payment continues;
• one invoice covers several locations or teams;
• card payment is replaced by direct debit.

Each change can affect evidence, matching, period, and professional treatment.

Roles and handoff

The owner confirms whether the service is active, who uses it, and which location or project it supports. Software can group the supplier history, connect invoice and payment, and highlight variance. The accountant reviews coding, timing, and tax.

DeinHans can use an established supplier, contract context and prior occurrences to prepare a likely recurring case, connect the current source and payment, and ask about meaningful changes. Current support is preparation, not a subscription-management product: DeinHans does not cancel services, guarantee contract matching, approve accruals, or assume that a repeated debit is valid. A familiar supplier should reduce search work, not reduce evidence requirements.

Source-to-result example

For one June studio month, a €2,400 rent debit is connected to the signed lease and an unchanged payment pattern; a €142.80 software debit is connected to a new invoice showing two added users; and an €89.00 advertising debit has no June invoice. The first becomes a contract-backed case, the second a changed recurring invoice, and the third a missing-evidence question. They should not all receive the same “recurring expense” status merely because they repeat.

Close checklist for recurring costs

Before closing the month, ask:

• Did every expected recurring source arrive?
• Does each debit have the current invoice?
• Are cancelled services still charging?
• Do annual or quarterly bills have a clear service period?
• Are credits and refunds connected to the original service?
• Were supplier, currency, or tax changes reviewed?
• Does the next month’s expectation reflect confirmed changes?

A small maintained register makes this faster and more reliable than treating every month as a copy of the last.

Review changes, not only missing items

Compare current price, service period, supplier entity, currency and invoice tax statement with the register. Record confirmed changes with effective date and evidence. A charge that arrived exactly on schedule can still be wrong if the contract was cancelled, the legal supplier changed or the annual service renewed on different terms.

Reconcile the register to both invoices and bank activity. An expected cost may have an invoice before payment, a payment before the final document, or a credit in a later month. Keep those states distinct and assign the missing step.