> ## Documentation Index > Fetch the complete documentation index at: https://alguna.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Period close > Close each accounting month per legal entity: the close checklist, posting and voiding the revenue journal entry, reconciliation, catch-up adjustments, reopening and the audit log Period close is the month-end routine for revenue. Each month of each legal entity runs through a checklist: billing is finished, the schedules generate cleanly, the revenue journal entry is posted, and the posted entry ties out to the schedule. Then the month is sealed. A closed month's recognized, deferred and contract-asset figures never change again. A later correction is booked into the open month as a catch-up adjustment, so what you reported stays what you reported. Use this page when you close the books for a month, or when you set up closing for the first time. How each charge is earned is on [Revenue Recognition](https://alguna.com/docs/revenue/recognition.md). For the object model behind the schedule, see [How Alguna Works](https://alguna.com/docs/concepts/how-alguna-works.md). Period close is dashboard-only: closing, reopening and posting are not in the public API. The [revenue schedule endpoints](https://alguna.com/docs/api-reference/v2/2026-04-01/revenue-schedules/get-organization-revenue-schedule.md) read closed months from their sealed figures. *** ## Where it lives Each month is closed per legal entity. Choose the legal entity at the top of the **Revenue Recognition** pages. | Page | What it shows | | - | - | | **Revenue Recognition → Periods** | One row per month: recognized revenue, deferred revenue at month end, the journal entry's status, the reconciliation result, and whether the period is open or closed | | The month page (open a row) | The month's figures, its close checklist, and the **Catch-up adjustments**, **Journal entry**, **Reconciliation** and **History** tabs | | **Revenue Recognition → Audit log** | Every close, reopen, posting, void, snapshot and adjustment for the legal entity, with who did it | When an earlier month is still open, the **Overview** page says so and links to it with **Continue close**. ### Permissions | Action | Permission | Built-in role | | - | - | - | | View the pages | Revenue Schedule View | — | | Close a month, run the switch-over, **Check again**, post, repost and void journal entries | Manage Accounting Periods | Admin | | Reopen a closed month | Manage Accounting Period Reopening | Admin | To let someone close months but not reopen them, give them a [custom role](https://alguna.com/docs/concepts/organizations-and-environments.md) with the first permission only. *** ## Starting to close in Alguna You may have closed months outside Alguna before. In that case, start from the month after your last manual close and seal everything before it as it stands. 1. Open the month you want to close first through the checklist. 2. On the **Earlier months closed** row of the checklist, click **Start here**. 3. Confirm **Seal N months**. Every earlier month closes at once, without the checks and without catch-up adjustments. Its figures freeze as they are now, and its history says it was sealed in the switch-over. **Start here** is only offered before the legal entity's first close. After that, months close one at a time through the checklist. *** ## The close checklist The month page lists the checks in order. Each check is **passed**, **to do**, **blocked**, or a **warning**. **Close period** is refused while any check is to do or blocked. A warning lets the month close, but only with a note explaining why. | Check | Stops the close when | Warning when | | - | - | - | | **Month has ended** | The month is still running. **Close period** is hidden until it ends | — | | **Earlier months closed** | An earlier month is open. Months close in order | — | | **Billing is current** | Billing has not finished with the month (see below) | Billing entries were billed in the month with no invoice | | **Schedules generate cleanly** | A subscription's schedule needs attention, for example a missing FX rate | — | | **Invoices issued** | — | Invoices dated in the month are still draft, upcoming, pending approval, scheduled or processing | | **Journal entry** | The month's entry is not ready yet, its posting failed, or it was voided | — | | **Exchange rates** | — | The entry converted revenue using Alguna reference rates instead of your own FX rates | | **Reconciliation** | The entry is not ready yet | The entry does not tie out to the schedule (unexplained breaks) | | **Invoices match the schedule** | — | An invoice differs from what the schedule billed | **Billing is current** confirms that billing for the month has finished: usage is up to date and every invoice for the month has been generated. The row says what is outstanding, and **Check again** refreshes it once that is resolved. Closing with warnings opens a dialog that lists them and asks for a note. The note is kept in the month's history and in the audit log, so whoever reviews the close can see why it went ahead. *** ## The journal entry Each month has one **standard** journal entry per legal entity. It moves the month's recognized revenue out of deferred revenue and into revenue. On the month page: 1. Click **Draft entry**. The entry is prefilled from the revenue schedule. 2. Review it. **Download supporting CSV** gives the lines behind every figure. 3. Click **Post**. The entry goes to your connected accounting system. If the system rejects it, the month shows **Posting failed** with the reason, and **Repost** tries again. A draft is never posted on its own: someone reviews and posts it. Posting uses the accounts set in your accounting integration. If your accounting system can't be reached, the page says so, and drafting, reconciliation and export keep working in the meantime. Which revenue the entry carries, and whether invoices post to revenue or to deferred revenue, are legal-entity settings. See [Accounting integrations](https://alguna.com/docs/revenue/recognition.md#accounting-integrations). ### Drill-down Open a journal entry to see every ledger line broken down into the items behind it: customer, subscription, invoice or credit note, product and month, with the amounts and the recognition policy behind each one. Filter by customer, invoice or product. The **Policies** section lists the ASC 606 / IFRS 15 rules behind the entry. ### Correcting a posted entry * **Adjustment entry.** To change a month that already has a posted standard entry, post an `adjustment` entry for the difference. Your ledger sums the entries for the month. * **Void entry.** This reverses a posted entry. Alguna posts a reversal dated today, with your reason. The original stays in the ledger, so both your books and your accounting system show the correction. Voiding cannot be undone. After voiding, post a new entry for the month. *** ## Reconciliation The **Reconciliation** tab checks the month two ways: * **Journal entries against the schedule**: one row per product with **Recognized**, **Posted** and **Variance** (posted minus recognized). Each variance gets a cause: **Unposted draft**, **Posting failed**, **Manual adjustment**, **Not posted** or **Unexplained**. Click a cause that names an entry to open it. * **Invoices against the schedule**: invoices whose invoiced amount differs from the scheduled amount. On **Periods**, an open month's reconciliation reads **Ties out**, **N unexplained**, **N explained** or **Does not tie out**, and a closed month reads **Sealed**. *** ## What closing does * The month's figures are sealed as they stood at the close. Every later report shows them as reported, even after a voided invoice, a late credit note or a corrected price. * Journal entries can't be dated in a closed month until it is reopened. * **Export** on a closed month returns the same CSV every time, matching the journal entry. ### Changes that touch a closed month An upstream change can move revenue a closed month already reported. The change might be a subscription edit, a product's recognition method, the revenue allocation mode, or a milestone. Alguna then asks you to **Restate closed months?** Choosing **Book catch-up** leaves the closed months as reported and books the difference into the first open month. The **Catch-up adjustments** tab of that month lists each adjustment with the month it came from, its reason, and its amounts. *** ## Reopening a month **Reopen** on a closed month asks for confirmation, because it restates a month that has already been reported on. The month becomes open again and reflects current data. Close it again to reseal it. Reopening needs Manage Accounting Period Reopening and is recorded in the month's history and the audit log. *** ## History and the audit log The month's **History** tab lists everything that happened in its close, newest first: closes, reopens, drafts, postings, failed postings and voids, each with its note. **Revenue Recognition → Audit log** covers the whole legal entity. It adds the catch-up adjustments booked, and each row shows its timestamp, event, entity, user and details. *** ## Next steps > [card] [Revenue Recognition](https://alguna.com/docs/revenue/recognition.md) > > How each charge is earned and deferred. > [card] [Accounting integrations](https://alguna.com/docs/revenue/recognition.md#accounting-integrations) > > Which revenue the journal entry carries. > [card] [Insights](https://alguna.com/docs/revenue-insights/insights.md) > > MRR movement, retention and receivables. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.