Can AI Draft Journal Entries? Accruals and Prepayments, Then Review

Yes. AI can draft journal entries for accruals and prepayments from a verified invoice, contract and period schedule. Review the document, the service dates, the calculation, account codes, debit and credit direction, reversal or release schedule and duplicate risk before posting. The accountant must approve the journal and retain evidence linking the source to the entry.

An accrual recognises an expense incurred before its invoice or payment is recorded; a prepayment holds a paid cost as an asset until the benefit is consumed. AI can confuse the two because both spread amounts across periods. Give it the economic event and dates first. Never ask it to infer those from a vague bank description.

Follow me on Instagram@sagnikteaches

Start with the document, not the debit line

Gather the supplier invoice or signed agreement, period covered, amount, currency, payment status and existing ledger postings. Add the accounting period end and the organisation's materiality and account-mapping policy. The draft journal should carry a source reference that a reviewer can reopen. A model response without the underlying document is a hypothesis, not a posting instruction. The bank statement extraction tutorial is relevant when the first evidence arrives as a PDF that may have been read incorrectly.

Connect on LinkedInSagnik Bhattacharya

Use a one-page source record: supplier reference; what was received; start and end dates; whether an invoice exists; whether it has already entered the purchase ledger; cash payment date; account code; reviewer; and open questions. If any field is unknown, keep it blank. For a $1,200 service fee covering three months, the start date matters more than the wording “quarterly support”. A payment on the last day of a month does not prove that the service starts the same day.

Subscribe on YouTube@sagnikteaches

Illustrative error: the contract says support begins 1 October, the invoice is dated 15 September and bank payment occurs 20 September. AI reads the payment date and expenses all $1,200 in September. The reviewer compares the contract dates and recognises that September has not yet consumed the service. The payment and service period answer different questions; the journal must represent the latter under the entity's accounting policy.

Where the document is confidential, use the practice-approved tool and data route. An initial experiment can use invented invoices with the same field structure. If a client file must be processed, check your engagement terms and access controls before uploading it. The accountant client-data tutorial deals with that separate tool decision. In the close pack, keep the original document and the approved entry in controlled storage rather than treating a chat transcript as the sole record.

Accrue an earned cost before its invoice arrives

Take an illustrative architecture practice that receives a subcontracted survey service in March, receives no invoice by the March close and expects a $900 charge based on an approved purchase order and completed service note. At 31 March the proposed accrual is debit survey expense $900 and credit accrued expenses $900. That recognises the cost in the period when the service was received and a liability for the amount still to be invoiced. The evidence is the approved order and completion note; the $900 is an estimate that should be labelled as such.

AI can draft the entry and the explanation, but the reviewer checks whether the service was actually completed by 31 March, whether the order amount includes items not yet delivered, whether another invoice or accrual already covers it, and whether the proposed codes match the chart of accounts. If the note shows only two of three survey stages complete, an automatic $900 accrual may overstate the expense. The accountant should obtain a supported estimate for the completed portion or defer the entry until the information is adequate.

Suppose the later invoice arrives for $960 in April. If the practice reverses the $900 accrual at the start of April, the invoice posts $960 to expense in April and the reversal credits $900, leaving an April difference of $60. Across both months, expense totals $960: March $900 and April $60. The reviewer must verify that the reversal occurred and the invoice was posted once. If the practice instead clears the liability directly, the entry pattern differs; mixing the two methods creates a duplicate or residual balance.

For an illustrative mistake, the model sees the $960 invoice and proposes a new $960 expense while the $900 accrual remains. March plus April would show $1,860 until corrected. A schedule that lists the March journal ID, April reversal ID and invoice ID exposes the duplicate. This is why the prompt should ask for an “existing-posting check” before producing a posting-ready draft. See the client-book error checks tutorial for wider anomaly searches.

Release a prepaid cost over the benefit period

Now use an illustrative $2,400 annual software subscription paid on 1 January for access through 31 December. If the entity's policy treats it as a prepayment, the initial entry is debit prepaid software $2,400 and credit bank or trade payable $2,400, according to how the payment and invoice are recorded. Each month, release $200: debit software expense $200 and credit prepaid software $200. After three months the remaining prepayment is $1,800. The dates, policy and existing purchase-ledger treatment must be checked before using these lines.

Intuit's prepaid-expense explanation describes the asset and its later release to expense. It also mentions recurring journals as an automation option. That does not justify creating one without checking whether the subscription is cancellable, has variable components or has already been booked by the system. The accountant determines the policy and reviews the first and last release dates.

The schedule should show period, opening asset, release, closing asset and journal reference. January: $2,400 opening, $200 release, $2,200 closing. February: $2,200 opening, $200 release, $2,000 closing. March: $2,000 opening, $200 release, $1,800 closing. At December close the asset should be zero if the original assumptions hold. If the contract starts mid-month, a straight $200 each calendar month may be inappropriate; document the chosen allocation basis and recompute it.

A second prepayment example is an insurance policy paid upfront for $1,800 covering six months. AI proposes $300 per month, which is arithmetically correct if all six months carry equal benefit and the dates align with the periods. If the practice's ledger already expensed the payment, the journal must reclassify the unexpired portion at the close rather than debit bank again. The cash has already moved. A model can produce a balanced but economically duplicated payment entry when it ignores the ledger state.

Follow a close pack through both kinds of adjustment

Consider an illustrative six-person accountancy practice closing 31 March for a client. Its close pack contains the $2,400 annual software subscription above, paid on 1 January, and the $900 survey service completed in March with no invoice. Assume the January and February prepayment releases have been posted, leaving $2,000 at 1 March. The March software release is $200, leaving $1,800 at 31 March. The survey accrual adds $900 March expense and $900 accrued liability. These figures are illustrative, not a general materiality threshold.

The junior accountant gives an approved AI workspace a structured extract: invoice reference, subscription dates, original $2,400 entry, January and February journal IDs, survey order, completion note and a list of open purchase invoices. The requested output is a draft journal sheet and questions. It returns two candidates: debit software expense $200, credit prepaid software $200; and debit survey expense $900, credit accrued expenses $900. Both entries balance, but balance alone says nothing about completeness or duplication.

The reviewer checks five things. First, the annual contract really ends in December and there was no mid-term change. Second, January and February releases total $400, so opening March asset is $2,000. Third, no March release has already been posted. Fourth, the survey completion note supports the $900 estimate and no supplier invoice is in the ledger. Fifth, the account codes and period are correct. The reviewer signs the working paper, posts the two entries, records journal IDs and checks the resulting balances.

In April, the survey invoice comes in for $960. The accountant checks whether the March accrual was set to reverse. If it was, verify the reversal and the $60 April difference. If not, clear the accrued liability against the invoice and recognise the $60 additional expense according to the practice's process. The reviewer marks the March estimate as settled and attaches the invoice to the schedule. An AI reminder can flag an accrual still open after the expected invoice date; it should not auto-clear it without a matched source.

Ask for a draft with an evidence column

Prompt AI to return one row per proposed entry, not a narrative that hides arithmetic. Require it to state any assumption explicitly and to stop when dates, amount or prior postings are missing. Feed it the approved account map rather than asking it to invent account names. A useful structure is journal date, debit account, debit amount, credit account, credit amount, explanation, source reference, schedule reference, existing-posting check and question for reviewer.

Using only the attached approved source record and ledger extract, draft candidate accrual or prepayment entries for the 31 March close. For each line give debit, credit, amount, period, calculation and exact source reference. Show a release or reversal schedule where needed. List missing dates, uncertain account codes and possible duplicate postings separately. Do not post, fill gaps from general knowledge or call any entry approved.

Illustrative model output: “Debit survey expense $900; credit accrued expenses $900; based on completion note S04 and order O19; question: confirm all work was delivered by 31 March.” The last question is useful. If the output instead says “confirmed completed” although the completion note is ambiguous, the accountant should return to the document. Mark the disputed field unresolved rather than asking the model to write a stronger justification.

A third small example uses a $600 utility estimate covering the final month of a quarter. The model may try to spread it across three months because the bill arrives quarterly. The reviewer checks meter readings and the prior accrual schedule. If $400 has already been recognised in the first two months, the quarter-end entry may be $200, not $600. The prompt needs cumulative postings, not just the new bill total.

Review arithmetic, period and posting status separately

Use a three-pass review. In the evidence pass, open the original document, confirm the entity, dates and amount, and compare with purchase ledger and bank record. In the accounting pass, check the classification, debit and credit direction, allocation method, estimates and account codes. In the posting pass, confirm that the entry has not already appeared and that the reversal or release will be monitored. Each pass answers a different failure mode; one tick labelled “checked” is too vague to be useful in a later audit.

A filled illustrative checklist might say: “Source C18 annual service agreement, $2,400, 1 January to 31 December; original payment posted J101; January and February releases J118 and J133, $200 each; proposed March release J draft 04, $200; remaining asset $1,800; reviewer initials and date pending.” That is much more reviewable than “AI checked the prepayment”. It also shows which numbers must change if a contract amendment appears.

Watch for negative and credit documents. An illustrative $120 supplier credit relating to the annual subscription changes the remaining cost. AI may treat it as a fresh expense because the document has an invoice-like layout. The accountant traces whether the credit reduces cash, payable or prepayment, and updates future releases from the effective date. Do not change prior approved periods without considering the practice's correction policy and materiality.

Reconcile the schedule after posting

At month-end, compare the prepayment schedule's closing total with the general ledger prepayment balance. Compare the accrual schedule's open items with the accrued-expenses balance. Differences need item-level explanations: a new contract, an invoice clearing an accrual, a manual adjustment or a missed release. Ask AI to identify unmatched references, but resolve them against original documents and journal IDs. The posting approval boundaries tutorial addresses why a matched line should still wait for human approval.

Measure the trial by review quality, not number of drafts generated. Count candidate entries, rejected entries, arithmetic corrections, duplicate catches, unresolved source questions and schedules reconciled after posting. If two of ten drafts omit prior journal IDs, improve the input format before processing more clients. If the model repeatedly confuses invoice date with service period, remove date interpretation from its job and supply the period as a verified field.

Finally, retain the source document, working calculation, AI draft, review changes, final posting reference and later reversal or release evidence together. If a reviewer cannot explain why $200 was released in March six months later, the workflow has failed even if the entry was correct. A good AI draft makes the arithmetic and assumptions visible; the accountant's approval turns it into a controlled journal.

Decide whether an estimate is ready for a journal

Some month-end costs are known in principle but uncertain in amount. An AI assistant can list the missing evidence: the work completed before the period end, the contractual rate, the purchase order cap, any supplier estimate and a prior-period comparison. It should not transform an unsupported guess into a confident accrual. The reviewer decides whether the available evidence permits a reasonable estimate under the entity's accounting policies and asks the supplier or service owner for clarification where it does not.

For an illustrative maintenance contract, the order says “up to $1,500” and the site manager confirms only one call-out was completed before the close. AI drafts an accrual for the full $1,500 because it sees the headline figure. That cap is not the cost of work performed. The accountant asks for the call-out rate and service note, then calculates an amount supported by that information. If the supplier later invoices a different sum, the difference is investigated and documented. The lesson is specific: a purchase order ceiling and an earned expense are not interchangeable.

Mark estimate confidence in plain terms, with a reason. “High: signed monthly fee and service confirmed” is more useful than a numerical confidence score generated by the model. “Low: no evidence of completion” should stop automatic drafting. An estimate can be updated when better information arrives, but the change needs an entry reference and explanation. Do not overwrite the original schedule so the first reviewer can no longer reconstruct what was known at the close.

Handle awkward contract dates without hiding the method

A contract can begin on the 15th, end after a leap day, include a free opening period or change price midway. If a $1,200 three-month subscription starts on 15 February, dividing it into three full calendar-month releases of $400 may misstate the first and last months. Intuit's prepaid-expense guide makes the same point: under the straight-line method, a service that does not start on the first day of a period is recognised on a pro-rated basis. The accountant chooses a reasonable allocation basis from the contract and accounting policy, documents it and checks the resulting schedule totals $1,200. AI can calculate a proposed day-based schedule, but the reviewer must verify inclusive dates, rounding and whether each month receives the intended portion.

For a quick numerical check, suppose the agreed method allocates $150 to the first partial month, $400 to each of the next two full months and $250 to the final partial month. The releases total $1,200. If AI outputs $150, $400, $400 and $300, the schedule is $50 too high despite each row looking plausible. Add a control at the bottom: opening balance plus additions minus releases equals closing balance, and all releases over the contract equal the original amount adjusted for genuine credits or amendments.

Foreign-currency invoices add another layer: the contract amount, payment amount and ledger carrying value can differ because of exchange treatment. Do not let AI replace the practice's accounting policy with a generic exchange rate from the internet. Give the reviewer the transaction date, recorded rate and actual ledger entries, then seek specialist advice if the treatment is material or unfamiliar. The tool's useful job is to expose the reconciliation gap and source references, not to declare a final accounting policy.

Questions about AI-drafted adjusting entries

Can AI choose the account codes automatically?

It can propose codes from an approved chart of accounts, but an accountant should confirm the economic substance, account mapping and reporting treatment. Do not accept a plausible code if the source document or policy points to a different account.

Should an accrual reverse next month?

That depends on the accounting process and how the later invoice will be recorded. A reversal can prevent double counting when the invoice is posted, but it must be scheduled, reconciled and checked. Record the chosen treatment in the working paper rather than allowing AI to assume every accrual reverses.

Can the model post journals after drafting them?

Keep draft creation separate from posting authority. A reviewer should verify the document, period, arithmetic, account codes, duplicate risk and balanced debits and credits, then approve the entry inside the accounting system with a traceable record.

Further reads

• How Accountants Use AI to Explain Tax to Clients in Plain English — Explain approved numbers to a client clearly.
• How to Clean Messy Data in Excel: Step-by-Step Guide — Prepare source tables for dependable comparison.
• AI Engagement Letters for Accountants: Faster Drafts, Clear Scope — Set scope for recurring accounting work.
• 7 AI Mistakes That Put an Accounting Firm's Client Trust at Risk — Review broader practice risks.
• Can AI Check a VAT Return Before You File? Coding Error Checks — Export your quarter's transactions, run VAT-specific checks for rate, zero-rated and reverse-charge coding errors, and sign off the return yourself.
• Can AI Select an Audit Sample? Document and Defend It — A small-practice method for AI-assisted audit sampling: a reproducible selection in Excel or Python and the documentation wording a reviewer can test.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Intuit QuickBooks help article, What are prepaid expenses and amortization? (updated August 2026), read 4 November 2026.