Prepaid and accrual schedules
Month-end > Schedules keeps the entries you'd otherwise book from a spreadsheet each month. It's part of the Close plan. Ledger Doctor never posts: it builds unposted journal entries in a GP batch, and a person reviews and posts them in GP.
Add a schedule
An approver adds each schedule with its two accounts as GP shows them:
- Prepaid: an amount spread over a number of months. Each month end debits the expense and credits the prepaid account. The months are equal to the cent and the last month takes the rounding, so 1,000.00 over 3 months is 333.33, 333.33 and 333.34.
- Accrual: an amount each month end, debiting the expense and crediting the accrued liability, as a reversing entry that GP reverses the next day.
The prepaid or liability account has to be a balance sheet account, and the expense an income statement account. Before a month is built, an approver can change its amount; for a prepaid, the difference moves to the last month that isn't built, so the schedule still adds up to its total. End the schedule stops the months not built yet.
Build the month's batch
Pick the period end. The page lists the entries due, and an approver chooses Build the batch in GP. They go into one batch named LD-SCHED- and the year and month (like LD-SCHED-202609), one journal entry per schedule, through GP's own eConnect procedures, the way GP integrations create entries. It's all or nothing: if GP refuses one entry, nothing is built, and GP's error codes are shown. Then review and post the batch in GP under Transactions > Financial > Batches.
Each month shows where it stands: Not built, In batch, not posted, Posted, or Not in GP when the entry was deleted in GP; a deleted entry can be built again.
The eConnect procedures come with GP's eConnect runtime. If a company doesn't have them, the page says so, and the Excel's This month's entries sheet has the entries to key in. Once the month is built, the same sheet lists its entries with their batch, journal entry number and where they stand in GP. Ledger Doctor setup grants Ledger Doctor the right to run them; after an upgrade from 0.26 or earlier, give it that right once: on the Ledger Doctor server, open a command prompt as an administrator in Ledger Doctor's folder and run LedgerDoctor.Service.exe grant (you need to be a SQL Server sysadmin; add --sql-user and a login to use a SQL login). Running setup again and choosing Update, or a SQL Server admin running EXEC LedgerDoctor.dbo.usp_grant_access;, does the same.
What the accounts should hold
For each prepaid and accrued liability account, the page shows what the schedules say it should hold at the period end next to its GL balance. The same amount fills in the account's reconciliation as its supporting balance; when it ties with no reconciling items, Ledger Doctor prepares it, and a person reviews it. The close binder includes the schedules workbook.