Closing the Month in the CRM: the Locked Period and What Your Accountant Receives
The last week of the month looks about the same in most small firms: a pile of receipts, two bank transactions nobody recognises, one invoice still sitting as a draft, and a few documents waiting for a second pair of eyes. None of it is difficult work. The difficulty is that all of it has to be finished before the numbers stop moving — and then stay finished.
Firmspace CRM handles that with a period close. The screen lives in the finance section and opens on the previous month by default, because that is the period a firm normally closes. It shows three things at once: the closing checklist for the chosen dates, the list of periods already closed, and the queue of documents waiting for review.
The checklist is not decorative. Before a period can be closed, the CRM counts what is still open inside those dates: bank transactions that have not been matched to anything, invoices still in draft, and documents a reviewer has returned with the mark needs fixing. Those three are blockers. Three more are warnings: documents still waiting for review, requests sent to the client that are still open, and expenses saved without a receipt attached.
The difference between a blocker and a warning is who carries the risk. A draft invoice or an unmatched bank line changes the numbers, so the period refuses to close while they are there. A missing receipt changes the story you can prove, not the arithmetic. You can still close with warnings on the screen — but you have to confirm that you have seen them, in one explicit step, and the note you leave is stored with the closing record.
Closing a period writes a record: from which date to which date, who closed it, when it happened, and the note that person left. From that moment the period is no longer a filter. It is a wall.
What makes the wall hold is where it stands. The check is not only in the finance screens: it sits in every write route that touches invoices, expenses and bank transactions, and one level lower it sits in the database layer itself. A screen added next year, a background job, or the AI assistant calling its own tools all run into the same refusal. The answer is a specific one rather than a generic error: the period is closed, and these are its dates.
That last point deserves saying plainly, because AI in accounting is often sold as if the assistant could do anything a person can. In this CRM the assistant works inside the same rules as everybody else. Ask it to change the amount on an invoice from a closed month and it fails — not because the tool is missing, but because the lock sits below the assistant, in the data layer.
A closed period is not frozen in every direction. Fields that do not change the bookkeeping stay editable: the review mark that says a document was checked or has to be fixed, the fiscal receipt data, the payment link sent to a customer, the record of when an invoice was sent, the reminder counter and the dunning level, and free notes. Asking the assistant to remind a customer about an unpaid invoice still works after the month is closed. Changing the amount, the line items, the customer, the status or the date does not.
Money that arrives late is a separate case, and it is handled deliberately. When a payment comes in for an invoice whose own date lies in a closed period, the CRM posts the payment by its payment date — which falls in the open period — and opens one narrow, intended exception to update that invoice. A closed month never becomes a reason to lose a real payment.
Mistakes inside a closed period are corrected the way accountants correct them: with a reversal, or with a correction document dated in the open period. Rewriting history is not on the list, and that is the point. The closed period stays a statement the firm can defend months later.
Reopening is possible, but it is a decision rather than a convenience. It requires a written reason of at least a few characters, that reason is stored in the record, and the right to reopen belongs to the owner, an administrator or a specialist with review access. The original closing record is not deleted; the period simply carries both facts — it was closed, and it was opened again with this explanation.
Once the period is closed, the accountant does not need a login. The CRM builds a handoff archive for a date range: CSV registers of the invoices, expenses and bank transactions of that period, the printed forms of the invoices from those dates up to two hundred of them so the archive does not grow without limit, and the register the market expects. In Germany the archive includes a DATEV booking batch for the year. In Ukraine an income book and a VAT register. In Uzbekistan the issued and received electronic invoice registers. A short readme explains what the package contains.
Two honest limits are written into that readme. The archive is a set of company data registers: it is not a tax return and not a signed document. And the DATEV file follows a fixed format that the accountant confirms before loading, with the revenue and bank accounts passed explicitly — 8400 and 1200 remain the usual defaults. Firmspace prepares the export. It does not pretend to be your accountant.
That is the whole shape of the process: finish the open items, close the month with a record of who did it and why, keep corrections in the open period, and hand over one archive instead of a folder of loose files. The assistant is useful on both sides of the wall — before the close, for finding what is still open, and after it, for reminders and questions. It simply cannot walk through the wall.