What a journal type is
A journal type is the category a transaction is filed under when it enters the ledger. Sales, purchases, cash receipts, cash payments, and general journals are the usual set. The type determines how the entry is numbered, what document (if any) is produced from it, how it is presented in listings and audit trails, and whether it behaves in any special way after posting.
In most accounting software this list is defined by the vendor and shipped with the product. A business gets a fixed set of journal types, sometimes with the ability to rename them or add a description. That works when the business's processes match the ones the software was designed around, which for early-stage businesses they usually do. Invoices go out, bills come in, cash moves, and occasionally an adjustment is posted.
What tends to change as a business grows is not the volume of those transactions but the number of transaction categories that do not fit any of them. Intercompany recharges, deferred revenue releases, project accruals, milestone billing, foreign currency revaluations, stock movements, payroll allocations across departments — each is a recurring process with its own numbering, its own approval expectation, and often its own reversal behaviour.
Where the workaround usually goes
When the system has no journal type for a process, the process does not disappear. It moves into a general journal with a description typed into a free-text field, or into a spreadsheet that is maintained alongside the ledger and posted from once a month.
This is a rational response, and a lot of well-run finance functions operate this way for years. The costs are specific rather than dramatic. Entries of different kinds share one numbering sequence, so isolating a single process in the ledger means filtering on a text field that depends on whoever typed it. Reversals are diarised by a person rather than performed by the system, which makes them dependent on that person's calendar. The document a counterparty expects — a recharge note, a credit advice — is produced outside the system and has no fixed link back to the entry it came from. And the knowledge of how each routine works sits with whoever built the spreadsheet.
What AOC lets a business define
In AOC Accounting, journal types are user-defined. A business creates the types it needs and configures each one's behaviour rather than fitting its processes into a fixed list.
What a user-defined journal type controls
- Transaction sequence: each journal type carries its own numbering, so entries of one kind are a continuous, gap-checkable series rather than scattered through a shared sequence.
- Document printing: a type can produce its own document from the entry itself, so the paperwork sent out and the record posted are the same event rather than two separate ones.
- Auto-reversal: a type can be set to reverse itself in the following period, so accruals and provisions unwind on a rule instead of on a reminder.
- Its own place in the ledger: because AOC uses a single combined ledger, a new journal type posts straight into the general ledger like any other transaction — there is no subledger to configure alongside it.
- Dimensional coding: entries under any journal type carry the same analysis dimensions (up to 10 per function), so a custom process is reportable by project, department, or entity from the day it is set up.
The practical effect is that a recurring process becomes a configuration rather than a routine. Setting up a journal type takes longer the first time than typing a general journal does. It is done once, and every subsequent instance of that process runs the same way regardless of who enters it.
A process that lives in a spreadsheet has to be remembered. A process defined as a journal type is executed by the system.
Auto-reversal, specifically
Auto-reversal is worth isolating because it is the setting that most often replaces a manual step outright. An accrual posted in one period is meant to reverse in the next. Where the system does not do this, someone posts the reversal by hand, which means someone has to remember, and a period-end checklist grows by one line for every accrual the business carries.
Configured on the journal type, the reversal is a property of the entry rather than a task. It happens at the right date, it happens whether or not the person who posted the original is available, and the pair of entries is visibly linked in the ledger. For a business carrying a handful of accruals this saves minutes. For one carrying dozens across projects and entities, it removes a class of error — the accrual that was posted and never reversed, found weeks later in a margin review.
Features and benefits
The features below all describe AOC Accounting and what each one gives a business using it.
| Feature | What it means for you |
|---|---|
| User-defined journal types | Recurring processes that do not fit a standard journal get their own type in the system, instead of a description typed into a general journal. |
| Per-type transaction sequences | Each kind of entry has its own continuous numbering, so a process can be traced and completeness-checked without filtering on free text. |
| Configurable document printing | The document a counterparty receives is generated from the posted entry, so paperwork and ledger record stay tied together. |
| Auto-reversal on the journal type | Accruals and provisions unwind on a rule at the right date, removing a manual reversal step and the risk of it being missed. |
| Combined AP, AR, and GL in one ledger | A new journal type posts directly into the general ledger — there is no separate subledger to set up or reconcile against. |
| Reports available immediately | Entries made under a new journal type appear in reporting as soon as they are posted, with no export or rebuild step. |
| Up to 10 analysis dimensions per function | Custom processes are reportable by project, department, entity, or cost centre without a parallel record being maintained. |
What it does not change
Configurable journal types do not decide what the right accounting treatment is. A poorly specified accrual configured to reverse automatically will reverse an incorrect figure precisely on time. The setting removes the mechanical steps around a process; it does not remove the judgement about what the process should be.
It is also worth defining fewer types rather than more. A journal type per genuine process is useful. A journal type per variation of a process produces a list nobody can navigate, which is its own kind of overhead. The value comes from the routines that repeat often enough that someone has already built a spreadsheet for them.
Where this fits
AOC is aimed at the space between simple starter software and full enterprise infrastructure. Businesses in that space generally do not need bespoke development, but they have outgrown a fixed list of five journal types — they are running processes their software has no category for, and holding those processes together with side files. Configurable journal types are the feature that brings those routines back inside the ledger.
See your own routines set up as journal types
Bring one process you currently run in a spreadsheet and see it configured with its own sequence, document, and reversal rule.