Short Answer
Carbon (Emissions) Allowance Invoice are intentionally implemented so that:
-
The user sees and handles it similar to an “invoice” (invoices list, approvals, contract workflow).
-
But the posted transaction in the accounting layer is a journal, not an AR/AP invoice.
This was done because an Emissions Allowance Invoice is meant to create or adjust a balance‑sheet liability for allowances, not to create an open receivable/payable like a normal cash invoice.
Why a journal and not a “real” invoice?
1. Nature of the transaction: liability, not cash
A Carbon/Emissions Allowance Invoice is used to:
-
Recognize that the company owes emissions allowances (or has consumed them) for a period.
-
Record a liability on the balance sheet and related expense on the P&L.
At that point:
-
There is no external cash payment due, and
-
The settlement of that obligation is done via Allowance Transfers.
Because of this, the accounting event is:
-
Balance‑sheet + P&L entry only (expense + allowance liability),
-
No AR/AP open item that needs payment/receipt tracking.
That is exactly what journals are for in IMOS/VIP.
2. Link to Allowance Transfers and closing the balance
Per IMOS - Emissions Expense Settlement Workflow
The flow is:
-
Post Emissions Allowance Invoice
-
Creates a journal to record the new liability.
-
-
Later, perform Allowance Transfers
-
Transfer journals then close or move that liability using Carbon Allowance inventory.
-
If the Allowance Invoice had been implemented as a standard AR/AP invoice, you would end up with open payables/receivables that don’t map cleanly to how EUA obligations are settled.
Using journals keeps it strictly as liability and expense accounting tied to allowance inventory and transfers.