Check depreciation postings against expected amounts, review fiscal-year posting types, and confirm the resulting book values before accepting a period run.
Key takeaways
- Compare each proposed posting with the expected amount for its date.
- Review posting types across the current fiscal year.
- Check posted entries, expense totals, and remaining book values together.
- Record unexplained differences before confirming the run.
You open the period, check the assets, post the entries, and move on to the next client. The risk is that one wrong amount can sit in fixed asset records for months before anyone compares it with the figures again. A short, deliberate check before you confirm the run is worth the time. This post covers 3 mistakes that operations leads can look for in a period run, with a simple way to check each one.
The examples come from three product guides: Microsoft's documentation for Business Central, the ERPNext documentation from Frappe, and Manager's guide to depreciating fixed assets. Each rule in this post applies only in the product where its guide describes it. If your client uses a different system, read that system's own documentation first, and treat these examples as a reason to check, not as rules that carry over.
A period run is the batch of depreciation postings you make for one closing period across a client's assets. The person who reviews the batch may be the one who has to explain the numbers later, to a client, to an auditor, or to a colleague who picks up the file. That is why the review should leave a trail, not only a yes or no at the end.
Mistake 1: posting amounts without comparing them to the expected figure
The first mistake is posting a depreciation amount without first comparing it to the expected amount for the date of the run.
Business Central's guide on depreciation methods for fixed assets uses the term expected (proportional) amount. In one example, you post a depreciation of 1,778 on 2/2/2023, which the guide says is the expected (proportional) amount of the year's depreciation at 32 days. Depreciation methods for fixed assets - Business Central
The expected figure depends on the date of the run, not only on the asset. The same guide shows this with a second example. If you run depreciation on 6/30/2023, Business Central will suggest 8,222, because there are 148 days from 2/2/2023 until 6/30/2023. Compare that with the 32 days in the first example. A run on a later date counts more days, so the figure you check changes with the date. A figure copied from an earlier run, or from a different date, is not a safe stand-in for the run you are checking.
Posting above the expected figure is a separate problem. The guide gives an example of a depreciation of 5,000 posted on 2/2/2023. It says that amount is more than the expected (proportional) amount on 2/2/2023 at 32 days. A posting above the expected figure is the kind of difference a review should catch before the run is confirmed. Find the reason before you accept it.
The method matters too. Under the Declining Balance 1 method in Business Central, the guide says that if you post an amount that doesn't align with that method, for example 5,000, Business Central suggests the remainder of the expected amount. That behavior belongs to this method in this product. Your client's assets may use other methods, so confirm the method for each asset before you rely on any figure a system suggests.
For a related review, see depreciation methods for client assets.
The guide also gives a larger example. It describes a depreciation of 95,000 posted on 2/2/2023, which it says exceeds the allowed depreciation amount for the year. Your review should compare each posting against the allowed amount for the year in your own setup. A posting far outside the expected range should stop the run for that asset, rather than be posted and sorted out later.
A simple routine for this check looks like this:
- For each asset, find the expected figure for the run date in your system.
- Put that figure beside the amount you are about to post.
- If the two differ, write down the difference and its reason before you confirm the run.
- If you cannot give a reason, hold that asset out of the run until someone can.
Keep the written notes with the run. A client who asks why a figure changed should get an answer from the notes, not from memory. Notes also help the next person who runs the period, because they show which differences were already explained and which still need a decision.
Illustrative example: compare before posting
Suppose an asset's expected depreciation is 30 and its proposed posting is 40. These illustrative amounts differ by 10. Record the difference and check its reason before confirming the posting. If you cannot explain it, hold that asset out of the run. This illustrates the comparison only; it does not calculate depreciation under a particular method.
Mistake 2: checking only this run's entries and missing other posting types
The second mistake is reviewing only the entries from the current run and leaving out other posting types that already count toward the posted depreciation for the fiscal year.
Business Central's guide says that the posted depreciation amount can contain entries with various posting types (write-down, custom1, and custom2) posted since the starting date of the current fiscal year.
That sentence has two parts that matter for a period run. First, the posted depreciation can include posting types other than regular depreciation. Second, the guide counts those entries from the starting date of the current fiscal year. That window is longer than one run, so a check that looks only at this month's depreciation lines can miss entries of those types that were posted earlier in the year.
The names in the guide are specific to Business Central. Your system may label these entries differently, or it may not use them at all. Confirm the posting types your client's system uses before you build the review. Ask the client's bookkeeper or the person who set up the records, and write down the answer.
A review that covers this check has three steps:
- Pull the posted entries for each asset from the starting date of the fiscal year up to the run date.
- Group those entries by posting type, so write-down, custom1, and custom2 entries stand out from ordinary depreciation.
- Compare each group total with what you expected for the year, and note any type you did not expect to see.
Grouping matters because a single total can hide the mix. Two assets can show the same posted total and still be made of very different entries. A list by type shows what sits behind a number, so you can explain it to your client and to whoever signs off on the period.
When you have the year-to-date list, compare its total with the depreciation figures you already have for the asset. If a posting type appears in the list but not in your run notes, find out where it came from before you move on. Entries that nobody has explained yet are the ones most worth a second look.
Check that the fiscal-year starting date in your system matches the client's fiscal year. If the start date is wrong, the year-to-date list will cover the wrong months, and the review will look complete when it is not. Keep a short list of the posting types each client uses, with a note on what each one means in that client's system. A new team member can then run the same review without guessing.
Mistake 3: confirming the run without checking the book value it leaves
The third mistake is confirming the posted entries without checking the book value they leave on each asset.
ERPNext's depreciation documentation from Frappe gives a worked example that shows the kind of tie-out this check needs. By the end of August 2026, seven entries have moved $5,320 into expenses and the labeler's book value is $42,680. Depreciation | ERPNext Documentation
The row editor reflects those posted entries and the value after depreciation. Depreciation | ERPNext Documentation The example gives three numbers you can check against each other: the count of entries, the amount moved into expenses, and the book value that remains. If your own review produces a different count, a different expense total, or a different book value, you have a reason to stop and investigate before you confirm the run.
Use the same habit for each asset in a run. Count the entries posted for the asset in the period, record the amount that moved into expenses, and confirm that the value after depreciation is the book value you expect. Write the three figures on the review sheet next to the asset's name. A sign-off sheet that lists them makes the review easy to repeat next month.
Manager's guide on depreciating fixed assets adds a point about tracking. It says, "Once you have done that, Manager will keep track of how much depreciation has been accumulated for the fixed asset." Depreciate fixed assets | Manager The word "that" refers to a step earlier in the guide, so read those steps before you rely on the tracking. Once you have, compare the accumulated depreciation that the system reports with the entries you reviewed for the run. If the two do not agree, treat it the same way you would treat a book value that does not match: find the reason before you confirm.
If the three figures do not match, work from the entries back to the summary, not the other way around. List the entries for the asset, add up the amounts that moved into expenses, and check the value after depreciation against your records. Then decide whether the difference is a posting error to fix or a difference to document. Do not confirm the run until that decision is written down.
A review order for the run
Run the review in this order: check the amounts first, then the posting types, then the book values. Each step depends on the one before it, so the order keeps the work simple.
Start with the amounts because they are the quickest to compare. If a posting does not match its expected figure, the later checks will be built on a number that may change. Next, review the year-to-date posting types, because they show whether the total includes entries you did not look at. Finish with the book values, since they show the result after the entries are in place.
Doing the steps in this order means that each error is found while it is still easy to fix. An amount found in the first step can be corrected before anything else is posted. A book value that does not match, found in the last step, means you go back to the entries and trace the difference. Write a short note for each step so the reason for every change is on record.
The order also helps when a client's records cover many assets. Work through the whole batch on one check before you move to the next. A full pass on amounts across all assets is easier to hand off than a pass that checks every line of each asset in turn, because the person who picks it up can see exactly which step is finished.
Why each check catches a different error
Each of the 3 checks catches a different kind of error, so skipping one leaves a gap the other two cannot cover. The expected-amount check catches a posting that does not fit its date. The posting-type check catches a total that includes entries you did not look at. The book-value check catches an end result that does not match the entries behind it.
Because each check has a different target, it is not enough to say the run looks right. A run can have correct amounts and still include a posting type you did not expect. A run can have a clean posting-type list and still leave a book value that does not tie to the entries. Treat the three checks as three separate questions, and answer each one before you confirm the run.
A simple test shows whether the 3 checks are complete for a given set of records. Ask whether a run could pass all three and still be wrong. If you can name an error the checks would miss, add a line for it to your run checklist before the next period. That habit keeps the checklist tied to the real risks in each client's records.
Ask clients three questions before the first run
Before the first run for a new client, ask which depreciation method each asset uses, which posting types appear in their records, and which fiscal-year starting date their system uses. The answers become the reference points for the 3 checks.
Write the answers in a client note and review that note at the start of each period. If a client changes a method, a posting type, or a fiscal-year setting, update the note before the next run. A short note like this saves time later and keeps the review consistent when someone else takes over the work.
For the initial handoff, use the client intake checklist.
What these examples do not cover
They do not cover every system, depreciation method, or client setup, and each rule applies only where its guide describes it. The Business Central figures apply to the Business Central examples in its guide. The Declining Balance 1 behavior applies to that method in that product. The ERPNext figures describe one labeler asset in one worked example. Manager's sentence describes tracking after the step that the word "that" points to, in its own guide. None of these should be read as a general rule for every set of records.
If a client uses a system that is not covered here, the general steps still apply: compare each amount with its expected figure, group the year-to-date entries, and tie the book value to the entries. The specific numbers in this post do not carry over. Use the documentation for the client's own system to find the figures and rules that apply there.
Checklist: what to confirm before you confirm the run
Before you confirm a period run, check each asset on these four lines. The list is a short version of the 3 checks, with a fourth line for limits. Copy it into your run checklist and fill it in for each asset.
- Expected amount: the posting matches the expected (proportional) figure for the run date, or the difference has a written reason.
- Posting types: year-to-date entries are grouped by type, including write-down, custom1, and custom2 where the client's system uses them.
- Book value: the count of posted entries, the amount moved into expenses, and the value after depreciation agree with each other and with your records.
- Limits: no posting is above the allowed depreciation amount for the year, as the client's system defines it.
Mark the run as ready only when every line has a result you can explain. If a line has no explanation, hold that asset out and resolve it before the run is confirmed.
Today, choose one asset from a client's current run and write its expected amount beside the proposed posting. Record any difference and its reason.
Questions before you confirm the run
Can an earlier run's figure replace the expected amount?
No, use the expected figure for the current run date. An earlier figure may cover a different number of days.
Should an unexplained difference stop the whole batch?
Hold the affected asset out until you can explain the difference. Keep its notes with the run so the next reviewer can follow the decision.
Do these examples apply to every system?
No, product-specific behavior applies only where the relevant guide describes it. Check your client's own system documentation before relying on a suggested amount.